One arm on the desktop app, one on the cloud, one in the database, one teaching the AI, and four left over for the CSS. You work on all of it, at once, and enjoy it a little too much.
You will
- Ship SnoutData Studio, a desktop SQL IDE, to Windows, macOS and Linux, sometimes on the same afternoon
- Run and grow SnoutData Cloud: hosted Postgres that pauses when idle and wakes before anybody notices
- Write a Postgres extension in Rust, then write the benchmark that proves it, then write the report about the benchmark
- Teach an AI assistant to read a schema without ever being handed a password
- Fix the CSS. There is always more CSS.
You are probably
- Fluent in TypeScript, comfortable in Rust, and on speaking terms with SQL that is longer than your arm
- Someone who reads the query plan before blaming the database
- Happy to own a thing from the first commit to the 3 a.m. pager, and to write the runbook so there is no second 3 a.m.
- Convinced that tabs are correct. This one is not negotiable.
A typical week
- Monday: an Electron release goes out to three operating systems
- Tuesday: you move a live database to another machine and nobody notices, which is the point
- Wednesday: Rust, pgrx and a benchmark that runs all night
- Thursday: you argue with a design token and lose
- Friday: it was DNS. It is always DNS.
Bonus points: You have opinions about connection pooling and you can keep them to under ten minutes.
Apply as the octopusWe have the product, the benchmarks and the research reports. What we do not have is someone who can turn all of that into a round. Our runway is currently measured in espresso shots.
You will
- Build and run our investor pipeline, from the first warm intro to the signed term sheet
- Turn our research reports and benchmark numbers into a deck that reads like a thriller, with the plot twist on slide 7
- Find grants, programs and strategic partners we did not know existed
- Keep the data room tidier than our migrations folder (the bar is high)
- Tell us, kindly, which of our ideas an investor will laugh at
You are probably
- Someone who has raised money before, or helped a founder raise it, and remembers how
- Able to say "pre-money valuation" with a straight face and explain it without one
- Comfortable with spreadsheets that have more tabs than our browser
- Curious enough about databases to tell a time series from a TV series
A typical week
- Monday: twelve intros, eleven follow-ups, one very promising coffee
- Tuesday: the deck, version 41, final_FINAL_v2
- Wednesday: a partner meeting where you translate "index scan" into "moat"
- Thursday: the data room, the cap table, the coffee
- Friday: you send the update email investors actually open
Bonus points: Your phone has a contact saved as "VC (the nice one)".
Apply to whisperDatabases are the most important thing nobody posts about. You will change that. Make Postgres go viral. Yes, really. We believe in you more than we believe in our own jokes.
You will
- Run SnoutData on LinkedIn and X, and pick the next place where developers hang out before they get there
- Turn a nine-page benchmark report into a nine-second clip people share
- Grow a community of people who say "snout" out loud, on purpose
- Answer every "why not just use a spreadsheet?" with grace, and a chart
- Work with us on launches, release posts and the occasional very serious meme
You are probably
- Someone who knows the difference between a post and a thread, and when a thread should have been a post
- Able to explain what a database does to your aunt, in one post, with no jargon
- A writer first: short, funny, honest, never cringe
- Comfortable with a screen recorder, a video editor and a deadline
A typical week
- Monday: plan the week, then throw away the plan because a release dropped
- Tuesday: film the new feature, cut it to 15 seconds, cut it to 9
- Wednesday: reply to every comment, including the one about tabs
- Thursday: write a post so good the engineers stop coding to like it
- Friday: read the numbers, keep what worked, retire what did not
Bonus points: You once made something go viral and you can tell us why it worked, not just that it did.
Apply to memeHow hiring works
We ran the hiring process through the planner. It came back cheap.
EXPLAIN ANALYZE hire(you);
Result: an offer
-> Hash Join: a small real problem, worked on together
-> Nested Loop: a call with the founders
-> Seq Scan on your_email (filter: tells us why you, and one thing you built, raised or posted)
Planning time: one email. Execution time: about two weeks.