Ivy League

Role: Software Engineer, Early Career

College: Not Specified

Interview Date: November 12, 2025 (posted date, implies very recent)

Interview Type: Full-Time

Result: Mixed/Borderline (pending, self-assessment)

Difficulty: Medium to Hard

Rounds: 4 interviews (3 technical, 1 behavioral)

Topics Asked: Algorithms (Binary Search, BST), Data Structures, Design, Behavioral (Googleyness: ownership, teamwork)

Experience:

This Reddit user shared their recent Google interview feedback for an Early Career Software Engineer role in the US.

Interview 1 (Behavioral/Googleyness)

Described as a "great conversation" with "strong alignment on ownership/teamwork." The candidate felt very positive about this round. Difficulty: Medium. Verdict: Strong.

Interview 2 (Algorithms – Binary Search)

The candidate fully solved the problem with clean code and no hints. There was a minor slip on exact STL function syntax, but logic, edge cases, and complexity were solid. Verdict: Good–Strong.

Interview 3 (Algorithms – BST)

The candidate presented a brute-force solution, then derived and implemented the optimal solution confidently, without hints. Difficulty: Medium. Verdict: Good–Strong.

Interview 4 (Data Structure/Design)

Started with a correct-but-not-logK approach, then moved to the intended O(log K) design. The candidate fumbled the final bookkeeping under time pressure, but the interviewer stated the logic was correct, though not implemented properly. Difficulty: Hard. Verdict: Mixed/Borderline.

All interviews were approximately 45 minutes. The candidate expressed anxiety about the last round despite positive feelings from others, seeking perspective on chances of passing, rejection, or an extra round.