Get unstuck without giving the problem away

A vague feeling of being stuck is difficult to coach because it can describe several different failures. You may not understand what the problem asks. You may understand it but lack an approach. You may have the correct approach and a broken implementation. You may pass the examples but miss one boundary. Each state needs a different next question.

Before requesting help, write one sentence that locates the block. For example: I cannot define the subproblem, I do not know how to update the left pointer, or my recurrence works except when the amount is zero. That sentence prevents a broad request from producing a broad answer and makes it easier to use a hint without revealing unrelated parts of the solution.

• Restate the constraint or invariant you are uncertain about.
• Try a tiny input by hand and write down the state after each step.
• Ask one Socratic question about the exact block.
• If still blocked, request a pattern or data-structure cue without pseudocode.
• Ask for pseudocode only after you can explain why the pattern fits.
• Read a complete solution only after recording your attempt and the point where it failed.

Nudge operates on supported LeetCode pages, which removes the repeated work of opening a separate assistant and recreating the setting. Its coaching stage can distinguish an early planning moment from inactivity or a nearly complete attempt. The product can then lead with a plan question, a narrower sub-question, or an edge-case prompt rather than applying the same hint format to every state.

Inline prompts keep attention near the editor. The side panel is available when the issue needs a conversation rather than one line. If editor context is important, Pro users include it deliberately with @code. The aim is not to eliminate frustration immediately; it is to shorten unproductive looping while preserving the remaining reasoning.

The most important part of a hint is what happens next. Do not keep escalating simply because more assistance is available. Close or ignore the conversation, implement the smallest new idea, and run a test. If it fails, explain what changed before asking again. This turns the assistant into a checkpoint rather than the driver of the solution.

After completing the problem, write the insight in your own words. Avoid copying the assistant's phrasing. Revisit the problem later from a blank state and see whether you can recover the invariant, recurrence, or pointer rule. A solution that only exists inside the old conversation has not yet become interview-ready knowledge.

• The environment prohibits AI or outside assistance.
• You are asking for successive hints without testing the previous one.
• You cannot explain the last suggestion in your own words.
• The real gap is a foundational concept that needs deliberate study.
• You are using the tool during a live interview or assessment without explicit permission.