Question 1

I couldn't tell what this site is for. Is it a place to ask questions and get answers?

Accepted Answer

No — it’s a record of real work , written by the person who did it. Engineers write one honest line about what they actually did today — the decision, the thing that broke, the why — on the day it happened. Founders read those logs when they’re hiring. The questions you saw are prompts that help someone start writing; they are not the product. What Proof is, in one page → Or read real logs → You were reading a feed, not a Q&A

Question 2

What is this Proof? Give me more details.

Accepted Answer

A private daily log — founders read it when hiring. One honest line about today’s work — the decision, the stuck, the why . Two minutes, from your phone. AI writes code now, so a résumé proves less every month; dated reasoning in your voice is the signal that’s left. Nothing goes public unless you choose. See real logs → Gets you read · never selection

Question 3

i am upload the a projecct, what is a status on it, can you explian that

Accepted Answer

Open the project page you submitted on — everything about your submission lives there . Three things sit on that page. The check — we open your hosted link and read your repo, and say what we found (a link that doesn’t answer, a secrets file, one commit). Fix anything and press re-check. The founder’s note , if they’ve written one — their words, and you can reply to it right there. Nothing else means nothing yet : no note means they haven’t written one, not that you were turned down. From now on a note also reaches you by email and in your bell, so you don’t have to keep checking. The founder reads the working thing first · host it

Question 4

By the way…you said you will be sharing me a assement link. Can u share that

Accepted Answer

It’s at /assessment — five rungs, you pick where you stand. It takes about a minute and it is not a test you pass. PICK Where you are today . Student · Code Monkey · Code Junkie · Product Engineer · Zero Maintenance Engineer PICK Where you want to be next . PICK How many days you are giving yourself. Nobody grades this and Proof never rates you — your own read is the record, and the page shows you what your own writing already contains so you can rate yourself from evidence rather than mood. When the days you picked run out, you get asked again; the only question is whether you moved. If you have never shipped anything for anyone yet, Student is the honest answer and it costs you nothing to say so.

Question 5

What does “a why” mean? Do I need to tag something for it to count?

Accepted Answer

A “why” just means you wrote the reasoning — why you did it, not only what you did. No tag, no button. “I fixed the deploy” is a what . “I fixed the deploy — it was an env var set on my laptop but missing in prod” has the why . That second half is what a founder can’t fake and can’t get from a résumé, so a log with the why is the one that counts toward being read. It’s the same why you type into your log — nothing to tag. Not sure how to add it? The guided composer literally asks you “Why this?” as a step.

Question 6

When someone reacts to my log, where do I see all the reactions and comments together?

Accepted Answer

Open the log — “What happened” lists them all, by name. Every reaction and every comment on that log — curious, respect, sharpen, asks, and replies — in one stream, in order, no counts. Tap any notification and it takes you to the whole conversation, not just the single reaction.

Question 7

Someone on X put it bluntly: “being good at interviews will bag you better offers than being good at your job.” Isn’t that just true?

Accepted Answer

Today, often — yes. And that’s the bug , not a strategy. An interview rewards interview-skill, which is a separate thing from doing the job — so the people who rehearse well win offers over the people who do the work. That’s a reason the signal is broken , not a reason to get better at rehearsing. Proof is the bet on the other side: a dated record of the decisions you made and why , so someone reads how you actually think before the room. Honest scope: it gets you read , not the offer — the offer’s still theirs to make. But getting read for how you work beats getting rehearsed for 45 minutes. See real logs → Gets you read · never the offer

Question 8

Is this a direct job portal or a talent showcase platform?

Accepted Answer

job portal showcase your work record You write what you worked through; founders read how you think , async. Open roles exist ( /next/roles ) — but the record is the mechanic, not the application.

Question 9

Is there a deadline for the bounty, or is it still active? Also, would an analysis using MobSF or Burp Suite be useful for this?

Accepted Answer

Still active, and there is no deadline. The security audit at /work/security-audit is a standing offer — ₹1,000 for verified findings you can show how to reproduce, paid whether or not each one gets acted on. It stays open until that page says otherwise. MobSF Burp or ZAP Proof is a web app, and there is no shipped mobile build — so an APK/IPA scanner has nothing to scan. An intercepting proxy, the request tab, and two accounts of your own are what find things here. Auth, access between accounts, and what one account can reach of another’s is where the real holes have been.

Question 10

What exactly do I do?

Accepted Answer

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

Question 11

Do I need a resume?

Accepted Answer

No. Your log is the interview. Companies hiring here read how you think — not what you claim.

Question 12

Why does “high agency” matter so much for getting placed?

Accepted Answer

It’s the first thing readers look for — and it can only be shown . Skills can be taught in a quarter; what you do when nobody assigns the next step is the rare thing. “Tell me about a time you showed ownership” is rehearsed by everyone; a dated decision with its because can’t be backfilled . Your log is the gym and the evidence — it gets you read closely; nobody can promise selection.

Question 13

I just graduated — how does a Proof log help me get hired, and who reads it?

Accepted Answer

recruiters an ATS founders + leaders, directly They read for how you think: where you got stuck and how you got unstuck, a mistake and its lesson, the why behind a decision. Ten honest days makes you readable — they reach out; you don’t chase . What readers look for →

Question 14

Why write here instead of LinkedIn or X?

Accepted Answer

There are things you can’t write there. Write them here. “I bombed this” · “I was wrong” · “I’m stuck”. Proof is private by default — no feed, no comments, nothing public until you open your URL at Day 30. The only readers are founders and engineering leaders, and honesty about being stuck is exactly what they read for.

Question 15

What's Proof for — discipline? Consistency? Community building, or build-in-public?

Accepted Answer

streaks build-in-public networking learning Learn here, network elsewhere. You write what you actually worked through, privately — writing the why daily is what sharpens the thinking, and the record it leaves is proof of how you think. Once you’ve learned here you can bring others — a mentor link, your own readers. No streaks; you log when you’ve worked through something worth keeping.

Question 16

Is the point discipline — or building a following / community?

Accepted Answer

a streak tracker build-in-public proof of how you think Build-in-public is performance — an audience and claps. Proof is private: the stuck, the wrong calls, the why. Founders read it async and reach out when hiring — you stop applying; the work comes to you .

Question 17

Is it worth maintaining a log even before I'm hired?

Accepted Answer

Yes — the practice pays you first. Hiring is the second-order effect. You interview better (your “when I got stuck” answers are already written), decide more clearly (the why forces it), write clearer prompts, and bank a dated record that’s yours forever. Day 30 opens an optional public URL — on your terms.

Question 18

If many people log for 10 days, how do they choose? Does a human really read?

Accepted Answer

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; structured logs read in minutes. AI screening résumés is the disease — we don’t cure it by AI-screening logs .

Question 19

Who is RK? And can one person really read everyone?

Accepted Answer

Radhakrishnan — he built Proof and reads every engineer who writes here. He curates /sample and writes back on your entry when you ask him a question. On scale, honestly: the ten-day filter does most of the work, and founders read the pool directly too. If one reader ever isn’t enough, the answer is more human readers — not an AI screen. Who is RK? →

Question 20

What was your strategy when you launched — and what is it now, for growing and retaining users?

Accepted Answer

Honestly: there was no launch. RK taught programming for 15 years — the last 8 teaching Indian engineers how to learn — and Proof is that offline practice turned into a system. No Product Hunt, no paid acquisition; people arrive through the teaching, the book, and each other. Retention isn’t engineered either — no streaks, no badges, on purpose: the practice pays you first.

Question 21

What is a WHY and how do I earn one?

Accepted Answer

The WHY is the because in your entry. DECIDED, LEARNED and CHANGED MIND ask for it directly; on BUILT it’s the second line — what you skipped and why. Every entry with a because counts, several a day all count; the role card shows your exact targets.

Question 22

What does the second line on BUILT mean?

Accepted Answer

The thing you skipped 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.

Question 23

How does this replace traditional hiring?

Accepted Answer

a résumé — a claim your log — a record It changes what gets read first , not the interview itself. Founders read your daily log async and reach out when the thinking fits a role — instead of you applying into a stack of open tabs. And writing the why daily makes you sharper at articulating how you think; that’s yours to keep, job or no job.

Question 24

What if I start from today? Am I too late for the open role?

Accepted Answer

Start today — the clock starts when you do. The pool counts your days inside your own rolling 20-day window; if your ten honest days land while the role is open, you’re in. If it closes first, nothing is wasted — you’ve banked WHYs and a dated record every future role reads the same way. Write Day 1 →

Question 25

What happens after I log for 10 days?

Accepted Answer

The filter 10 days inside 20 most signups never cross it The pool Founders see your consistency — anonymized, #ZME tag not your name, not your raw logs Your name opens at Day 30 — only if you choose A reader, not a job

Question 26

Will logging 10 days get me the job?

Accepted Answer

It gets you read . Founders read the pool and reach out to the thinking they want. Nobody can promise selection — anyone who does is selling something. Gets you read · never selection

Question 27

Is this only for the role that's open right now?

Accepted Answer

No — roles come and go. Your record compounds. 48 founders and leaders read this pool; the opportunity that finds you may not be the one that was announced.

Question 28

How long until a founder shows interest in me?

Accepted Answer

No typical timeline — and nobody here will invent one. Founders read async, when they’re hiring; interest arrives when your thinking meets a real opening. What’s promised is narrower and real: cross the 10-day filter and you get read . Anyone promising you a date is selling something.

Question 29

If I get a job through Proof — is it work-from-home? Is the office in Bangalore?

Accepted Answer

Proof isn’t the employer — it has no office you’d join. Every role belongs to a specific company; office, remote, and city are that company’s call — on the role card, settled directly with the founder once they reach out. No recruiter sits in between.

Question 30

Who can see my log?

Accepted Answer

Founders + leaders read entries on the platform Only RK your private notes — never your team or founder Your yes first mentors + pair partners — withdrawable anytime Nobody can ever edit your words but you.

Question 31

I'm building my own project. Does writing about it — technical parts + learnings — count?

Accepted Answer

Yes — and add the because . Every decision in your own project is yours. “Chose X over Y because…”, “skipped tests today because…” — that’s what you internalize forever, and what a hiring manager reads for tradeoffs.

Question 32

Is this some kind of ChatGPT or LLM app? Everyone types into it.

Accepted Answer

a generator a ledger 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. No model answers you, no model edits you; humans read what you wrote.

Question 33

Isn't this just gaming interviews — writing what founders want to hear?

Accepted Answer

The opposite — entries lock. You can’t rewrite history to fit a role. A log is written before you know who’s reading. To game it you’d have to fake real reasoning, dated, for weeks — which is just building the reasoning. And in the interview, “you wrote this on Day 12 — walk me through it” catches a fabricator in minutes. The strongest signal is honesty about being stuck; the struggle is the point.

Question 34

Can I edit a log after I post it?

Accepted Answer

Yes — until it seals at 9:42 AM the next morning . Open it from the confirmation screen or your record: change the wording, fix a typo, add a link. After it seals it’s locked word for word and dated — so nobody (including you) can rewrite history to fit a role later. Write honestly today; you have until morning to tidy it.

Question 35

I already write about my deploys on my own blog. Can I bring that here, or do I retype it?

Accepted Answer

Bring it — don’t retype it. Write one thing you learned as a stuck or decided entry in your own words, then attach the article with + attach a link . The log is the reasoning — what you got stuck on, what you chose and why; the blog is the evidence a reader can open. Your post stays yours, wherever it lives.

Question 36

There&rsquo;s no sign-in just to log — so how does anyone get hired through this?

Accepted Answer

Two different doors. Logging is open; the hiring side signs in. Logging is deliberately low-friction so you can write the moment something happens. Founders and leaders do sign in — they log in to read the work and reach out. You don’t apply to them; you keep a record, they read it async, and when your thinking fits what they’re hiring for they come to you. The login that matters for hiring is theirs, not a wall in front of yours.

Question 37

I'm already a strong, experienced engineer — and still can't find a job. What does Proof change?

Accepted Answer

Proof can’t fix a brutal market — it fixes who gets to see how you actually think. If you’re strong and still stuck, the leak is usually the channel, not you. Applications filter on keywords and titles; the thing that’s actually scarce now — judgment, the calls you made and why — never reaches a human before an ATS or a recruiter screens you out. Proof inverts that: founders and leaders read your dated reasoning async and reach out, with no application in the way. It won’t manufacture a role, and anyone who promises you one is selling something — but it puts the part of you a résumé can’t carry in front of people who hire on exactly that.

Question 38

Do “Zero Maintenance Team” companies actually exist — and how do I find them?

Accepted Answer

It’s a standard, not a directory (yet). A Zero Maintenance Team is one where challenging up is the job, and the best idea wins — whoever it’s from, however junior. Some companies already hire this way: they read how a person thinks , not just the résumé. If that’s the team you’re building, raise your hand → and RK will reach out.

Question 39

How do I screen a candidate for high agency and ownership?

Accepted Answer

Look for a dated artifact of their thinking from when nobody was watching — interview answers to “tell me about a time…” are rehearsed; dated records can’t be backfilled. Agency leaves traces: a decision made without permission plus the because , a workaround shipped before the meeting about the blocker, who they asked when stuck and how soon. That’s exactly what a Proof log holds — and why ten days of one reads louder than any screening question. High-agency people write “I decided X over Y because…” unprompted; low-agency people write status updates. How readers spot it →

Question 40

I hire mechanical / electronics / robotics — is Proof only for software engineers?

Accepted Answer

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.

Question 41

I sent a few people to Proof. Can I follow their progress and mentor them?

Accepted Answer

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 inside someone’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.

Question 42

How do I see who applied to my role?

Accepted Answer

/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.

Question 43

How do I post a role?

Accepted Answer

Same page — /f2/roles , two minutes. You set the bar (days logged, WHYs, consistency); engineers see exactly that bar on the role card.

Question 44

When do candidates show up?

Accepted Answer

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.

Question 45

My WhatsApp group already has 1,000 members. Why does Proof matter here?

Accepted Answer

Because after a year, a thousand-member group leaves nothing behind. You have a member count, not a record — and those are worth very different amounts.

Three things the group cannot do, and each one is easy to check for yourself.

It can’t answer a question about itself.“Who here has actually shipped something with Postgres?” A thousand members and no way to know. The messages scrolled past months ago.

Nobody outside can read it. A company hiring will not scroll forty thousand messages. It will read twelve records. So your thousand people are invisible to exactly the people who could pay them.

Help evaporates. When a member spends an hour helping another member, the hour leaves no trace and the helper carries nothing away. Proof records who learned from whom — 145 of those links exist so far.

The ask is not that you move your group. That fails, and it should — the group is where people talk, and WhatsApp is better at talking. Proof is where the work gets recorded. The two are not the same job.

The way it actually starts is paid work, not adoption. When money comes through your group — a gig, a project, a placement — it runs on Proof, and the record happens as a by-product of getting paid rather than as one more thing to keep up with. Nobody has to be persuaded to log anything.

What this is not yet: no community has been brought across at scale. Rooms here are small, and a leader with a thousand members would be the first to do this properly. That is the offer and it is also the risk, and you should hear it as both rather than only the first half.

Straight answers.