AI ADOPTION ANALYST (ONSITE ROLE)

RADIANS INC • Memphis, TN

2h • Onsite

About The Position

You are the connective tissue between Radians' business units and the AI Integration team. You build relationships with stakeholders in sales, order entry, operations, finance, and customer service, uncover their repetitive pain points, and translate those into scoped initiatives the team can deliver. You also own the adoption side — making sure tools we ship are actually used and measured once they're live. This is not an engineering role, but it is technical-adjacent. You don't need to write production code, but you need to understand what the engineer is saying, read SQL, and follow a technical conversation without a translator. The department is being built deliberately small and fast. You'll be hired for your curiosity and judgment more than your resume — we'd rather have someone 2 years in with sharp instincts than someone 10 years in with a fixed playbook.

Requirements

• 2+ years in a business-analyst, junior product manager, solutions-consultant, or technical-project-coordinator role.
• Demonstrated ability to facilitate requirements-gathering conversations with non-technical stakeholders and produce structured output (user stories, scoped specs, process maps).
• Technical fluency — you can read code (you don't have to write it), understand what an API does, write SQL queries well enough to validate your own hypotheses, and follow along in design discussions.
• Strong written communication. Half of this job is writing clear summaries that land with executives. Writing samples will be requested during the interview.
• Curiosity-driven — you seek out how things actually work, not how they're documented. You ask "why" three layers deep.
• On-site at Radians Memphis HQ, full-time.

Nice To Haves

• Distribution, manufacturing, or ERP-adjacent industry experience. Prophet21 experience is a bonus; transferable ERP knowledge works too.
• Exposure to AI/ML tooling — even as a user, not a builder. If you've used ChatGPT or Claude to improve your own work and have opinions on what the output can and can't do, say so.
• SQL experience beyond basic SELECT — JOINs, subqueries, window functions.
• Experience supporting tools through an adoption curve (office hours, docs, training) rather than just shipping v1.
• A portfolio of "things I made" — internal tools, automation scripts, dashboards, Airtable bases, whatever. We care about someone who builds, even if the tools are small.

Responsibilities

• Scoping and discovery — for every new initiative, you spend time with the business owners to understand the current workflow, pain points, data sources, and desired outcomes. You turn "we're doing this manually" into a scoped spec the engineering side can build against.
• Adoption stewardship — once tools ship, 20–30% of your week is spent on tools that have already launched: answering usage questions, running office hours, capturing feedback, and bringing it back as the next iteration cycle. Without this, tools launch and decay silently; this role is what prevents that.
• Quick-hit triage — small stakeholder asks that don't merit a full project come to you first. You scope them, often execute the non-technical parts yourself, and hand off to the developer only when code is actually needed. Target turnaround: a working answer or solution inside a week.
• Stakeholder communication rhythm — regular touchpoints with department leads, demos, status updates, escalation paths. Many of these flow through Microsoft Teams with AI-assisted notetaking and scope conversations already built in.
• Feedback loop to roadmap — you're the primary source of data on which initiatives are ready to move from backlog to active. Your read on the business matters as much as any written spec.

What This Job Offers

• Job Type: Full-time
• Career Level: Entry Level
• Education Level: No Education Listed