Skip to content
aitrainer.work - AI Training Jobs Platform
Engineering Full-Time
Arini

Senior Software Engineer (US)

Arini • San Francisco Bay Area

Company

Arini

Annual salary

$190k – $250k/yr

Location

San Francisco Bay Area

Listed

31d ago

Experience:
4 to 10 years
Workplace:
Fully in person, 5 days a week, at Arini's San Francisco office. The whole engineering team works on-site. Lunch and dinner are provided in the office.
Equity:
0.1%, 0.5%, based on seniority.

On-site in San Francisco Bay Area.

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

  • Design and build the platform modules that run operations for the largest outpatient healthcare enterprises, covering scheduling, patient communication, insurance, accounts payable, reconciliation, credentialing and reporting
  • Own a product line or vertical from design through build, deployment and operation, and drive reliability, security and lower error rates as Arini adds hundreds of clinic locations
  • Work closely with forward deployed engineers, customer success and the CTO/co-founder (Rami) to turn one-off customer solutions into reusable products. For example, you might take the EHR-to-bank reconciliation demo and turn it into a product that works for many enterprises
  • Build and operate AI agents in production, with the evaluation, guardrails, observability and client feedback loops that tune them automatically. This is applied agent work, not model training or research
  • Lead infrastructure projects from scoping to rollout, such as tools that let non-technical team members configure custom modules for clients
  • Design and improve data models, pipelines and integrations into practice management, billing, payment and vendor systems (including ones without APIs), and own on-call and root-cause analysis for what you build

What you need

  • We need a senior- to staff-level backend or systems engineer with at least 4 years of experience. 6, 7 years is ideal, roughly graduating in 2018, 2019. You should have built and run reliable, scalable production systems at a fast-growing startup or a top tech company. You should be comfortable owning modules end to end in a fast, in-person team with little hand-holding, and you should already build with AI coding tools like Claude Code and Codex every day. Bonus points if you've built AI agents in production or come from a top engineering school or a company like Meta, Palantir, Sierra, Decagon, Perplexity or ElevenLabs.

Common questions

How do I apply for the Senior Software Engineer (US) role at Arini? +

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 Arini role pay? +

The listing gives $190k – $250k/yr.

Is this role remote? +

The listing gives the location as San Francisco Bay Area. Fully in person, 5 days a week, at Arini's San Francisco office. The whole engineering team works on-site. Lunch and dinner are provided in the office.

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.

See all 10 Software Engineer interview questions →

Related roles

Arini

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 →