Cubbie Conference December 10, 2026 in San Francisco Get tickets →

All open roles

Chief Technology Officer

Full-timeSan FranciscoTwo-year tour

Everything Cubbie runs on: what gets built, what gets turned off, and how fast a decision becomes something a user can touch.

Cubbie publishes 24,819 software products and runs a marketplace on top of them. One codebase does all of it, and you own that codebase.

This is a hands-on job before it is a management one. You read the schema, write the migration, and ship the change yourself. Whoever you hire will be hired against work you have already done and to a standard you have already set in the code, which is the only way that standard survives.

You decide what gets built next and what gets turned off. Both halves count. A platform that only ever grows becomes a platform nobody can change, and the second decision is the one that keeps the first one cheap.

You also set where the line sits between what a person signs off and what the product does on its own. Everything Cubbie puts in front of a buyer or a vendor is read as fact by somebody about to spend money, so that line is what the platform's credibility rests on. It is yours to set and yours to hold.

The tour

This role runs as a two-year tour. That is the term on both sides. Near the end of it we sit down together and decide whether to run another one.

You will know in your first week what the tour is for: what you own, what has to be true by the end of it, and how that is measured.

By day ninety

An architecture you can put on one page and defend, with the parts of the system that do not fit it named and scheduled to go.

A path from a change to production that a person can walk in a day, and the tests and checks that make walking it safe.

Everything running in production owned by a named person, instrumented, and alerting when it stops. Nothing running that nobody is watching.

A written standard for what may reach a buyer or a vendor without a person signing it off, and the product held to it.

And the first engineering hire made, or the case made in writing that the next hire belongs somewhere else.

Build your package

This role is $800,000 a year, and you decide how much of it arrives as salary, as a bonus, or as ownership. Pick a starting shape, then move the sliders until it looks like the offer you want. What you build here goes to us with your application. Nothing here is an offer.

Starting shape

2.000% of Cubbie, vesting over two years

The package

Base salary$400,000

Performance bonusNone

Equity, granted once$400,000

Package, per year$800,000

Your stake

Share of Cubbie2.000%

Worth today$400,000

At $100,000,000$2,000,000

At $250,000,000$5,000,000

The trade

Pay given up, over two years$800,000

Worth it above$40,000,000

You give up $800,000 of pay over two years for a stake worth $400,000 today. It pays off if Cubbie is worth more than $40,000,000, against $20,000,000 now.

Apply

One page. Five questions, a short block on how you work, and a link to something you built or grew. There is no resume to attach and nothing to upload.

A page, a repository, a product, a post, an account.

Hyper-compatible fit

How you would actually work. Short answers are fine.

How much of your working week would Cubbie have?
How far would you move for this?
This role runs as a two-year tour. Where do you land on that?