DEV Community

Cover image for How to act in a job interview
Phillip L. Cabrera M.
Phillip L. Cabrera M.

Posted on

How to act in a job interview

I recently made the decision to check out a more technology related job position at the company I work for.

When I attended said test, the first thing I noticed was that one of the members of said department was programming in JavaScript 😁 which I already started to like.

As I began the interview with the head of the department with all professionalism, she asked me if she had any idea of the nature of the position for which she was applying. I immediately told her that I vaguely understood that it was a position for a development team, to which she replied: No, here we develop a few solutions for the areas of the company that we provide service to.

It is a position whose main function is to provide support in the face of any inconvenience or situation that the systems present. In short, the position has more to do with part of DevOps but mostly it tries to be technical support, ensuring a continuous delivery of high quality in regards to solutions to possible problems that the systems present, that is. incidentally they are georeferential systems (with satellite positioning).

After having clarified that point, the young woman proceeded to do the behavioral interview on site, which she always recommends to be totally honest. I remember right now that one of the requirements for the job was to have solid knowledge of Java, unfortunately I told him that I had knowledge but in JavaScript, but if he gave me the opportunity I could learn the language and give me time for that process and so on with a technical test to check my progress.

she Finally she gave me a small technical test (exam) with the following points:

  1. Carry out an SQL query to find out the number of records from a location whose contracts have been made as of a specific date, (it should be noted that all these data were in separate tables joined by a foreign key).
  2. The second point was to put in my own words an analysis and solution to the scenario in a SQL statement was taking more than 30 seconds to complete.
  3. The last point consisted of making the necessary script in the language of my choice and that said script would do the following:
    • Read from table A records with a specific condition.
    • Enter these records resulting in table B.
    • In table B update the records with a specific condition.
    • Finally, display the square root of the highest value in table B on the screen.

After a few days, the manager of the department I was applying for wrote to me and told me, I just reviewed your technical test and as far as I'm concerned, if you are fully committed to learning Java you are more than welcome in my team.

You can already imagine my answer.👍🏽💪🏽

With this experience I encourage you to apply for any job in spite of not meeting all the requirements. The experience gained in these interviews, especially with the feedback they give you, is invaluable. So don't be afraid and apply, you never know what might happen.

Top comments (1)

Collapse
 
ant_f_dev profile image
Anthony Fung

Congratulations!

I remember one of the interviews I had earlier in my career. I already knew someone there and we were talking in a meeting room while waiting for my interviewer to arrive. It was a relaxed conversation, and I casually leant back in my seat. Then my interviewer arrived and the actual interview started.

It was a good few minutes in before I realised I was still slumped in my chair (I know, bad for posture). Remembering all of the body language advice, I slowly propped myself up, leaning ever so slightly forward to indicate interest and enthusiasm. I say 'slowly', but to everyone but me it probably looked like the most awkward posture correction ever 😁