Rapid Fire and Fresher Round Questions
Fifty short questions with one line answers, plus the questions asked specifically of freshers and career changers.
- SQL Interview
-
HTML Interview
- HTML Interview Questions: Fundamentals
- HTML Interview Questions: Forms, Tables and Media
- HTML Interview Questions: Semantics and Accessibility
- HTML Interview Questions: SEO, Performance and Tooling
- Scenario Based Interview Questions
- Rapid Fire and Fresher Round Questions
- Live Coding and Project Explanation Rounds
The rapid fire round
Some interviews open with a fast sequence of short questions to establish a baseline before moving on. The answers are one line each, and hesitating on several in a row sets the tone for the rest of the interview.
Questions only. Practise these until each answer is immediate.
- What does HTML stand for?
- What does the doctype do?
- Name three void elements.
- Difference between
idandclass? - How many heading levels are there?
- What does
altdo? - What does
<br>mean semantically? - Difference between
ulandol? - What is
dlfor? - Which element makes a link?
- What does
target="_blank"do? - What must accompany it and why?
- What does
rel="nofollow"mean? - Difference between
thandtd? - What does
colspando? - What gives a table its accessible name?
- Which attribute is submitted with a form field?
- Difference between GET and POST?
- What does an unchecked checkbox submit?
- What groups radio buttons?
- What does
requireddo? - What does
readonlydo differently fromdisabled? - Which enctype is needed for file uploads?
- Default
typeof a button inside a form? - What does
deferdo? - What does
asyncdo differently? - Where should a stylesheet be linked?
- What is the DOM?
- Difference between
textContentandinnerHTML? - Which is safer and why?
- What is
querySelector? - What is event bubbling?
- What is event delegation?
- What is
mainfor? - How many
mainelements per page? - What does
navdo? - What is a landmark?
- What does
aria-labeldo? - First rule of ARIA?
- What does
tabindex="-1"mean? - What is a skip link?
- Minimum contrast ratio for body text?
- What does
loading="lazy"do? - Where must you not use it?
- What does
srcsetdo? - What does a canonical tag do?
- Difference between
robots.txtandnoindex? - Name the three Core Web Vitals.
- What causes layout shift?
- What does
<meta charset="utf-8">do?
Fresher and career changer questions
These come up when you have no commercial experience. They are not trick questions; they are testing motivation, self direction and honesty.
- How did you learn HTML?
- Walk me through a project you built. Why did you build it that way?
- What is the hardest bug you have solved?
- How do you find out how something works when you do not know?
- What do you do when a page does not behave as you expected?
- What is the last thing you learned about the web?
- Which parts of front end work do you find most interesting, and why?
- Have you used a screen reader? What did you learn?
- How do you know your markup is correct?
- What would you improve about the first page you ever built?
- Do you follow any specifications, documentation or standards sources?
- Tell me about a time you got something wrong.
- How do you handle feedback on your code?
- What are you working on at the moment?
- Where do you want to be in two years?
The one that matters most
Walk me through a project you built.
This question is asked in almost every junior interview and it is the one candidates prepare least. Prepare a three minute answer covering:
- What it is and who it is for. Twenty seconds.
- Three specific technical decisions and why you made them.
- One thing that went wrong and how you fixed it.
- One thing you would do differently now.
The last two matter more than the first two. A candidate who can say I built the filter with hidden classes and then found the filtered items were still in the tab order, so I switched to the hidden attribute has demonstrated more than any list of features.
Preparing properly
- Build something real and deploy it. A live URL beats a description.
- Know your own code. Being unable to explain your own project is the fastest way to fail an interview.
- Practise out loud. Answers that are clear in your head come out badly the first time you say them.
- Prepare the negatives. The mistake question, the disagreement question and the weakness question all come up.
- Have questions ready. Not having any reads as not being interested.
Practice
- Have someone ask all fifty rapid fire questions. Aim for under ten seconds each.
- Record your three minute project walkthrough and listen back.
- Write down your answer to the mistake question and practise it until it is comfortable.
- Prepare three questions to ask the interviewer.