Company
Bland
Annual salary
$170k – $220k/yr
Location
San Francisco, CA
Listed
22d ago
- Experience:
- 3 to 7 years
- Workplace:
- 5 days in-office in Levi's Plaza, San Francisco (relocation available)
- Equity:
- Competitive equity
Open to people who live in the US, Canada or the UK
We can only put candidates forward for this role from those three countries for now. See the contract AI training jobs open in more countries.
On-site in San Francisco, CA.
Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.
Apply for a referral →The recruiter emails you before anything happens and may suggest other jobs that suit you better.
About this role
The phone call is still the main way people reach the businesses they depend on, and the experience has barely changed in decades. We are building what replaces it. Few conventions exist for this kind of product, so much of the work involves deciding how something should behave before anyone has built it.
We are hiring engineers to take on that work across the entire system. Depending on your strengths, you may work on the core agent: how it reasons, when it speaks and when it waits, how it handles interruptions, and how new models from our research team reach live calls. You may work on the tools customers use to shape, test, and understand agents whose behavior is never fully deterministic. Many of our engineers do both.
Current efforts include self-improving agents, which review their own conversations, diagnose what went wrong, and verify fixes before releasing them. Projects of that scope come up regularly, and engineers here help define them as well as build them.
We care about delight at every layer of the product, from the interface to the API to the way a call sounds to the person on the other end. The team is small and moves quickly, and you will have real ownership from your first week.
Our stack
TypeScript end to end, with React, Node, PostgreSQL, Temporal, and Kubernetes on AWS. Our speech and language models run on our own GPU infrastructure.
What we look for
Experience building with LLMs in production, and with real-time or latency-sensitive systems.
Strong fundamentals and the range to work anywhere in the stack, whether your background leans toward product and interfaces or toward backend systems.
A record of taking ambiguous problems from idea to production with little direction.
High standards for the quality and feel of what you ship.
Daily use of AI coding tools.
Strong opinions, loosely held, and low ego. You argue for your position, change your mind when the evidence points elsewhere, and put the right outcome for the team ahead of being right.
Common questions
How do I apply for the Software Engineer, Full Stack (Agentic AI) (US) role at Bland? +
Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.
What does this Bland role pay? +
The listing gives $170k – $220k/yr.
Is this role remote? +
The listing gives the location as San Francisco, CA. 5 days in-office in Levi's Plaza, San Francisco (relocation available).
Software Engineer interview prep
Questions Software Engineer interviewers often ask. They aren't taken from this listing.
How do you approach designing a system when the requirements are still likely to change?
I design around the parts of the problem I'm confident are stable, like the core data model, and keep the parts most likely to change, like specific business rules, isolated behind clear interfaces. Over-engineering flexibility everywhere just adds complexity to parts of the system that were never going to change.
What's your process for debugging an issue that only reproduces in production, not locally?
I add targeted logging around the suspected area and compare production data or configuration against my local setup, since an issue that's environment-specific usually traces back to a real difference between the two rather than a fundamentally different bug. I avoid making speculative changes without first confirming where the divergence is.
How do you decide when a piece of code needs a test versus when it's low-risk enough to skip?
I prioritize tests for logic with real business consequences if it breaks, or code that's likely to be touched again later by someone unfamiliar with it. Simple, rarely-changed glue code gets less coverage, since the cost of a thorough test there often exceeds the risk it's protecting against.
How do you evaluate a proposed technical solution's trade-offs, like performance versus maintainability?
I start from the actual constraint that matters for this specific system, whether that's genuinely performance-critical or whether maintainability is the bigger long-term cost, rather than defaulting to whichever trade-off I personally prefer. Optimizing for performance the system doesn't need just adds complexity nobody benefits from.
Related roles
Browse all referral roles
Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.
See all referral roles →