Failing Interviews

Two weeks ago I attended an interview for a junior Java Developer at a Financial Software company. It was a long and tiring day interviewing as part of a group interview and in the end I didn't get it. But wanted to share my experience if it might help someone or have had a similar experience.

I arrived at 8:30 for a 9am start, first we were given a high level overview of the company and what the software does. First time i've encounter B2B car and asset finance so everything was new. Then we were given a two tests to take one was numeric dealing with charts and percentages and the other verbal reasoning. We were not allow enough time and didn't get the numeric test done and never touched the verbal reasoning. I took this as try to put us off before the real tests began.

Next we were split into two groups, one did a coding test which i was in and the other a one-on-one interview. The Coding test was implementing the Fibonacci sequence and use JUnit to test. I got the test done quickly but did not give the best solution which was to use recursion. Just could not think how it could be done given the method signature. I moved onto a written SQL test which was easy and then there were a few more tests if we had time. I felt I did good even if it wasnt the best solution. I then went into the one-on-one interview, although they did not give away too much I also felt i did good.

During the lunch break i googled the fibonacci question and was simpler than i expected so was a little disappointed with my answer. This came back to haunt me in the group interview after I was advised i made it to the next round. I was asked how I could prevent an overflow but could not give a good answer. not sure what else could be done other than use a double instead of a int for the value.

The group interview is where it went from good to bad, they really started honing in and asking specific questions about test, performance and database questions. Seem they wanted to keep asking until I failed.

In the end they said they went for someone with more experience. fair explanation but given the recruiter said they wanted someone more junior because they are paying lower. Yet they go for someone more experienced. Also seem strange that say that a junior will do the same work as a senior from the start but want a junior.

I don't want to seem like sour grapes but I'm not sure if they were just looking to hire someone more senior and pay less, but not so senior that they would turn down the salary. No point dwelling but was hoping to get more feedback to help improve my study plan. The interview made me not want to touch code again because it was honestly tiring and now wondering if i'm cut out for this or giving up too easy.

I plan to get back to coding and may try some Python after the up coming public holidays. for now I'm trying to figure our what to do next and come up with a plan.