AgentMail Founding Product Engineer at AgentMail owns product development from ambiguous customer problems to usable developer tools. The role involves building frontend, APIs, backend services, and shaping developer experience.
Responsibilities
You’ll own products from an ambiguous customer problem to something developers use every day.
That means you’ll:
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 they’re 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 agents’ 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. You’ll have significant influence over the design and interaction patterns of AgentMail.
Help define the product engineering culture. You’ll be one of the earliest engineers explicitly focused on product and will shape how we build products as the team grows.
Who we’re looking for
We’re looking for an engineer who thinks about the why behind what they’re building.
Qualification
You’re comfortable moving quicklyWhat this role is notWork on a new categoryCare about API design
Required
You can take a vague problem like “developers can’t figure out why their agent didn’t respond to this email” 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 they’re 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’re comfortable moving quickly, shipping imperfect things, learning from usage, and iterating.
You don’t need to have been called a “Product Engineer” before.
We’re much more interested in whether you’ve built things people love and whether you can independently go from customer problem → idea → product → shipped software → learning.
What this role is not
This isn’t a role where a PM hands you a spec and a designer hands you a Figma file.
You’ll 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.
You’ll have a tremendous amount of autonomy—and an equally high bar for ownership.
Work on a new category. We’re building infrastructure for a world where billions of AI agents need identities and ways to communicate with humans, businesses, and each other.
Preferred
Exceptional frontend engineer with strong product and design instincts
Strong engineering fundamentals beyond frontend
Ability to translate vague problems into products
Enjoy talking to customers and understanding underlying problems
Contextualize technical decisions by customer and business impact