What exactly do I do?
Three steps. Sign in with Google. Write one honest line about today’s work — two minutes, from your phone. Repeat daily. That’s the entire practice; there is no application form.
Do I need a resume?
No. Companies hiring here read your log instead — how you think, not what you claim. Your record is the interview.
I just graduated — how does a Proof log help me get hired, and who reads it?
Not recruiters or an ATS —
founders and engineering leaders read the logs directly, so you skip the resume-keyword filter entirely. They don’t read for what you shipped; they read for how you think: where you got stuck and how you got unstuck, a mistake and what it taught you, the why behind a decision, where you changed your mind. Ten honest days of that makes you readable — and they reach out. You don’t chase.
What readers look for →Why write here instead of LinkedIn or X?
Because it’s private by default. Nothing you write is public until you choose to open your URL at day 30 — no feed, no comments, no one to troll your thinking or perform for. A log is where you can write “I bombed this” honestly; social media is where you can’t. The only readers are founders and engineering leaders, when they’re hiring.
Is the point discipline — or building a following / community?
Neither. It’s not a streak tracker, and it’s not build-in-public. Build-in-public is performance — writing for an audience and claps. Proof is private: you write what you actually worked through — the stuck, the wrong calls, the why behind a decision — with no feed and no likes. The outcome is that your writing becomes proof of how you think; founders and engineering leaders read it async and reach out when they’re hiring. You stop applying; the work comes to you. And daily isn’t a rule — there are no streaks. You log when you’ve worked through something worth keeping.
Is it worth maintaining a log even before I'm hired?
Yes — the practice pays you first, the hiring is the second-order effect. Maintaining a daily log makes you interview better(you’ll have written your “when I got stuck” answers ten times), think and decide more clearly (writing the whyforces it — tradeoffs and system design get easier), get more from AI (clear thinking writes clear prompts), and build a dated record of your reasoning that’s yours forever. After 30 days you can open a live public URL of your WHY entries — opt-in, shown on your terms. That’s why it’s safe to just start.
If many people log for 10 days, how do they choose? Does a human really read?
Yes — a human reads every one. Ten days of daily writing is a hard filter (most signups never cross it), so the pool stays small. And each log is structured, so ten days reads in minutes. AI screening resumes is the disease — we don’t cure it by AI-screening logs.
What is a WHY and how do I earn one?
The WHY is the becausein your entry. DECIDED, LEARNED and CHANGED MIND ask for it directly; on BUILT it’s the second line — what you skipped and why. Each entry with a because counts once, and several entries a day all count. The role card shows your exact targets.
What does the second line on BUILT mean?
The thing you skipped or postponed today — not what you built. “I didn’t build the browser extension because the site version came first.” Tradeoffs are reasoning; readers value them as much as the build itself.
How does this replace traditional hiring?
It doesn’t replace it — it changes what gets read first. Traditional hiring starts from a résumé: a claim about your past. Proof gives founders your daily log — how you actually think, what you got stuck on, what you decided. They read it async, on their own time, and reach out when the thinking fits a role. So instead of you applying into a stack of open tabs, the opportunity finds you. The interview still happens; this is what gets you to it. And the practice changes you: putting the whyinto words every day makes you sharper at articulating how you think — that’s yours to keep, job or no job.
What happens after I log for 10 days?
Ten days of writing (inside a 20-day window) crosses the consistency filter and you enter the pool founders read — but anonymized. They see that you showed up: your consistency, your why-count, the decisions you reasoned through, under a #ZME tag. Not your name, and not your raw logs. Your identity opens at Day 30, and only if you choose to go public. So ten days makes your disciplinevisible — not your private writing. You’re not promised a job; you’re promised a reader.
Will logging 10 days get me the job?
Honest answer: it gets you read. Founders read the pool and reach out to the thinking they want on their team. Nobody can promise selection — anyone who does is selling something.
Is this only for the role that's open right now?
No. 42 founders and leaders read this pool, and the opportunity that finds you may not be the one that was announced. Roles come and go; your record compounds.
Who can see my log?
Founders and leaders on the platform read entries; your private notes to RK are never visible to anyone but RK. A campaign mentor or pair partner can read your log only if you explicitly say yes — and you can withdraw anytime. Nobody can ever edit your words but you.
I'm building my own project. Does writing about it — technical parts + learnings — count?
Yes — in fact it’s a good one to document. Every decision in it is yours. One suggestion: don’t stop at technical + learnings. Add the because. “Chose X over Y because…”, “skipped tests today because…” That’s far more valuable for you to internalize — you will never forget it — and for the hiring manager to understand how you handle tradeoffs.
Is this some kind of ChatGPT or LLM app? Everyone types into it.
No. You type into ChatGPT to get the machine’s words. You type into Proof to put your words on record — dated, locked the next morning, never rewritten by anyone. One is a generator; this is a ledger. No model answers you, no model edits you, and humans — not AI — read what you wrote.
Isn't this just gaming interviews — writing what founders want to hear?
The opposite, really. A résumé is written for an audience; a log is written beforeyou know who’s reading, and each entry locks the next morning — you can’t rewrite history to fit a role. To “game” it you’d have to fake real reasoning, dated, for weeks, which is just buildingthe reasoning. In the interview it works against gaming: “you wrote this on Day 12 — walk me through it” catches a fabricator in minutes. And the strongest signal is honesty about being stuck — you can’t perform your way to looking coachable by hiding the struggle, because the struggle is the point.
I hire mechanical / electronics / robotics — is Proof only for software engineers?
No. Proof reads how someone thinks— what they got stuck on, what they traded off, what they decided and why. That signal is the same whether the build is firmware, a circuit, or a mechanism; anyone who builds can articulate their reasoning, and people who’ve shipped physical things often show it most clearly. Honest part: most who’ve logged so far come from software, so a hardware pool is thinner today — tell RK the disciplines you want and the next onboarding wave points at them.
I sent a few people to Proof. Can I follow their progress and mentor them?
Yes — ask RK for a mentor link and share it. Whoever signs up through it appears in your book: name, days logged, how recent. Reading the words insidesomeone’s log takes that person’s explicit yes — they’re asked once, in the app, and can change their mind anytime. Sharing is adding; consent is reading.
How do I see who applied to my role?
/f2/roles— your role card shows the count, and “View interest” expands the list; each row opens that engineer’s full log. You also get an email the moment someone raises their hand.
How do I post a role?
Same page —
/f2/roles, two minutes. You set the bar (days logged, WHYs, consistency); engineers see exactly that bar on the role card.
When do candidates show up?
Interest arrives as engineers cross your bar — a 10-day bar means the first cohort matures about ten days after your role goes loud. You don’t have to wait: the pool’s deepest current logs are readable from day one.