# The Take-Home AI-Use Call, Scored to Use Openly, Disclose, or Do Unaided

*You will read any take-home's AI policy and type against five dimensions, pick one of three actions, and write a disclosure line you can defend in the debrief.*

- Canonical URL: https://www.refolk.ai/candidates/guides/take-home-ai-use-call
- Pillar: Interviewing
- Format: Framework
- Published: 2026-10-10
- Last reviewed: 2026-10-10
- Reading time: 15 min

You have a take-home or an online assessment in front of you, and you need one decision: can you use AI on it, and what exactly do you have to say about it. This guide is for candidates mid-assignment who want a repeatable call, not a shrug. It turns the stated policy and the assessment type into a scored judgement that lands on one of three actions and gives you the disclosure wording to go with it.

Generic advice stops at "use AI transparently" and leaves the two hard cases unhandled: a silent policy, and a policy that permits AI yet demands you own every line in the debrief. Below is a procedure for both.

## What the five dimensions are and why they decide the call

The call turns on five dimensions: the stated posture, the assessment type, how much authorship AI would take, whether a debrief is scheduled, and any legal or data constraints. Score each, and the scores point to one of three actions: use openly, disclose, or do unaided.

Two of these dimensions do most of the work. The stated posture tells you the rule you are living under. Whether a debrief is scheduled tells you how high the ownership bar sits regardless of posture, because the conversation about the take-home is the test, not the artifact. The other three are tie-breakers that pull the call toward caution when the first two are ambiguous.

**80% - US candidates who say employer AI policies are vague, rare, or absent**

Only 18% say most employers have explicit, clear policies (Greenhouse 2026 report).

That gap is why this is a judgement call and not a lookup. The information you need is usually not published, so you score what you can read and ask for the rest.

> **Rule:** Absence of a ban is not permission
>
> On real assignment banks most postings do not mention AI at all. When the policy is silent, the dimension defaults to the conservative read: ask first, and if you get no answer, work unaided.

## The five postures a stated policy can take

Published policies cluster into five postures, and your first job is to decide which one you are reading. Each maps to a different starting point for the score.

| Posture | What it says | Exemplar | Starting action |
| --- | --- | --- | --- |
| Permitted, no disclosure | AI fine for prep; no mention needed | Prep-only "green" tier | Use openly |
| Permitted, with citation | Use it, cite tools, answer in your own words | GitLab | Disclose |
| Permitted, with notification | Allowed if you tell the interview team | Code.org | Disclose |
| Prohibited unless stated | Complete without AI unless told otherwise | Anthropic, PwC | Do unaided |
| Silent | No AI line anywhere in the materials | Most postings | Ask, then unaided |

GitLab says transparent AI use is welcome in technical assessments and that a take-home may use AI for research if you cite it, answer in your own words, and disclose the tools you used. Code.org permits candidates to use AI on take-homes and interviews provided you disclose your usage with the interview team. Anthropic asks candidates to complete take-home assessments without Claude unless indicated otherwise, and says it will be clear when AI is allowed. PwC tells candidates they should not use these tools during any assessment.

The silent posture is the common one and the one blog posts duck. On a sample of 1,765 job descriptions, only one company explicitly allowed AI in take-homes and none explicitly banned it. An open tracker of 20 companies found 10 ban candidate AI use and 8 allow or require it, which tells you that among companies that bother to publish, the split is roughly even and you cannot guess your way to the right posture.

> **Watch out:** Reading silent as allowed is the most common error
>
> No ban mentioned is not a yes. On real banks most postings never mention AI tool policy, so absence means the question is open, not settled in your favour. Default unaided or send the recruiter one line.

## The default when the instructions say nothing

When the policy is genuinely silent or ambiguous, the documented default is conservative: ask first, and if you cannot get an answer, produce work that reflects your independent capability. This protects you against the risk that AI use would violate an unstated policy, and you can note in the submission that you produced the work independently.

The inverse rule governs what you volunteer. When nobody has asked and your use was light and bounded, describe what you built and what you can defend, and leave the authorship confession out. Over-disclosing a prep-only use reads as either naivety or a flag you planted on yourself.

So the "ask first" step and the "do not over-disclose" step are not in tension. Ask when the rule is unknown. Disclose when the rule or the brief requires it. Stay quiet when neither the rule nor a request is in play and the help was minor.

#### From a silent policy to a defensible submission

1. **Read** - Confirm no AI line exists in the brief or invite
2. **Ask** - Send the recruiter the calibration question
3. **Wait** - If an answer arrives, follow its wording exactly
4. **Default** - No answer means work unaided and note independence
5. **Disclose** - Only if the rule or the brief asks for it

*When nothing is stated, the path runs ask, then default unaided, then disclose only if required.*

## The one message that resolves a silent policy

When the policy is silent, send the recruiter a single calibration line before you write anything. It is the highest-leverage move in the whole procedure, because the information genuinely is not published and asking signals professional behaviour rather than doubt.

**Recruiter calibration message for a silent AI policy**

```
Hi [name], I want to make sure I approach this appropriately. What is your policy on AI tool use during the assignment, and is there anything you would like me to note about how I worked?
```

*Send before you start. Keep it to two sentences; swap "assignment" for the exact word the brief uses.*

Recruiter guidance beats guesswork. Before writing code, confirm whether AI use is allowed and in what form. Use the company's wording back to them, not your own assumptions, and do not start the clock on a timed assessment until you have asked where asking is possible.

[Refolk](/candidates) tailors your resume and cover letter to each posting from your own history, which frees the hour you would otherwise spend rewriting application material and lets you spend it on the calibration and the debrief rehearsal that actually move this decision.

## Scoring the five dimensions and landing on an action

Score each of the five dimensions, then read the dominant signal. The stated posture and the debrief carry the most weight; the other three pull toward caution. This table is the scoring sheet to keep open.

| Dimension | Pulls toward use openly | Pulls toward disclose | Pulls toward do unaided |
| --- | --- | --- | --- |
| Stated posture | Permitted, no disclosure | Permitted with citation or notification | Prohibited, or silent with no answer |
| Assessment type | Take-home, async | Take-home with scheduled debrief | Timed or proctored round |
| Authorship AI would take | Bounded helper tasks | A drafted section you then rewrite | The core answer itself |
| Debrief scheduled | None | Yes, and you can explain every line | Yes, and you could not explain it |
| Legal or data constraints | None | Standard confidentiality | Recorded video under state consent law |

How to read it: if any dimension points to "do unaided," that signal dominates, because a single breach cannot be cured later. If no dimension points to unaided and at least one points to disclose, the action is disclose. Only when every dimension points to "use openly" do you use openly without a line.

#### Posture against debrief

Horizontal axis runs from Permitted posture to Prohibited or silent posture. Vertical axis runs from No debrief scheduled to Debrief scheduled.

| Quadrant | What it means |
| --- | --- |
| Permitted, no debrief | Use openly; keep a light decision log in case they ask |
| Prohibited, no debrief | Do unaided; absence of a check is not a loophole |
| Permitted, debrief scheduled | Disclose and rehearse; be ready to defend every line |
| Prohibited, debrief scheduled | Do unaided; the debrief will expose anything you cannot explain |

*The scheduled debrief raises the ownership bar even when the posture permits AI.*

The debrief deserves its heavy weight. Across 19,368 live interviews analyzed between July 2025 and January 2026, 38.5% of candidates were flagged for AI-assisted answers, a rate that tripled from 9% to 45% in one three-month stretch. Take-homes feel safer than live rounds, but a scheduled follow-up is a human detector, and it does not need software to catch an answer you cannot explain.

## The procedure, start to finish

Run these seven steps in order. The disclosure step is conditional: you write and place a line only if the rule or the brief asks for it, otherwise you hold it.

#### From assignment in hand to a defensible submission

1. **Read for an explicit AI line** - Scan the assignment and invite email for one of the five postures. You are done when you can quote the exact sentence or confirm none exists.
2. **Classify the assessment type** - Name whether it is a take-home case, timed coding, one-way video, or live round. You are done when you have named exactly one type.
3. **If silent or ambiguous, ask the recruiter** - Send the calibration message before any work begins. You are done when the question is sent and no line is yet written.
4. **Score five dimensions and land on an action** - Rate posture, type, authorship, debrief, and constraints, then pick use openly, disclose, or do unaided. You are done when one action is chosen.
5. **Produce the work to the calibrated level** - If permitted, use AI for bounded tasks and keep a decision log. You are done when every line is defensible.
6. **Write the disclosure line** - State tool, your decisions, and your checks, and place it per the brief. You are done when you have one or two factual sentences, or have confirmed none is required.
7. **Rehearse the debrief** - State your reasoning before prompting, inspect every generated change, test it, and note where you rejected a suggestion. You are done when you can defend any line unaided.

Step five is where discipline pays off. If use is permitted, deploy AI for tightening tests, improving naming, drafting documentation, and checking edge cases, not for asking for the whole answer. The decision log is your insurance for step seven: it records where you accepted, rejected, or modified a suggestion, which is exactly what a debrief probes.

## How to write the disclosure line

A compliant disclosure names three things in a sentence or two: which tool, which decisions were yours, and what you checked before you shipped it. A line missing any of the three reads as vague and invites the questions you were trying to prevent.

**Disclosure line for a permitted-with-disclosure take-home**

```
I used [tool] to help with [specific bounded support, e.g. drafting the test scaffold and suggesting edge cases], then I [your human work, e.g. wrote the core logic, rejected two suggested approaches, and refactored the data layer] and checked the final version for [accuracy, correctness against the brief, and readability].
```

*Fill the bracketed parts with specifics. One or two sentences; place it where the brief asks or at the top of your README.*

Vague fails on purpose-built grounds: a line like "I used AI to help" raises more questions than it answers, because a marker cannot tell whether you mean spell-check or a ghost-written paragraph. Specific wins because it demonstrates the judgement the employer is actually scoring. GitLab, for one, evaluates how you appropriately leverage AI and expects you to discuss how you collaborate with it, so a precise line is evidence in your favour, not a confession.

> A specific disclosure line is a cheap differentiator, because almost nobody writes one.

The behaviour is rare where it is required. A survey of 500 US job seekers found 54.2% would never bring AI up with an employer, and only about one in eight always discloses. Set against near-universal adoption, a precise line marks you as the candidate who can be trusted with the tool.

| Metric | Value | Source |
| --- | --- | --- |
| Job seekers using AI in search | 36% | Gdoc.io 2026 |
| Job seekers using AI in search | 80% | Clutch 2026 |
| Would never tell an employer | 54.2% | Gdoc.io 2026 |
| Live-interview AI flag rate | 38.5% | Fabric 2026 |

The two adoption figures differ because the surveys differ in sample and wording, so read them as a range rather than a single truth. Either way, the share who disclose is a small fraction of the share who use.

## Why employers increasingly permit-with-disclosure rather than ban

Employers testing genuine AI-collaboration skill are assessing a scarce trait, which is why the permit-with-disclosure posture is spreading. In Refolk's index of professional profiles, the talent that can do this well is thin and concentrated.

| Skill (US Software Engineers) | Count | Share of Python pool |
| --- | --- | --- |
| Python | 55,005 | 100% baseline |
| Artificial Intelligence | 1,707 | 3.1% (derived) |
| Prompt Engineering | 1,618 | 2.9% (derived) |

In Refolk's index, 55,005 US profiles titled Software Engineer list Python, but only 1,707 list Artificial Intelligence and 1,618 list Prompt Engineering, each roughly a 3% slice. The AI and prompt-engineering pools are nearly equal, a ratio of about 1.05, which suggests the two skills travel together. The scarcity is also geographic: Refolk's index shows 1,707 US Software Engineers tagging AI against 173 in the UK, a derived 9.9x gap. When the skill is this rare, banning the tool in assessment throws away the signal an employer most wants, so they ask you to use it openly and show your judgement instead.

That is the strategic read behind the posture table: a prohibited policy is often about integrity on a specific role, while a permit-with-disclosure policy is the employer actively trying to measure how you collaborate with the tool.

Ask me this: `Software engineers in the US who list both Python and Prompt Engineering as skills.` - [run the search](https://www.refolk.ai/start?q=Software%20engineers%20in%20the%20US%20who%20list%20both%20Python%20and%20Prompt%20Engineering%20as%20skills.).

*Returns the US engineers whose profiles pair core Python with prompt-engineering, the scarce overlap employers probe in AI-collaboration take-homes.*

## How this call goes wrong

The call fails in predictable ways, and most failures are a dimension misread rather than a bad intention. Each one below has a check you can run before you submit.

- **Reading silent as allowed.** No ban is mentioned, so you use AI freely. Check: absence is not permission; on real banks most postings never mention policy, so default unaided or ask.
- **Vague disclosure.** "I used AI to help" feels honest but tells a marker nothing. Check: does your line name the tool, your decisions, and your review? If not, rewrite it.
- **Over-reliance you cannot defend.** A clean submission paired with a hollow debrief. Check: can you explain every line unaided? Submitting AI-generated work you cannot explain is a fast path to rejection at any company that runs a thorough follow-up.
- **Over-disclosing when unasked.** A volunteered confession on prep-only use. Check: was disclosure required or requested? For light, bounded help you do not need to proactively tell a recruiter.
- **Disclosure as a fix for a breach.** Using AI where banned, then disclosing. Check: a disclosure sentence does not fix a rule breach; if the posture is prohibited, do the work unaided.
- **Treating all rounds alike.** Applying take-home rules to a live or proctored round. Check: the rules may differ by type, so ask before you start and use the company's wording.
- **Assuming permitted means no ownership expected.** Even GitLab requires you to explain your prompts and technical decisions and to avoid presenting generated content as your own. Check: permitted raises your ownership bar, it does not remove it.

> **Watch out:** Disclosure never cures a breach
>
> Using AI where it is prohibited and then confessing still means you broke the rule. One published policy names a missing disclosure as grounds for removal, and Greenhouse states undisclosed use outside its guidelines may disqualify candidacy.

The through-line of these failures: the artifact is not where candidates lose. The take-home is not the test, the conversation about the take-home is the test, and anything you cannot explain becomes a liability the moment somebody asks a follow-up question.

## Before you submit

Run this checklist against the assignment in front of you. If any item fails, do not submit yet.

#### Pre-submission check

- [ ] I can quote the stated AI posture, or I confirmed none exists and asked the recruiter
- [ ] I named the assessment type and applied its rules, not a take-home default to a live round
- [ ] My action is one of use openly, disclose, or do unaided, chosen from the five-dimension score
- [ ] Where I used AI, I have a decision log and can explain every line unaided
- [ ] My disclosure line names the tool, my decisions, and my checks, or I confirmed none is required
- [ ] I did not use AI anywhere the posture prohibits it
- [ ] I rehearsed the debrief and can defend my reasoning for each change I accepted or rejected

## Keeping the call current

Re-run the posture read for every employer, because policies are published unevenly and change without notice. The structural gap is the thing to remember: 80% of US candidates report employer policies as vague, rare, or absent, and 63% of job seekers have now been interviewed by an AI, up 13 points in six months. The direction of travel is more AI in the process and more scrutiny of how you use it, not less.

Two mechanisms are worth watching rather than any fixed number. First, detection in live rounds is climbing fast, so a concealment strategy that works today degrades quickly; the defensible-disclosure strategy does not. Second, state law is moving: Illinois already requires advance notice, a general explanation, and consent before AI analyzes a recorded video interview, which means a video round can carry legal constraints a take-home does not. Re-check the posture, re-check the type, and re-score. The five dimensions do not change; the values you plug into them do.

## Frequently asked questions

### Can I use AI on a take-home assignment if the instructions say nothing about it?

Treat silence as a reason to ask, not as permission. On a sample of 1,765 job descriptions, only one company explicitly allowed AI in take-homes and none explicitly banned it, so most assignments simply do not mention it. The documented default when you cannot get an answer is to work unaided and note that you produced the work independently. Absence of a ban is not the same as a green light.

### How do I disclose AI use to an employer without raising red flags?

Write a specific line that names three things: which tool you used, which decisions were yours, and what you checked before shipping. A template that works: "I used AI to help with X, then I did Y and checked the final version for accuracy, relevance, tone, or evidence." Vague lines like "I used AI to help" raise more questions than they answer, because a marker cannot tell whether you mean spell-check or a ghost-written paragraph.

### Should I use ChatGPT for a take-home interview if the policy permits it?

Yes, but only for bounded tasks you can explain: tightening tests, improving naming, drafting documentation, or checking edge cases. Do not ask for the whole answer. Even where use is permitted, GitLab expects you to explain your prompts and technical decisions and to avoid presenting generated content as your own. Permitted never means no ownership expected. The follow-up conversation is the real test.

### What happens if I use AI where it is banned and then disclose it?

Disclosure does not cure a breach. Using AI where it is prohibited and then confessing still means you broke the stated rule. One company publishing a policy names a missing disclosure as grounds for removing you from the process, and Greenhouse states that undisclosed AI use outside its guidelines may disqualify candidacy. If the posture is prohibited, the correct action is to do the work unaided.

### Will the employer actually detect AI use on a take-home?

The debrief detects it even when software does not. Across 19,368 live interviews analyzed between July 2025 and January 2026, 38.5% of candidates were flagged for AI-assisted answers, a rate that tripled from 9% to 45% in one three-month stretch. Take-homes feel safer, but the follow-up conversation exposes anything you cannot explain, which is why defensibility matters more than concealment.

---

*From the Refolk guide library. I revise these guides rather than replacing them, so the current version is always at https://www.refolk.ai/candidates/guides/take-home-ai-use-call*