My First Interview in 3 Years — Senior Software Engineer (Frontend) at Headout | by Yashpreet Bathla | May, 2026 | Medium

Overview

A senior frontend engineer documented a 3-round interview experience at Headout for a Senior Software Engineer (Frontend) role — the candidate's first interview after 3 years at a single company. The loop covered a recruiter screen, a vanilla JavaScript machine coding round, and a 1.5-hour frontend system design round. The candidate was rejected but received unusually detailed, specific feedback, which the author describes as rare and valuable.

Role & Compensation Details

• Position: Senior Software Engineer — Frontend
• Company: Headout
• Outcome: Rejected ❌ (with detailed written feedback)
• Context: Candidate's first interview after 3 years at Tessell

Interview Process Summary

• Round 1: Recruiter Screen (culture + motivation)
• Round 2: Frontend Machine Coding (Vanilla JS)
• Round 3: System Design + Frontend Architecture (1.5 hours)

Round-by-Round Breakdown

Round 1 — Recruiter Screen

Easy

A thorough recruiter conversation covering background, motivations, and culture fit. The recruiter was noted as warm and professional. The conversation had real substance — not just a box-checking exercise.

What the interviewer focused on: Genuine motivation for the role, communication clarity, and whether the candidate had researched the company.

Tip: Prepare specific answers about why the company and role appeal to you. Recruiters at good companies are assessing culture fit seriously, not just scheduling the next round.

---

Round 2 — Frontend Machine Coding (Vanilla JS)

Medium

No React, no Tailwind, no npm packages. Pure Vanilla JavaScript, plain CSS, and HTML.

Problems covered:

1. Infinite scroll / pagination — the candidate implemented using both:
   • Intersection Observer API (modern approach)
   • Manual scroll position + screen height calculation (classic approach)
2. Virtualized list — rendering 10,000+ items without DOM bloat

The interviewer explored both approaches comparatively: performance characteristics, trade-offs, edge cases (fast scrolling, sudden window resizes, scroll position stability when items load).

What the interviewer focused on: Understanding of , not just . The candidate needed to explain trade-offs between approaches, not just produce working code.