AI Engineer

About The Role We're looking for an AI-native engineer to build the autonomous agents that power Yolk SalesOS. You'll work directly under the engineering head and the founders, and you'll be the one bringing the agents to life. The architecture gets set above you; the agents get built by you. Do this well and you grow fast. We're now bringing in the engineer who will turn agent designs into shipped, reliable systems — the discovery prompts, the objection-handling logic, the orchestration that decides what the coach says and when. This role sits close to the heart of the product. The person who gets this right will write code that real reps lean on during real deals. A word of honesty This is an early-team role at a fast-moving company, which means it is hands-on and unglamorous in the way that matters. You will write the agent code, not just diagram it. You will build the eval harness yourself. You will chase down why a coaching response was wrong at 9pm because a customer demo is tomorrow. You will work from a product requirement, figure out the right agent design, and live with the calls you make. The senior team sets the architecture, but inside it you own the implementation end to end — and "it works on my machine" is not the bar. If you want a research seat where you read papers and prototype in notebooks, this is the wrong role. If you want to ship autonomous agents into production and watch them earn their keep on live sales calls, read on. What you'll do • circle]:fill-d-green [&>circle]:stroke-d-green [&>path]:stroke-white" aria-hidden="true"> Build and iterate the agents themselves — from design to production: coaching reps, analyzing deals, surfacing insight in real time. • circle]:fill-d-green [&>circle]:stroke-d-green [&>path]:stroke-white" aria-hidden="true"> Build tool-use and integrations that let agents reach CRMs, transcripts, calendars, and internal data (Gong, Fireflies, Stripe, Apollo, Resend). • circle]:fill-d-green [&>circle]:stroke-d-green [&>path]:stroke-white" aria-hidden="true"> Build prompt pipelines for structured outputs, classification, summarization, and coaching feedback — and the eval harnesses that prove they're good. • circle]:fill-d-green [&>circle]:stroke-d-green [&>path]:stroke-white" aria-hidden="true"> Write orchestration code that manages agent state, retries, fallbacks, and human-in-the-loop checkpoints — including the failure paths most people skip. • circle]:fill-d-green [&>circle]:stroke-d-green [&>path]:stroke-white" aria-hidden="true"> Own the database operations, FastAPI endpoints, and background workers that the agent workflows run on. What we're looking for • circle]:fill-d-green [&>circle]:stroke-d-green [&>path]:stroke-white" aria-hidden="true"> A bachelor's in Computer Science or equivalent, plus at least 3 years building software in production — strong fundamentals, proven track record. • circle]:fill-d-green [&>circle]:stroke-d-green [&>path]:stroke-white" aria-hidden="true"> Obsessed with agents and LLMs. You've built something real with OpenAI, Anthropic, or open models — shipped at work or on your own — not just read about them. • circle]:fill-d-green [&>circle]:stroke-d-green [&>path]:stroke-white" aria-hidden="true"> You think in planning loops, tool selection, memory, and reliability, not prompt-in / text-out. • circle]:fill-d-green [&>circle]:stroke-d-green [&>path]:stroke-white" aria-hidden="true"> Strong Python, comfortable in async/await, and you reason about error handling, edge cases, and what happens when a model call fails. • circle]:fill-d-green [&>circle]:stroke-d-green [&>path]:stroke-white" aria-hidden="true"> AI-native in how you work: Cursor, Claude Code, Copilot daily — and you understand every line you ship, not just the ones you typed. • circle]:fill-d-green [&>circle]:stroke-d-green [&>path]:stroke-white" aria-hidden="true"> A fast learner who dives into unfamiliar code, reads the source, and asks sharp questions instead of waiting to be unblocked. • circle]:fill-d-green [&>circle]:stroke-d-green [&>path]:stroke-white" aria-hidden="true"> You take an architecture you didn't design, extend it, and stress-test it — comfortable implementing patterns rather than setting them, for now. Nice to have • circle]:fill-d-secondary-gray [&>circle]:stroke-d-secondary-gray [&>path]:stroke-white" aria-hidden="true"> You've shipped multi-step LLM pipelines or RAG before. • circle]:fill-d-secondary-gray [&>circle]:stroke-d-secondary-gray [&>path]:stroke-white" aria-hidden="true"> You know FastAPI, async Python, PostgreSQL and SQLAlchemy, or message queues. • circle]:fill-d-secondary-gray [&>circle]:stroke-d-secondary-gray [&>path]:stroke-white" aria-hidden="true"> You've worked in sales tech or RevOps. • circle]:fill-d-secondary-gray [&>circle]:stroke-d-secondary-gray [&>path]:stroke-white" aria-hidden="true"> You've contributed to an open-source AI or agent project. What success looks like — first weeks • circle]:f