← All roles

Founding Product Engineer

Seattle · Full-time

Part product manager, part frontend engineer, part harness builder. You talk to customers, read the data, decide what gets built, and ship it every week — on the harness every Ergoly worker runs in.

A machine with a dish on top catching a stream of speech bubbles, a stack of written pages inside it.

Who we are

Ergoly gives agencies and consultants AI workers that live in their own tools, learn the craft by watching them work, and get deployed into client businesses under the agency's own name. The product is live, and agencies are running real client work through it today.

We are pre-seed, and it is early. The product works and customers depend on it, but most of what it will become is still a line on a roadmap. Which of those lines get built first — and which never do — is the job.

Everyone here works with a team of AI workers of their own, and most of us run many agent sessions at once. Nothing is someone else's department, and what you build reaches real agencies and their clients within days.

The role

Two workstreams, running in parallel from the start.

The product

You decide what gets built next, from what customers tell you and what the usage says. Agree the outcome, timebox it to a week, and ship it — spec, harness, interface. It is done when customers use it every week, not when it merges.

The factory

The factory, on the product layer. Your own orchestrator is how you work on day one. The job is turning it into an entire machine: one that takes what customers say and do, shapes it into a week of work, ships it through AI workers, and measures the usage on the way out.

Where you sit

Between the customers and the platform.

You care about how much customers use the product — not how many sign up.

GTM

Turns the market into trials

Customer

Turns trials into activated customers

Product · you

Turns activated customers into more value and usage

Platform

Keeps it secure, reliable, performant and compliant

The actual problem

Shipping a feature is not the goal. Customers using it is.

We can build far more than customers will use. Your job is picking what they will, and proving it.

A feature nobody uses is a cost, not an accomplishment.

What the first month looks like

A small, finished week first. Then a feature every week.

The work trial is small on purpose and stays inside Ergoly: one person on our team who uses the product every day, or one known product problem we hand you. Nothing to wait on and no one else's work in the way, so you can get all the way to the end.

After that, a feature ships every week. On Monday we agree the outcome and give it a week — no more. By Friday it ships. The bets get bigger as the small ones land.

Week 1

The work trial

The product

  • One person inside Ergoly who uses the product daily — or one known product problem we hand you
  • The outcome agreed on day one, and sized to fit the week
  • Shipped to production in our own workspace, with nothing and no one to wait on
  • Usage measured, and shown to us on Friday: did it get used, and how do you know?

The factory

  • Your own orchestrator running on our systems, shipping the trial's work

Week 2

The product

  • First customer-facing feature shipped: outcome agreed, timeboxed to the week
  • Its usage measured per client

The factory

Being built: your orchestrator, turning into a machine.

Week 3

The product

  • Second feature shipped, a bit bigger, built with Platform
  • Week 2's feature kept, changed or pulled, based on usage

The factory

  • Customer requests and usage feed straight into what the factory builds next
  • Specs your AI workers build from, without you

Week 4

The product

  • Third feature shipped
  • Next features agreed with the team, including the first one longer than a week

The factory

  • A feature goes through the factory from request to shipped, without you building it by hand

The outcome

Features ship every week, and customers use them — measured, not assumed.

What is in it for you

  • Own the product from day one — what gets built, in what order, and whether it worked.
  • Pre-seed equity, while the product is live but most of the roadmap is not built yet.
  • A flat team of adults. No product layer, no ticket queue — you work directly with the people building and using it.
  • Every tool you want, and the budget to run as many agents as the work needs.

The numbers

Work trial
One week, paid, full-time
After the trial
Competitive full-time comp + pre-seed equity
Location
Seattle
Reports to
Dan, cofounder

We start with a paid, full-time work trial — one week, full system access, real work from day one. It is the same job on both sides of it.

How to apply

Three questions.

No cover letter, no take-home, no six rounds. Answer these three and we will read them ourselves.

You can also apply from a terminal: ssh apply@join.ergoly.ai asks the same questions and reaches the same two people.

Do you live in Seattle, or would you relocate?

The role is in Seattle. Answering "neither" does not end the conversation — we would rather know now.

Are you legally authorized to work in the United States?
Will you now or in the future require sponsorship for employment visa status (for example, H-1B)?

A few paragraphs. Include the numbers.

Disagreeing well is the point of this question.