Hiring still tests the one skill AI took first.
The job was never the puzzle. It's code you didn't write, a 2 a.m. page, a bug in a teammate's PR.
Nobody trains for that. So we built the place that does.
LeetCode was just the start. Go Offbook.
Break it. Fix it. Defend it.
Coming next to Offbook: your app goes down at 2 a.m., and you’re the one who brings it back. Then you explain every choice to an interviewer who keeps asking why.
Yes, there’s AI. It just won’t do it for you.
https://t.co/HFyA3gIx5g
@sahill_og LeetCode grinding as a career strategy is dying anyways. Two years memorizing patterns so you can perform them in an interview — AI does that in four seconds now, and companies know it.
@ayesha_fatiima The levels aren't harder algorithms. Each one changes the rules under code you already wrote.
Practise it like this:
- A bank: deposit, transfer
- Add scheduled payments
- Merge two accounts
- "What was the balance at 3 PM?"
If level 4 forces a rewrite, that's the gap.
Last week a global email provider was down for a day. Not from traffic. From retries and failing health checks.
We rebuilt that outage. Run it. Then fix it.
Also new: SQL on a real Postgres 16. Deadlocks, leaky tenants, migrations with zero downtime.
https://t.co/HFyA3gIx5g
@Prayag12B Interesting opinion. So do you think there can be a day engineers just voice command agents and they do even the hard part of solving complex incidents or do you think there will always be a human in the loop involved somewhere?
12 Nov: a global mail service went dark for ~24 hours.
They undid the bad change at 01:06 UTC. Mail stayed down.
We rebuilt the day on Offbook. Replay it, then break the loop yourself.
Start the free week → https://t.co/HFyA3gIx5g
Then open: https://t.co/nohSpG1Qy6
@FangYi11101 Spent two years grinding LeetCode so an AI could solve it in four seconds and the interviewer could ask about fsync instead.
The Blind 75 crowd is about to find out they majored in a dead language.
Reversing a linked list was never the job. It was the hazing.
@geniusvczh Count the circular dependencies:
rollback needs MFA, MFA needs the tenant that’s down, and the break-glass password lives behind the glass.
Three, in one incident.
Ask “what does your recovery path depend on?” in a design round and watch the whiteboard go quiet.
@johncrickett Agreed, and add one to the list: reading code you didn’t write
The agent writes 400 lines in a minute. Someone still has to find the line that charges the customer twice on a retry.
AI didn’t make fundamentals optional. It made 10x more code that needs them.
@scottbolinger The code got cheaper. Being wrong didn’t.
A viral AI-written date parser this week turned February 31 into 3 March without a word. Product sense wouldn’t have caught that. Reading the code did.
Delighting humans is great. It doesn’t get paged at 3am.
@mecid We read it.February 31 parses fine. It comes out as 3 March.
Hour 25 is welcome too, and so is a +99:99 timezone.
Deploying without reading works great until the TV guide shows the match on the wrong day.
@SubhadipShips He did. It’s called keeping Linux alive for 35 years. Writing v1 was the easy part. Reading and judging thousands of other people’s patches every release, without breaking the world, is the work.
@tQuietEngineer Every company has a service nobody left can explain. The engineer who can open it cold and find the fault is the one you want on that bridge call. That skill can be practised. Almost nobody practises it.
@AkshatMandloi10@smallest_AI “Nobody wants the pager” is the real job description now. Writing code got cheap. Reading code you didn’t write, at 2am, with only logs and a timeline, didn’t. Good to see a hiring loop that tests for it.
A 2000 rating tells you someone memorised patterns.
It doesn't tell you what they do when production crashes and the cause is somewhere in 40 files they have never opened.
That second skill is the job. It's also the one nobody practises.