Founding Product Engineer

Ergoly Inc; Seattle (WA); On-site; USD 120,000 - 160,000; Full time

Benefits offered by this job

Pre‑seed equity

Job summary

Ergoly Inc is building AI teammates that live in agencies’ tools and client businesses. You will own the product from day one, deciding what to build, how to ship, and how to measure success, with a weekly cadence. You’ll work closely with customers and engineers to turn feedback into value while leveraging an equity-backed, early-stage team environment.

Seattle-based, full-time, paid trial included. Join a flat team with direct access to the builders and users, and get the tools you need to run

Qualifications

• Experience shipping features weekly.
• Ability to translate customer feedback into product decisions.
• Comfort working across product and engineering to deliver end-to-end solutions.

Responsibilities

• Own the product from day one: decide what to build, in what order, and validate outcomes.
• Define scope and timebox work to a weekly cadence, shipping features with its harness and interface.
• Collaborate directly with customers and the internal platform teams to ensure relevance and reliability.
• Ship a new feature every week and measure usage to guide the next steps.

Skills

Product management

Frontend engineering

Customer interviews

Job description

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 AI teammate runs in.

Who we are

Ergoly gives agencies and consultants AI teammates 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 teammates 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 teammates, 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

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.

The product

The factory

Week 1

• 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?
• Your own orchestrator running on our systems, shipping the trial's work

Week 2

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

Week 3

• Second feature shipped, a bit bigger, built with Platform
• Week 2's feature kept, changed or pulled, based on usage
• Customer requests and usage feed straight into what the factory builds next
• Specs your AI teammates build from, without you

Week 4

• Third feature shipped
• Next features agreed with the team, including the first one longer than a week
• 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.