Featured

Why 98% of NEW SOFTWARE DEVELOPERS don’t get Job Offers...



Published
Important things every new software developer should be doing during job interviews. No matter what happens, just remember that getting rejected might not be your fault. There are plenty of bad interviewers out there. Try not to take a rejection personal.

WATCH NEXT:

What I would do starting over: https://youtu.be/glgmavKWg3Y

My dev job salary history: https://youtu.be/QILxmJpH6wM

0:00 Software dev interview tips 1 & 2
2:06 Software dev interview tips 3 & 4
3:11 Software dev interview tips 5 & 6
6:14 Software dev interview tips 7 & 8
10:45 Software dev interview tips 9, 10, 11

Did you spend too much time on leetcode instead of building a portfolio. This is kind of a tricky one to balance. Spending a lot of time on leetcode can definitely help you develop problem solving skills that can help with technical interview questions. But this doesn’t mean you can build applications.

What we do day to day is build applications and for me personally, I would much rather hire someone who can demonstrate that they can build apps over someone who has memorized solutions to tons of leetcode questions. But admittedly, software development interviews are kinda messed up in a lot of ways. A lot of what you encounter comes down to the people doing the interview. Even teams at the same company will often do things differently.

For example, is the interviewer more into discussing everyday situations and code problems, or have they bought into the cracking the code interview book paradigm?

I think the low level algorithm approach is often flawed because most of us don’t have to regularly do some of this.

The programming languages we use often have builtin utilities to do this stuff or we use libraries or in the situations we do have to come up with an algorithm, we usually have plenty of time to think through it, whiteboard it, plan and code it without the pressure of some stranger looking over our shoulder to see if we would do it like he would in a short amount of time when he has probably had lots of interviews to refine and think about the problem.

That said, this is one of the competitive advantages of leetcode experts and recent college grads who memorized some of this stuff for quizzes. But even CS grads usually forget a lot of this stuff and have to brush up when they know that they will be doing a tech interview at a company that asks these kinds of questions.

I know plenty of senior software engineers who’ve been rejected for a job because they stumbled on an algorithm problem they haven’t thought about in twenty years. But sooner or later you’re going to end up in these kind of interviews. You’ll win some and lose some so don’t take it personal.

I’ve received lots of job offers and I’ve lost some because I didn’t quickly solve a set of algorithm questions that had nothing to do with anything I’ve ever worked on.

To make things more confusing, there are a bunch of ways to do algorithm tests. You might have to write it out on a white board. This can suck because you run out of space. I mean, outside of interviews I rarely write code syntax on white boards. Most of the time I use a white board to map out concepts and relationships not write actual code.
Category
Job
Be the first to comment