Don’t send a generic resume — generate a resume and cover letter tailored to this exact role.
DibsList is a small team in San Francisco building a permissioned object graph for physical goods. We're hiring engineers and community-minded humans who want to ship the future of consumer infrastructure.
We’re a tiny, opinionated team. We meet in person three days a week in SF, write everything down in shared docs, and ship to production on Friday afternoons because nothing else keeps you honest like a Friday deploy.
We’re funded by a small group of believer-investors and we’re hiring slowly and on purpose. The next three hires will set the tone for the next ten.
How we work
Decisions live in shared docs. Slack is for ‘heads-up,’ not architecture debates.
If you can demo it on Friday, ship it on Friday. The next iteration is closer than you think.
We treat user data the way we'd want our own treated. The first answer is always ‘don't store it.’
Less code, fewer abstractions, fewer features. Every feature that lives also has to be maintained.
If the docs disagree with the code, the code wins. Then we fix the docs.
Burnout is a debt with compounding interest. We pay it down on purpose.
Own a vertical slice end-to-end: schema → API → web. You'll ship features that thousands of users feel — within days, not quarters.
Own the long tail of receipts. Every new retailer is a puzzle. You'll build the system that solves them automatically — with the LLM only when the deterministic stack runs out.
Be the voice that early adopters meet first. Write, ship, recruit, and obsess over the activation funnel from invitation to inventory-first-loaded.
The package
Top-quartile salary for early-stage SF startups.
Real ownership. Founder-grade vests for the founding cohort.
Unlimited PTO with a 4-week minimum enforced.
Latest M-series MacBook + display + chair. Whatever else you need.
Three days/week in our SF office; Tuesdays are quiet code days.
You'll have meaningful input on hiring, comp, and culture from week one.
Don't see your role?
If you're a designer with brand chops, a privacy engineer, an ops generalist, or someone who's spent a decade in retailer ops and wants to flip teams — we want to hear from you.