- 291 words -
I've been a software engineer at Dashlane for a bit more than two years now and amongst the different things that I enjoy in this job there is the fact that I am trusted to lead technical interviews for candidates joining my team and sometimes other teams.
I never had the opportunity to be on this side of the interview table before so for me it was a great challenge to learn how to lead a technical discussion while assessing the skills of the person being interviewed.
I believe that after two years of interviewing and more than 40 interviews (and counting!) I grew the skills to be a good technical interviewer. So I decided to write a series of two articles to help other software engineers to become great interviewers. These articles are now published on Dashlane engineering blog 🎉
The first article How to create a good problem solving interview focuses on the strategy to create a problem solving interview which is interesting for the candidate and allows the interviewer to assess the right skills and compare candidates on objective data.
The second article Becoming a good technical interviewer focuses on tips for people who never lead an interview before and who might -like me- have doubts about how to start doing it the right way.
I'm quite proud of these pieces of writing because I think there are some interesting information which can be useful to a lot of people. Also it was a great opportunity to see how much proofreading by native English speakers my writing needs, which makes me think that the articles of this blog are most probably filled with weird sentences and terrible grammatical mistakes. But hey, I'm doing this for fun so... 🤷
No other posts in the category [interview]