Getting a coding test for a position can be thrilling! It can also be terrifying if you don’t know what you’re doing.

Don’t fret! Even the least experienced developers can make a way. For more on this, check out the video at the bottom of the page.

A viewer named Block reached out to me for advice on a coding test. They were working with Google ARcore, a technology used for augmented reality.

Block didn’t have enough exp with this technology and they ended up with a series of bugs in their coding test. They really wanted this job, but they weren’t sure how to proceed. In the details below, I’ll be addressing Block but this applies to any coding test regardless of your expertise.

1. Take Notes!

The first thing I suggest is make note of these bugs. It sounds like you’re not too experienced with ARcore, yet. If you’re looking to specialize in this area, these bugs will give you a starting place to study.

You can research these bugs and learn what caused them to occur. Don’t expect to understand it 100%. This is just an exercise to get you in the headspace of an ARcore developer.

2. Steal Your Code!

Okay, technically, you wrote it so it isn’t stealing. But the next thing you should do is Copy/Paste your code somewhere else for later.

You can tinker with it and figure out where you went wrong at a later date. This also fits in with your research from step 1 since you can learn to debug those issues from earlier. With this, you have a leg up on others who are just starting with the technology.

In fact, you can use this as a talking point in future interviews. Interviewers want people with passion and if you can explain how you single-handedly debugged a major error, you’ll appear more knowledgeable (which you are!)

Additionally, you can reach out to the company later down the line and let them know you figured things out. They may give you another shot.

3. Write a Report

Let’s say you’re running low on time and don’t quite have the flexibility to research a fix. In your code submission, include detailed bug reports on these problem areas. For each bug, include:

• Expected functionality
• What actually occurs (the bug)
• Steps to reproduce
• Additional notes

You might not have all the skills to fix them in time for your submission, but at the very least show them you’re willing to learn and do the hard work. They might offer you an entry level position if you can show them your potential.

4. Write Your Ideas!

For the last tip, let’s say you have no idea what you’re doing with this code. Don’t be afraid to use pseudocode!

Try to come up with an abstract solution you can explain with words instead of code. Provide notes on each step needed and be as detailed as possible.

The goal of these tests is to show your thought process, not just find the right answer. If you can explain your methods, it might land you the position over someone with the hard skills.

I landed a position at a company with this same method. The engineer in charge of hiring even told me later on that they picked me over other applicants because of my technical interview.

While I didn’t have as much technical skill as most of the applicants, I was the only one to provide a clear overview of my solutions. I didn’t know how to build it, I knew what was needed and sometimes that’s what counts.

5. Have FUN!

Above all else, my final FINAL piece of advice is to have fun with it! Don’t get bent out of shape over a coding test. Even if you don’t pass, you won’t miss out on anything.

Take your time, do what you know, and find a good explanation for the rest. For more on this, watch the YouTube video below.

Join the mailing list to see updates like this every week!
Coding Fanatic

Sources

Image by JohnArtsz from Pixabay

Image by Steffen Salow from Pixabay

Image by Photo Mix from Pixabay

Image by Free-Photos from Pixabay

Image by Free-Photos from Pixabay