Engineering interviews at Fruugo.com

I have been conducting a large number of software engineering interviews lately and wanted to communicate five points that will help you.

As part of Fruugo's online interview, candidates are required to walk me through their solution to our Java tech challenge. In your explanation, a good place to start is the requirement as this is the context for your solution.

The interview invite explains what is going to happen in the hour-long session that is the last stage of a three-stage process.

Therefore, to present yourself in the best light, it is an excellent idea to remind yourself of your code before the interview. You may have forgotten some of its nuance and any points that you would like to highlight.

I remain surprised at how many people have clearly not read the interview invite. I know that people are busy with a lot going on, but winging-it is not a good idea when a new job depends on your performance. You will stand out if you prepare.

To prepare, read the interview invite to be fully aware of what you will be expected to do. If you have any questions, ask. Practice explaining your solution.

Also, test that you can present your code from the computer you will use during the call. Become familiar with how to use Google Meet and its screen presentation feature. This familiarity will help you settle into the interview.

I recommend you start Chrome (this seems to work best with Google Meet), create a Google Meet session, join it, and present your screen. This will help you. I have seen permission issues that you will want to resolve beforehand.

An interview is a two-way street, and the best ones are more like conversations than question-and-answer sessions.

When answering questions, I prefer a yes or no answer followed by a concise elaboration.

If the question is about experience that you do not have or which is not a focus in your current role, say so, and concisely elaborate to relevant experience that you do have.

I do not hire for tools experience; I hire for knowledge of fundamentals and potential.

Therefore, I will not ask a question such as when were generics introduced in Java? I am more likely to ask why generics are useful or what the benefits are of automatic garbage collection.

And lastly, do not distract yourself in the interview. Please turn off Slack and silence your phone.