Somewhere between the first call and the offer, a US front end employer will ask you to build something. It might be a timed exercise on a testing platform, a take-home to finish over a weekend, or an hour of live coding with someone watching. Almost every guide to this treats it as etiquette: be gracious, ask clarifying questions, write clean code.
That advice is fine and it is also missing the point. The coding test is the most heavily regulated part of the whole hiring process, and almost nothing written for candidates says so. In federal law it is not a conversation. It is a selection procedure, and once something is a selection procedure, obligations attach to it and rights attach to you.
This page sets out what those are, from the regulations and the enforcement guidance rather than from opinion. If you want the pay and skills picture instead, that is on our front end developer jobs guide, and the application process end to end is covered in how to apply for developer jobs in the USA.
What the Law Calls a Coding Test
The Uniform Guidelines on Employee Selection Procedures, at 29 CFR Part 1607, are the rules federal enforcement agencies apply to hiring tests. Their definition, at section 1607.16(Q), is broader than most engineers assume:
"Any measure, combination of measures, or procedure used as a basis for any employment decision. Selection procedures include the full range of assessment techniques from traditional paper and pencil tests, performance tests, training programs, or probationary periods and physical, educational, and work experience requirements through informal or casual interviews and unscored application forms."
Read the second sentence twice. Performance tests are named, which is what a coding exercise is. So are probationary periods, work experience requirements, and — the part that surprises people — informal or casual interviews and unscored application forms.
That matters because of a widespread belief that a company reduces its legal exposure by keeping the process casual: no scoring, no rubric, just a chat and a gut call. The opposite is closer to the truth. An unstructured chat is a selection procedure exactly as a scored test is, and it is considerably harder to defend as job related, because there is no record of what was measured.
It Has to Be About the Job
The standard a test has to meet is not "is it hard" or "is it a fair puzzle". Where a selection procedure disproportionately excludes people on the basis of race, colour, religion, sex or national origin, the employer has to show it is "job-related and consistent with business necessity". The EEOC's guidance on employment tests puts the test of that plainly:
"An employer can meet this standard by showing that it is necessary to the safe and efficient performance of the job. The challenged policy or practice should therefore be associated with the skills needed to perform the job successfully. In contrast to a general measurement of applicants' or employees' skills, the challenged policy or practice must evaluate an individual's skills as related to the particular job in question."
"As related to the particular job in question" is the operative phrase, and it is worth holding on to when a front end interview turns into a whiteboard round on binary trees. A test of skills the job does not use is weaker ground for the employer, not stronger.
One more line from the same guidance is worth knowing if the exercise arrives from a third-party assessment platform:
"While a test vendor's documentation supporting the validity of a test may be helpful, the employer is still responsible for ensuring that its tests are valid under UGESP."
Buying the test in does not move the obligation. The employer still owns it.
A note on weight, because it cuts both ways: that EEOC document carries its own disclaimer that its "contents do not have the force and effect of law and are not meant to bind the public in any way". It explains existing law rather than creating new law. The regulation in Part 1607 and the statute behind it are what bind.
Adverse Impact, and the Rule of Thumb Everyone Misquotes
Part 1607 sets out the general principle at section 1607.3(A):
"The use of any selection procedure which has an adverse impact on the hiring, promotion, or other employment or membership opportunities of members of any race, sex, or ethnic group will be considered to be discriminatory and inconsistent with these guidelines, unless the procedure has been validated in accordance with these guidelines, or the provisions of section 6 below are satisfied."
How adverse impact gets measured is the well-known four-fifths rule, at section 1607.4(D):
"A selection rate for any race, sex, or ethnic group which is less than four-fifths (4/5) (or eighty percent) of the rate for the group with the highest rate will generally be regarded by the Federal enforcement agencies as evidence of adverse impact, while a greater than four-fifths rate will generally not be regarded by Federal enforcement agencies as evidence of adverse impact."
Here is where nearly every summary of this goes wrong. The four-fifths rule is repeatedly described as a legal threshold, so that passing it means passing the law. The EEOC's own interpretive questions and answers say otherwise:
"This '4/5ths' or '80%' rule of thumb is not intended as a legal definition, but is a practical means of keeping the attention of the enforcement agencies on serious discrepancies in rates of hiring, promotion and other selection decisions."
And, in the same document: "The 4/5ths rule of thumb speaks only to the question of adverse impact, and is not intended to resolve the ultimate question of unlawful discrimination." Section 1607.4(D) says as much itself — smaller differences can still constitute adverse impact where they are significant "in both statistical and practical terms".
There is also a preference in the regulation that hiring teams rarely know about, at section 1607.3(B): where two procedures are available which serve the employer's interest and are "substantially equally valid for a given purpose", the employer "should use the procedure which has been demonstrated to have the lesser adverse impact". A realistic take-home and a whiteboard puzzle that predicts the same thing are not equivalent under that sentence.
Timed Tests, and the Right to Have One Adjusted
This is the most immediately useful part of this page, because it is an enforceable right that costs nothing to exercise and is very widely unknown.
The ADA regulations contain a section specifically about administering tests, at 29 CFR 1630.11:
"It is unlawful for a covered entity to fail to select and administer tests concerning employment in the most effective manner to ensure that, when a test is administered to a job applicant or employee who has a disability that impairs sensory, manual or speaking skills, the test results accurately reflect the skills, aptitude, or whatever other factor of the applicant or employee that the test purports to measure, rather than reflecting the impaired sensory, manual, or speaking skills of such employee or applicant (except where such skills are the factors that the test purports to measure)."
The duty runs to applicants and not only to employees. Section 1630.9(a) makes it unlawful "not to make reasonable accommodation to the known physical or mental limitations of an otherwise qualified applicant or employee with a disability", unless the employer can show undue hardship.
What that means in practice, for a timed coding exercise, is spelled out in the interpretive appendix to section 1630.11:
"An employer may also be required, as a reasonable accommodation, to allow more time to complete the test. In addition, the employer's obligation to make reasonable accommodation extends to ensuring that the test site is accessible."
The appendix goes further, and names what happens when a timed test simply cannot be made accessible: alternative formats include "large print or braille, or via a reader or sign interpreter", and where testing in an alternative format is not possible, "the employer may be required, as a reasonable accommodation, to evaluate the skill to be tested in another manner (e.g., through an interview, or through education license, or work experience requirements)".
How asking actually works
Four points from the EEOC's enforcement guidance on reasonable accommodation, each of which removes a reason people talk themselves out of asking:
- You do have to ask. "Generally, the individual with a disability must inform the employer that an accommodation is needed." The employer is not required to guess.
- Plain language is enough. An individual "may use 'plain English' and need not mention the ADA or use the phrase 'reasonable accommodation'".
- It does not have to be in writing. "Requests for reasonable accommodation do not need to be in writing."
- Timing is open. A request may be made "at any time during the application process or during the period of employment" — and the appendix to Part 1630 covers the case where you only realise mid-test, in which case you must tell them "upon becoming aware of the need".
The guidance also states the employer's side, which is the sentence worth quoting back if a request is treated as an odd one: an employer "must provide a reasonable accommodation to a qualified applicant with a disability that will enable the individual to have an equal opportunity to participate in the application process and to be considered for a job", short of undue hardship. Employers are expressly permitted to ask about it up front, too — they "may tell applicants what the hiring process involves (e.g., an interview, timed written test, or job demonstration), and may ask applicants whether they will need a reasonable accommodation for this process".
The guidance's own illustration of getting this wrong is blunt: an employer that cancelled an interview rather than provide a sign language interpreter "has violated the ADA".
Should a Take-Home Be Paid?
This is the question candidates actually argue about, and it deserves an honest answer rather than a confident one.
There is no federal regulation and no Department of Labor fact sheet specifically about unpaid work trials, job auditions or take-home assignments for applicants. Part 785 of the wage and hour regulations, which governs hours worked, does not address applicants at all. Anyone telling you there is a clear federal rule here is overstating it, in either direction.
What does exist is the statutory definition the whole of wage and hour law turns on. Under the Fair Labor Standards Act, as Wage and Hour Division Fact Sheet #22 puts it, the term "employ" includes "to suffer or permit to work", and:
"Work not requested but suffered or permitted to be performed is work time that must be paid for by the employer."
That is a definition about employees, and an applicant is generally not yet one. But it is the reason the line moves when an assignment stops looking like an assessment and starts looking like delivery. A four-hour exercise against a synthetic brief is an assessment. Building a working feature against the company's real backlog, to be merged, is the thing that definition was written about.
The nearest official test for an unpaid work-like arrangement at a for-profit employer is the seven-factor "primary beneficiary" test in Fact Sheet #71 — but be careful with it, because it was written for interns and students, and three of its seven factors are about formal education programmes, academic credit and the academic calendar. Those do not map onto a take-home given to an experienced candidate. Its first factor does, though, and it is the useful one: "The extent to which the intern and the employer clearly understand that there is no expectation of compensation. Any promise of compensation, express or implied, suggests that the intern is an employee."
One historical note, since out-of-date versions circulate: the Department of Labor formally rescinded its previous six-factor internship test in January 2018, in Field Assistance Bulletin 2018-2, and adopted the courts' primary beneficiary test instead. If a guide quotes six factors, it is eight years stale.
The practical position
- Scope, not principle, is the argument to have. "Is this paid?" invites a no. "This looks like about twelve hours — would a four-hour version answer the same question?" is a scoping conversation, and a reasonable employer will take it.
- Ask what happens to the work. If the output ships, you are not being assessed, you are delivering. That is a fair thing to say out loud.
- Ask what is being measured and how. An employer who can answer has a job-related procedure. One who cannot has a vibe check, and you have learned something either way.
- Get the time limit in writing before you start. It is the thing most often left vague and most often disputed afterwards.
What To Do With All This
None of the above is a reason to arrive at an interview quoting regulations. Used that way it will cost you the job and deserve to. It is useful in four quieter ways:
- If you need an adjustment, ask for it. Plain language, no diagnosis required, no form, any time in the process. This is the single highest-value item on this page.
- Judge the process, because it tells you about the team. An employer who can say what the exercise measures and why is describing an engineering culture. So is one who cannot.
- Do not read a casual process as a safe one. For you, an unstructured interview is the stage where an unrelated judgement is hardest to see and hardest to challenge.
- Prepare for what the job uses. Front end assessments that predict the work tend to look like the work: a component with states nobody designed, a layout that has to survive a narrow screen, something keyboard operable. Our front end guide covers the two skills that are measurable on the job, which are also the two that are most convincing in an assessment.
Frequently Asked Questions
Are take-home coding tests legal in the USA?
Yes. Employers may test applicants. What the law regulates is how: a test is a selection procedure under 29 CFR Part 1607, so where it disproportionately excludes a protected group it has to be job related and consistent with business necessity, and it has to be administered so that a disabled applicant's results reflect the skill rather than the disability.
Does a coding exercise really count as a selection procedure?
Yes. Section 1607.16(Q) defines one as "any measure, combination of measures, or procedure used as a basis for any employment decision" and names performance tests explicitly, alongside probationary periods, work experience requirements and even "informal or casual interviews and unscored application forms".
Can I ask for more time on a timed coding test?
If you have a disability that the timing disadvantages, yes. The interpretive appendix to 29 CFR 1630.11 states that an employer "may also be required, as a reasonable accommodation, to allow more time to complete the test". The employer can refuse only by showing undue hardship.
Do I have to disclose a diagnosis to get an adjustment?
You have to let the employer know you need an adjustment for a reason related to a medical condition, but the EEOC's guidance says you may use "plain English", need not mention the ADA or the phrase "reasonable accommodation", and need not put the request in writing.
When should I ask for an accommodation?
A request may be made at any point in the application process. If you only realise partway through a test, the appendix to Part 1630 says you must tell the employer on becoming aware of the need, so say so then rather than afterwards.
Should a take-home assignment be paid?
There is no federal rule specifically on unpaid assignments for applicants, so the honest answer is that it depends on what is being asked. The distinction that matters is assessment against delivery: an exercise on a synthetic brief is one thing, work against the company's real backlog that will ship is another.
What does the four-fifths rule actually mean?
It is a rule of thumb for spotting adverse impact: a selection rate for a group below four-fifths of the highest group's rate is generally treated as evidence of it. The EEOC is explicit that it "is not intended as a legal definition" and "speaks only to the question of adverse impact".
Is an informal chat safer for an employer than a scored test?
No, and the assumption is common. Part 1607 covers informal or casual interviews and unscored application forms as selection procedures too, and an unstructured process is harder rather than easier to defend as job related, because nothing records what was measured.
People Also Search For
Take home coding test
A selection procedure in federal law, not an informal favour. Settle the scope and the time limit in writing before you start it.
Frontend developer interview questions
The ones that predict the job tend to look like the job: component states, narrow screens, keyboard operability. Puzzles the role never uses are weaker ground for the employer.
Unpaid coding assignment
No federal rule addresses applicant work trials. The useful line is assessment against delivery, and whether the output is going to ship.
Coding test accommodation ADA
More time is named in the appendix to 29 CFR 1630.11. So are large print, braille, a reader or an interpreter, and assessing the skill another way where the format cannot be adapted.
Four fifths rule hiring
A rule of thumb at 29 CFR 1607.4(D) for flagging adverse impact, which the EEOC says is not a legal definition and does not settle whether discrimination occurred.
Frontend developer technical assessment
Four common shapes: timed online exercise, take-home, live or pair session, and portfolio review. All four are selection procedures.
Live coding interview
Ask what is being measured. An employer who can answer has a job-related procedure; one who cannot is telling you something about the team.
Frontend developer jobs USA
Web developers were at a $92,650 median in May 2025, with the top tenth above $162,290. The pay and skills picture is on the main front end guide.
Related career guides
- Front End Developer Jobs in USA — what the work pays, the outlook on the current projection round, and the two skills that are measurable.
- How to Apply for Developer Jobs in the USA — the rest of the process, from the vacancy announcement to the background check and the I-9.
- Entry Level React Developer Jobs in USA — what to build before you are assessed, and how to read a junior advert.
- Remote Frontend Developer Jobs in USA — what the word remote hides on a US advert, including where you owe tax.
- React JS Developer Contract Jobs in USA — the staffing and consulting layer, and the pay rules that apply inside it.
- React Software Engineer Jobs in USA — the levelled enterprise ladder, and how equity and bonus are taxed.
- React Developer Internship Jobs in USA — the student route, and whether an internship has to be paid.
- JavaScript React Developer Jobs in USA — the fundamentals round, and the two standards its questions are drawn from.
- React TypeScript Developer Jobs in USA — what the type system round tests, and what types do not do at runtime.
- React Front End Engineer Jobs in USA — the levelled ladder, and which states require the band in the advert.
- Full Stack React Developer Jobs in USA — the backend half, and the security questions a senior round is really asking.
- Senior React Developer Jobs in USA — senior processes add architecture and system design, and the grade changes your overtime status.
- Web Developer Jobs in USA — the BLS occupation front end work is counted in, in full.
Official sources
- Uniform Guidelines on Employee Selection Procedures, 29 CFR Part 1607 — sections 1607.3, 1607.4(D) and 1607.16(Q), 2025 edition of the Code of Federal Regulations.
- Equal Employment Opportunity Commission — "Employment Tests and Selection Procedures", and the questions and answers interpreting the Uniform Guidelines.
- Equal Employment Opportunity Commission — Enforcement Guidance on Reasonable Accommodation and Undue Hardship under the ADA.
- ADA regulations, 29 CFR 1630.9 and 1630.11 with the interpretive appendix to Part 1630.
- Department of Labor, Wage and Hour Division — Fact Sheet #22 (Hours Worked), Fact Sheet #71 (Internship Programs) and Field Assistance Bulletin 2018-2.
This article is for general informational purposes and is not legal advice. Regulations, enforcement guidance and wage data change, and an individual situation can turn on facts this page cannot know — confirm the current position with the EEOC, the Department of Labor and the employer's own process before relying on any of it.
