Technical Product Manager

TECHNICAL PRODUCT MANAGER — AI AGENTS / BUILDER

New York City | 5 Days Onsite

$175,000–$275,000 Base + Highly Competitive Equity

WHAT IF YOUR JOB WAS TO BUILD THE COMPANY OF THE FUTURE?

Most product teams build software for customers.

This team is asking a bigger question:

What happens when AI fundamentally changes how an entire company works?

We're partnering with one of the fastest-growing AI-native software companies in New York to add a Technical Product Manager to a tiny, highly autonomous team with an unusually broad mandate: Make every person in the company dramatically more effective through AI.

This isn't a traditional Product Management role. It isn't an "internal tools" job. And it isn't a role where Product writes requirements and waits for Engineering to build them.

This is a role for a software engineer who thinks deeply about product — someone who wants ownership not only of HOW something gets built, but WHAT should exist in the first place.

THE MISSION

The next generation of great companies won't simply use AI.

They'll operate differently because of it.

This team exists to figure out what that actually looks like.

They're already building AI teammates capable of doing real work end-to-end — from engineering and software-development workflows to onboarding, company knowledge, operational processes and entirely new ways of working.

The mandate is intentionally broad.

Find the highest-leverage problem in the company.

Understand it deeply.

Decide what should exist.

Build it.

Put it into people's hands.

Measure whether it actually works.

Then improve it, automate more of it, or kill it and move on.

If you're looking for a perfectly defined roadmap, this probably isn't your job.

If you're energized by a blank page and the opportunity to invent how an AI-native company should operate, keep reading.

THIS ROLE HAS A REAL ENGINEERING BAR

Let's be explicit:

We're looking for someone who has built and shipped production software.

Not simply a Product Manager who works closely with engineers.

Not simply someone who can prototype.

And not someone whose technical background began when AI coding tools arrived.

You should have genuine software engineering fundamentals and be comfortable getting directly into a production codebase.

Claude Code, Codex, Cursor and similar tools should make you a dramatically faster engineer — not turn you into one.

The strongest candidates may have started as Software Engineers and moved toward Product, been Founding Engineers or technical founders, or simply become the engineer on the team who kept asking:

"Are we actually building the right thing?"

WHAT YOU'LL DO

You'll join a small, highly autonomous team operating almost like a startup inside an already fast-growing AI company.

You'll move constantly between product thinking and engineering execution.

You might:

• Find a complicated workflow and determine how agents could own it end-to-end

• Prototype and build AI products yourself

• Work directly in the codebase alongside other exceptional engineers

• Explore how parts of the software-development lifecycle can become increasingly autonomous

• Design systems, APIs, integrations and agent workflows

• Turn messy operational problems into production software

• Use AI coding agents aggressively to increase your own engineering velocity

• Make product and technical tradeoffs without waiting for layers of approval

• Ship quickly, measure what happens, iterate and sometimes throw the whole thing away

• Decide which problems are worth solving rather than execute against an inherited backlog

You'll have unusual freedom to move across the company, find leverage and build.

WHO WE'RE REALLY LOOKING FOR

There isn't one perfect career path.

Some profiles we're especially interested in:

• Software Engineer → Product Manager / Technical PM

• Staff or Senior Software Engineer with exceptional product instincts

• Founding Engineer → Product

• Technical Founder who personally built the product

• Early Engineer who became increasingly responsible for product direction

• Very early PM with substantial prior professional software engineering experience

• Product Engineer or Forward Deployed Engineer who owns both customer problems and implementation

The title matters much less than the evidence.

THE SIGNALS THAT MATTER

You have built real software.

You can read and navigate a production codebase.

You're comfortable reasoning about architecture, APIs, data models, debugging, testing, deployment and technical tradeoffs.

You've shipped—not just demoed.

You have strong product instincts and naturally ask why something should exist before worrying about how to build it.

You've operated with significant ownership, ideally somewhere fast-moving where there wasn't much of a playbook.

You use AI coding tools constantly and have strong opinions about where agents work, where they fail and how they're changing software development.

And you still want to build.

YOUR BACKGROUND MAY INCLUDE

• Roughly 5–15 years across software engineering, technical product, or founding roles

• Meaningful professional software engineering experience

• Production experience with modern software systems

• 0→1 product development

• Highly technical B2B SaaS, AI, developer tools, infrastructure, data platforms or agentic systems

• High-ownership experience at an exceptional engineering organization or fast-growing technology startup

• Founder, founding engineer or very early product experience

• Hands-on use of Claude Code, Codex, Cursor, Devin or similar AI development tools

• Deep familiarity with the software development lifecycle

• Strong communication across engineering, product and business teams

THE PROFILES WE GET EXCITED ABOUT

Former founders.

Future founders.

Founding engineers.

Software engineers who became obsessed with Product.

Product-minded Staff Engineers.

Engineers from exceptional technical organizations who were given unusually high ownership.

People who have built something from nothing.

People already pushing AI coding agents far beyond autocomplete.

People who hear:

"What would it take to automate the software-development lifecycle?"

…and immediately start thinking about how they'd build it.

WHAT PROBABLY WON'T WORK

This probably isn't the right fit if your recent experience has primarily been:

• Roadmap and backlog management

• Coordinating engineering teams without personally engineering the product

• People management rather than hands-on IC building

• Growth optimization on mature products

• Big-company Product with narrow, highly defined ownership

• AI strategy without hands-on development

• No-code/low-code automation

• AI-assisted prototyping without deeper software engineering experience

This team isn't looking for someone to manage the people building the future.

They want another person who can build it.

WHY THIS ONE IS DIFFERENT

You could join another AI company and build another AI feature.

Or you could spend the next several years answering a much bigger question:

What does a company look like when AI agents aren't bolted onto the organization — but become part of how the organization itself operates?

This company is already well funded, growing rapidly and building an AI-native platform in a massive legacy market.

But this particular team gets something unusual:

A tiny team.

Exceptional autonomy.

Serious resources.

Hard engineering problems.

Almost no limits on what it can explore.

And permission to rethink how work gets done from first principles.

If you're an engineer who may eventually start a company yourself — or you've already done it once — this is the kind of environment that's hard to find.

Come help build the operating model everyone else may be copying five years from now.

COMPENSATION

$175,000–$275,000 base salary

Highly competitive equity

LOCATION

New York City

5 days/week onsite