You do two good years of work and remember three things about it. JobOS keeps the record as it happens — then turns it into a resume, tailors it to the role, and tracks where every application went.
The demo is a real account with a journal already in it — no sign-up, nothing to delete afterwards.
Two good years at a company, and when I sat down to write a resume I could recall about three things. Not because nothing happened — because nobody writes down the ordinary week, and the ordinary weeks are where most of the work lives.
Each rewrite started from the last resume rather than from reality. Details rounded off. "Improved performance" replaced the night I found the query doing 1,400 lookups. The document drifted further from what I had actually done.
I once skipped a role I was qualified for because I thought I was short one bullet point. I had shipped that thing twice — just not under that name. I could not see it because I had no record to check against, only memory.
It is keeping the record in the first place, and then generating everything else from it. Write down one true thing a day. When you need a resume, it is already written. That is the whole idea, and everything in JobOS is downstream of it.
The entries that make you better are the ones people forget fastest — and half of them happen nowhere near an employer. So a company is optional on every kind of entry.
Something you built or shipped.
“What did you actually build today, and for whom?”
Something you understand now that you did not before.
“What do you understand now that you did not this morning?”
A problem you are in the middle of.
“What are you stuck on, and what have you already ruled out?”
A technique worth keeping.
“What shortcut or technique do you want to still know in a year?”
It went badly. Write it down before you rationalise it.
“What went wrong, and what would you watch for next time?”
It went well. Resumes are made of these.
“What went well, and how would you prove it to someone?”
Six kinds of entry — what you shipped, what you learned, the wall you hit, the trick worth keeping, what went badly, what went well. A company is optional on every one, because plenty of what makes you better happens on a Sunday.
A structured master resume you edit in the browser and export as an ATS-friendly PDF — built from entries you actually wrote, not from a blank page at 11pm.
Paste a job description and the model reshapes the resume to match it, drawing only on real entries. Where the posting wants something your record cannot support, it tells you instead of inventing it.
Matching roles arrive from public job APIs, ranked against your actual history, each with a tailored resume ready for review — and every application tracked through to its outcome.
Server components mean the database query and the markup live in the same file. Less plumbing to get wrong.
Serverless Postgres that scales to zero. Branching means a migration can be tested on real-shaped data before it touches production.
Better Auth, hosted by Neon, writing into the same database. Identity is a table I can join against, so ownership is a foreign key rather than an API call.
The schema is TypeScript, the migrations are readable SQL, and a wrong column name is a compile error rather than a 2am page.
Layered over my own design system rather than a component library, so the whole product shares one palette and one type scale.
Gemini's free tier does the work; Groq catches the rate limits. Both sit behind one interface, so swapping either is a config change.
The ATS template is JSX, so the on-screen preview and the exported file cannot drift apart.
Push to deploy, and the same edge runtime the Neon driver is built for.
The shell: design language, navigation, placeholder screens, database schema and the seams that later phases plug into.
Log daily work — and everything around it. Six kinds of entry, a company optional on all of them, because plenty of what makes you better happens nowhere near an employer.
A structured master resume you edit in the browser and export as an ATS-friendly PDF.
Paste a job description; the model rewrites your resume to match it — using only real facts drawn from your journal.
Pull matching roles from legitimate public job APIs, rank them, and track every application through a pipeline.
A scheduled agent that finds the day's best matches, tailors a resume for each, and queues them for your review.
Experimental autonomous apply, and the multi-tenant layer that turns JobOS into a product other people can use.
In six months it is a resume. In two years it is the answer to every interview question you would otherwise have to invent on the spot.
Explore the demo account