(AI Solutions Engineer, Delivery Lead)
You join as an early member of the engineering team.
We build governed AI operators, which we call BOBs, that do real work inside small and mid market businesses. Not copilots. Not chat wrappers. Systems with role contracts, budget limits, audit trails, and a human who can see exactly what the system did and why.
You will own client deployments end to end, from the first discovery conversation through production and measurement, working alongside a senior CX and Product partner who owns the client relationship. What you learn in each deployment goes back into the platform so the next one starts further ahead.
We are a small team with production clients and a growing pipeline. We are good at the engineering and we are good at the outcomes. What we need now is another person who can hold the whole arc: hear a business problem directly from the operator who has it, design the system that solves it, write the code, put it in production, prove it worked, and then make the platform smarter so the next deployment goes faster than the last.
Most engineers can do the middle of that arc. Fewer can do the front of it. Almost nobody does the back of it unless asked. We are hiring for all three.
You will also help guide the technical bar for the rest of the engineering team.
Roughly how a month breaks down, so you can decide whether this is the job you want:
You write the code. This is not an architecture role with a hand off to someone else. If you have not shipped production code in the last eighteen months, this is the wrong role.
Discovery sessions, workflow mapping, design reviews, go live, and the conversation where you show an owner what the system did last week and what it cost. Typically two to three concurrent accounts.
Turning what you just learned into platform capability: identity and state, tenant scoped memory, playbook construction, tool and action surfaces. Configuration over code forks, every time.
Everyone here is expected to lead from the front: design review for other engineers, holding the delivery standard, mentoring, and setting the example by doing the work well. Your influence comes from what you ship and how you handle yourself in front of a client, not from a reporting line.
You have a partner. A seasoned CX and Product leader who owns the client relationship: agenda, cadence, expectations, escalation, follow up, solution design and commercial temperature. That person runs the room.
You are in the room. Not on the recording, not reading the readout. For discovery and design review you are present and asking your own questions, because a requirement that reaches you secondhand has already lost the detail that mattered.
Technical discovery, the code, deployment, evals, guardrails, instrumentation, and the technical relationship with the client's operator and their technical counterpart.
Renewals, pricing, upsell, invoicing, change order negotiation, quarterly business reviews, and the tier one support queue. You flag commercial risk. You do not carry the quota or the relationship maintenance.
We draw this line on purpose. We have seen what happens to engineering throughput when we do not.
You will design against four primitives.
Every interaction anchored to objects under strict org level isolation.
Tenant scoped transcripts, documents, embeddings, and artifacts in partitioned data planes.
Model instructions constructed dynamically from each tenant's methodology, ICP, and vocabulary. No fixed framework unless the client asks for one.
Tenant specific tools loaded through an orchestrator. Configuration over code forks.
Our production bar, which is not negotiable:
We optimize for velocity under constraint. Not speed without discipline, and not discipline without shipping.
Required:
Nice to have. Genuinely nice to have, not a hidden filter:
Who this is wrong for:
Membership based care with a doctor you can actually get on the phone, not a carrier phone tree.
Take the time. We care that the work ships and the clients are covered.
You own the delivery engineering standard, you decide how deployments run, and nobody above you is going to relitigate your architecture in a hallway.
You will touch every layer, talk to every client, and see the direct line from what you built to what the business did.
Send to careers@bob.pro:
If that page is interesting, the process is:
The role, the company, compensation, your questions.
You sit with the engineers you would be working next to and with your CX and Product partner. They ask their own questions and their read carries real weight. We are small enough that everyone here works with everyone.
We hand you a real, anonymized client problem and you work it. When you are done we look at the repo together to see what you built. We are watching how you worked the problem, not whether you finished it.
Four steps, 2 weeks, and you will know where you stand after every one.
Essential storage remembers this choice. With your permission, analytics also preserves bounded campaign attribution and loads Google Tag Manager and Apollo. Booking links still work if you decline. Read the privacy policy.