F

Facebook

Software Engineer, Front End

Interview Date

July 2025

Result

Unspecified (candidate doesn't expect an offer)

Difficulty

Easy/Medium (issues with specific JavaScript knowl

Rounds

Technical Screening, Full Loop (2 Coding, 1 Architecture and Design)

Drive Type

Full-Time

Topics asked

JavaScript (trivial questions)Architecture and Design (designing pagesrendering elements)

Detailed experience

Role: Software Engineer, Front End

College: Not Specified

Interview Date: July 2025

Interview Type: Full-Time

Result: Unspecified (candidate doesn't expect an offer)

Difficulty: Easy/Medium (issues with specific JavaScript knowledge, not problem-solving)

Rounds: Technical Screening, Full Loop (2 Coding, 1 Architecture and Design)

Topics Asked: JavaScript (trivial questions), Architecture and Design (designing pages, rendering elements)

Experience:

This candidate, with nearly 3 years of full-time and 5-6 years of intern experience, interviewed for a Frontend Software Engineer position at Meta.

The experience didn't align with typical expectations of hard LeetCode problems.

Technical Screening: Involved "like two JavaScript questions" which were "pretty trivial," more akin to tasks expected in a work setting if one knows JavaScript.

Full Loop: Consisted of two coding interviews, asking a total of four JavaScript questions. These also felt "pretty trivial" for someone proficient in JavaScript.

Architecture and Design Interview: Focused on questions related to designing a page and rendering elements, which was unexpected for the candidate who prepared for hard LeetCode-style problems.

The candidate doesn't expect an offer, feeling they performed "either bad or just average." The coding questions themselves weren't hard; the main issues stemmed from not knowing "specific JavaScript things off the top of my head," rather than struggling with problem-solving.

The candidate's advice is to brush up on specific JavaScript knowledge before such interviews.

Posted on - 12 Nov 2025