Careers at Selfhost.dev

For people who cannot leave rough edges alone.

We are building the place where developers deploy apps, run managed databases and operate infrastructure from one calm control plane. If you like turning vague friction into sharp, shipped work, you will recognize yourself here.

Selfhost.dev product dashboard showing infrastructure metrics
incoming signal

Someone got stuck. The page, product or process gets clearer by tomorrow.

ship log research -> test -> release -> learn
selfhostreview session replay
growthmap high-intent thread
qawrite repro before release
salesturn field notes into product input
04

open roles

Remote

every listed role

Flutter / Ruby / Go

plus PostgreSQL and AWS

Real product

customers, signals, releases

The invitation

Come help make infrastructure feel less like a tax.

Selfhost.dev is a managed-database and app-deployment platform for teams that want the control of infrastructure without the ceremony of running every piece by hand.

We ship the product, the website, the QA discipline, the research habit and the customer conversations as one system. That is why the roles below do not sit in separate boxes. They all touch the same question: what would make this easier, clearer and more trustworthy?

The work surface

You will not be working on abstractions.

The page, console, demos, docs, calls, bug reports and session recordings all feed each other. The work is tangible enough to inspect and small enough to change.

Selfhost.dev projects demo interface
Projects Apps, backend services and managed servers moving from GitHub to production.
Selfhost.dev databases demo interface
Databases Managed database flows where reliability and clarity matter at the same time.

Culture, as receipts

A day here is a string of useful observations.

We do not need everyone to be loud. We need people who notice, write clearly and move the work one step closer to something customers can trust.

09:12 Behavior

A visitor hesitates on pricing.

Analytics turns the pause into a concrete experiment, not a vague opinion.

11:04 Community

A thread asks why deploying databases still feels ritualistic.

Research captures the language, the alternatives and the right moment to be useful.

14:30 Quality

A release looks fine until one stateful edge case says otherwise.

QA writes the repro, engineers fix it and the customer never has to learn the bug existed.

17:48 Field

A sales call exposes a sharper product sentence.

The insight goes back into the website, demo flow and roadmap instead of dying in a CRM note.

How we work

The operating system is simple.

Fewer layers. Better context. High standards for the invisible details. Enough autonomy that your judgment has somewhere to go.

01

Remote, but not vague.

Decisions are written, context is preserved and useful updates beat performative meetings.

02

Small team means real surface area.

A good observation can change a page, a product flow, a test plan or the next customer conversation.

03

Taste is part of the job.

Infrastructure should be reliable, but also legible. We care about the sentence, the edge case and the last click.

04

Intern work is not theater.

You will work around real product behavior, real conversations, real QA signals and real customer context.

Last thing

Bring us a sharp observation.

About the product. About the market. About a broken flow. About an edge case everyone else missed. The best applications usually start there.