Senior Software Engineer (US)
Interface AI • Financial District, San Francisco, CA
Company
Interface AI
Annual salary
$230k – $250k/yr
Location
Financial District, San Francisco, CA
Listed
51d ago
- Experience:
- 3 to 6 years
- Workplace:
- 5 days/week in-office at the new 21st-floor office at 44 Montgomery St, Financial District, San Francisco. In-person collaboration is real and intentional.
- 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 Financial District, 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.
What you'll do
- Lead the design and build of scalable, observable and maintainable platform services that power interface.ai's agentic AI products for credit unions and community banks
- Own technical decisions end-to-end, including architecture, APIs, data models, performance and security, and deliver reliable systems under real limits on latency, reliability, cost and scale
- Work closely with the VP of Engineering, CTO and Co-Founder Bruce Kim, CEO Srinivas Njay, and the product, design and data teams, in the office in real time, to turn product bets like the AI-first contact center and AI-native consumer banking into shipped systems
- Build and extend backend systems in TypeScript and Python, and shape frontend experiences in JavaScript/React
- Lead the integration of LLM-based and agentic AI capabilities into production from design to deployment. This is applied AI engineering, not research.
- Define and enforce engineering standards for code review, testing, deployment and incident response, and bring AI-native tools (Claude Code, Cursor) into daily work to raise team speed and quality
What you need
- We need someone with **3-6 years of software engineering experience **building production-grade platform systems in TypeScript and/or Python, who has a record of leading the systems they shipped, not just contributing to them. You should be comfortable owning technical decisions end-to-end and using LLM-based and agentic AI in production every day, in person in SF. We want to see that you've built core systems at scale, taken products from 0 to 1 and owned whole domains, ideally including recent time (2+ years) at a Series A to D startup. Bonus points if you have experience with conversational or voice AI, NLP pipelines or agentic architectures, a background in fintech, banking or regulated financial services, or time as an early or founding engineer at a startup that shipped.
Common questions
How do I apply for the Senior Software Engineer (US) role at Interface AI? +
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 Interface AI role pay? +
The listing gives $230k – $250k/yr.
Is this role remote? +
The listing gives the location as Financial District, San Francisco, CA. 5 days/week in-office at the new 21st-floor office at 44 Montgomery St, Financial District, San Francisco. In-person collaboration is real and intentional.
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 →