A HackerRank AI-assisted interview is a live round where the hiring company turns on an in-IDE assistant. If that assistant refuses to write a full solution, you are probably on a single-file Coding question in Guarded mode, not a broken panel. Code Repos run Unguarded, with Plan mode and Agent mode, and the interviewer sees every prompt in real time.
Google autocomplete still surfaces hackerrank ai assisted interview practice and hackerrank ai assisted interview reddit. Most of those threads collapse the format into "they gave me Copilot." The candidate knowledge base, last updated 11 days ago, is more specific than that. The format splits by question type, and the two sides do not behave the same.
What actually gets turned on?
You cannot enable the assistant yourself. HackerRank's candidate docs are blunt: it appears only when the hiring company enables it for that interview, and only on supported question types. If the panel is missing, treat the round as a standard live coding session. Using an outside model in that case is the same as any other unauthorized aid.
Two interviewer UIs exist right now. The new candidate article describes the current Interview experience. The admin article still labels itself as the legacy experience. You can tell which one you got from the workspace: a single editor vs an Agentic Development Environment with a repo, terminal, and file tree.
Default model, when the company does not pin one, is GPT-5.6 Terra. The selector can also offer Claude Opus 5 / Sonnet 5 / Haiku 4.5 and GPT-5.6 Sol / Luna. The set on screen is whatever that company configured. Do not spend the first three minutes hunting for a model that is not there.
Why does Guarded mode look broken?
This is the part Reddit threads keep misreading.
In the new Interview experience, HackerRank maps the assistant like this:
| Question type | Workspace | Mode | What the assistant will do |
|---|---|---|---|
| Coding | Single-file editor | Guarded | Syntax, navigation, errors, concepts. No complete solutions. |
| Code Repos | Agentic Development Environment | Unguarded | Plan mode + Agent mode: investigate, generate, edit files, fix issues. |
That table is from the candidate knowledge base, not a blog recap. If you paste "write the function" into a single-file Coding question and the assistant talks about the algorithm instead of dumping a passing solution, that is the product working as designed.
The legacy admin FAQ still says "in interviews the assistant operates in unguarded mode." That sentence is about the interview product as opposed to HackerRank Tests (the take-home / OA product), where the assistant stays guarded and will not reveal full solutions. It is not a promise that every live question will generate code. On legacy Coding questions, even unguarded mode only exposes Ask mode. Plan, Agent, inline completions, and model switching are documented as unavailable in Guarded mode, and they only show up on Project / Code Repository questions when Unguarded is on.
So the first diagnostic, before you panic that "AI is off":
- Is the panel visible at all? If not, the company did not enable it, or this question type does not support it.
- Are you in a single file or a repo? Single file → expect Ask, not an agent that rewrites the file.
- Did a Pending tool call dialog appear? That is Agent mode. You have to Allow or Cancel. Ignoring it is not a stall; it is a decision the interviewer can see.
HackerRank's Summer 2026 release added 159 Plan-Build-Review repository tasks for interviews. The industry default is drifting toward the repo side. Do not walk in having only practiced LeetCode in a blank editor.
What does the interviewer actually see?
Three surfaces, all from HackerRank's own interviewer docs — not from "someone on Blind said":
- Live panel. Prompts and assistant replies stream to the interviewer as they happen. Plan, Ask, and Agent are all visible. Inline completions you accept land in the shared editor.
- Chat transcript in the interview report. The interview report has an AI Assistant Chat control on both Coding and Code Repos responses. Nothing you typed into the panel is off the record.
- Diff View, but only on front-end, back-end, and full-stack questions. It compares the project at the start of the interview with the current tree. It is not a hidden plagiarism score. It is a "what changed" view.
HackerRank's admin FAQ also says Plan mode is optional. You can go Ask → Agent, or live in Agent the whole time. Skipping Plan is allowed. It is also obvious, because the transcript then has no plan. Interviewers are told they can weigh those Plan interactions as part of how you collaborate with AI. That is not a published numeric rubric. It is a visible absence.
Ask mode has a mechanical rule that eats people: you have to tag the problem statement. Untagged questions get generic answers. The interviewer sees you retry the same vague prompt three times. Tag it once.
You can also choose not to use the assistant at all. That is documented. It is a valid strategy on a Guarded Coding question where the panel cannot write the solution anyway. On a Code Repo ticket, sitting next to an unused agent for 40 minutes is a different signal — you are leaving a tool on the table that the format was built to watch you use.
What does a strong Code Repo session look like?
Take a ticket that shows up in real repo rounds: implement LRU cache, capacity 2, then hit the hidden eviction order.
This is the first patch models ship. get() returns the value and does not move the key to recent. The public tests still pass if they only check return values.
class LRUCache:
def __init__(self, capacity: int):
self.cap = capacity
self.order = [] # oldest at index 0
self.data = {}
def get(self, key: int) -> int:
if key not in self.data:
return -1
# missing: move key to most-recent
return self.data[key]
def put(self, key: int, value: int) -> None:
if key in self.data:
self.data[key] = value
self.order.remove(key)
self.order.append(key)
return
if len(self.data) == self.cap:
old = self.order.pop(0)
del self.data[old]
self.data[key] = value
self.order.append(key)
cache = LRUCache(2)
cache.put(1, 1)
cache.put(2, 2)
assert cache.get(1) == 1
cache.put(3, 3)
print("get(1) after put(3) =", cache.get(1)) # -1 (1 was evicted)
print("get(2) =", cache.get(2)) # 2
The hidden test is: after get(1), key 1 is more recent than 2, so put(3) should evict 2, not 1. The agent wrote a map plus a list and forgot that get is a recency event. The code compiles. That is the trap.
A session that matches what the interviewer docs say they are watching looks like this:
-
Plan mode first, no code. One paragraph: hash map plus recency list,
getandputboth bump recency, evict the head on overflow. Edge case:geton a missing key must not shuffle the list. Plan mode, per HackerRank, does not edit files. If the plan already skippedgetrecency, Agent will implement the skip. - Allow the tool call, then read the diff before Accept. The Pending dialog is a gate. Cancel is a documented, legal action. Accepting a 40-line rewrite you have not read is the thing Diff View exists to show.
-
Say the bug out loud, then patch one line.
getneedsself.order.remove(key); self.order.append(key)before the return. That edit is worth more than a clean Agent dump, because the transcript now has: plan → generation → you catching the model.
Fixed get:
def get(self, key: int) -> int:
if key not in self.data:
return -1
self.order.remove(key)
self.order.append(key)
return self.data[key]
Rerun the same four calls. get(1) after put(3) is now 1, and get(2) is -1. That is the whole interview skill in twelve lines: the assistant wrote something that looked done, and you refused to ship it.
On a Guarded single-file question the same LRU still appears, but the assistant will not dump this class for you. Ask about "what recency means on get" or "why a dict alone is not enough." Then you type. The transcript still exists. The prompts are the answer.
How is this different from a HackerRank OA?
Do not mix the two products.
Interview (this article): a human is on the call. AI use is in the open. The report is a chat transcript, not a plagiarism flag for using the panel.
Tests / Screen (the OA / take-home): the admin FAQ says the assistant stays in Guarded mode and will not reveal full solutions. Proctoring, tab switches, and integrity reports are a different stack. "Can I use ChatGPT during the OA?" is not this format. If your recruiter said "HackerRank assessment" with no interviewer on the calendar, you are probably in Tests.
If the pipeline is OA then live, those are two preps. The OA side is take-home / timed coding. The live side is the format above. aceround.app — an AI interview assistant — is built for the live round, including catching a bad AI patch while someone is watching. The same desktop client also covers coding-test / OA practice; do not walk into Screen with Interview habits, or the other way around.
Ask the recruiter the only question that changes the plan: is this an AI-assisted Interview, or a HackerRank test? If they do not know, assume standard until the panel appears.
A 20-minute practice you can run tonight
You do not need HackerRank's IDE to rehearse the judgment the format scores.
- Pick a small repo bug, not a blank-editor LeetCode. LRU, a rate limiter that uses wall-clock time, a pagination off-by-one.
- Write a five-line plan in a comment. No code.
- Ask any coding model for the implementation. Do not paste it in yet.
- Run one hidden case you did not put in the prompt. For LRU:
put 1, put 2, get 1, put 3. - Narrate the first thing the model got wrong, then patch it yourself.
If you cannot find the bug in step 4, you are not ready for Unguarded Agent mode. That is the actual practice, not memorizing Plan Mode's UI labels.
The question worth leaving in the comments: when the assistant is on, do you still write the first draft yourself, or do you start in Agent and only keep the edits you can defend?
Sources: HackerRank candidate KB — AI Assistant in Interview (updated 11 days ago); HackerRank admin KB — AI-Assisted Interviews (legacy UI, updated 8 days ago); Interview Report; Summer 2026 release notes (159 Plan-Build-Review repo tasks).
Disclosure: I used AI to help draft and edit this post. The Guarded vs Unguarded split, feature tables, and interviewer surfaces are from HackerRank's public knowledge base, checked today. The LRU example is a local Python replay, not a dump from an interview session.
Top comments (0)