Skip to content
aitrainer.work - AI Training Jobs Platform
Product Full-Time
Axle.insure

Technical Product Manager (US)

Axle.insure • New York, NY

Company

Axle.insure

Annual salary

$160k – $220k/yr

Location

New York, NY

Listed

110d ago

Experience:
5+ years
Workplace:
In-person 4 days a week at Axle's Flatiron/NoMad office in NYC, with approximately occasional travel to enterprise client sites.
Equity:
0.10% - 0.30% equity

On-site in New York, NY.

Send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role.

Apply for a referral →

The recruiter emails you before anything happens and may suggest other jobs that suit you better.

What you'll do

  • Own and facilitate design sessions with enterprise clients, running structured conversations to deeply understand their products, workflows, and customers better than they do
  • Define how Axle fits into each client's product, technology stack, and operational processes, documenting design decisions across people, process, and technology
  • Travel to client sites (~once/month) to build relationships, lead in-person discovery sessions, and reinforce trust at the executive and operator level
  • Translate client feedback and real-world friction into clearly scoped product requirements that Product & Engineering can execute against without ambiguity
  • Partner with Technical Account Managers and Deployment Strategists post-session to ensure what was designed in the room is executable in the field
  • Develop a library of design patterns, solution architectures, and client workflow documentation that accelerates future implementations
  • Grow into a trusted internal authority on Axle's product capabilities, limitations, and roadmap, the person Sales, CS, and Engineering all rely on to understand what's possible

What you need

  • We need someone with 5-7+ years of experience in Product Management, Solutions Engineering, or Technical Product Management who has proven experience leading design sessions and discovery workshops with enterprise clients. You should be comfortable owning the room with Fortune 500 stakeholders, translating complex insurance and API workflows into product decisions, and have a track record of driving successful enterprise product adoption. Bonus points if you have experience at a fintech, infrastructure, or API-first company in insurance, automotive, or lending.

Common questions

How do I apply for the Technical Product Manager (US) role at Axle.insure? +

Use the Apply for a referral button on this page to send us your LinkedIn and CV. If your experience fits, we'll introduce you to the recruiter filling this role. They'll email you to check you're interested, then put you forward for this job or others that suit you better. It's free.

What does this Axle.insure role pay? +

The listing gives $160k – $220k/yr.

Is this role remote? +

The listing gives the location as New York, NY. In-person 4 days a week at Axle's Flatiron/NoMad office in NYC, with approximately occasional travel to enterprise client sites.

Product Manager interview prep

Questions Product Manager interviewers often ask. They aren't taken from this listing.

How do you rank competing feature requests when every stakeholder believes theirs is the most urgent one on the list?

I score each request against the outcome the team has committed to for the quarter, then weigh expected impact against the effort engineering estimates. That gives me a defensible order to show stakeholders, and when someone disagrees we argue about the inputs rather than about whose request matters more.

How do you structure a roadmap so it communicates direction without promising dates the team cannot keep?

I organize the roadmap around problems to solve in rough time horizons, now, next and later, instead of a dated list of features. Commitments get firmer as work gets closer, and I state plainly which items are bets and which are committed, so sales and leadership know what they can promise to customers.

How do you plan a round of user interviews so the findings change what you build rather than confirming what you hoped?

I write the riskiest assumption down first and design questions around past behavior, not opinions about a feature idea. Asking people what they did last time the problem came up produces evidence, while asking whether they would use something produces polite agreement that tells me nothing.

How do you combine quantitative usage data with qualitative interview findings when the two seem to disagree?

I treat the numbers as telling me what is happening and the interviews as telling me why, so a disagreement usually means I am measuring the wrong thing or talking to the wrong segment. I go back and check who is in each sample before drawing a conclusion, because resolving that mismatch is often the most useful finding of the whole study.

See all 10 Product Manager interview questions →

Related roles

Axle.insure

Browse all referral roles

Salaried roles at startups, AI companies and established businesses, all filled by referral. One application covers every role.

See all referral roles →