3 ms·
I have a job at a startup as a software engineer. I waded through dozens of interviews like Sahat's. "Do whiteboard problems," "solve this benign algorithm prob
by abustamam 11y ago
I have a job at a startup as a software engineer. I waded through dozens of interviews like Sahat's. "Do whiteboard problems," "solve this benign algorithm problem."
The two job offers I did end up getting went something like this:
1. "Show me a project you worked on. Tell us about it. Tell us about future features. Okay, implement one of those features right now."
2. approaching me after an event I spoke at "Hey, are you by chance looking for a job? We'd love to have you with us." at "interview" "tell me about your past experience, some projects you worked on, and how you learn new things."
I feel like both of these "interviews" tackle two very important things as a software engineer--can you use what you currently know to add a new feature? And if you don't currently know it, do you know how to find it out?
I didn't know a lick about React, SVG, animation, databases, lodash, es6, or trees, before I started working at my current job. But because they were able to see how quickly I could learn new things, I started as a contractor (to "test the waters" so to speak) and impressed them by proving them right.
And I think that's exactly what companies should strive for--hiring people who can pick things up quickly. Of course, consulting firms may not have this luxury, because they need to deliver now now now, but for SaaS companies, I don't see why this method wouldn't work.