Member of Technical Staff

Chosen HQ; San Francisco (CA); On-site; USD 180,000 - 240,000; Full time

Job summary

Chosen HQ LLC seeks an engineer to own complete systems—from design to production—for an AI-driven browser automation platform. You will work on the three-layer product: agents that build and repair automations, the console/API used by customers, and the underlying infrastructure running at scale in production.

You will need strong judgment, shipped LLM-powered features to real users, and comfort working across frontend, backend, database, and cloud infrastructure.

Qualifications

• Two or more years building and running software in production.
• Owned a system end to end and was the one paged when it broke.
• Shipped LLM-powered features to real users and can discuss agent failures.
• Worked across frontend, backend, database, and infrastructure on production cloud systems.
• Built things in direct response to customer feedback and enjoy those conversations.
• Move quickly, iterate on what you learn, and care about craft.

Responsibilities

• Own whole systems from design through production for the product with three layers: agents, console/API, and scalable infrastructure.
• Carry large pieces of each layer through development and production deployment.
• Provide reliable, scalable, and observable automation at scale in real production traffic.
• Define engineering standards and practices for a team that is about to grow.
• Collaborate across frontend, backend, database, and infra to ship end-to-end features prioritized by customer needs.

Skills

Production software

End-to-end ownership

LLM features

Full-stack work

Customer feedback

Fast iteration

Tools

AWS

Browser automation

Distributed systems

Job description

Why it is worth a look:

• Funded. $5M raised
• Early. The team is still small enough that you would be setting the engineering standards, not inheriting them.

We are partnering with a San Francisco startup that has built an AI coding agent for automating enterprise software, starting with the systems that have no API at all. A developer describes a workflow once and triggers it through an API; the platform writes the browser automation, tests it, runs it on hosted infrastructure, and repairs it on its own when the target system changes. For customers, that works out to roughly a 90% cut in development time.

Why it is worth a look:

• Funded. $5M raised
• Early. The team is still small enough that you would be setting the engineering standards, not inheriting them.
• Hard problems. LLM agents, browser automation, and distributed systems, with real production traffic behind all of it.

The role

You will own whole systems, not tickets. The product has three layers: the agents that write and repair automations, the console and API customers use to deploy and watch them, and the infrastructure that runs them at scale. You will carry large pieces of each from design through production.

We are looking for judgment as much as output. Problems here usually arrive half-formed. We want someone who can find the shape of the right solution, make the technical call, and get it shipped without waiting for a spec.

One thing to know before you apply: their automations sit inside clinical operations. A broken run can hold up a clinic's work and, downstream, a patient's care. That is why reliability gets more of their attention than almost anything else.

What you will build

• The agent layer. The workflow builder and maintenance agents that generate automations and repair them when they break, driving low-level browser actions through tool calls.
• Scale. The worker fleet, job queues, and live coordination layer that carry tens of thousands of runs a day now and need to carry millions.
• The developer surface. APIs, SDKs, and observability tools that show customers why a run failed and what will fix it.
• Product, end to end. Features across frontend, backend, database, and infrastructure, prioritized by what customers tell them they need.
• How the team works. Engineering standards and practices for a team that is about to grow.

Who we are looking for

Required

• Two or more years building and running software in production.
• You have owned a system from end to end and were the one who got paged when it broke.
• You have shipped LLM-powered features to real users and can speak in detail about the ways agents fail.
• You work comfortably across frontend, backend, database, and infrastructure, on production cloud systems.
• You have built things in direct response to customer feedback and enjoy being in those conversations.
• You move quickly, iterate on what you learn, and still care about craft.

Helpful, not required

• AWS
• Browser automation, distributed systems, or healthcare data.

Logistics

• Location: San Francisco, on-site.
• Compensation: $180K–$240K.
• Eligibility: US citizens and holders of a valid US work visa only.