Hello everyone, I took a few notes about what's important to my eyes when going through HR interviews processes for dev jobs, this list focuses on soft skills; consider it as a pre filled form that you must have written and memorized before the interview (even better if you can have it under the eye during the interview):
- prepare your lowest and highest desirable salary/rate and stick to it
- don't sell your expertise way lower than your market value just to get a contract, this might raise suspicion and produce the inverse effect of not scoring the gig/job
- generally interviews start with a round of personal presentations, be sure to know your own and be fluid with it; you should spin your personal introduction in a way that is never negative
- make an inventory of your strengths as a person so you won't have to stutter when the HR interviewer asks you to list some
- if the inventory of your strengths is long (the more the better, don't be shy), then identify the top 3 and be ready to elaborate on them with precise examples
- make a list of your top professional successes
- make a list of the top 3 inspiring persons you know of (whether they're famous or not) and why you qualify them as such
For me the most important thing, whatever language/techno is used in the position you're applying for, is:
- KNOW YOUR ALGORITHMS
- KNOW THE DATA STRUCTURES that are used in the language you'll be tested in (linked lists, maps, sets, etc.)
- KNOW THE SPECIFITIES and the main concepts of the language you'll be tested in (multi or single threaded, event loop, etc.)
- KNOW THE MAIN DESIGN PATTERNS that are used out there (singleton, factory, observer, etc.)
There are several platforms that will allow you to be comfortable with timed tests (I hate those) and to get used to the kind of questions and environment you'll be working on before diving into the actual test, for instance:
If you do all that, it's great to be able to show your technical skills; but, still, you'll need to be convincing on another aspect: oftentimes recruiters expect from you to know what real-word problem the organization in which you're applying for a position solves.
It sounds obvious but: do research the organization/cie you're about to meet. Get to know the main aspects of their business, from a general perspective; even better, try to use some of the expressions of the lingo that organization uses every day !
I'll try to update this list as I go along... feel free to add in to it in your comments !
Top comments (0)