This morning I attended my first job interview during last 2 years period. I hadn’t arranged it before because I was pretty happy working for my current (still or yet) employer. Actually, I’m working for a large nation wide chain of supermarkets. If your are so curious to know it name you can find it out from my resume.
My start point is:
E0 - my current employer,
S0 - my current salary.
My goal is: to find a new job with more opportunities to become a high skilled Java developer with higher salary.
[TODO: compose a short post about: why do I want to change my current work place, what I seek and what I expect]
To achieve the goal I decided to apply for a set of open vacancies in well established western companies, then attend a few interviews and choose an employer that fits my needs best. As I mentioned before, today was my first meeting.
I’m eager to write down my fresh feelings and emotions because I’m afraid that after a while I forget it or become less interested in analysis of my mistakes. All names of persons and companies are hidden under faceless variable names.
I’m not going to show my attitude to any of employers I’ve dealt with. I’d rather like to investigate my own mistakes, to analyse my actions which potentially could be done in a better way.
What had been done before:
- arranged my resume
- reviewed OO basics, GoF design patterns
- reviewed Java core by reading Bruce Eckel
- have read a first part of the famous book about modern trends in interviewing techniques How Would You Move Mount Fuji?
- have taken a bunch of extremely useful advices from my IT friends (special thanks to Alex Getman)
- read inspirational articles about successful behavior during interview like Top 10 Interview Questions
In spite of great previously planned list, I honestly listed here only those items which I really managed to review.
On the interview
It took near an hour while I was talking with my potential team lead and project manager. To reveal my oral skills I was asked to describe my Master’s Degree thesis. It was my great mistake not to prepare for it. I was going round the mathematical problem and even didn’t said that I developed quite complicated Swing GUI application using Matisse and my custom Chart component. I didn’t touch on interaction through file system of GUI part with program which implemented a mathematical algorithm and written in Fortran. But interviewer swallowed it
I was doing my Diploma for so long, therefore if I had been prepared for describing it in English today’s morning It would have been my star time. But I haven’t used this incredible chance.
After this tet-a-tet conversation with a project manager we were joined by an team leader. The team leader changed our topic into more technical one. I was asked a few technical questions: hash tables, transactional isolation levels, Ant, some theory like coupling and cohesion, RDBMS indexes (B-tree,…). But I wasn’t asked questions about lots and lots of my strong sides like multithreading, design patterns etc. I didn’t show my analytical attitude in problem solving and wide programming background. The only one reason of such a pity situation is that I didn’t capture their attention and didn’t lead them into my way.
To sum up, I’d like to say that as I understand (I haven’t received their decision yet) the overall effect that I’ve made is quite well. But it was from a point of view on a freshmen, a recently graduated student who are willing to start as a Junior Developer. And as long as I consider myself as an experienced Developer I must learn all my strategical mistakes and get rid of them. I’m feeling that I haven’t revealed all my good qualities. The total effect wasn’t as good as, of course, it could be, in spite of the level of my preparedness. I’m little bit disappointed.
And as a result of my analysis I figured out a few notes: (I suppose, this list as an incomplete and open for extending)
Strong sides:
- I made an appointed at 9 a.m. when it’s not too hot in the office, it isn’t overcrowded and people are fresh. I was on time, I hadn’t got troubles with transport and wasn’t nervous as I could be in case I was in hurry.
- I wasn’t nervous about my English conversational skills because I knew that I could more or less clearly explain what I think.
- I have got quite a lot of developer’s experience and read lots of smart books which encourages me
Weak sides:
- I hadn’t written a cover letter which would have positioned me as a mature Developer, not as a student as I was seemed afterwards.
- My resume was transferred via ICQ as a link to my Internet page, so it didn’t lay on the table to HR manager, and wouldn’t stay there. Moreover, it was in plain html what is good for the Internet and open source community, but not for an office manager who don’t know how to print it.
- When interviewer brought the printed resume, one major page was missed. I had got an extra copy with me, but I didn’t offer it. Probably I forget to do it because I printed it on a home level ink-jet printer.
- The resume was, mainly, copied from my academic CV. It caused overloading of information about my education and wrong order of paragraphs. The main part which is obviously interested to an employer was hidden in the forest of my diplomas.
- I hadn’t prepared a brief, clear and impressive messages about almost certainly asked questions: my diploma thesis, my current project, who am I and so on. You know, interview shouldn’t be an improvisation rather a well prepared acting.
- A big pause after I was asked about my salary expectations in a year period when I’ll probably become a Senior Developer and hilarious arguments to defend my position. It was something like this:
based on current market affairs and on level of salary which I’m gaining now and on the offer of increase which I’d be offered by my current employer if I told boss about my
decision to leave company, bla-bla-bla-… BIG PAUSE (I was trying to don’t make mistake and don’t say 8$$ instead of 9$$
)
Don’t rely on interviewer’s telepathic skills, when you are saying something, try to ask yourself what of your positive side do you try to show!







