Google 2026 New Grad R1: Wrong Two-Pointer Start, DP Recovery, and No Dry Run

Role: Software Engineer, New Grad
Result: Final outcome not disclosed
Report time: January 2026

Technical R1

The coding problem required dynamic programming, but the candidate initially believed a two-pointer solution would work.

They described the two-pointer direction to the interviewer, who allowed them to begin coding. After about 20 minutes, a dry run showed that the pointer movement was invalid. The interviewer then pointed out the issue, and the candidate switched to dynamic programming.

The candidate completed the DP code under time pressure but did not have time to explain it fully, dry-run it, or attempt a follow-up.

The source does not preserve the problem's input, objective, constraints, or examples. Those missing details make it impossible to identify or link an exact practice question.

Behavioral round

The original behavioral interviewer did not appear, so that session was rescheduled. The candidate felt well prepared but did not yet have a behavioral result when they posted.

The candidate asked whether one weaker coding signal could still lead to R2 if the behavioral round was strong. Commenters offered opinions about hiring signals, but no official decision rule was established.