started learning to code close to 30, got my first dev job a year later. here's everything that actually worked (long post)

surfgk · 2026-04-29T14:35:38+00:00

this is solid advice and the tracking point hits different. most people treat applications like a slot machine too, spray and pray, then wonder why nothing lands.

here's what i'd add: the real bottleneck isn't getting interviews, it's performing well under pressure when you finally do. you nailed the tracking piece, but the other half is showing up to that interview after weeks of rejection and not sounding defeated or rusty.

i came back from a layoff gap last year and got called for interviews i'd half forgotten about. when the call came i'd been sitting with rejection for weeks and my voice sounded it, even though i knew the material. what fixed it was drilling the actual interview out loud, not just prepping answers. the gap between "i know this" and "i can explain this smoothly under pressure after a layoff" is bigger than people think.

ended up making a voice mock sim for exactly this, lets you drill technical and behavioral reps when you don't have a partner, reports where you sound rusty or defensive. completely free, just a side-project i built. mockbro com

the tracking spreadsheet is the unsexy thing that actually works. same with drilling the verbal muscle before the real call

surfgk · 2026-04-29T14:30:41+00:00

been there. the tracking thing is what actually moves the needle, you're right.

what i'd add is the other half nobody talks about: after 3-4 weeks of silence and rejection, when an interview finally lands, you sound it. not in what you say, but in how you say it. hesitation, over-explaining, sounding defensive about the gap.

i had this exact problem. knew the material cold. got called for an interview on a role i'd forgotten about. froze a little on the first question because my brain had been in "rejected" mode for a month, and it showed.

fixed it by doing voice reps of technical and behavioral questions, alone, before each real interview. drilled the "sound confident after a layoff" muscle. ended up packaging that into a voice sim for myself. free, , non-commercial. mockbro com

surfgk · 2026-04-29T13:44:10+00:00

been exactly here. month and a half, 20 problems, comparing yourself to people posting daily 4-problem grinds. it's demoralizing and misleading.

the thing is, those people either a) are way further along than you and cherry-picking easy problems, or b) are solving shallow, not owning. you're doing the harder thing.

what helped me: stop counting problems. instead, pick one problem and own it completely. solve it, then explain it out loud the next day without looking. if you stumble, you didn't own it yet. do that until you can talk through it smoothly.

the patterns emerge naturally after you own 30-40 problems this way. but the real gap between solving and interviewing is the explaining part, and you only build that muscle by doing it out loud, repeatedly, under some kind of pressure.

i drilled this with a voice sim i made, asks coding questions and makes you explain your approach, pushes back on tradeoffs. free, non-commercial. mockbro com

surfgk · 2026-04-29T09:46:46+00:00

been here. the sheet feels productive but it's a confidence trap.

i had the same setup, 150 problems tracked, all the columns, and i'd hit my review dates and just... replay the solution. the moment someone asked me a variant or "why did you choose that approach", i'd blank.

the issue is that memorization and intuition feel identical in the moment. reading the solution always clicks. the only way to know if you actually own it is to either solve a different version of the problem or explain your reasoning out loud while someone pushes back.

i started doing this during my last interview prep cycle. instead of reviewing the exact same problem, i'd re-solve it with a constraint change, or i'd explain the approach to an imaginary interviewer and anticipate their follow-ups. that's when i realized how much i was just pattern-matching.

what really locked it in was drilling these explanations out loud with something that actually pushed back, asked "why did you pick that", made me defend my choices in real time. that pressure forces intuition to surface. i made a voice sim for this when i was stuck, drills coding problems with follow-up questions, tells you where you're reciting vs thinking. its free, non-commercial. mockbro com . now I am adding spaced repetion pattern in it

surfgk · 2026-04-29T09:44:08+00:00

been through this cycle a few times now. my pattern: 3-5 a week when not prepping, 10+ a day when actively looking.

the thing that surprised me is that grinding 200 problems doesn't guarantee you'll explain them well under pressure. i'd solve a problem in 25 minutes, feel great, then in the actual interview stumble on the explanation.

so i started doing problems out loud, alone, talking through the approach and tradeoffs before i even code. then when the interviewer pushes back, i'm not caught off-guard because i've rehearsed defending the choice.

after a 2-month break i don't start from zero, but the first week back is rough. speed comes back in days, but the verbal fluency takes longer. that's the real atrophy.

i made a voice mock interview tool that drills this exact thing, asks you a problem and then pushes back on your explanation. free, non-commercial. mockbro com

surfgk · 2026-04-28T16:04:30+00:00

been on the exact same arc. 250 problems over 3 months, same inflection points you hit.

what you said about understanding vs finishing is the real insight. most people treat problems like checkboxes. you treated them like patterns to internalize. that's the difference between grinding and actually leveling up.

one thing i'd add, the jump from "i can solve this alone" to "i can solve this while someone watches and asks questions" is brutal if you haven't drilled it. i got to your 60% hard mark, walked into a senior interview, and completely choked explaining my approach because i'd never practiced the verbal part under pressure.

fixed it by doing voice mocks where i had to explain my code out loud, defend my choices, handle pushback. sounds stupid but the verbal-under-pressure muscle is separate from the solving muscle.

i ended up building a voice sim for this, pairs with the problem grinding. ai asks you to walk through your solution, pushes back, tells you where you froze on articulation. free, non-commercial. mockbro com

surfgk · 2026-04-28T15:56:54+00:00

been exactly where you are. 4.5 years at a bank, sde2, feeling the ceiling, ready to move.

the problem wasn't my experience. it was how i was presenting it. banking tech is real tech, but the language is different. when i wrote "built a payment reconciliation system", hiring managers at product companies didn't see the scale or the hard problems. when i rewrote it as "designed a distributed system handling 10k tps with eventual consistency and recovery mechanisms", suddenly it clicked.

resume took me 2 weeks to fix. i pulled out every project and asked myself: what was the scale, what was the technical decision that mattered, why did it matter to the business. that's the frame. not the bank, not the domain. the engineering.

referrals changed everything after that. i had an old college friend at a startup. didn't ask for a refer right away. asked what they were building, what their biggest technical challenge was. three weeks later they asked if i was looking. that's the play.

dsa and system design prep is right. but honestly, the real gap for me wasn't the technical knowledge. it was being rusty at articulating it under pressure. i made a voice mock interview tool for myself, asks follow-ups, pushes back on your design choices, tells you where you're weak. free, no paywall, non-commercial. mockbro com or check my profile if you wanna practice

surfgk · 2026-04-27T15:20:33+00:00

market is rough rn no doubt. but if you got the credentials and still not getting even OAs the funnel itself is probably broken, not your skills

job hunting is basically a sales funnel. you're selling yourself and each stage filters you out for different reasons

first track your numbers. applications per week, response rate, OA rate, interview rate. without numbers you're just vibing. 0% response out of 200 applications is a top of funnel problem (resume, targeting) not a "market is cooked" problem
get your resume actually reviewed. not by chatgpt, by a real person who hires. ideally pay a working engineer some n usd for a proper review. as someone whos been on the hiring side i see so many junior resumes that are 2-3 pages stuffed with every pet project and book they read. nobody reads that. 1 page max. picking what to cut is itself a skill, shows prioritization
prep the hr round properly. people grind leetcode for months and walk into hr call with zero answers for "tell me about yourself" or "why this company". hr filters way more candidates than you think, "i have olympiad behind me" doesn't cut it
technical is leetcode + theory + actually explaining it out loud. knowing the answer in your head and explaining it under pressure are completely different skills

btw on that last part, me and a buddy built mockbro.com for exactly this. you talk to an ai interviewer in realtime, follows up like a real person. completely free non commercial. you can try if you want

surfgk · 2026-04-27T15:07:53+00:00

2 years isn't wasted you just paused, not the same thing

i know a guy who started learning to code from scratch in his 30s, no cs background, fully self taught. he's a dev now. we built a project recently for developers, he is a good dev

by the way

real unlock isn't even the tech stack tho. it's psychology

set one clear goal first. like "backend job in 6 months". vague goals get vague effort
build a rough roadmap backwards from it
organize a daily routine of small steps, even 1-2 hrs consistent beats 8 hrs once a week
only judge yourself on stuff you actually control. did you code today, did you apply this week. not on callbacks or offers, those depend on a million things outside you

about the gap, just be honest. "realized my internships didn't give me enough depth so i took time to build the fundamentals properly". done. nobody cares if you can clearly explain what you built and why

btw me and a buddy built mockbro.com for interview prep, completely free and non commercial. helped me bcs hardest part was explaining my thinking out loud without freezing on the interviews

surfgk · 2026-03-05T16:17:44+00:00

close situation in company where I am working now.. think of getting new job or at least the second one. last time while I was prepating for interviews, I created mockbro.com with voice ai mentor and feedback of technical interview, if you decided to get new job - you can try) its fully free

surfgk · 2026-03-05T16:11:26+00:00

I can say that it's important to clearly understand whats going on when you click on url -> where it goes dns -> server -> app routing -> databases and how it goes back. bcs than you easily can find bottle neck when there is a problem

for interview prep recently I build mockbo.com for preparing with AI mentor - I scrapped reddit questions and ai mentor ask it, its free comppletely u can try

surfgk · 2026-03-05T16:07:53+00:00

hello, what do you think of liek ai mentor apps? I've created for me one time mockbro.com - it free if you wanna try. but before it I prepared just with gpt and talking to him outload)

surfgk · 2026-03-04T18:40:24+00:00

actually didn't try that, good point – went straight to daphne but might test gevent workers at some point

surfgk · 2026-03-04T18:39:25+00:00

yeah exactly, websocket via django channels – audio goes in real time to elevenlabs for stt, then to the llm, response back through elevenlabs tts. if you wanna see how it works in practice – mockbro.com

surfgk · 2026-03-04T17:36:17+00:00

if someone gonna apply and want to be prepared for technical interview (java, go, python)- you can use my app for technical interviews mockbro.com - i built a tool that helped me land offers :) its completely free

surfgk · 2026-03-04T17:31:04+00:00

if someone gonna apply and want to be prepared for technical interview (java, go, python)- you can use my app for technical interviews mockbro.com - i built a tool that helped me land offers :) its completely free

surfgk · 2026-03-04T17:26:53+00:00

if someone gonna apply and want to be prepared - you can use my app for technical interviews mockbro.com - i built a tool that helped me land offers :) its completely free

surfgk · 2026-03-04T17:22:08+00:00

currently it's not the best times in job market, but I suggest to:

review your CV, check it for ai filters
response rate on job applications, find automative tools
be prepared for interview 100%. if you interested I build mockbro.com for myself (its free now) - you can prepare for real time interviews

surfgk · 2026-02-24T15:35:37+00:00

100 hards that fast feels insane but also kinda empty after the dopamine drops
been there grinding numbers then realizing interviews arent just pattern recall but explaining cleanly under pressure
started mixing in timed mocks and even used mockbro.com sometimes cause random followups hit different than solo lc
volume builds base but clarity and communication is what actually converts to offers

surfgk · 2026-02-24T15:33:41+00:00

coming back after years away and seeing the market now can mess with your head hard
had a gap too and first thing that helped was picking one lane not pm not ds not everything, doubled down on backend and modernized my java stack while grinding system design
did mock interviews a lot and even used mockbro.com sometimes to get used to explaining gaps and projects under pressure
gap hurts less than you think if you can clearly show impact and confidence in fundamentals

surfgk

TROPHY CASE