3 Great Technical Questions to Ask Your Junior Front-End Engineering Candidates
Senior engineers are hard to come by–so many companies have started to focus on hiring junior developers to train up rather than pay the hefty price tag for intermediate and senior developers.
However, hiring a good junior front-end developer isn’t as simple as having them solve an algorithm question on a whiteboard.
We’ve previously talked about how important it is to develop interview questions that accurately assess skills and match the candidate’s experience – but what does that look like for a junior front-end developer?
First and foremost:
Does the question represent an actual task the candidate would do on the job?
Computer science trivia or algorithm questions almost always are a poor reflection of what a candidate would actually be doing on the job AND it will bias you more towards candidates with a traditional academic background, drastically reducing your qualified candidate pool.
Some potential skills to think about when you create a question for a junior front-end developer:
- Can they use math functions correctly for displaying HTML elements?
- Can they resize images like pictures and bars in a bar chart?
- Are they able to communicate the rationale behind their design decisions?
Your interview questions should depend on the specifics of your business, but you want to focus on the junior engineer’s ability to carry out basic UI development.
With that in mind, here are three questions we’ve seen be successful in junior front-end engineer interviews:
Bar Chart Challenge
In the example question below, ask candidates to render a simple bar chart from a given data set. They don’t have to collect the data themselves (that’d be a more advanced task). Provide it as a JSON variable, which the candidate should know how to access.
This question is helpful if your junior developers would be working on any usage chart or dashboards while on your team. It’s also a good challenge for an entry-level developer with no professional coding experience to evaluate their different front-end skills.
When you create a question, you should also define the success criteria. This will allow you to quickly evaluate the candidate when the interview is finished and reduce bias in the interview process because you’re using the same success criteria for each candidate.
The success criteria for the Bar Chart challenge are as follows:
- Good implementation – Candidate just uses the counts as a pixel width
- Better implementation – Candidate calculates the percentage of cell width from count / total words
- Best Implementation – Candidate calculates the cell width percentages against the highest count
Web Developer Challenge
This one is suited for entry-level web developers.
Have them build a simple login page that contains some basic form validation. It again assesses baseline HTML/CSS/JS skills to reflect what they’d be working on in pretty much any web developer role.
The design requirements are also a bit more open-ended than in the Bar Chart Challenge, which allows you to discuss design decisions more in-depth if that is a priority for you.
Because of the open-endedness of this question, the success criteria are also a bit more open to interpretation. You can refine them further to fit the needs of your team better:
- The candidate follows the instructions
- The code is clean and readable
- The candidate can work with loosely-defined tasks
✅ Don’t forget to ask the candidate questions about their code during the interview! Turning the interview into a discussion can reduce interview stress and get more insight into the candidate’s thought process.
CoderPad Playback Challenge
And now, an interview question directly from our playbook. This is a slightly more complex challenge and may be more suitable for a junior dev with a year or two of professional development experience.
We ask the candidate to recreate part of one of our key features, Playback Mode, which allows interviewers to review a candidate’s work in a pad.
The candidate must create a function that reads a series of timestamped JSON data and returns the playback state.
Here are some success criteria you can use to develop a rubric for your version of the question:
- Is the output correct per the respective timestamp?
- Did they understand the data structures in the challenge and minimize iteration over those structures?
- Did they manipulate the strings in a straightforward and understandable way?
- Is the code well-organized?
The best interviewing format & other resources
Selecting the right question for junior developer candidates is just one part of setting up an excellent interview operation.
You can improve the process by creating an iterative interview exercise that has a candidate working on a take-home project by themselves. Qualified candidates then move on to a live coding interview where they build on the work they created in the take-home project.
We dive deep into this particular process – and how to combine it with pair programming to create an even better interview– in a blog post that you can find here.
✅ Don’t forget that there are many things even good junior developers may not know yet. If there is something they struggle with during the interview, teach them about it! Even if they’re not the right candidate for you at the moment, you’ll help them learn something new and they’ll have some good things to say about your company in the future.
We also have the following interviewing resources available for your reference at any time: