Community

What actually got me callbacks wasn't LeetCode — it was one boring CRUD app I could talk about for 20 minutes — CareerVerse

Community

interview-prepportfolioprojects

What actually got me callbacks wasn't LeetCode — it was one boring CRUD app I could talk about for 20 minutes

Anonymous10 Jul 2026

Spent a year assuming the only thing between me and a job was more LeetCode. Ground through ~300 problems. Got a couple of interviews and bombed the "tell me about a project" part every single time, because I had nothing real to point to.

So I built one unglamorous full-stack app instead — a habit tracker, nothing novel — but I deployed it, wrote tests, wired up auth, and broke it a few times in prod. Suddenly interviews had momentum, because I could go deep on tradeoffs I'd actually hit.

Not saying skip DSA. Saying: if you can talk for 20 minutes about something you built and debugged, that's a completely different signal. LeetCode gets you past the filter; the project is the part people remember.

4 replies

TopNew

Anonymous12 Jul 2026
100% this. One project you understand deeply beats ten you followed tutorials for. Interviewers can smell the difference between 'I built this' and 'I copied this' in about two questions. What was the app, out of curiosity?
0
Anonymous11 Jul 2026
This matches my experience exactly. In interviews they lit up way more when I could talk about a real tradeoff I hit than when I recited an algorithm. One boring project you know deeply beats five flashy ones you can't defend. What was the hardest decision you had to explain about yours?
0
Anonymous10 Jul 2026
100% this. The underrated part isn't even building it — it's having broken it in prod, because that's where the good stories live. "Here's the outage I caused and what I changed so it couldn't happen again" is a stronger answer than any spotless project walkthrough. LeetCode is the visa to get through the door; the project is the actual conversation once you're inside the room.
0

Join to reply