Product Manager

AJAIA•New York, NY

11h•$100,000 - $175,000•Onsite

About The Position

Ajaia is hiring a Product Manager to own products in Ajaia's product suite end to end. You will talk to users and customers every week, decide what gets built next and why, and say plainly what does not get built, including when the loudest voice in the room wants it. You will write specs an engineer can build from without a follow-up meeting, prototype with AI tools when a working demo settles an argument faster than a deck, and stay on the number after launch and act on what it tells you. This is a builder's seat: you will contribute to the code and the design yourself, not only direct them. AI use is a core execution requirement at Ajaia, not optional tooling. You will use AI daily to sort through usage data, draft specs, and build working prototypes yourself, and you are judged on what you keep from that output, not on how much of it you generated. The tools change fast, and staying current on what is worth using is part of the job.

Requirements

Highly organized across multiple priorities and open questions at once.
Sharp judgment on what to build next, and clear about what not to build.
Strong plain writing: specs and decisions other people can act on without a follow-up meeting.
AI fluent: you use AI daily to sort signal, draft specs, and prototype, and you can tell good output from slop.
Comfortable contributing to code and design directly, with AI tools making you faster at both.
Comfortable holding a priority call under pushback, or changing it for stated reasons.
1 or more years in product management, or work that proves the same skill.
On-site in New York.

Nice To Haves

Experience with a B2B product used by an operational or compliance function.
Comfort reading usage data or a support queue yourself.
Exposure to a regulated industry such as financial services, insurance, healthcare, or legal.
Prior experience in a 0-to-1 or early-stage product role.

Responsibilities

Talk to users and customers every week.
Turn messy, sometimes contradictory signal, usage data, support tickets, sales requests, and what people say in interviews, into a ranked call on what gets built next.
Say plainly what does not get built, including a well-funded customer's request, when the evidence does not support it.
Write specs an engineer can build from without a follow-up meeting: the outcome, what is in and out of scope, where a human stays in the loop, and acceptance criteria someone could test.
Prototype the core flow yourself, wireframes, a clickable mock, or a working demo, when that settles the argument faster than a deck would.
Contribute to the code and the design directly: ship a small feature or fix with AI tools, mock the screen yourself, and hand engineers something running instead of something described.
Partner with the design team on what the solution should be and how it holds up for the people using it.
Partner with the delivery team and engineers on how the build runs and the date it ships by.
Present the roadmap and the tradeoffs to the people who fund it, including when a client or a salesperson is unhappy with the call.
Hold a priority decision under real pushback, or change it, and say why either way.
Ship it, then watch the number after launch and act on what it says.