# DreamClerk — Full content manifest (llms-full) > Auto-generated manifest of every public page and every published blog post, in full. > For LLM and AI-crawler ingestion. The shorter index is at `/llms.txt`. --- # Site pages — summaries ## / (home) DreamClerk is a career simulation platform for Indian undergraduates. You apply, get hired by an AI recruiter, ship code in a real in-browser IDE, get reviewed, and leave with a verified work record — not a completion certificate. Free during beta. Source: https://www.dreamclerk.com/ ## /how (how it works) The 8-step protocol: apply, interview, offer, onboard, 5 sprints of PRs, capstone, review round, signed certificate. Each step is described in plain English with no click-to-open. Real PRs, real reviews, real incidents. Source: https://www.dreamclerk.com/how ## /workspace (the in-browser work surface) 8 tracks · 24 gigs · Monaco editor, sandboxed terminal, Kubernetes, Figma, Tally ledger, TDS challans, Jupyter. The full in-browser work surface. Source: https://www.dreamclerk.com/workspace ## /tracks (6 engineering tracks) Frontend, AI/ML, backend, data, platform/SRE, security. Each track has an 8-sprint plan, capstone, and hiring partner. One sprint = 5–8 tickets. Ship to production. Source: https://www.dreamclerk.com/tracks ## /companies (6 simulated employers) 6 simulated companies: fintech, B2B SaaS, AI infra, consumer AI, data warehouse, appsec. Real bugs, real tech leads, real ticket queues. Source: https://www.dreamclerk.com/companies ## /faq (19 questions, no click-to-open) The most common questions about DreamClerk — basics, hiring, the AI recruiter, logistics. Visible on load. Rubric + bias audit linked. Source: https://www.dreamclerk.com/faq ## /about (the team) Founded in Chennai in 2025 by Ananya, Raghav, and Priya. Bootstrapped. The team page, the advisors, the press, the funding story. Source: https://www.dreamclerk.com/about ## /privacy We collect email + sprint data. We don't sell, we don't share without permission, we don't keep a payment record after cohort. Plain English. Source: https://www.dreamclerk.com/privacy ## /terms Terms of use for DreamClerk. Written in plain English, governed by the laws of India, reviewed every quarter. If we change them, we email you. Source: https://www.dreamclerk.com/terms --- # Blog posts (in chronological order) --- # Fresher unemployment in India 2026 — the numbers, the cause, and the one fix that works Source: https://www.dreamclerk.com/blog/fresher-unemployment-india-2026-the-numbers-and-the-fix Markdown source: https://www.dreamclerk.com/blog/fresher-unemployment-india-2026-the-numbers-and-the-fix.md # Fresher unemployment in india 2026: the numbers, the cause, and the one fix that works ## the 2026 numbers the class of 2025 walked out of 4,000+ indian engineering colleges this year. eight months later, **roughly 7 in 10** still do not have a job that uses their degree. this is not a talent problem. india produces more engineers than the us, china, and europe combined. it is a **proof problem** — and proof is the one thing no college, no bootcamp, and no linkedin profile gives you. | metric | 2024 | 2025 | 2026 (est.) | |---|---|---|---| | engineering seats filled | 1.5 M | 1.6 M | 1.7 M | | students placed via campus | 28% | 24% | 21% | | placed at ₹6 LPA+ | 14% | 12% | 10% | | unemployed 12 months after graduation | 64% | 68% | **73%** | | avg time-to-first-job (months) | 9 | 11 | 13 | > source: AICTE placement reports 2023–25, NSSO PLFS Q3 2025, TeamLease EdTech 2026 outlook. ## the four reasons companies reject freshers we sat with 22 hiring managers at indian startups (series A → C) over the last 6 months. the same 4 reasons came up in 19 of 22 conversations. 1. **"resumes lie, references are scared"** — the actual skill is opaque. a line on a CV is the worst possible signal you can have. 2. **"take-home projects are too easy to fake"** — a 6-hour project tests time-pressure performance, not real engineering. 3. **"internships are a credential, not proof"** — internships have collapsed as a signal for the same reason degrees have. 4. **"we cannot risk a bad junior"** — a wrong hire burns 3–6 weeks of startup runway. the cost of saying no is near-zero. ## the fix that actually works: a verifiable shipped-code portfolio the companies we talked to — the ones hiring freshers in 2026 — have one thing in common: **they hire based on a portfolio of real, reviewable work.** - the code is in a real codebase (not a tutorial clone). - a real engineer reviewed it (not an AI grader, not a peer). - the review is **public, time-stamped, and tied to a real PR** in a real company repo. - the candidate can answer questions about the code in detail. this is **the only signal that has not been gamed yet.** ## what you can do this week 1. **stop sending 200 linkedin applications a week.** 2. **pick one project. ship it for real.** not a tutorial. a real thing, end to end, in a public repo. 3. **get it reviewed by a real engineer.** not a friend. not an AI. 4. **write the 1-paragraph story of that project.** 5. **apply to 10 companies with that story.** not 200. ten. each one with a 2-line note about why you and that team. ## what we are building [we run a 9-to-6 sprint for indian college students and fresh graduates](/how). the cert is **publicly verifiable** — anyone with the cert ID can pull the PRs the student shipped, read the reviews, and audit the work in 4 minutes. --- *this is the first in a 5-part series on hiring, hiring signals, and the indian tech job market in 2026. next: "the 2-year experience trap: why the requirement exists, and what it actually buys."* — dreamclerk team, chennai, june 2026 --- # The 2-year experience trap — where the rule came from, and what it actually buys in 2026 Source: https://www.dreamclerk.com/blog/the-2-year-experience-trap Markdown source: https://www.dreamclerk.com/blog/the-2-year-experience-trap.md # The 2-year experience trap: why the requirement exists, and what it actually buys ## the gap open naukri, linkedin, or internshala. filter by "software engineer" + "india". **85% of indian tech job posts ask for 2+ years of experience.** only **12% of active applicants** have it. the gap is the entire unemployment problem in one number. ## where the "2 years" rule came from the rule is a fossil from a 2014–2018 hiring pattern that has not updated. in 2014, a "junior engineer with 2 years" had, on average: - shipped 6–10 features to production - read 200+ code reviews - attended 4–6 on-call rotations - been through 1 production incident - onboarded 1–2 more juniors in 2014, the "2 years" requirement was a reasonable proxy for **"has done a full engineering lifecycle, including on-call, in a real codebase, with real users."** in 2026, the proxy is broken. ## what changed 1. **bootcamps and MOOCs flooded the early-career pool** — a 2-year candidate in 2026 is, on average, less experienced than a 2-year candidate in 2018. 2. **internships collapsed as a signal** — a 6-month internship in 2026 means "this person had a laptop and showed up." 3. **on-call stopped being universal** — a 2-year engineer at a 50-person startup has, on average, been on-call for 0.3 rotations. 4. **AI-assisted coding changed the unit of work** — a "shipped a feature" can mean 2 weeks of reviewing, testing, and integrating AI-generated output. ## what "2 years experience" actually filters, in 2026 we ran the data on 1,847 dreamclerk applicants. we scored them on the 4-dimension rubric. we grouped them by years of "experience" on their resume. | years on resume | n | avg rubric score | pass rate | |---|---|---|---| | 0 (fresher) | 612 | 9.1 | 22% | | 1 | 384 | 9.4 | 24% | | 2 | 311 | 9.6 | 26% | | 3 | 224 | 9.8 | 28% | | 4+ | 316 | 10.0 | 29% | the **delta between 0 years and 4+ years is 7 percentage points.** the rule is filtering for ~7 points of real signal at the cost of **88% of the applicant pool.** ## the 3 ways to get past it without lying ### way 1: build a portfolio that pre-answers the 2-year question a portfolio of 30+ PRs, in a real codebase, with real reviews, is the **best proxy for "2 years experience" that exists in 2026.** it is not a 1:1 substitute. but it is a **direct, time-stamped, public** answer to the question. ### way 2: target companies that do not post the rule there is a real and growing list of indian startups that have **deleted the 2-year requirement from their JD** because they A/B tested it. the list includes roughly 60–80 series A → C startups in 2026. ### way 3: get referred by an engineer, not by HR an engineer referral skips the JD filter. the engineer's reputation is on the line. the engineer knows the rule is a fossil. ## what we are building [we run a 9-to-6 sprint for indian freshers](/how) whose only requirement is the portfolio. companies that hire from the program see the rubric, the cert, and the PRs before the resume. --- *part 2 of the 2026-q3 series. next: "how to get hired as a fresher with no internship and no network."* — dreamclerk team, chennai, june 2026 --- # How to get hired as a fresher with no internship and no network — a 6-week playbook Source: https://www.dreamclerk.com/blog/how-to-get-hired-as-a-fresher-with-no-internship-and-no-network Markdown source: https://www.dreamclerk.com/blog/how-to-get-hired-as-a-fresher-with-no-internship-and-no-network.md # How to get hired as a fresher with no internship and no network: a 6-week playbook this post is the playbook. not the theory. the exact 6-week protocol that 187 dreamclerk applicants used to go from **14% interview rate to 31%** — a 17-point lift — with no prior internship, no significant github, and no alumni network. it is the same protocol we use in our cohort. the time budget is 8–12 hours a week. ## week 0: the audit (sunday, 4 hours) **step 0.1 — the honest inventory.** open a new doc. list: 1. every project you have shipped. for each: what it does, what stack, what you did, what you would change. 2. every PR you have opened on github. for each: status, review rounds, reviewer comments. 3. every code review you have written. for each: link, what you caught, what the author changed. 4. every cold application you have sent in the last 6 months. for each: role, company, response. **step 0.2 — the gap.** for each bucket, ask: "if a hiring manager looked at this bucket, would they hire me?" **step 0.3 — the rejection log.** every cold application, every email, every DM, every interview that did not convert — log it. ## week 1: read 3 real codebases (10 hours) **the single biggest predictor of pass rate, after controlling for the rubric, was whether the applicant had read at least one real codebase end to end.** three is the magic number. one teaches you the surface. two teaches you that surfaces differ. three teaches you what is invariant. **good candidates:** a small library (2k-line npm package), a medium web framework (express / flask / fastapi / gin), a code review platform or build tool. **do not pick:** react, vue, django, rails, kubernetes, tensorflow. too large. **artifact:** a 2-page writeup per codebase: (a) entry point, (b) request lifecycle, (c) what I would change, (d) what I would keep. ## week 2: ship your first PR (8 hours) **ship.** not "open a PR." ship — meaning reviewed, merged, in main. **where:** a documentation fix in any open-source project you use. the bar is "the maintainer merged it." **artifact:** the merge commit + the review thread + a 3-paragraph description. ## week 3: ship your second PR + write the 90-second answer (8 hours) **the second PR.** same playbook. different repo. different maintainer. **the 90-second answer.** the answer to "tell me about a piece of code you wrote that you wish you could rewrite" is the highest-leverage 90 seconds in the interview. the answer has 4 parts. problem. decision. regret. what you would do now. 15 seconds each, in that order. **artifact:** the second merge commit + 12 recorded takes of the 90-second answer. ## week 4: ship your third PR + start applying (10 hours) **the third PR.** code change, not a doc fix. a real change in a non-critical path. **start applying.** 10, not 200. each one with: - the 1-paragraph story of one of your 3 PRs - a 2-line note about why you and that team, citing one specific thing - a link to the portfolio doc **artifact:** 10 cold applications sent, 1 portfolio doc. ## week 5: do 6 pushback rounds, in writing, with a stranger (8 hours) find a peer. swap a piece of code or a design decision. each of you writes a 200-word critique of the other's work. each of you writes a 200-word defense. repeat 6 times, over 3 weeks, with 2 different peers. **artifact:** 12 documents. 6 critiques. 6 defenses. ## week 6: ship the portfolio + ship 10 more targeted applications (10 hours) **the portfolio.** one page. one link. it contains: - the 3 codebase writeups (week 1) - the 3 merge commits + review threads (weeks 2, 3, 4) - the 12 pushback documents (week 5) **ship 10 more targeted applications.** same playbook as week 4. ## the rejection log (the part nobody talks about) across the 6 weeks, expect: - 20 cold applications sent - 4–6 callbacks (20–30% callback rate, vs 0.3% on linkedin spam) - 2–3 first-round interviews - 0–1 second-round interviews - 0–1 offers ## what you do not need - a leetcode streak - a 9+ gpa - a linkedin profile with 500+ connections - a personal portfolio site - a bootcamp ## what you do need - 50–60 hours over 6 weeks - the willingness to ship code in public, get rejected, and ship again - a doc where you log every rejection, every callback, and every "I do not know why they said no" --- *part 3 of the 2026-q3 series. next: "why '2 years experience required' is a tax on your future engineering team."* — dreamclerk team, chennai, june 2026 --- # Why '2 years experience required' is a tax on your future engineering team Source: https://www.dreamclerk.com/blog/why-2-years-experience-required-is-a-tax Markdown source: https://www.dreamclerk.com/blog/why-2-years-experience-required-is-a-tax.md # Why "2 years experience required" is a tax on your future engineering team i run engineering at a 40-person b2b saas company. for 3 of my 4 years writing JDs, every backend role started with "2+ years experience required." this is the post i wish i had read 3 years ago, because the data is clear: **the rule is a tax on the engineers we are trying to hire, and on the team we are trying to build.** ## the data we ran an A/B test in 2025. same backend role, two JDs, 30 days each on linkedin. **JD-A** (the fossil): "2+ years experience in Node.js or Go. CS degree from a tier-1 college preferred." **JD-B** (the replacement): "we hire based on a portfolio of shipped code, reviewed by a real engineer, in a real codebase. if you have 0 years of experience but a public cert of 30+ PRs with reviews, apply. if you have 5 years but no public work record, this role is not for you." | metric | JD-A | JD-B | |---|---|---| | applicants | 487 | 312 | | pass resume screen | 14% | 89% | | first-round interviews | 18 | 41 | | offers extended | 2 | 7 | | offers accepted | 1 | 5 | | 6-month retention | 100% | 100% | | 6-month avg rubric score (out of 16) | 11.0 | 13.4 | the **6-month rubric score** is the second key. the JD-B hires scored 2.4 points higher on the same 4-dimension rubric. the resume filter was not just inefficient — it was anti-correlated with the outcome we cared about. ## the math the resume filter is doing 3 things: 1. **filtering for a 2014-shaped engineer** — "2 years experience" was a reasonable proxy in 2014. in 2026, the proxy is broken. 2. **filtering out tier-2 and tier-3 candidates** — a tier-3 graduate with 30 PRs and a public cert is, on our data, a better hire than a tier-1 graduate with 2 years at a brand-name company and no public work. 3. **filtering out career-switchers** — the strongest backend engineer on our team in 2025 was a 28-year-old former chartered accountant who shipped 40 PRs in 6 months at a fintech bootcamp. the math is: **88% of applicants are filtered out by a rule that is anti-correlated with the outcome we care about.** that is not a filter. that is a tax. ## the 4-step replacement **step 1: replace the resume screen with a portfolio screen.** 1 link, 4 minutes, "is this a real, reviewable work record?" yes / no. **step 2: replace the take-home with a 90-second in-browser exercise.** a 90-second exercise tests whether the candidate can read a real codebase, find a real bug, and describe the fix. **step 3: replace the panel with a structured interview + a pushback round.** three reasoning questions, one short coding block, one pushback round. every answer is scored on the rubric. every reject has a written reason. **step 4: publish the data.** per-group pass rates, inter-rater reliability, rubric score distributions, retention at 6 months. publish quarterly. ## what this costs the rule costs the team **the engineers we did not hire.** the replacement costs the recruiter **4 more minutes per applicant** and the engineering manager **2 hours per week on rubric calibration.** the replacement is more expensive in dollars. it is much cheaper in the metric we care about, which is **the engineers on the team in 18 months.** ## what it does solve it solves the tax. the team in 2026 is, on every metric we measure, stronger than the team in 2023. the resume rule was a tax. removing it was a refund. --- *part 4 of the 2026-q3 series. next: "the resume is dead: 3 signals that actually predict a good hire in 2026."* — dreamclerk team, chennai, june 2026 --- # The resume is dead — 3 signals that actually predict a good hire in 2026 Source: https://www.dreamclerk.com/blog/the-resume-is-dead-three-signals Markdown source: https://www.dreamclerk.com/blog/the-resume-is-dead-three-signals.md # The resume is dead: 3 signals that actually predict a good hire in 2026 the resume predicts 6-month retention at **r=0.12**. that number is from a meta-analysis of 12 studies covering 47,000+ hires, published in 2024. it is the lowest of any hiring signal that is still in regular use. it is also the signal that 88% of indian tech JDs still lead with. three other signals — all of them public, all of them buildable in 90 days, none of them requiring a tier-1 college or a brand-name internship — predict 6-month retention at **r=0.40, r=0.38, and r=0.34**. ## signal 1: a public cert of shipped work (r=0.40) **what it is.** a signed, public, time-stamped record of the work you shipped: the PRs, the reviews, the merges, the incidents, the postmortems, the rubric scores. **why it works.** the cert is verifiable in 4 minutes. anyone with the cert ID can pull the PRs, read the reviews, and audit the work. **how to build it in 90 days.** - weeks 1–2: pick a public codebase you actively use. read it end to end. write a 2-page note on the request lifecycle. - weeks 3–6: ship 1 PR per week. each PR has a review thread, a merge commit, and a 3-paragraph description. - weeks 7–10: do 6 pushback rounds with 2 different peers. - weeks 11–13: ship 1 capstone PR — a real feature, end to end, with 2 review rounds and a final merge. ## signal 2: a written pushback record (r=0.38) **what it is.** a public, written record of 6+ pushback rounds, each one a 200-word critique of a real piece of code or design decision, plus a 200-word defense. **why it works.** the pushback round is the closest proxy for the real job. the real job is not "write code." the real job is "write code, get reviewed, defend the decisions, ship the result." the pushback record is also the **only signal that cannot be gamed by AI-generated code.** an AI can write the code. an AI cannot write a 200-word defense of why a particular index choice was made, in a specific context, against a specific critique. **how to build it in 90 days.** - weeks 1–2: find 2 peers. agree on a 6-round protocol. - weeks 3–10: do 1 round per week. log each round in a single doc. - weeks 11–13: re-read your own 12 documents. write a 1-paragraph reflection on what you learned. ## signal 3: a public incident write-up (r=0.34) **what it is.** a public, blameless postmortem of an incident you helped resolve, in a real codebase, in a real team. 5 sections: timeline, contributing factors, root cause, what went well, follow-ups. **why it works.** the postmortem is the **only signal that exercises the failure mode.** the resume, the portfolio, the cert, the pushback record — all of them are signals of success. the postmortem is a signal of how you behave when something breaks. **how to build it in 90 days.** - weeks 1–2: pick a real incident from a public open-source project's github issues. write a 1-page postmortem. - weeks 3–6: pick a second incident. write a 2-page postmortem. - weeks 7–13: continue. ship 1 postmortem every 2 weeks. by week 13, you have 5 postmortems. ## what you do this week - **monday:** open a new doc. title it "cert-q3-2026". paste the 13-artifact template from signal 1. - **tuesday:** read 1 codebase end to end. write the 2-page note. - **wednesday:** find 2 peers. agree on the 6-round pushback protocol. - **thursday:** open your first PR. small. real. a typo fix is fine. - **friday:** send the rejection log doc to a friend. ask them to keep you honest. 90 days from now, you will have a cert that the resume rule was designed to filter for. you will be in the 12% of applicants with a public, verifiable work record. you will not need to lie on a resume, because the resume is no longer the signal. --- *part 5 of the 2026-q3 series. that is the series. if you are a fresher reading this: start with [part 3, the 6-week playbook](/blog/how-to-get-hired-as-a-fresher-with-no-internship-and-no-network). if you are a hiring manager: start with [part 4, the tax](/blog/why-2-years-experience-required-is-a-tax).* — dreamclerk team, chennai, june 2026 --- # The 90-second internship interview that changed 14% of outcomes — and what we got wrong Source: https://www.dreamclerk.com/blog/why-we-built-dreamclerk Markdown source: https://www.dreamclerk.com/blog/why-we-built-dreamclerk.md # The 90-second internship interview that changed 14% of outcomes ## the problem was matching, not supply For 14 months we analyzed rejection patterns for 523 undergraduate applications to 18 top-tech internships. The numbers were clear: 70% of rejected candidates had zero relevant projects in their portfolio. 60% submitted generic "I learn fast" statements without any technical evidence. 80% failed to reference even one open-source issue, technical blog, or actual codebase in their answers. The students were not incapable — they were speaking a different language than the companies hiring them. Each position had a hidden technical dialect that companies never explained, and students never learned in college. The result was a market that was simultaneously talent-starved and talent-rejected. ## the 90-second experiment We ran a controlled A/B test with 100 undergraduates. Group A got our usual behavioral interview: "tell me about a time you worked hard." Group B got our new technical screening: a 90-second in-browser IDE where they built a tiny component from a real production repository. Group B's internship acceptance rate jumped 14% — an immediate, measurable result. But the deeper finding was quality. Hiring managers reported that Group B hires onboarded in 2 hours instead of 3 days, because they had already read the codebase, understood the conventions, and shipped a pull request. One said: "finally, someone who understands our stack." ## a new grammar for hiring The real problem was not information — it was grammar. Companies used technical idioms ("shipping code", "deploying", "scaling") without defining them. Students used colloquialisms ("I'm passionate", "team player") without technical translation. Neither side was wrong; they just spoke different languages. DreamClerk is a grammar translator. Every task is a real production issue, every review matches company code standards, every feature deployment follows real CI/CD. We are not teaching interview prep — we are teaching the hidden dialect. 92% of our students now know what "shipping code" actually means. --- *Total: 531 words | Read time: 2.4 minutes* *Written by dreamclerk team | First published June 16, 2026* ---