• Home
  • Skills
  • Projects
  • Blog
  • Contact
Resume
Naser Rasouli

Author

Naser Rasouli

Front-End developer - sharing lessons learned, notes, and write-ups from real projects.

GitHubLinkedIn

Last posts

BEM Methodology in CSS: predictable naming for clean styles
2026-02-18•1 min read

BEM Methodology in CSS: predictable naming for clean styles

A practical guide to BEM to avoid style conflicts, structure class names, and keep CSS maintainable.

Why console.log After setState Shows the Old Value
2026-02-04•1 min read

Why console.log After setState Shows the Old Value

React batches state updates, so logging right after setState prints the previous value. Here’s why and the right ways to read the fresh state.

Cleanup Functions in useEffect: Stop Leaks Before They Start
2026-02-04•1 min read

Cleanup Functions in useEffect: Stop Leaks Before They Start

A practical guide to writing cleanup in useEffect so you avoid memory leaks, duplicate listeners, and setState on unmounted components.

Frontend Interview Flow: Stages, Signals, and Prep

Frontend Interview Flow: Stages, Signals, and Prep

2026-01-17
frontendinterviewjavascripthtmlcss

What is a frontend interview really looking for?

Interviewers want proof you can ship a reliable UI—not how many frameworks you know. They check:

  • Understanding of the web and the browser
  • Problem-solving and analytical skills
  • The reasoning behind your technical choices
  • Code that a team can maintain

Typical frontend interview flow

Steps can shift, but often follow this arc:

  1. Initial screening
    Resume walkthrough: experience, projects, learning path.

  2. Web fundamentals
    Request/response cycle, the browser’s role, client vs server, HTTP and APIs.

  3. Frontend-specific topics (headline-level, but analytical)

    • HTML: semantic structure, accessibility, metadata, basic SEO
    • CSS: Flex/Grid layouts, responsive design, style organization, basic UI/UX concepts
    • JavaScript: scope/closures, async/await, event loop, data handling, DOM work
    • Frameworks: component architecture, state management, routing, performance

  4. Technical task or challenge
    Analyze a problem, implement a small task, or review/fix code.

  5. Experience and decision-making
    Why this solution? What if you had more time? How would you adapt at scale?

  6. Collaboration and mindset
    Explaining clearly, team communication, accepting feedback, owning outcomes (especially for Mid/Senior).

What signals do interviewers extract?

  • Do odd bugs scare you, or can you trace root causes?
  • Can you justify decisions logically, or do you rely on cargo-cult patterns?
  • Is your code maintainable and readable, or merely “works”?
  • Is your web/browser understanding deeper than framework usage?

How to prepare

  • Lock in fundamentals: HTTP, caching, CORS, basic security, DOM, event loop.
  • Build small but real projects and document your decisions.
  • Practice debugging: async/promise errors, simple memory leaks, broken layouts.
  • Use a response pattern: problem → options → chosen approach (why) → what you’d improve with more time/resources.
  • Timebox tasks and simplify: ship an MVP first, then refine.

Wrap-up and what’s next

A frontend interview isn’t about memorizing Q&A; it’s about demonstrating thinking, web understanding, and collaboration. Next in this series, we’ll dive into specialized questions for each area (web, HTML/CSS, JavaScript, frameworks, and practical tasks) to show what each question measures and how to answer with clarity.