Product Engineering Manager

Product Engineering Manager

As Product Engineering Manager, you will lead a focused team of Product Engineers and be accountable for the quality, pace, and impact of what the team ships. Managers at Aaru remain builders. You will set technical direction, shape product decisions, review critical designs, write and debug code when it is the highest-leverage use of your time, hire exceptional engineers, and develop the people already on the team.

You will partner closely with a Product Manager and Product Designer. Together, you will select problems, define the product domain, and establish a roadmap that balances immediate customer value with reusable product foundations. You will also create the operating mechanisms that let multiple work streams move quickly without losing clarity, quality, or ownership.

This is a line-management role, not a distant function-head role. Your primary responsibility is to make a small team unusually effective: give people context, set a high bar, resolve ambiguity, provide direct feedback, and ensure that commitments become excellent production systems.

• Build, lead, and develop a high-performing team of Product Engineers with clear ownership, strong technical judgment, and a high standard for product craft.

• Set technical direction for the team's product domain across frontend, backend, APIs, data models, workflow orchestration, integrations, observability, and model-dependent behavior.

• Partner with Product and Design to identify the most important user problems, define a coherent roadmap, and make principled decisions about scope and sequence.

• Create an execution model for parallel work streams: clear DRIs, credible milestones, early risk discovery, focused reviews, and fast escalation when dependencies or assumptions fail.

• Stay close to the work through system design, architecture reviews, code review, debugging, product critique, user sessions, and direct contribution to the hardest or most ambiguous problems.

• Ensure that the team turns specific customer evidence into generalizable product capabilities rather than accumulating custom branches, configuration debt, or manual operations.

• Establish a quality bar for AI-native product development, including evaluations, human review points, instrumentation, rollout criteria, fallbacks, provenance, and safe rollback.

• Define clean interfaces with Platform Engineering and Simulation Engineering. Work through missing primitives explicitly and contribute to shared foundations when that is the right organizational answer.

• Build tight feedback loops with Deployment and customers so that field failures, confusing workflows, and unexpected model behavior become prioritized product and engineering work.

• Own production quality for the team's systems, including reliability, latency, security, permissions, cost, on-call health, incident follow-up, and maintenance.

• Recruit exceptional engineers from sourcing through close. Build a team with the right mix of product sense, technical depth, speed, and ownership.

• Set expectations clearly, provide frequent and candid feedback, recognize exceptional work, address performance problems early, and invest in each engineer's growth.

• Improve the broader engineering organization through reusable patterns, stronger development tools, better technical communication, and a culture of thoughtful urgency.

• The team has five credible feature opportunities but only enough capacity to pursue two. Determine which problems matter, what evidence would change the decision, and how to sequence the work without creating strategic drift.

• A major customer request is valuable but highly specific. Find the underlying general problem and design a capability that serves the customer without turning the product into consulting software.

• A new research capability produces impressive demonstrations but inconsistent user outcomes. Define the evaluations, interaction design, constraints, and rollout plan required before it becomes a product feature.

• Product delivery is repeatedly blocked by missing platform primitives. Decide what belongs in Product Engineering, what belongs in…