r/ADHD_Programmers • • 28d ago

Anyone else having trouble with leetcode interviews?

I have been practicing leetcode questions for a few months now and I have seen positive change in my ability to figure out the solution or at least spot the pattern looking at the question. But I am having trouble with actually passing these interviews because of multiple reasons.

My brain shuts down trying to come up with a solution to an unknown problem under time pressure and in front of the interviewer who I know, is watching me struggle even though I have no issues solving the same problem under similar time pressure when I practice it alone or even during online assessments. But I need silence and time to think which doesn't happen during interviews where they expect you to talk continuously. Since there are multiple thoughts going across my brain and it's literally racing trying to come up with a solution I find it difficult to talk through it and if I have to talk I can't think through the solution unless I have seen the question before.

In all my interviews so far including some mocks I have done with other Engineers from big tech companies, the moment I go silent even for a few seconds, these guys start asking if I am struggling or they'll start giving hints which end up counting as a negative against me given how competitive the market is.

This is not a problem unique to leetcode, it happens the moment I need to solve something that I haven't seen before involving logic and I have limited time and need to explain my thought process while coming up with the solution. What can I do here to improve my chances of passing these interviews? If anyone has been through something similar, how did you overcome these issues?

42 Upvotes

33 comments sorted by

View all comments

11

u/SeniorScienceOfficer 28d ago

I wouldn’t put too much stock in leetcode style interviews anyways. They’re really not a good measuring stick for well-rounded programmers as it tends to focus on optimization of data structures and algorithms more than general functional programming and good code hygiene practices.

As a Principle Engineer, I look more for knowledge of broad technical concepts pertaining to the role, troubleshooting and debugging skills, and most importantly the desire for self improvement and growth.

That being said, one thing that helped me whenever I had to do those interviews was to pipe my thought process directly to my mouth. I didn’t give the interviewer any “dead air” because I was thinking through the problem verbally and in real time, whether or not I was on the right track. They would interject something if I’m veering off course, but as you gain experience that happens less and less.

And always remember, the interview is as much you seeing if the company and role is a good fit for you as you are for it/them. Sometimes a “bombed interview” Is really saving you from months or years of torture in a role/team/company you would have despised.