About the role
Why now
We've tripled in the past month. Demand is high and accelerating. We just raised $6M to pull together an A-team and execute. 20 customers today, and the technical surface area is massive: voice, browser agents, reinforcement learning, self-improvement loops. The engineering team today is Arjun (CTO) and contractor engineers. You and one other founding engineer will set the technical culture for everyone who comes after.
What you'll work on
There's no lane. You'll touch all of it.
Monday. A customer's agent is struggling with a pricing objection it hasn't seen before. You dig into the conversation logs, figure out where the LLM lost the thread, and ship a fix to the orchestration layer. By lunch it's live.
Wednesday. Arjun sketches out a new approach to generative UI on a whiteboard. The widget needs to adapt its layout in real-time based on what the prospect cares about. You prototype it that afternoon and have something demo-able by end of day.
Thursday. The eval pipeline flags a regression. Agent quality dipped on a specific customer's demos after yesterday's deploy. You trace it to a prompt change, roll it back, and add a test so it doesn't happen again.
Friday. You're building the infrastructure for agent versioning, so customers can preview changes before they go live. This is the kind of problem nobody has solved well because nobody has had to. You're designing it from scratch.
The technical pillars:
-
The Agent. LLM orchestration, conversation flow, tool use, voice. The agent needs to understand products it's never seen before and explain them clearly to prospects with different levels of context.
-
The Experience. Embeddable, generative UI that adapts in real-time. Fast load, complex interactive demos, works across products and screen sizes.
