Coding Interview Accommodations: Ask Before You Open the Test Link

You can ask for coding interview accommodations. The timing decides most of what you get. Ask the recruiter in writing before you open any test link. On HackerRank, a recruiter can add accommodation time to a test. That works only while you haven’t started it. Once you click start, that option is gone. Each live round needs its own request. It runs in a fixed slot with a busy interviewer. So name every round on your schedule. Then say what changes in each. Extra time on the online assessment is one ask. A written prompt in the coding round is another. A break between onsite rounds is a third. In the US, the ADA requires employers to provide reasonable accommodations so applicants can compete for a job. Below, one Android engineer with ADHD plans requests for a full loop. A sample email to the recruiter follows, with notes on why each line is there.

Coding interview accommodations on an online assessment must be set before you start

Take an Android engineer with five years of Kotlin and an ADHD diagnosis. A recruiter has just sent a HackerRank link for a 90-minute online assessment. The onsite comes after it, with two coding rounds, one Android system design round and one behavioral round.

The usual mistake is to start the test, struggle with the clock and email the recruiter afterward. HackerRank’s help article for test owners, Extend Test Duration for Candidates, shows why that fails. A test owner can add a time accommodation of 25, 50, 75 or 100 percent. They can also enter a custom amount in steps of five. That works only while the candidate hasn’t started. A second setting adds minutes after a test begins. HackerRank describes it for time lost to problems like a dropped connection. Using it for your accommodation depends on the recruiter’s goodwill. The article carries no specific date.

The candidate can’t change any of this. Only the employer’s account users can. So the engineer leaves the link unopened and writes to the recruiter first. Our post on the CodeSignal General Coding Assessment covers another reason to wait. A first score on that platform can follow you to later companies.

Each live round needs its own request because its slot is fixed

A live coding round usually sits in a 45 or 60 minute slot. The interviewer often has another meeting right after. So asking that interviewer for extra time at minute 40 rarely works. They can’t move their calendar from inside the call. The recruiter can book a longer slot. That has to happen before the day.

The engineer thinks about what actually goes wrong in each round. In coding rounds, they lose the thread when a prompt is only spoken. A written prompt in the editor fixes most of that. They also want 50 percent more time. ADHD UK’s interview adjustments guidance recommends an extra 50 percent of time. The UK charity says that figure is about lowering interview pressure, not about ADHD alone. The page shows no date.

The system design round has the same spoken-prompt problem. Here the engineer asks for the prompt in writing and for permission to keep short notes. ADHD UK’s guidance also supports letting candidates refer to notes. For the onsite as a whole, the engineer asks for a 15-minute break between rounds. Four rounds in a row wear down focus more than any one of them.

The behavioral round needs no change for this engineer, so the request leaves it out. A short list that skips one round shows the engineer thought about each one.

The recruiter routes the request, so send one message that covers the loop

At Google, the recruiter passes the request to a separate team. In a 2020 Google blog post, a deaf Googler describes her hiring process. Her recruiter brought in Google’s Candidate Accommodations team. That team arranged captioning for her phone and onsite interviews. Amazon’s UK and Ireland accommodations page says its support covers the interview. It sends candidates in unlisted countries to their recruiting partner. That page shows no date.

Robby Grodin runs NextPath, a paid job-search cohort for software engineers. In a February 2026 post on interview accommodations, he says to make one clear request. He warns against offering a fallback in the first message. A fallback invites the company to pick the easier option, even when it helps you less. He also says to ask as early as possible.

A sample email that lists each round and its change

The engineer sends this before opening the assessment link.

Hi Priya, thanks for sending the assessment. Before I start it, I’d like to request accommodations for a disability that affects focus under time pressure. Here is what helps in each part of the process.

For the online assessment, I’d like 50% additional time, set before I open the link. For the coding rounds, I’d like the problem written in the editor at the start. A 90-minute slot in place of 60 would also help. For Android system design, I’d like the prompt in writing and permission to keep short notes. On the onsite day, a 15-minute break between rounds would help.

Who handles accommodation requests? And which interviewers will know about them? I’ll wait to open the assessment until the extra time is in place.

The first paragraph names the need in one clause. It describes what the condition affects, without a diagnosis. The engineer can share more later if the company asks. Each round then gets one concrete change. A recruiter can forward those requests as they stand.

The last paragraph asks two questions. The first finds the person who can approve the request. The second tells the engineer who will know about it. That’s worth asking, because companies handle it differently. The closing sentence stops the most common failure. The assessment won’t start until the time is added.

The ADA changes the conditions of a test, not what it measures

Some candidates worry that an accommodation will lower the bar for them. US law points the other way. The EEOC issued its guidance on job applicants and the ADA in October 2003. It says employers can’t refuse to consider you because you need an accommodation. It names adjusting the time allowed for a written test as one possible change. It says a test shouldn’t require a skill your disability impairs, unless the test measures that skill.

A coding round measures problem solving and code, not reading a prompt aloud at speed. So a written prompt fits the guidance well. The bar for the solution itself stays the same.

The same guidance says an employer may ask for reasonable documentation. It applies when the disability or the need isn’t obvious. It also says when you disclose is your own decision. The ADA doesn’t require any particular point. Outside the US, the rules differ. The UK government has a page on reasonable adjustments. It lists changing the recruitment process so a candidate can be considered. None of this is legal advice. For a dispute, talk to an employment lawyer or your local equality body.

When the recruiter offers less than you asked for

Suppose Priya replies that the coding slots can’t go past 60 minutes. She offers the written prompt and the assessment time instead. That’s a partial yes. Grodin says to discuss alternatives once the company pushes back. That has now happened. The engineer judges each substitute by whether it fixes the problem the email named.

For this engineer, the written prompt removes most of the lost time in coding rounds. So a 60-minute slot with a written prompt may be enough. The engineer says so in one line and accepts. If the offer had been a longer slot with a spoken prompt, it would have helped much less. Then the engineer would say that plainly and ask again for the written prompt.

If the onsite date leaves too little time to settle all of this, push the date first. Our post on postponing an onsite interview covers how to ask for one specific later date.

Leave a Comment