The Famed Technical Interview
What the technical interview is really like for Software Engineers…
As you may know by now, I’m a NYC kid through and through. I went to some of the most diverse schools in Brooklyn from kindergarten up until college. This diversity is not only in race, but also ethnicity, socioeconomic background, and passions. So naturally as an adult, I know people in many different career paths. This includes medicine, entertainment, business, and so much more. The thing about the software and technology path is that it is such a new space for one to make a living. As a result, many people have no idea what it’s like to work in this space or even what to expect when trying to make it in this space.
I’ve interviewed with dozens of technology companies from FAANG (or MAANG) to financial companies to the most niche startups. So everything I share in this post comes from my personal experience during the process as well as stories I’ve heard from my colleagues and friends. In this blog post, I’m going to break down one component of the process to getting your foot in the door of a technology company. The component that there are the most complaints about. Everyone’s worst nightmare. That is… the technical interview. You’ll become very intimate with what to expect on the three sections of the interview: Behavioral, Technical, Reverse Interview
Behavioral Section — 5 to 20 minutes
Good afternoon! My name is Chuma Steve Okoro. I’m a Nigerian-American problem solver based in New York City. This is how I start almost every interview because they always start the same with some form of introduction. It makes sense too because you’re talking with someone you’ve never met before so naturally, you’d introduce yourself. Often times, interviewers like to start with something along the lines of “Tell me about yourself and your background”. Some things to keep in mind are:
- This is a technical interview, so make sure you share something about your technical background
- Your interviewer is a potential…