Image 1 — leetcode was making me worse at interviews (kind of)
Image 2 — leetcode was making me worse at interviews (kind of)
Image 3 — leetcode was making me worse at interviews (kind of)

leetcode was making me worse at interviews (kind of)

quick backstory. when i was prepping for interviews, basically 100% of my time went into leetcode. grind problems, get faster, repeat. i figured if i could solve hard enough problems, the interview would take care of itself.

then i started actually interviewing and realised i'd completely ignored the other half. the part where you have to explain your thinking out loud, handle the interviewer constantly nagging you about your approach, answer follow-up questions without freezing, talk through a system design while someone watches. i'd spent six months training the silent-solo-coding half and zero time on the live-performance half, and the live half was exactly where i kept losing.

and the frustrating thing is that second half is genuinely hard to practice. you cant really do it alone, thats the whole point. it only exists when theres another person there. interviewing. io is $150+ a session(quite expensive), peer mocks mean coordinating with someone elses schedule and hoping they show and are actually good at it.

so i ended up building the thing i wanted, an AI that runs full live mock interviews. it makes you talk through your approach, pushes back mid-problem like a real interviewer would, throws follow ups at you, and afterwards tells you where you actually fell apart (went quiet, talked a bunch of nonsense or missed the hint, etc). coding, system design, and behavioral.

its at the point where it works but i might be a little biased on its flaws, so id love some outside opinions:

if the live-performance half was your weak spot too or not, would an AI interviewer feel useful, or would it feel like it misses something a real human gives you?

whats the one thing that'd make or break whether you actually used it?

would you trust AI feedback on how you came across in an interview, or does that part feel off?

genuinely not trying to sell anything, its free and i mostly just want to know if im building something people want or if im missing something obvious. happy to send it over if anyone wants to check it out.

u/ResolveLess5322 — 1 day ago

leetcode was making me worse at interviews (kind of)

quick backstory. when i was prepping for interviews, basically 100% of my time went into leetcode. grind problems, get faster, repeat. i figured if i could solve hard enough problems, the interview would take care of itself.

then i started actually interviewing and realised i'd completely ignored the other half. the part where you have to explain your thinking out loud, handle the interviewer constantly nagging you about your approach, answer follow-up questions without freezing, talk through a system design while someone watches. i'd spent six months training the silent-solo-coding half and zero time on the live-performance half, and the live half was exactly where i kept losing.

and the frustrating thing is that second half is genuinely hard to practice. you cant really do it alone, thats the whole point. it only exists when theres another person there. interviewing. io is $150+ a session(quite expensive), peer mocks mean coordinating with someone elses schedule and hoping they show and are actually good at it.

so i ended up building the thing i wanted, an AI that runs full live mock interviews. it makes you talk through your approach, pushes back mid-problem like a real interviewer would, throws follow ups at you, and afterwards tells you where you actually fell apart (went quiet, talked a bunch of nonsense or missed the hint, etc). coding, system design, and behavioral.

its at the point where it works but i might be a little biased on its flaws, so id love some outside opinions:

if the live-performance half was your weak spot too or not, would an AI interviewer feel useful, or would it feel like it misses something a real human gives you?

whats the one thing that'd make or break whether you actually used it?

would you trust AI feedback on how you came across in an interview, or does that part feel off?

genuinely not trying to sell anything, its free and i mostly just want to know if im building something people want or if im missing something obvious. happy to send it over if anyone wants to check it out.

u/ResolveLess5322 — 1 day ago

leetcode was making me worse at interviews (kind of)

quick backstory. when i was prepping for interviews, basically 100% of my time went into leetcode. grind problems, get faster, repeat. i figured if i could solve hard enough problems, the interview would take care of itself.

then i started actually interviewing and realised i'd completely ignored the other half. the part where you have to explain your thinking out loud, handle the interviewer constantly nagging you about your approach, answer follow-up questions without freezing, talk through a system design while someone watches. i'd spent six months training the silent-solo-coding half and zero time on the live-performance half, and the live half was exactly where i kept losing.

and the frustrating thing is that second half is genuinely hard to practice. you cant really do it alone, thats the whole point. it only exists when theres another person there. interviewing. io is $150+ a session(quite expensive), peer mocks mean coordinating with someone elses schedule and hoping they show and are actually good at it.

so i ended up building the thing i wanted, an AI that runs full live mock interviews. it makes you talk through your approach, pushes back mid-problem like a real interviewer would, throws follow ups at you, and afterwards tells you where you actually fell apart (went quiet, talked a bunch of nonsense or missed the hint, etc). coding, system design, and behavioral.

its at the point where it works but i might be a little biased on its flaws, so id love some outside opinions:

if the live-performance half was your weak spot too or not, would an AI interviewer feel useful, or would it feel like it misses something a real human gives you?

whats the one thing that'd make or break whether you actually used it?

would you trust AI feedback on how you came across in an interview, or does that part feel off?

genuinely not trying to sell anything, its free and i mostly just want to know if im building something people want or if im missing something obvious. happy to send it over if anyone wants to check it out.

u/ResolveLess5322 — 1 day ago

leetcode was making me worse at interviews (kind of)

quick backstory. when i was prepping for interviews, basically 100% of my time went into leetcode. grind problems, get faster, repeat. i figured if i could solve hard enough problems, the interview would take care of itself.

then i started actually interviewing and realised i'd completely ignored the other half. the part where you have to explain your thinking out loud, handle the interviewer constantly nagging you about your approach, answer follow-up questions without freezing, talk through a system design while someone watches. i'd spent six months training the silent-solo-coding half and zero time on the live-performance half, and the live half was exactly where i kept losing.

and the frustrating thing is that second half is genuinely hard to practice. you cant really do it alone, thats the whole point. it only exists when theres another person there. interviewing. io is $150+ a session(quite expensive), peer mocks mean coordinating with someone elses schedule and hoping they show and are actually good at it.

so i ended up building the thing i wanted, an AI that runs full live mock interviews. it makes you talk through your approach, pushes back mid-problem like a real interviewer would, throws follow ups at you, and afterwards tells you where you actually fell apart (went quiet, talked a bunch of nonsense or missed the hint, etc). coding, system design, and behavioral.

its at the point where it works but i might be a little biased on its flaws, so id love some outside opinions:

  • if the live-performance half was your weak spot too or not, would an AI interviewer feel useful, or would it feel like it misses something a real human gives you?
  • whats the one thing that'd make or break whether you actually used it?
  • would you trust AI feedback on how you came across in an interview, or does that part feel off?

genuinely not trying to sell anything, its free and i mostly just want to know if im building something people want or if im missing something obvious. happy to send it over if anyone wants to check it out.

u/ResolveLess5322 — 1 day ago

i kept failing interviews i shouldve passed, so i built an AI to practice the part leetcode cant teach. looking for people to tell me whats broken

bit of backstory first. i spent months grinding leetcode, hundreds of problems, could solve most mediums alone no stress. then i kept bombing actual interviews, and for the longest time i assumed it meant i just wasnt good enough technically.

eventually it clicked that the technical part usually wasnt even the issue. i could solve the thing. i just couldnt perform it, going quiet at the wrong moments, rambling, blanking on follow ups i actually knew, falling apart the second the interviewer asked me something. solving alone and doing it live while someone watches and expects you to talk are completely different skills, and nothing i was doing trained the second one.

the annoying part was there wasnt a great way to practice it. interviewing. io is like $150+ a session, peer mocks mean scheduling around someone elses life and hoping they show up. so i ended up building the thing i wished existed, an AI that runs full live mock interviews (coding out loud, system design, behavioral), pushes back on your approach mid-problem, and tells you where you actually fumbled after.

im at the stage now where it works but i genuinely need people to break it and tell me whats bad about it. so a few honest questions:

if youve struggled with the "i know it but cant show it live" thing, does an AI interviewer sound like something you'd actually use, or does it feel like it'd miss the point vs a real person?

whats the one thing that would make or break it for you?

and honestly, would you trust AI feedback on your interview performance, or is that the part that feels off?

not trying to sell anything here, its free and i mostly just want to know if im building something people actually want or if im too close to it to see the obvious flaw. full disclosure obviously, its mine. Let me know if anyone is interested and wants to check it out.

u/ResolveLess5322 — 2 days ago

i kept failing interviews i shouldve passed, so i built an AI to practice the part leetcode cant teach. looking for people to tell me whats broken

bit of backstory first. i spent months grinding leetcode, hundreds of problems, could solve most mediums alone no stress. then i kept bombing actual interviews, and for the longest time i assumed it meant i just wasnt good enough technically.

eventually it clicked that the technical part usually wasnt even the issue. i could solve the thing. i just couldnt perform it, going quiet at the wrong moments, rambling, blanking on follow ups i actually knew, falling apart the second the interviewer asked me something. solving alone and doing it live while someone watches and expects you to talk are completely different skills, and nothing i was doing trained the second one.

the annoying part was there wasnt a great way to practice it. interviewing. io is like $150+ a session, peer mocks mean scheduling around someone elses life and hoping they show up. so i ended up building the thing i wished existed, an AI that runs full live mock interviews (coding out loud, system design, behavioral), pushes back on your approach mid-problem, and tells you where you actually fumbled after.

im at the stage now where it works but i genuinely need people to break it and tell me whats bad about it. so a few honest questions:

if youve struggled with the "i know it but cant show it live" thing, does an AI interviewer sound like something you'd actually use, or does it feel like it'd miss the point vs a real person?

whats the one thing that would make or break it for you?

and honestly, would you trust AI feedback on your interview performance, or is that the part that feels off?

not trying to sell anything here, its free and i mostly just want to know if im building something people actually want or if im too close to it to see the obvious flaw. full disclosure obviously, its mine. Let me know if anyone is interested and wants to check it out.

u/ResolveLess5322 — 2 days ago

i kept failing interviews i shouldve passed, so i built an AI to practice the part leetcode cant teach. looking for people to tell me whats broken

bit of backstory first. i spent months grinding leetcode, hundreds of problems, could solve most mediums alone no stress. then i kept bombing actual interviews, and for the longest time i assumed it meant i just wasnt good enough technically.

eventually it clicked that the technical part usually wasnt even the issue. i could solve the thing. i just couldnt perform it, going quiet at the wrong moments, rambling, blanking on follow ups i actually knew, falling apart the second the interviewer asked me something. solving alone and doing it live while someone watches and expects you to talk are completely different skills, and nothing i was doing trained the second one.

the annoying part was there wasnt a great way to practice it. interviewing. io is like $150+ a session, peer mocks mean scheduling around someone elses life and hoping they show up. so i ended up building the thing i wished existed, an AI that runs full live mock interviews (coding out loud, system design, behavioral), pushes back on your approach mid-problem, and tells you where you actually fumbled after.

im at the stage now where it works but i genuinely need people to break it and tell me whats bad about it. so a few honest questions:

if youve struggled with the "i know it but cant show it live" thing, does an AI interviewer sound like something you'd actually use, or does it feel like it'd miss the point vs a real person?

whats the one thing that would make or break it for you?

and honestly, would you trust AI feedback on your interview performance, or is that the part that feels off?

not trying to sell anything here, its free and i mostly just want to know if im building something people actually want or if im too close to it to see the obvious flaw. full disclosure obviously, its mine. Let me know if anyone is interested and wants to check it out.

u/ResolveLess5322 — 2 days ago

i kept failing interviews i shouldve passed, so i built an AI to practice the part leetcode cant teach. looking for people to tell me whats broken

bit of backstory first. i spent months grinding leetcode, hundreds of problems, could solve most mediums alone no stress. then i kept bombing actual interviews, and for the longest time i assumed it meant i just wasnt good enough technically.

eventually it clicked that the technical part usually wasnt even the issue. i could solve the thing. i just couldnt perform it, going quiet at the wrong moments, rambling, blanking on follow ups i actually knew, falling apart the second the interviewer asked me something. solving alone and doing it live while someone watches and expects you to talk are completely different skills, and nothing i was doing trained the second one.

the annoying part was there wasnt a great way to practice it. interviewing. io is like $150+ a session, peer mocks mean scheduling around someone elses life and hoping they show up. so i ended up building the thing i wished existed, an AI that runs full live mock interviews (coding out loud, system design, behavioral), pushes back on your approach mid-problem, and tells you where you actually fumbled after.

im at the stage now where it works but i genuinely need people to break it and tell me whats bad about it. so a few honest questions:

if youve struggled with the "i know it but cant show it live" thing, does an AI interviewer sound like something you'd actually use, or does it feel like it'd miss the point vs a real person?

whats the one thing that would make or break it for you?

and honestly, would you trust AI feedback on your interview performance, or is that the part that feels off?

not trying to sell anything here, its free and i mostly just want to know if im building something people actually want or if im too close to it to see the obvious flaw. full disclosure obviously, its mine. Let me know if anyone is interested and wants to check it out.

reddit.com
u/ResolveLess5322 — 2 days ago

i kept failing interviews i shouldve passed, so i built an AI to practice the part leetcode cant teach. looking for people to tell me whats broken

bit of backstory first. i spent months grinding leetcode, hundreds of problems, could solve most mediums alone no stress. then i kept bombing actual interviews, and for the longest time i assumed it meant i just wasnt good enough technically.

eventually it clicked that the technical part usually wasnt even the issue. i could solve the thing. i just couldnt perform it, going quiet at the wrong moments, rambling, blanking on follow ups i actually knew, falling apart the second the interviewer asked me something. solving alone and doing it live while someone watches and expects you to talk are completely different skills, and nothing i was doing trained the second one.

the annoying part was there wasnt a great way to practice it. interviewing. io is like $150+ a session, peer mocks mean scheduling around someone elses life and hoping they show up. so i ended up building the thing i wished existed, an AI that runs full live mock interviews (coding out loud, system design, behavioral), pushes back on your approach mid-problem, and tells you where you actually fumbled after.

im at the stage now where it works but i genuinely need people to break it and tell me whats bad about it. so a few honest questions:

if youve struggled with the "i know it but cant show it live" thing, does an AI interviewer sound like something you'd actually use, or does it feel like it'd miss the point vs a real person?

whats the one thing that would make or break it for you?

and honestly, would you trust AI feedback on your interview performance, or is that the part that feels off?

not trying to sell anything here, its free and i mostly just want to know if im building something people actually want or if im too close to it to see the obvious flaw. full disclosure obviously, its mine. Let me know if anyone is interested and wants to check it out.

reddit.com
u/ResolveLess5322 — 2 days ago

i kept failing interviews i shouldve passed, so i built an AI to practice the part leetcode cant teach. looking for people to tell me whats broken

bit of backstory first. i spent months grinding leetcode, hundreds of problems, could solve most mediums alone no stress. then i kept bombing actual interviews, and for the longest time i assumed it meant i just wasnt good enough technically.

eventually it clicked that the technical part usually wasnt even the issue. i could solve the thing. i just couldnt perform it, going quiet at the wrong moments, rambling, blanking on follow ups i actually knew, falling apart the second the interviewer asked me something. solving alone and doing it live while someone watches and expects you to talk are completely different skills, and nothing i was doing trained the second one.

the annoying part was there wasnt a great way to practice it. interviewing. io is like $150+ a session, peer mocks mean scheduling around someone elses life and hoping they show up. so i ended up building the thing i wished existed, an AI that runs full live mock interviews (coding out loud, system design, behavioral), pushes back on your approach mid-problem, and tells you where you actually fumbled after.

im at the stage now where it works but i genuinely need people to break it and tell me whats bad about it. so a few honest questions:

if youve struggled with the "i know it but cant show it live" thing, does an AI interviewer sound like something you'd actually use, or does it feel like it'd miss the point vs a real person?

whats the one thing that would make or break it for you?

and honestly, would you trust AI feedback on your interview performance, or is that the part that feels off?

not trying to sell anything here, its free and i mostly just want to know if im building something people actually want or if im too close to it to see the obvious flaw. full disclosure obviously, its mine. Let me know if anyone is interested and wants to check it out.

reddit.com
u/ResolveLess5322 — 2 days ago

i kept failing interviews i shouldve passed, so i built an AI to practice the part leetcode cant teach. looking for people to tell me whats broken

bit of backstory first. i spent months grinding leetcode, hundreds of problems, could solve most mediums alone no stress. then i kept bombing actual interviews, and for the longest time i assumed it meant i just wasnt good enough technically.

eventually it clicked that the technical part usually wasnt even the issue. i could solve the thing. i just couldnt perform it, going quiet at the wrong moments, rambling, blanking on follow ups i actually knew, falling apart the second the interviewer asked me something. solving alone and doing it live while someone watches and expects you to talk are completely different skills, and nothing i was doing trained the second one.

the annoying part was there wasnt a great way to practice it. interviewing.io is like $150+ a session, peer mocks mean scheduling around someone elses life and hoping they show up. so i ended up building the thing i wished existed, an AI that runs full live mock interviews (coding out loud, system design, behavioral), pushes back on your approach mid-problem, and tells you where you actually fumbled after.

im at the stage now where it works but i genuinely need people to break it and tell me whats bad about it. so a few honest questions:

  • if youve struggled with the "i know it but cant show it live" thing, does an AI interviewer sound like something you'd actually use, or does it feel like it'd miss the point vs a real person?
  • whats the one thing that would make or break it for you?
  • and honestly, would you trust AI feedback on your interview performance, or is that the part that feels off?

not trying to sell anything here, its free and i mostly just want to know if im building something people actually want or if im too close to it to see the obvious flaw. full disclosure obviously, its mine. Let me know if anyone is interested and wants to check it out.

u/ResolveLess5322 — 2 days ago
▲ 144 r/leetcode

grinded hundreds of leetcode problems and still kept failing interviews , took me embarrassingly long to figure out why

bit of a confession. i did SO many problems, blind 75 like four times, most of neetcode, and i still kept bombing actual interviews.

for the longest time i assumed it meant i wasnt good enough technically and just had to grind more. so i did. didnt help.

then it slowly clicked, the technical part usually wasnt even the issue. i could solve the thing. i'd literally get home and re-solve the exact problem in 5 mins no stress. the issue was doing it live, with someone watching, expecting me to talk while i think. i'd go quiet at the wrong moments, then ramble and bury the point, blank on follow ups i actually knew, fall apart the second they gave a hint instead of using it. turns out solving alone and performing under a watching interviewer are just completely different skills, and leetcode only trains one.

honestly the main reason im posting is it felt really isolating. like everyone else had figured out something i hadnt and i was the only one whose brain just left the room the moment it counted.

so genuinely, has anyone else been stuck at this exact wall?? the "i know my stuff but cant show it live" thing. just want to know im not the only one, and curious what actually helped for the people who got past it.

reddit.com
u/ResolveLess5322 — 3 days ago
▲ 13 r/founder+1 crossposts

building was the easy part, distribution is giving me hell. "i will not promote"

i have been trying, i am posting , i am commenting, nothing. Nothing at all. i hear people talking about their first their first 100 users, i am out here struggling to even get my first user. Is there some kinda script manual um not getting? Coz when i make a post i genuinely get a maximum of 3 upvotes or none literally.

Someone please help, i am genuinely stuck.

reddit.com
u/ResolveLess5322 — 4 days ago

building was the easy part, distribution is giving me hell. "i will not promote"

i have been trying, i am posting , i am commenting, nothing. Nothing at all. i hear people talking about their first their first 100 users, i am out here struggling to even get my first user. Is there some kinda script manual um not getting? Coz when i make a post i genuinely get a maximum of 3 upvotes or none literally.

Someone please help, i am genuinely stuck.

reddit.com
u/ResolveLess5322 — 4 days ago
▲ 27 r/micro_saas+1 crossposts

I just made my first internet money ever and I couldn't be happier

The last couple of months, I had about 10 different real saas ideas. 7 of them I actually started building and only 4 were finished. From those 4 I only published 3 and only one, my current project did not fail immediately.

I had huge problems with finding the right idea, I tried various different approaches like going through starter story or acquired or indiehacker searching for tools I liked to copy them and add a little twist, or I tried solving my own problems which worked for myself, but I couldn't make a real product out of those.

I was really disappointed after my last fail, when I randomly checked twitter and I saw a viral post about a new tool that just got released and everyone went crazy in the comments saying how they liked the idea. So, I dug deeper and finally found something I could use, similar idea, but different use case.

I instantly started building and 2 weeks later I had my first prototype ready. I posted about it on reddit and after 3 days, someone actually bought a subscription.

I was so happy, I couldn't believe what I was seeing, because after all those months were I was trying to build something for people and no one cared, finally someone liked my product and decided to pay for it.

So the lesson is: Always keep going and never give up, just ship more and suddenly you will build something valuable. Every failed project has value for yourself and you will learn from it and why it failed.

If you have read so far and want to know what tool finally worked for me, here is a link to my website. Maybe you will be my second customer ;)

PS: I know I'm talking here like I just became a millionaire when in reality I just made 29 dollars. But we'll get there, step by step.

u/ResolveLess5322 — 4 days ago

i could solve everything alone and still failed the interview

bit of a rant/lesson, bear with me.

i used to treat interview prep like a grind counter. do enough problems, hit some number, youre ready. so i did, neetcode, blind 75 a few times over, could knock out most mediums alone without much drama.

then i sat in a real interview and it fell apart, but not in the way i expected. i didnt totally blank or anything dramatic. what actually happened was messier. i solved it, mostly, but i couldnt explain what i was doing as i went. went quiet at the wrong moments, then over-explained tiny stuff nobody cared about, fumbled a follow up i definitely knew the answer to, needed the interviewer to nudge me toward a line i'd have caught instantly on my own. walked out having "solved it" and still got rejected.

took me way too long to get why. knowing how to solve a problem and being able to perform it live while someone watches and expects you to talk are just two totally different skills. leetcode only trains the first. i had loads of the first and almost none of the second, and grinding more problems was never gonna fix a gap that had nothing to do with problems.

and its not just "freezing" btw, thats what i assumed at first. its a whole spread of stuff:

  • going quiet and making them dig your thinking out of you
  • the opposite, rambling and turning your answer into a monologue
  • blanking on follow ups you actually know
  • not knowing how to structure the answer out loud
  • falling apart the second they give a hint instead of using it

all different symptoms, same root thing, you can do the work, you just cant show it under pressure. and you cannot practice ANY of that alone in a leetcode tab, because the whole problem only shows up when theres another person in the room.

stuff that actually helped once the penny dropped:

  • record yourself solving out loud like its real. painful to watch back but you hear every silence and every ramble
  • do real reps with a human watching, even a friend. the nerves show up less on the day if youve felt them a few times
  • narrate BEFORE you type not after. "im weighing two approaches, let me talk through the tradeoff." feels awkward, works

anyway wasted a lot of hours on the wrong thing. genuinely curious where other people land, was it the actual algorithms that failed you in interviews, or was it this, knowing your stuff but not being able to get it across live?? for me the problems were never the problem.

reddit.com
u/ResolveLess5322 — 5 days ago

i could solve everything alone and still failed the interview

bit of a rant/lesson, bear with me.

i used to treat interview prep like a grind counter. do enough problems, hit some number, youre ready. so i did, neetcode, blind 75 a few times over, could knock out most mediums alone without much drama.

then i sat in a real interview and it fell apart, but not in the way i expected. i didnt totally blank or anything dramatic. what actually happened was messier. i solved it, mostly, but i couldnt explain what i was doing as i went. went quiet at the wrong moments, then over-explained tiny stuff nobody cared about, fumbled a follow up i definitely knew the answer to, needed the interviewer to nudge me toward a line i'd have caught instantly on my own. walked out having "solved it" and still got rejected.

took me way too long to get why. knowing how to solve a problem and being able to perform it live while someone watches and expects you to talk are just two totally different skills. leetcode only trains the first. i had loads of the first and almost none of the second, and grinding more problems was never gonna fix a gap that had nothing to do with problems.

and its not just "freezing" btw, thats what i assumed at first. its a whole spread of stuff:

  • going quiet and making them dig your thinking out of you
  • the opposite, rambling and turning your answer into a monologue
  • blanking on follow ups you actually know
  • not knowing how to structure the answer out loud
  • falling apart the second they give a hint instead of using it

all different symptoms, same root thing, you can do the work, you just cant show it under pressure. and you cannot practice ANY of that alone in a leetcode tab, because the whole problem only shows up when theres another person in the room.

stuff that actually helped once the penny dropped:

  • record yourself solving out loud like its real. painful to watch back but you hear every silence and every ramble
  • do real reps with a human watching, even a friend. the nerves show up less on the day if youve felt them a few times
  • narrate BEFORE you type not after. "im weighing two approaches, let me talk through the tradeoff." feels awkward, works

anyway wasted a lot of hours on the wrong thing. genuinely curious where other people land, was it the actual algorithms that failed you in interviews, or was it this, knowing your stuff but not being able to get it across live?? for me the problems were never the problem.

reddit.com
u/ResolveLess5322 — 5 days ago

i could solve everything alone and still failed the interview

bit of a rant/lesson, bear with me.

i used to treat interview prep like a grind counter. do enough problems, hit some number, youre ready. so i did, neetcode, blind 75 a few times over, could knock out most mediums alone without much drama.

then i sat in a real interview and it fell apart, but not in the way i expected. i didnt totally blank or anything dramatic. what actually happened was messier. i solved it, mostly, but i couldnt explain what i was doing as i went. went quiet at the wrong moments, then over-explained tiny stuff nobody cared about, fumbled a follow up i definitely knew the answer to, needed the interviewer to nudge me toward a line i'd have caught instantly on my own. walked out having "solved it" and still got rejected.

took me way too long to get why. knowing how to solve a problem and being able to perform it live while someone watches and expects you to talk are just two totally different skills. leetcode only trains the first. i had loads of the first and almost none of the second, and grinding more problems was never gonna fix a gap that had nothing to do with problems.

and its not just "freezing" btw, thats what i assumed at first. its a whole spread of stuff:

  • going quiet and making them dig your thinking out of you
  • the opposite, rambling and turning your answer into a monologue
  • blanking on follow ups you actually know
  • not knowing how to structure the answer out loud
  • falling apart the second they give a hint instead of using it

all different symptoms, same root thing, you can do the work, you just cant show it under pressure. and you cannot practice ANY of that alone in a leetcode tab, because the whole problem only shows up when theres another person in the room.

stuff that actually helped once the penny dropped:

  • record yourself solving out loud like its real. painful to watch back but you hear every silence and every ramble
  • do real reps with a human watching, even a friend. the nerves show up less on the day if youve felt them a few times
  • narrate BEFORE you type not after. "im weighing two approaches, let me talk through the tradeoff." feels awkward, works

anyway wasted a lot of hours on the wrong thing. genuinely curious where other people land, was it the actual algorithms that failed you in interviews, or was it this, knowing your stuff but not being able to get it across live?? for me the problems were never the problem.

reddit.com
u/ResolveLess5322 — 5 days ago

Um stuck, or maybe i am just scared of failing??

A couple of months ago, i posted about my SaaS product. It was a prototype. My post blew up and i got tonnes of feedback. It was great at first. Some people gave their genuine opinions of how i could improve the product, some people didnt think the idea was solid enough for me to continue pursuing it and for some unknown reasons others just hated it or me, not sure which was which.

Anyway i took the constructive feedback , and made the product better. I had a subtle relief that i was done building it but i was mostly scared that i was done with the easy part(building).

But now the issue is, i know if i want to get proper users i have to market my app, and get early testers on it but i dont quite know how to do that. I built a twitter account, instagram account and a discord community but i dont know how to get people to follow or interact. Do i just post memes about my niche or aggressively market my app?

I once posted on twitter and got zero interactions on my post which i will admit, was a hard hit on my ego and took a toll on my expectations.

I was gonna ask claude for advice but i figured, i'd rather hear from people who are going through the same or have been through it.

If anyone is interested, check my app out. Would really love some constructive feedback.

u/ResolveLess5322 — 7 days ago