Dear new developer,
Interviewing is a two way street, and that means that you need to be evaluating your employer as much as they are evaluating you. Yes, you need a job, but your employer needs your skills. It’s also important to note that you’ll never have as much leverage with an employer as you do before you are an employee. You are going to spend a lot of waking hours working on behalf of this organization. Learn something about it.
Interviews are hard to do well. They are designed to extract as much information as possible from the candidate for the employer to be able to make a good decision. Good employers want the exchange to be bi-directional and will take steps to make that happen, whether that is publishing blog posts about the internals of the company or allowing plenty of time for questions or allowing access to individual contributors on the team.
Sometimes the biggest hints about how you will be treated come out in non verbal communication:
- is the interviewer prepared
- do things start on time
- is it a real conversation or a grilling session
- does the interviewer appear happy
- do they do what they say they are going to do during the interview
- are they flexible during the interview
- do they respond to questions
All of these can add up to paint a picture about the company and the position. Note that none of these are related to the actual work you’ll be doing. That is important as well, but the context in which you do the work is crucial. If you are being paid $200k/year to do a job that makes you miserable, you will likely be unhappy. If you are paid $100k/year to do a job with a team and a project that you enjoy, you will likely be happy. (This assumes that you can live well on either $200k or $100k–feel free to double the numbers if that isn’t the case).
You will never be in a better position to leave a job than before you start it. That is the right time to make sure the information exchange is not one way.