Work on softwarethat never guesses.
overads puts five marketing tools in one login and prints a labelled blank wherever a number would be a guess. We are a small remote team. We hire slowly, and we read every note.
The three roles below are pipeline, not open yet. Early notes still count: they are how the short list forms.
Where we’re looking next
- Write to usEngineeringFull-time · Remote · ±5h ISTPipeline
Founding product engineer (full-stack)
Next.js + TypeScript on the front, Postgres + Drizzle + Lambdas behind. You will own a platform connector end-to-end and pair on the AI loop. We want depth over breadth.
- Write to usDesignFull-time · Remote · ±5h ISTPipeline
Founding designer (product + brand)
You set the visual system, write the copy on the buttons, and ship dashboards that look like nobody else's. Comfort in Figma and a code editor at the same time.
- Write to usGrowthContract · Remote · NY / SF / BLRPipeline
Growth, in residence
Run our own paid media on overads, write the field notes that come out the other side, and tell us where the product is wrong. Six months, with option to convert.
None of these are open today, and we keep a short list anyway. Write to hello@overads.io and tell us what you would build here: which surface you would take over, what you would fix first, and one thing you have shipped that we can look at. A human reads every note and replies within a business day.
The rules are the culture
The product refuses to invent numbers, and the team is run the same way. Here is the day-to-day, without the brochure gloss.
The house rule
Blanks, never guesses
If an ad platform does not publish a number, the product prints a labelled blank instead of an estimate. The same rule governs the docs, the marketing site, and this page.
Boring to write. Very calm to maintain.
Design here
Measured
The darkening over this page's own hero was measured against the photograph at two screen sizes before it shipped. Taste first, then arithmetic to prove it.
Ownership
One surface, end to end
You will not be tenth on a feature team. You take one surface and it is yours for at least a quarter.
Async-first
Decisions land in prose
The bar for a meeting is high and the bar for a thoughtful doc is normal. Writing is most of the job, whichever role you are in.
Everyone takes a turn in the support inbox. No exceptions.
The stack
Boring where it must not break
TypeScript end to end: a Next.js app, Postgres behind it, and small nightly jobs that read each ad platform. Customers' ad accounts are read-only, their logins are encrypted, and every workspace is walled off from the others.
Read-only by design
The app can see a customer's campaigns but never pause, edit or touch them.
Encrypted logins
Platform tokens are encrypted at rest and never written to a log.
One connector per platform
Each platform's quirks stay inside its own folder, behind one shared interface.
Before you write
Anything else? Email hello@overads.io and a human will reply within a business day.


