Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
DataDrone Inc. is seeking an experienced AI platform expert to own the production LLM workflow design.
You will shape prompts, agent usage, and retrieval strategies to ensure accurate, bounded, and measurable outcomes in client deployments. You will lead the creation of guardrails and evals, diagnose difficult LLM issues, and collaborate with Integration Engineers to ship production-ready solutions that stand up to real-world use.
DataDrone runs partner implementation practices that ship one outcome in 45 days. The AI practice gets one production AI workflow live in 45 days on frontier LLMs - past the pilot graveyard, into real use. Typical outcome: roughly 80% of a manual process automated and running.
We sell outcomes, never licenses. No shelfware, no drift. We prove the work with screenshots, not poetry - and that means workflows that hold up in production, not demos that fall over. The work is the conversation. No surprises.
You're the AI platform domain expert. You own the technical design of the production AI workflow: how we prompt, where we use agents and tool-use, how we wire LLM APIs, what guardrails we set, and how we prove it with evals. You're the person who knows what the model does well, where it breaks, and how to design around both.
You translate a locked use case into a design that survives production - accurate, bounded, and measurable. You set the eval bar so QA has something concrete to validate against. When the team hits a hard LLM problem, you're the one who solves it.
You start the day on the active design problems: the prompt that needs tightening, the agent loop that needs bounding, the guardrail that needs to hold. You spend deep blocks designing and testing - prompts, tool-use schemas, retrieval strategy, eval suites - and pairing with the Integration Engineer to get the design into the real stack. You set the accuracy and guardrail bar with QA so "done" is measurable, not a vibe. When the model behaves in a way the client didn't expect, you diagnose it and design the fix. You close the day with design decisions documented and the eval picture honest. No drift, no hand-waving.
You design for production, not for the demo. You assume the model will surprise you and you build guardrails and evals so it can't surprise the client. You set a measurable bar because "it looks good" isn't a standard. You'd rather ship one workflow that holds than ten that impress in a sandbox and break in week two.
LLM APIs and the model console; prompt and eval frameworks; agent/tool-use and retrieval tooling; the practice's AI Copilot; Notion (design docs, prompt and eval libraries); Trello / Jira / Linear for build tracking; CRM (read access for client context).
You do the deep LLM work and you do it where it actually ships - to production, in 45 days, in front of real users. No prototype theatre, no shelfware. You set the standard for how the practice designs AI workflows, and you prove it with screenshots, not poetry. The hard problems land on your desk because you're the one who can solve them.