Tackling The Coding Project

How To Tackle Your Coding Project

Welcome to Day 3 on our series on how to nail your frontend interview. As mentioned in day 1 we are going to talk about each phase. If you haven’t read Day 2’s article Click Here

In this part of the series, we are going to talk about the coding project, also known as the coding assessment. You usually receive this after your resume is shortlisted amongst the dozens of others. Do not take this part of the process lightly because you are likely competing with other people for that exact role, and usually, there are about 1–3 roles available.

What to Expect From a Coding Project?

This varies with the position you are applying for. You are most likely to get a project based on the work you are going to be doing at the company. For development, we are mainly tasked with building full-working apps, each with its own requirements. Requirements are the tasks you are expected to achieve. It is important to follow these requirements to the letter and not create your own requirements when doing the project. I know that as developers, we can be creative and innovative, but when giving specific requirements, it is important to keep to what is needed and what is not. I hate to bear bad news, but when you are working, you will rarely be awarded for adding extra features that are yet to be approved.

How Long Is The Project?

Once again, this varies with the position and the company you are applying for. The duration is usually 2 hours to 2 days; for some, it can even be up to a month. I suggest starting early for the longer durations; this gives you enough time to test your project before submission. Also, note that it is important to plan your tasks. I suggest you use task-managing apps like Jira, Backlog, and Clickup.

General Tips

• README file, always add a comprehensive readme file that explans your project and its purpose.
• List of packages used.
• List assupmtions and decisions in bullet point format if there are any.
• For frontend devs make sure your app is responsive.
• Ensure your code is organized and readable.
• Comments should explain why and not the code.
• Use linters and fomatters.

Thats all for this post Tchau 👋🏾