# Engineering Manager, Product at Aaru

- Company: Aaru
- What the company does: Humans are unreliable narrators of their own behavior. Memory fails, incentives distort answers, and social pressure warps what people say away from what they actually do. Backed by General Catalyst, Felicis and Redpoint.
- Company website: https://aaru.com/
- Type: Startups
- Level: Senior
- Location: NYC
- Work setup: On-site
- Pay: $280K to $425K base salary per year (USD)
- Posted: 2026-08-22
- Apply by: 2026-10-08
- Apply: https://jobs.ashbyhq.com/aaru/3dfc9130-51d5-47b3-94eb-e1df4ef0c0d1
- Page: https://www.1752.vc/careers/jobs/aaru-engineering-manager-product/

## About the role

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.

## What they're looking for

- 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 Platform, and whether temporary embedding or shared ownership is the fastest durable path
- Two workstreams are moving quickly but making incompatible architectural choices. Establish the shared contract before the divergence becomes expensive
- A workflow is technically correct but users do not trust it. Diagnose whether the issue is product framing, interaction design, provenance, latency, model behavior, or actual quality—and direct the team toward evidence rather than opinion

Tags: Technical Staff