It's a Trap! Technical Interviewing at a Startup | Startup Institute
Getting a job offer from a startup can involve many factors such as cash burn rate, staffing needs, and fit within the culture of the company. One of these factors for engineers and developers is an assessment of technical aptitude and thinking ability in the form of a technical interview. This assessment can be critical in the interview process and may weigh significantly on the decision to make you an offer. Sure, exceptions to the norm always exist, but for the most part as an engineer interviewing for a job at a startup there's going to be some form of test from a technical perspective.
After I graduated Startup Institute Boston (SIB) I interviewed at multiple startup companies in the Boston/Cambridge area before I happily accepted an offer at Backupify as an Operations Engineer. Before joining Backupify and doing SIB, I led college recruiting for my last employer. And because I've had some great adventures interviewing at startups, here's my take on what I have learned.
Why Perform Technical Interviews?
Maybe you've networked your way in the front door for an interview and you may have a great resume and a fully stocked github to show off your body of work. Why shouldn't a job offer be handed to you immediately after meeting you in person? Why do these technical interviews at all?
Here's the bottom line: talking up your skills, having a great resume and maybe even producing a bunch of awesome applications previously is great. However, as a VP of Engineering trying to hire for a junior Ruby on Rails developer for example, its hard to gauge your level of knowledge and general problem solving / thought process without asking you to solve some sort of problem on the spot.
Read full article from It's a Trap! Technical Interviewing at a Startup | Startup Institute
No comments:
Post a Comment