Product Manager

The company is an AI implementation consultancy and product studio. We help organizations move from AI experimentation to measurable return on investment across four practices: AI Strategy and Advisory, Workforce Training and Enablement, Process Optimization, and Custom AI Development. Our work sits with executives and the people who do the work, and it is judged on whether something changed in production, not on whether a pilot looked good in a deck.

Position Overview

The company is hiring a remote Product Manager to own products in the company'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.

You will work with a US-based team and US clients. Most of your users, stakeholders, and engineers sit in New York, so this role is built around daily overlap with US Eastern hours, not asynchronous handoffs.

Compensation: Competitive, benchmarked to senior product roles in your market, plus a performance bonus tied to product outcomes. We will share a specific number for your location early in the process.

How we expect you to work

AI use is a core execution requirement at the company, 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.

Remote works here when the writing is strong. Decisions, specs, and priority calls get written down where the team can read them, not held in your head until the next call.

What you will do

• Talk to users and customers every week. Not a quarterly survey. Real conversations, real usage, on US time.

• 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.

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 written and spoken English: specs and decisions other people can act on without a follow-up meeting, and customer calls you can run without a translator.

• 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.

• Available for at least 7 to 8 hours of daily overlap with US Eastern time (9am to 6pm ET), consistently.

• Reliable internet, a quiet place to take customer calls, and your own laptop.

• Legally able to work as an independent contractor or through an employer of record in your country.

• A bachelor's degree is preferred and is not a requirement.

Nice to have

• Prior experience working remotely with a US or UK team.

• 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.

Benefits

Competitive benefits.