I created some study notes for my interviews in early 2017. I’ve posted them to Github so that others can benefit from it. These notes are specifically for theory based Java interviews, typically done in service based companies (as opposed to coding based interviews done in product companies). Hope it helps.
Hit me up in the comments for if you wish to have more topics added, or for any updates.
Table Of Contents
Design / Clean Code
Experience hosting interviews
In my current organization, I have been taking interviews for last 3 months to fill a few open positions in our team. I have filtered 100s of resumes, have had ~20 telephonic interviews and ~4 face-to-face interviews.
As it might be clear from the statistics mentioned above, the ratio of the resumes filtered seems very low. After going through 100s of resumes, they start blending together. One of primary reasons for that is the way candidates write resumes.
I’d suggest candidates to follow these tips to make their resumes stand out:
- Resume length should ideally be 1 page, maximum 2 pages. Most of resumes I see are more than 4 pages!
- Don’t write summary section. 1 page resume itself is summary of your skills & career.
- Don’t write objectives. I have observed that all candidates write similar objective.
- Don’t write detailed description about client companies. It is your resume not the client’s.
- Don’t write detailed description about project itself. Whatever the project, your individual contribution to it is more important.
- Write about tasks you performed, and not about roles & responsibilities you had.
- Write about impact of the tasks you performed (preferably with some statistics). Eg: Improved performance of application by 15% by re-architecting the cache layer.
- Don’t write your detailed address (though do mention the city), marital status, religion, passport details etc. These details will be asked for by HR during onboarding process.
- Education and Projects should be mentioned in reverse chronological order (with more information about recent projects and least about the oldest ones).
- Check for spelling mistakes, spacing errors, case issues. It should be apparent how much care and effort you have put into it.
- Share your resume as PDF to retain your formatting. Different versions of MS Word will screw up the formatting.
It pains me that candidates are missing out on interviews just because of these basic mistakes. In the end recruiters have no way to segregate candidates if there is no objective data available. On the other hand, team members like me have limited hours in the day to take screening interviews just to understand candidates’ skill-sets.