Ivy League

Role: Software Engineer, Product (E4)

College: Not Specified

Interview Date: 2025 (Recruiter contact Day 1, Phone screen Day 28, Onsite Day 49)

Interview Type: Full-Time

Result: Passed (Offer received, entered team matching)

Difficulty: Easy-Medium

Rounds: Recruiter Call, Phone Screen (Coding), First Onsite Coding, Behavioral, Second Onsite Coding, Product Architecture (Total 6 rounds)

Topics Asked: Linked List, Binary Tree, Data Structures, Algorithms, Behavioral (ambiguity, difficult decisions, conflict resolution), Product Architecture

Experience:

This Reddit user shared a detailed timeline and experience for a Meta Software Engineer (E4) role in 2025.

Recruiter Call

Discussed profile, role fit, and interview structure.

Phone Screen (Coding)

Consisted of two easy-medium questions, described as Meta-tagged/minmer variants involving linked list and binary tree problems.

First Onsite Coding

Two easy-level coding questions (not Meta-tagged).

Behavioral

Three main questions with several follow-ups, covering experiences like facing ambiguity, making a difficult decision, and having a conflict with a colleague.

Second Onsite Coding

Two easy-medium questions, again Meta-tagged/minmer variants.

Product Architecture

A question from the Meta-tagged "hello interview" set.

The candidate confirmed passing all rounds and entered the team matching phase, eventually receiving an offer.