Senior Product Engineer (AI-native)

Mixmax; USA; Remote; USD 140.000 - 190.000; Vollzeit

Benefits dieser Stelle

Remote work

Small, senior team

Direct impact on products

Zusammenfassung

Mixmax is a leading revenue-tech company optimizing customer interactions within Gmail and CRM. We seek a product-focused engineer to own end-to-end AI-driven platform projects, from brief to customer-facing feature, coordinating architects, agents, and design.

You’ll ship in tight cycles, validate with tests and metrics, and collaborate with a senior team to shape the next wave of AI-enabled products. Remote-friendly, US-friendly time zones encouraged.

Qualifikationen

• 6+ years building and running production software, with deep backend experience across the stack.
• An AI-native setup you can show us: Claude Code, Codex, Cursor or similar; with your own skills, rules, MCP servers or agent workflows, and examples of running agents in parallel.
• Strong judgment on agent output, catching subtle bugs, security issues and architectural drift.
• Experience designing distributed systems on AWS: event-driven flows, queues, idempotency, failure recovery and cost.
• Ownership of quality without a QA team: test strategy, CI, observability, feature flags and incident response.
• Product sense: explain why a project matters to customers, trim scope to essentials and measure results.
• Clear written communication in English: specs, decision logs and async updates keep a distributed team aligned.
• Comfort with ambiguity and change; you help shape evolving processes.

Aufgaben

• Shape the work. Turn a brief into a spec with clear user need, acceptance criteria, technical plan, cost, security and instrumentation, with product and design.
• Design the system. Make 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, and monitor costs.
• Verify everything. Review agent output with a critical eye, write Playwright and unit tests, and pass PR and release gates.
• Ship and watch. Release behind feature flags, set up monitoring and analytics, and validate the feature for users.
• Take your turn on support. Join the rotation, handle incidents, and convert recurring problems into briefs.
• Improve the system we build with. Contribute patterns and learnings to the shared context repo.

Kenntnisse

AI agents

Systems design

Product ownership

AWS

Security minded

English communication

Tools

Claude Code

Codex

Cursor

MCP servers

Jobbeschreibung

About Mixmax

Mixmax is the #1 product helping revenue teams work proactively by eliminatingbusywork and creating seamless customer experiences, used by thousands of sales andcustomer 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 tocustomers.

How we work

• There are no fixed feature teams. Every engineer sits on one bench, and small pods of 1–3people (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, givethem 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 QAhandoff.
• Designs are code. Designers ship AI-generated, production-ready prototypes; youbuild against them.
• Autonomy with accountability. You decide how to build, which tools to use and whento ship behind a flag. Compliance, production safety and customer-data rules alwaysapply.
• 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 featurecustomers 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, andlog the decisions that matter.
• Orchestrate agents. Run multiple coding agents in parallel, feed them the rightcontext (skills, rules, repo cards and our internal MCP servers), and keep cost andtoken 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.
• Ship and watch. Release behind feature flags, set up Datadog monitors and productanalytics, use Cleric.ai to investigate production issues, and confirm the featureactually works for users.
• Take your turn on support. Join the support rotation, handle incidents, and turnrecurring problems into new briefs.
• Improve the system we build with. Contribute skills, patterns and learnings to ourshared context repo so the next pod moves faster.

In your first 90 days you’ll: set up your AI-native environment, ship a scoped project witha pod, take a support rotation, and contribute at least one learning or skill back to theshared repo.

About you

You already build with agents every day, and you think like a systems designer andproduct owner more than a ticket-taker.

You’ll likely have:

• 6+ years building and running production software, with deep backend experience andthe range to work across the stack.
• A working AI-native setup you can show us: Claude Code, Codex, Cursor or similar;with your own skills, rules, MCP servers or agent workflows, and examples of runningagents in parallel.
• Strong judgment on agent output. You catch subtle bugs, security issues andarchitectural drift, and you know when not to trust a green test run.
• Experience designing distributed systems on AWS: event-driven flows, queues, idempotency, failure recovery and cost.
• Ownership of quality without a QA team : test strategy, CI, observability, feature flags and incident response.
• Product sense. You can explain why a project matters to customers, cut scope to theessentials and measure the result.
• Clear written communication in English. Specs, decision logs and async updates arehow a distributed team stays aligned.
• Comfort with ambiguity and change. The way we work is still evolving, and you helpshape it.

Our stack

TypeScript and Node.js (Express), MongoDB, AWS (Fargate, Lambda, SQS, EventBridge, DynamoDB), Terraform, React in an Nx/pnpm monorepo, Vitest and Playwright, GitHub Actions, Datadog and Cleric.ai (AI SRE) for observability, Linear and internal MCP servers that give agents context on our services and tooling.

Nice to have:

• Building LLM-powered product features: agents, tool use, MCP servers, evals.
• Building internal agent tooling: PR review bots, sandboxed agents, context services.
• Gmail, Google Workspace or CRM (Salesforce, HubSpot) integrations.
• SOC 2 or security-conscious engineering in a SaaS company.

Why this role

• You work the way engineering is heading. Agents, verification gates and specs ascode are how we ship today, not a pilot.
• Real ownership. You choose the work from a prioritized list, decide how to build it, andsee it through to customers.
• Small team, direct impact. No layers between you and product, design, CS orleadership.
• Shape the model. Our operating model is young; your learnings and skills become howeveryone works.

Location: remote, ideally LATAM (Brazil or Argentina preferably). If Europe, has to work Brazil/Argentina time zone. We can’t hire in the US at present.