San Francisco, CA • In-person
We9re looking for a Founding Product Engineer to help define what using AgentMail actually feels like.
What you9ll doYou9ll own products from an ambiguous customer problem to something developers use every day.
That means you9ll:
- Build products end-to-end. Work across polished frontend experiences, APIs, backend services, data models, and infrastructure when the product calls for it.
- Talk directly to customers. Interview developers, watch them use AgentMail, dig through support conversations and usage data, and understand where they9re getting stuck.
- Turn customer problems into products. Figure out what should be built-not just how to build it-and develop conviction about which problems are actually worth solving.
- Build AgentMail Studio. Help create the interface developers use to understand, debug, and interact with their agents9 email-from inspecting messages and threads to testing workflows and understanding what happened under the hood.
- Shape our developer experience. Improve everything between a developer signing up and getting something useful into production: onboarding, SDKs, APIs, debugging tools, docs, and the console.
- Prototype quickly. Turn an idea from a customer conversation into something they can use days later.
- Sweat the details. We care deeply about how our products look, feel, and behave. You9ll have significant influence over the design and interaction patterns of AgentMail.
- Help define the product engineering culture. You9ll be one of the earliest engineers explicitly focused on product and will shape how we build products as the team grows.
Who we9re looking forWe9re looking for an engineer who thinks about the why behind what they9re building.
You might be a great fit if:
- You9re an exceptional frontend engineer with strong product and design instincts.
- You have strong engineering fundamentals and are comfortable going beyond the frontend-working with APIs, backend systems, databases, queues, and distributed systems when necessary.
- You can take a vague problem like 44developers can9t figure out why their agent didn9t respond to this email44 and turn it into a product without waiting for a detailed spec.
- You enjoy talking to customers and can separate what someone asks for from the underlying problem they9re actually trying to solve.
- You can contextualize technical decisions in terms of customer and business impact.
- You care about API design and developer experience, not just UI.
- You have strong opinions about products but are willing to change your mind when the data or customer evidence says otherwise.
- You9re comfortable moving quickly, shipping imperfect things, learning from usage, and iterating.
- You have extremely high agency. When something is broken or missing, your instinct is to fix it.
You don9t need to have been called a 44Product Engineer44 before.
We9re much more interested in whether you9ve built things people love and whether you can independently go from customer problem 12 idea 12 product 12 shipped software 12 learning.
What this role is notThis isn9t a role where a PM hands you a spec and a designer hands you a Figma file.
You9ll be expected to participate in the entire product process: talking to users, deciding what matters, designing solutions, writing the code, shipping them, and figuring out whether they worked.
You9ll have a tremendous amount of autonomy-and an equally high bar for ownership.
