Skip to content
~45 DAYS · ~2 HRS A DAY

Your first engineering job —before your first job.

Real tickets. Real reviews. A record a recruiter can check.

RAZORPAY · 7-DAY REFUND BEFORE YOU START
NTF-04IN PROGRESS
Restock event listener drops duplicates
6 SP · DUE IN 4D
➜ claude
> why do these two counts disagree?
· reading services/reviews/count.ts
> …that part is on me.
✓ MERGED +214 −38
DP
DEV PATEL · AI REVIEWER
Good root cause. But why did you trust the mirrored doc without checking the sandbox?
01 — THE WORK

A real board. Real due dates.

One ticket, one pull request. Go quiet and it returns to the pool — like at work.

board.teeos.internal / sprint-04
REV-05YOU
Review count includes unapproved entries
8 SP · DUE IN 2D
TO DO3
NTF-04Restock event listener drops duplicates6 SP · DUE IN 4D
CHK-11Coupon field accepts expired codes3 SP · DUE IN 6D
IN PROGRESS2
API-02Vendor timeout not retried5 SP · DUE TOMORROW
CODE REVIEW1
CHK-09Split checkout total rounding2 SP · WITH DEV PATEL
MERGED12
NTF-01✓ Email capture UI +214 −38MERGED 2D AGO
CHK-06✓ Guest cart persistence +61 −12MERGED 5D AGO
SCROLL THE BOARD →MERGED · 12
02 — INSIDE THE JOB

Four surfaces from your first month.

Engineering OnboardingEDITED 3 WEEKS AGO · PRIYA SHARMA
• Checkout service owns totals. Cart owns line items.• Any change touching orders needs a second reviewer.
STALEdocs drift — confirm against the sandbox

The internal docs a real team runs on.

@@ services/reviews/count.ts
− return reviews.length;
+ const v = reviews.filter(r => r.approved);
+ return v.length;
“Why did you trust the doc without checking the sandbox?”
CHANGES REQUESTED✓ MERGED

Reviews that push back.

➜ claude
> /reviews/count says 48, admin says 61
· two definitions of “review”
· spec never says which is public
> …that part is on me.

Claude Code included. Prompts reviewed like PRs.

Kabir RaoAI ENGINEERING MANAGER · 15:47
5 orders stuck in ‘processing’ since 14:20, support’s escalating — can you look?

One week, production breaks. You get the ping.

03 — THE 45 DAYS

What the 45 days look like.

~100 hours, at your pace. Deadlines sit on tickets, not on you.

  1. FIRST WEEK

    Offer letter, employee number, repo access, first ticket.

    KEEP: OFFER LETTER
  2. TICKETS 3–8

    Reviews come back with changes. You fix them before anything merges.

    KEEP: CORRECTION PAIRS
  3. MID-TERM

    Production breaks without warning. You get the ping.

    KEEP: RCA DOCUMENT
  4. ON COMPLETION

    License issued. Merged PRs, corrections, transcripts — public.

    KEEP: PROOF PAGE
04 — WHY THIS EXISTS

AI writes the code. Judgment is the job.

Judgment only forms against real consequences. So we gave you some.

  1. 01THE TYPING JOB IS GONE

    Nobody pays you to know what AI knows.

    WHAT WE DO ABOUT IT

    Claude Code included — and your prompts reviewed like pull requests.

  2. 02THE JUDGMENT JOB SURVIVED

    Someone still has to decide whether the answer is right.

    WHAT WE DO ABOUT IT

    Every PR reviewed against a fixed rubric. Corrections, not a grade.

  3. 03THE TRAP

    You need a job to build judgment, and judgment to get the job.

    WHAT WE DO ABOUT IT

    ~100 hours of assigned work, one real incident, one public record.

WHAT YOU ACTUALLY DO
  • Ship real tickets against real due dates
  • Fix review corrections before anything merges
  • Handle one unannounced incident, write it up
  • Leave with a record a recruiter can open
WHAT THIS IS NOT
  • Video lectures
  • DSA sheets or interview prep
  • A job guarantee, placement help, or hiring partners
  • A human reviewer — your manager and reviewers are AI
05 — THE LICENSE

A URL, not a PDF.

Every PR merges on public GitHub under your own account. Checkable without trusting us.

devlicense.com/p/DL-2026-00047EXAMPLE
DevLicenseEXAMPLE
LICENSE №
DL-2026-00047
HOLDER
Ananya Iyer
TeeOS · PRODUCT ENGINEERING · 12 JAN – 26 FEB 2026
VERIFIED RECORDISSUED 26 FEB 2026
MERGED PR
14
CORRECTIONS
23
SPIKES
5
RCA FILED
1
PROMPTS REVIEWED
96
AI SCORE
41 → 76
THE RECORD4 OF 19 SHOWN
  1. CHK-09✓ MERGED
    Split checkout total rounding
    +61 −12 · 2 CORRECTIONS
  2. NTF-04✓ MERGED
    Restock listener drops duplicate events
    +214 −38 · 1 CORRECTION
  3. INC-01RCA FILED
    Orders stuck in processing — root cause analysis
    1,240 WORDS · DETECTED 15:47 · MITIGATED 16:29
  4. API-02✓ MERGED
    Vendor timeout not retried
    +38 −4 · 3 CORRECTIONS
Every row links to the PR, the review thread and the AI transcript.

Example record. Real proof pages publish at the end of the first term.

06 — QUESTIONS

Before you pay.

What exactly do I get for ₹4,999?

One enrollment into TeeOS — a fictional merch company with a real codebase, board, docs, team chat and manager. You get an offer letter with your name and employee number, about 100 hours of assigned work broken into roughly 14 tickets and 5 discovery spikes, one pull request per ticket with a review on every one, one unannounced production incident, Claude Code included with the AI budget for your tickets and your prompts reviewed the same way your code is, and a public proof page at the end. One payment. No subscription, no upsell, no locked modules.

Is this a job or an internship? Do I get paid?

No. DevLicense is simulated work experience, not employment. There is no employer–employee relationship, no salary and no stipend — you pay us, we do not pay you. TeeOS is a company we invented. The repository, the tickets, the deadlines, the pull requests and the reviews are real, and the pull requests are merged on public GitHub under your own account. On your CV, call it what it is: simulated professional work experience, with a public record attached.

Is there a job guarantee or placement assistance?

No. We do not place anyone, we have no hiring partners, and we will not pretend otherwise. Anyone selling you a job guarantee for ₹4,999 is selling something they cannot deliver. What you get instead is evidence a recruiter can check without trusting us: merged pull requests, the corrections a reviewer sent back and the fixes you shipped, a written production investigation, and a 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, your reviewer and your teammates are AI, running a fixed rubric — you should hear that from us rather than discover it later. That is what makes a review land in hours instead of a week, and it is why every participant is held to the same standard. The corrections are specific, and you have to fix them before anything merges. If you want a human reading your code line by line, that is a separate tier and it costs what a human costs.

Is this real, or is it a scam?

Fair question — ₹4,999 is real money and we are new. Three things you can check before paying. Payment runs through Razorpay, so there is an order ID, a receipt and a refund path, not a UPI handle. The registered entity, address and support email are on the contact page. And the work outlives us: your pull requests are opened, reviewed and merged on real public GitHub under your own account, so the commit history stays inspectable whether or not DevLicense is still here in two years. TeeOS is fictional. The code, the reviews and the record are not.

How much time does it take, and what if I fall behind?

About 100 hours of work — roughly 45 days at two hours a day. That is an average pace, not a deadline, and nothing expires. Deadlines sit on individual tickets, the way they do in a real job: go quiet past about twice a ticket’s estimate and that ticket returns to the pool, and you pick up a fresh one when you are back. You lose the ticket, never the license or anything already merged. For exams or a placement drive you apply for leave inside the company — a short handoff note to your manager — and due dates extend by up to three weeks.

What does a recruiter actually see, and can they verify it?

A public URL, not a PDF. It lists every pull request you merged with its diff and review thread on GitHub, the reviewer’s original objection next to the commit where you fixed it, your written investigation of the production incident, and your AI-collaboration score at the start against the score at the end. It does not say “completed a course”. A recruiter can open the work and disagree with it — that is the point. A certificate asks to be believed; a license asks to be checked.

Can I get a refund?

Yes, before you start. Full refund within 7 days of payment, as long as your onboarding access has not been issued. Once access is issued and work items are assigned, the enrollment is non-refundable — each ticket set is authored for one engineer and leaves the pool when it is assigned to you. If we cancel your start and cannot restart it, you get a full refund. Refunds go back through Razorpay to the original payment method, usually within 5–7 working days.

Something else? hello@devlicense.com — a person replies.

ENROLLMENT · ONE-TIME PAYMENT

₹4,999One payment. No subscription, no upsell.

No timer, no expiring price. Every ticket set is written for one engineer.

SECURE PAYMENT VIA RAZORPAY

Full refund within 7 days if your access hasn’t been issued.