Forward-Deployed Engineer

Role Overview

You'd work closely with customers to understand the problem behind the request, then turn that understanding into software that works in the real world. Some days are spent mapping a workflow with a technical founder. Other days are spent reading a codebase, debugging an integration, or shipping the fix yourself in TypeScript, Go, or Python, with every AI aide you need.

The work sits between product engineering and customer engineering. You need enough technical depth to make good calls in unfamiliar systems, and enough curiosity to keep asking what the customer is actually trying to accomplish. What you learn in the field should find its way back into the product.

Who thrives here:

• You can read a codebase, make a sensible change, and explain the tradeoff to someone who does not live in it.

• You are comfortable with an incomplete brief. You know how to turn a vague request into the next useful question, a small prototype, or a shipped fix.

• You like being close to users and solving inefficiencies. Customer conversations are part of the engineering work, not an interruption from it.

• You can work in TypeScript, Go, or Python and pick up the surrounding stack as needed.

• You keep going when the bug only appears in a customer's environment and the logs are not telling the whole story.

• You enjoy a dynamic week: a customer conversation in the morning, a hard technical problem after lunch, and something real in front of a user before the day is over.

• You want to stay close to the frontier of AI and technology, where the problems are still being discovered and the documentation has not been written yet.

• You get energy from being the person who walks into an unfamiliar room, asks the useful question, and leaves with a problem worth solving.

Some nice-to-haves:

• Experience in a customer-facing engineering, solutions engineering, or implementation role

• React, Next.js, APIs, databases, and cloud infrastructure

• Work on developer tools, AI products, or internal systems that other teams rely on

• A habit of writing down what you learned so the next person does not start from zero

• Active in technical or open-source communities, and a people-first engineer who makes the room better

• Public work you can point to, whether that is writing, talks, projects, or a thoughtful online presence

• Active on Twitter/X or another technical community, with a real interest in what builders are making and discussing

Why this role?

You get a close view of how real companies work and a direct line between what you learn and what gets built. You are close enough to the problem to shape the product instead of waiting for a handoff three layers away, and close enough to the customer to see whether the thing you shipped actually helped.

This is a seat for someone who wants meaningful equity, broad ownership, and the freedom to experiment with the newest AI tools while the rules are still being written. You will work with a strong technical setup, health coverage, flexible time off, and relocation support when the team is building in San Francisco.  

There is room to travel when being there matters, spend real time with customers, and help shape products that could define how people work with AI.