Hacker News new | past | comments | ask | show | jobs | submit login

If anyone is interested in doing a mock technical interview, please reach out, email in profile. I have interviewed developers since 2015. I’m currently a software development manager for an enterprise with a team of 4 that I personally hired, and 4 more contractors that I also interviewed and validated.

I really enjoy the process of interviewing, especially junior candidates, but companies understandably limit the feedback that is able to be provided to candidates after the fact. With a mock interview, I can go through an interview much the way I would conduct it for a real business, but I can provide as detailed of feedback as you would like and we can have a conversation after the fact about how the interview went, strengths, weaknesses, etc.

I will provide this service in 2 different ways - if you would like to keep it private, we can do it on a paid basis. If you are willing to share it with everyone else, it is completely free to you and it will be posted online. I’m hoping most people take the second approach as I feel that this could be a valuable contribution to the community. I’ll provide more details on either option if you’re interested.

Disclaimer: this is offered by me on a personal basis, and does not reflect the opinions, thoughts, beliefs, or anything else from any employer I currently work for or have in the past. This is offered purely for educational purposes with a fictitious base company, and there is no job or result from this interview other than some additional experience and knowledge.




Around 2008 the company I worked for was bought by a huge company so it worked out, but if it hadn’t we fully had a plan to get a group together to review resumes and give mock interviews. Every blip since I’ve threatened to do so and never have.

That was also the first company I ever gave interviews for, and we grew a lot so I did quite a few. To this day, one of the most surprising things I’ve learned about interviewing on either side was how terrifying being the responsible party for a hiring decision was.

I was confident about digging myself out of any technical problem I got myself into (or at least, I knew my strength, and to refuse situations I couldn’t clever my way out of). But somehow the spectre of being the person who said we should hire the new terrible coworker was daunting.

Fixing a crashing bug? No problem. Fixing someone who writes crashing bugs? Oh boy.

For quite a few years I recalled that feeling when I interviewed and it kept me relaxed. I suspect it worked better than the advice to picture the audience naked.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: