Finding your dream Android Developer role in the midst of a pandemic. (Part III)

Samdan Tetteh
4 min readOct 24, 2020

The Technical Test

This is the part of the requirement process where your problem-solving abilities are tested. Different companies have different ways of accessing you during this stage, some of the options you can be provided with are:

  • Online Test/Pair Programming - This approach is usually taken by large tech companies who are usually looking for developers to hit the ground running and solve complex problems they face on a daily basis. As a candidate, you are usually paired with a senior developer where he/she presents you with a problem and examines how you go about solving this problem. This could be a question involving a sorting algorithm, a basic android list implementation, or you are presented with a codebase in which you will have to fix bugs, as I had in one of my experiences. The interviewer is looking at the steps you go through in solving this problem. I suggest you look into ways developers are expected to solve problems and do well to follow these steps.
  • Offline Test- This is where you are given a real-life problem in the form of building a simple mobile application. You are given a deadline or you are asked to present your finished work when you feel it is done per your standards. The key here is to present a production-ready code that follows development standards such as Clean Architecture and SOLID principles. Make sure your finished code is well documented, you have written automated tests to test out your logic and User Interface, and don’t forget to include a well managed README.md file that explains the work done.

Try not to schedule this stage as soon as you are done with the previous stage unless you feel confident. I will suggest you register with platforms such as HackeRank, DevSkiller, etc. Also look into other ways to help you prepare.

Culture Fit (Final Stage)

The final stage interview is when you bring it all home and land your dream role. Remember it is not done until you receive an offer from the hiring company so don’t take the final stage lightly. From my experience, developer final stage interviews can take three forms and will usually last between two to three hours depending on the hiring company, the role you are applying for, and possibly the number of candidates involved at this stage.

  • System Design(Whiteboard session) - The most usual question asked at this stage is “Talk about a mobile application you have worked on and explain how you designed it”. Some companies can also ask you to explain the design behind the test application you were asked to work on during the technical stage. This is where mobile architectures such as MVP, MVVM, MVI, MVVM/i, etc. come in. Make sure you understand the differences between at least three of these in terms of testability, the abstraction of code, and the drawbacks of each architecture. I have learned the best way to do this is to code a simple application using these architectures.
  • Agile Methodologies - Most tech companies if not all, build software products using the agile software development process. Therefore they have already structured agile set-ups and are looking for someone with some experience working in an agile team. This is so not to slow the development team down once he/she joins. You can be asked questions such as, “Which members in the agile team are involved in the product backlog refinement process” or “If a ticket is not completed in the sprint what do you suggest should be done in such a scenario”. Make sure you research on agile methodologies and all of its ceremonies.
  • Behavioural Questions - This is when you show you are a good fit for the company. Companies know “techies” can be reserved and don’t like to get involved. From my experience, the best candidates that get hired are those who show they can work well in a team, are enthusiastic, share ideas and suggestions they believe can benefit the product and company as a whole. These questions are designed to help the interviewer determine such characteristics. There is a lot of material online to help you with such questions. However, I would advise you to answer all questions at this stage with the STAR method with examples backing your answers. Relate your answers to your past experiences and the role you are applying for.

One thing for sure is you do get better at interviewing the more you do it. The quicker you are willing to learn the quicker you will land your dream role 😀. I will end this series with some key points:

  • Be Positive - Find the right tone in which to present your positive aspects. You have to talk about your achievements to show you are the right person but try and do it without being boastful.
  • Questions - Always make sure you have at least three to five intelligent questions to ask the interviewers. It’s best to avoid questions around salary, benefits etc.
  • First Impressions - It goes without saying that first impressions always last. Make sure you wear your smartest outfit, turn up five to ten minutes early (never earlier…or later!) even for an online interview.

At this point, I would like to wish you all the best and good luck in landing your dream role.👏🏽

--

--

Samdan Tetteh
0 Followers

Software Engineer (Mobile) @ Whitbread UK