Your first engineering job —before your first job.
Simulated work experience for engineering freshers. ~100 hours of real tickets, code reviews and one production incident — and a public record a recruiter can check.
Good root cause. But why did you trust the mirrored doc without checking the sandbox?
- ~100HOURS OF REAL WORK
- ~18TICKETS · ONE PR EACH
- 1PRODUCTION INCIDENT
- 1PUBLIC URL THAT PROVES IT
One ticket, start to finish.
- 01CHAT · 15:47
It arrives.
Assigned to you, with a clock. One week it arrives at 3:47pm, because production is broken.
- 02IT PORTAL → CLAUDE CODE
You work it.
Claude reads the code with you. You decide whether it is right.
- 03PULL REQUEST · PROMPT REVIEW
It gets judged.
Two reviews: the code, and how you asked for it. Nothing merges until the corrections are made.
AI writes the code. Judgment is the job.
Judgment only forms when being wrong costs something. Here it does — with a reviewer, before it counts.
- DPDEV PATEL · REVIEWERCHANGES REQUESTED
Good root cause. But why did you trust the mirrored doc without checking the sandbox?
- YOUYOU+14 −3
Checked the sandbox: totals are rounded per line there. Moved rounding to the cart total, added a test for the split case.
- DPDEV PATEL · REVIEWER✓ APPROVED · MERGED
That is the fix.
A URL, not a PDF.
Every PR on public GitHub, under your own account. Checkable without trusting us. Type your name — this is what yours looks like.
- CHK-09✓ MERGEDSplit checkout total rounding+61 −12 · 2 CORRECTIONS
- NTF-04✓ MERGEDRestock listener drops duplicate events+214 −38 · 1 CORRECTION
- INC-01RCA FILEDOrders stuck in processing — root cause analysis1,240 WORDS · DETECTED 15:47 · MITIGATED 16:29
- API-02✓ MERGEDVendor timeout not retried+38 −4 · 3 CORRECTIONS
Corrections are the point — a record of being coached, not of being wrong. Example record; real pages publish at the end of the first term.
A page like this one is yours in ~45 days at ~2 hours a day.
Everything the job comes with.
- 01
Offer letter & employee ID
On the org chart from day one.
- 02
~18 tickets, ~100 hours
Bugs, a vendor integration, one full feature.
- 03
AI manager & reviewers
Fixed rubric. Reviews in hours, not weeks.
- 04
PRs on your own GitHub
Merged under your account. Outlives us.
- INCLUDED
Claude Code included
The real tool, with the AI budget your tickets need.
- 06
Prompts reviewed like code
What Claude got wrong — did you catch it?
- 07
One production incident
Unannounced. You get the ping.
- 08
A public proof page
Every PR and correction, at one URL.
₹4,999No subscription. No timer. No upsell.
Razorpay · full refund within 7 days if your access hasn't been issued.
Fifteen minutes with the team first.
Bring your branch, your year, what you have built. We tell you plainly if this is the right next step — and what to do instead if it is not.
Before you pay.
What exactly do I get for ₹4,999?
One enrollment into Fabrix — an invented company with a real codebase, board, docs, chat and manager. An offer letter with your name and employee number. About 100 hours of work in around 18 tickets, one pull request each, every one reviewed. One unannounced production incident. Claude Code included, with your prompts reviewed the way your code is. A public proof page at the end. One payment, nothing locked.
Is this a job or an internship? Do I get paid?
No. It is simulated work experience — you pay us, we do not pay you, and there is no employer–employee relationship. The company is invented; the repository, tickets, reviews and merged pull requests on your own GitHub are real. On your CV: simulated professional work experience, with a public record attached.
Is there a job guarantee or placement help?
No — and anyone selling a job guarantee for ₹4,999 is selling something they cannot deliver. What you get is evidence a recruiter can check without trusting us: merged PRs, the corrections you fixed, a written incident investigation, and one page they can open during the call. Turning that into an offer is still your job.
Who reviews my work — a person or an AI?
Your manager, reviewer and teammates are AI on a fixed rubric. That is why a review lands in hours instead of a week, and why everyone is held to the same bar. The corrections are specific and you must fix them before anything merges.
How much time does it take? What if I fall behind?
About 100 hours — roughly 45 days at two hours a day, at your pace; nothing expires. Deadlines sit on tickets, not on you: go quiet past about twice a ticket’s estimate and it returns to the pool; you pick up a fresh one when you are back. Exams or a placement drive: apply for leave in the company and due dates extend by up to three weeks.
Can I get a refund?
Yes, before you start: full refund within 7 days of payment if your onboarding access has not been issued. After access is issued and work is assigned, it is non-refundable — each ticket set is authored for one engineer. If we cancel your start and cannot restart it, full refund. Refunds go back through Razorpay in 5–7 working days.
Something else? Support: hello@devlicense.com