Preparing the scenario
Before moving to Berlin and before I started to actively look for jobs, I started running mock interviews Some interviews were for jobs in Berlin, some were across other cities in Germany. After doing several dozens of them of those, here are 9 tips for developer interviews that I can give.
This means I didn’t only accept calls from companies in Berlin but all over Germany. At this stage, I wasn’t applying anywhere, but was only accepting recruiting calls. And I decided to try to do my best as I was really ready to accept the offer and relocate the next day.
9 tips for developer interviews:
- Almost every company has switched to micro-service architecture and using Docker and K8s. Elastic stack and Terraform are present in some companies, but many are not.
- Understanding Jenkins and basic usage is a must, but for some companies, developers are the ones also in charge of Jenkins configuration. Id’ say around 20-30% of companies require developers to be actively engaged in the OPS part of the business.
- All API’s are RESTful and none of them asked about GraphQL
- Even if the ad says “full-stack” and you are a backend developer (like me) you have a shot. Simply do the tasks that are backend-related and ignore the frontend. Of course make sure to communicate that with the recruiters.
- Don’t try to be a smart-ass and do an MVC approach instead of REST simply because you don’t know any JS framework and you wanna impress them showing that you went one step further providing an actual GUI that the user can click. They’re not searching for that… they wanna see your understanding of the REST principles.
- Have readme-files always. Have the methods documented. If you can’t invest 10-15 minutes to make your readme file look nice then what are the chances you’re code will be nice?
- Unit tests are a must. This should go without saying but in today’s world, I’ve seen a lot of companies and developers not writing any tests. That’s a waste of time, resources… I could build a new feature in the meantime… you know, the classic excuses. So let me repeat myself again: TESTS ARE THE ONLY PROOF YOUR CODE WORKS. You clicking on stuff and the result turns out to be something you expected can just be a happy coincidence.
- Just because you never used all of the technologies they have written don’t be afraid. Nobody in their right mind can expect that you have a working knowledge of everything they need. You’ll learn a thing or two along the way.
KISS & Recap
⇐ Click left or right for another interesting read ⇒