Product Engineer
Posted 9 Oct 2026
Advertised as “Senior Product Engineer (AI-native)”
BranchFactor Summary
The original posting with the fluff stripped out
- Expected experience
- 6+ yrs
- Management level
- Individual contributor
- Employment
- Remote
No salary listed for this role.
About Mixmax
Mixmax is the #1 product helping revenue teams work proactively by eliminating busywork and creating seamless customer experiences, used by thousands of sales and customer teams inside Gmail and their CRM.
In 2026 we rebuilt how engineering works around AI agents. We are a small, senior team that ships with agents doing most of the typing, and engineers doing the thinking: deciding what to build, designing the system, directing agents, and owning what goes to customers.
How we work
- There are no fixed feature teams. Every engineer sits on one bench, and small pods of 1–3 people (often an engineer, a PM and a designer) form around a prioritized brief, ship it end to end, and dissolve.
- Agents are the default way to build. You orchestrate several agents in parallel, give them context, and verify what they produce.
- Every project follows one contract. A living spec with acceptance criteria, an append-only decision log, a release brief for sales and CS, and an honest retrospective.
- Verification gates, not handoffs. An agent verifier checks every PR against the spec, and another checks every release on staging before customers see it. There is no QA handoff.
- Designs are code. Designers ship AI-generated, production-ready prototypes; you build against them.
- Autonomy with accountability. You decide how to build, which tools to use and when to ship behind a flag. Compliance, production safety and customer-data rules always apply.
- We talk in weeks and scope down until it hurts. Outcome over output; we don't release and forget.
What you'll do
You will own product and platform projects end to end, from a one-line brief to a feature customers use, with AI agents as your main way of building.
- Shape the work. Turn a brief into a spec with clear user need, acceptance criteria, technical plan, cost, security and instrumentation, together with product and design.
- Design the system. Make the architectural calls, keep them simple and scalable, and log the decisions that matter.
- Orchestrate agents. Run multiple coding agents in parallel, feed them the right context (skills, rules, repo cards and our internal MCP servers), and keep cost and token spend in check.
- Verify everything. Review agent output with a critical eye, write the Playwright and unit tests, and pass the PR and release gates yourself.