Conduit logo

Member of Technical Staff

Conduit

San Francisco, CAFull-time$130–220K/yrSeen 2mo agoStill listed 6 days ago

Most applications go out cold — see where you stand first. No sign-up to start.

Watch jobs like this.

Don't just apply. Show up ready.

Olive works from this exact posting.

At a glance

Compensation
$130–220K/yr
Location
San Francisco, CA
Schedule
Full-time
Work Authorization
Not specified

Olive lists jobs from US employers, including remote roles you can work from the United States.

Job overview

Conduit builds AI agents for hospitality businesses, handling guest communications and internal operations. The Member of Technical Staff works across the stack, owning product areas and making design decisions. The work spans response generation, knowledge retrieval, tool orchestration, evaluation, observability, agent controls, voice, performance, infrastructure, data pipelines, integrations, and APIs. The team values production experience, pragmatic model choices, and careful evaluation.

Skills & qualifications

RequiredNice to have

Skills

Production SystemsFull-Stack DevelopmentInformation RetrievalModel EvaluationPragmatic Model Selection

Qualifications

Production Systems Experience

Benefits

Medical Insurance
401(k) Match

Full job description

About Conduit Conduit is an AI agent platform purpose-built for hospitality. Hotels, vacation rentals, and resorts deploy our agents across guest-facing communication and internal operations, running millions of workflows a day. Hospitality is 10% of global GDP and it turns on customer experience. Resolving a guest request immediately is most of that experience, and resolving one means moving across several tools and between several people. That coordination is the work, and it is what our agents do. Role: Member of Technical Staff There is no hierarchy on the engineering team and everyone can work anywhere in the stack. People end up specializing in the product lines they gravitate toward, but that happens on its own rather than by assignment. We want the engineering org as flat as we can keep it. Why this role is different

  • Free rein with AI agents, and full ownership of what comes out. Nobody tells you which tools to reach for or how much of the work to hand off. Where to use an agent and where to do it yourself is your call, and how well you make that call is what we evaluate you on.
  • You will touch most of the stack and end up owning parts of it. You work across the codebase instead of in one lane. The modules you go deep on become yours, and the team depends on you for them.
  • The design decisions are yours to make. You choose the approaches, and the ones that hold up stay in the platform for decades. That is real weight to carry and it is most of why the role is interesting.
  • You are directing a fleet of agents. You sketch the work, design it carefully, and the agents execute against that design in parallel. You get a lot of output for each unit of work you put in, and getting good at running that is a skill that follows you everywhere else.

What the work looks like

  • Response generation pipeline. The router, orchestrator, and synthesizer that classify intent, assemble context, select tools, generate a response, and decide whether to send it or escalate.
  • Knowledge retrieval. Models ground their answers in whatever context they are given, so reliability comes down to whether that context is correct, complete, and current. Customer data is usually none of those. You build the retrieval, ranking, and validation that makes the output trustworthy anyway: a hierarchical knowledge base with scope-based queries, contradictory docs, stale articles, and the edge cases that live in one rep’s head.
  • Tool orchestration. The agents modify reservations, dispatch maintenance, send confirmations, and close the loop. You design the tool-use and function-calling layer that runs multi-step workflows end to end, including what happens when a third-party API goes down mid-conversation.
  • Evaluation and testing. The eval framework that measures quality against real conversations and catches regressions before customers see them.
  • Observability. The trace that shows what the agent retrieved, what it considered, what it ignored, where confidence dropped, and why it chose what it did. That trace is what lets a CX team trust the system and improve it.
  • Controls for people who are not engineers. The people running these agents day to day are support leads. You make the agent’s behavior legible, testable, and adjustable by someone who has never written code.
  • Voice. Real-time conversations with transcription and the same tool use as text, under tighter latency.
  • Speed and cost. Model routing, caching, prompt optimization.
  • Infrastructure, data pipelines, integrations, and API work. The systems underneath all of the above.

Who you are

  • You have shipped production systems that real users depend on.
  • You are comfortable anywhere in the stack and pick up whatever the problem needs.
  • You think about retrieval as seriously as generation.
  • You are pragmatic about models. Sometimes the right answer is a frontier model, sometimes a small fine-tuned one, sometimes a regex.
  • You care about evaluation. You do not ship a prompt change without knowing what it does across a thousand real conversations.
  • You want a small team where the thing you push changes the product that day.

Compensation and Benefits

  • $130-220K base
  • 0.20%-1.20% equity
  • Comprehensive health insurance and 401k match

How this job compares

Set against the 41,448 open Software Engineer jobs on Olive Jobs, counted November 1, 2026.

Pay
  • This posting$130–220K/yr
  • California median$165–246K/yr7,747 salary ranges
  • US median$135–217K/yr32,925 salary ranges

This range's midpoint, $175K, is 15% below the California median midpoint ($205K) — in the middle half of Software Engineer salary ranges in California.

Openings
Olive Jobs lists 9,646 open Software Engineer jobs in California and 41,448 across the US. 7% of them nationwide are listed as remote or flexible.
Hiring the most in California
Experience
This posting asks for at least 1 year of experience — less than three in four Software Engineer postings that state a minimum ask for (median 5 years, across 33,633 postings).
Education
14,754 of the 41,448 open Software Engineer jobs (36%) ask for a bachelor's degree or higher.

Counted across the open, public US postings on Olive Jobs on November 1, 2026. Pay medians are the middle values of the low ends and of the high ends of postings that list both ends of a range in the same cadence (a yearly salary or an hourly rate); a range's midpoint is halfway between its ends. Pay and experience figures resting on fewer than 20 postings are left out.

You've read the whole posting — now see how you match it.