Affirm HackerRank Online Assessment: Format, Time & Questions

Last updated: October 2026

Quick Answer

The Affirm HackerRank online assessment is the first technical screen for software engineers: a timed coding session that candidates report at roughly 60 to 90 minutes, focused on arrays, strings and hash maps, and sometimes proctored. Affirm does not publish the format, so everything below is candidate-reported. Drill the patterns in OphyAI Coding Interview, and rehearse talking through your reasoning in OphyAI Interview Practice.

Part	What candidates report
Platform	HackerRank
Length	About 60-90 minutes (one prep site; your invitation email states the real limit)
Topics	Arrays, strings, hashing; a 2022 Glassdoor report names shortest unique substring
Supervision	Some reviews describe a proctored session; others describe a live screen with an engineer
Alternative	A take-home is reported as an option for some candidates

What Affirm Is Testing in This Round

The screen checks fundamentals under time pressure, and whether the code you submit looks shippable. Candidate guides describe clean, readable code with edge cases handled as mattering more than a clever trick, which fits a lender where money bugs are regulated events. For the full loop, see the Affirm interview guide.

Reported red flags:

• Passing the sample case but failing empty, duplicate or single-element input.
• Code that works but is unreadable: one-letter names, no structure.
• Spending the whole session on one hard problem instead of banking easier points first.

What to Expect

Candidate reports are mixed, so confirm each point with your recruiter.

• Where it sits. One 2026 Glassdoor review lists the order as online assessment, recruiter screen, then technical interviews. The hub guide lists the recruiter call first. Order varies by team and time.
• Duration. TechPrep reports a 60-90 minute HackerRank session. A 1point3acres poster called the full-time software engineer assessment lengthy. Neither gives an official limit.
• Proctoring. A Glassdoor reviewer describes a proctored HackerRank session with two engineers watching. Treat it as possible, not certain.
• Language. One 1point3acres poster stressed knowing the Java version. Pick a mainstream language you know well and check which versions the editor offers.
• Difficulty. One candidate found it harder than standard LeetCode practice, and said it was “pretty complicated” if you had only done LeetCode.

Example Questions and How to Answer Them

These are reported themes or practice problems, not leaked questions.

1. Shortest unique substring in a list of strings

A 2022 Glassdoor candidate reported this. Approach: For each string, generate substrings by increasing length, count occurrences across all strings in a hash map, then pick the shortest substring with a count of one that comes from that string. State the cost (substrings per string times the length of each) and mention a suffix structure only if asked.

2. A hashing problem on arrays

A recent Glassdoor report describes an arrays-and-hashing problem. Approach: Ask what happens with duplicates, negative numbers and empty input. Build the map in one pass, then check the complement or count. Name the time and space cost in a comment.

3. String manipulation with edge cases

One 2022 candidate advised practicing string manipulation. Approach: Decide how to treat case, whitespace and empty strings before coding. Write small helper functions with real names instead of one long loop.

Practice these timed in OphyAI Coding Interview, then re-solve one with nothing open.

How to Prepare in 3 Days

• Day 1: patterns. Solve 4-5 problems each on arrays, strings and hash maps. Write tests for every solution and use full variable names.
• Day 2: timed sessions. Run two 75-minute sessions in a HackerRank-style editor: read all problems first, solve the easiest first, and leave 10 minutes to re-test edge cases. If a take-home is on offer, ask your recruiter which format suits you. See coding interview examples and solutions for practice sets.
• Day 3: narration and logistics. Practice explaining your approach aloud, then check your invitation email for the time limit, allowed languages and any proctoring rules. Run a mock in OphyAI Interview Practice for the thinking-aloud habit.

Start practicing →

Common Mistakes

• Treating it as a pure algorithm contest. Readability and edge cases are what candidate guides say Affirm rewards.
• Not reading the invitation for rules on tools, tabs and proctoring.
• Assuming AI help is fine. Several candidate guides report that Affirm prohibits AI tools in interviews. We could not find an Affirm page saying so, so ask your recruiter. See which companies allow AI in interviews. Use OphyAI for preparation, not during the assessment.
• Skipping a run of your own edge cases before submitting.

Related Guides

• Affirm interview guide (the full loop, compensation and system design)
• Coding interview examples and solutions
• Technical interview prep for software engineers

Frequently Asked Questions

Does Affirm use HackerRank?

Candidate reports say yes. TechPrep describes the technical screen as a HackerRank session, and Glassdoor reviewers mention HackerRank with a proctor. Affirm has not published its assessment format, so confirm the platform, language options and time limit in your recruiter’s invitation before you schedule your preparation.

How long is the Affirm HackerRank assessment?

One prep site reports a typical 60 to 90 minute session. Another candidate called the full-time engineering assessment lengthy. Because Affirm publishes no official limit, treat 60-90 minutes as a planning figure and rely on the time stated in your own invitation, which HackerRank tests normally show before you start.

What questions does the Affirm HackerRank test ask?

Reported themes are arrays, strings and hashing. A 2022 Glassdoor review names shortest unique substring in a list of strings, and a recent review describes an arrays-and-hashing problem. These are individual reports, not an official bank, so prepare the patterns and not specific answers.

Is the Affirm online assessment proctored?

Some candidates say so. One Glassdoor reviewer describes a proctored HackerRank session with two engineers, while a prep guide describes a live screen with an engineer as an alternative to a take-home. Policies may differ by team, so ask your recruiter what supervision applies and what you may have open.

What happens after the Affirm HackerRank assessment?

Candidate reports describe a hiring manager conversation and a virtual onsite with practical coding, system design and a values round. Timing varies by team, so ask your recruiter for the expected cadence after you submit. The Affirm interview guide covers each later stage and the reported three-to-five-week timeline.

Sources and verification notes

Checked October 2026. Direct fetches of Affirm’s careers site, HackerRank’s help pages and the third-party pages below were blocked by the network in this environment, so the details were read through search result summaries. Affirm does not publish its assessment format, so every specific here is candidate-reported, and we found no first-party statement on its AI policy.

• TechPrep, Affirm’s interview process (2026): reported 60-90 minute HackerRank session and take-home or live alternative. Third-party, checked October 2026.
• Glassdoor, Affirm interview reviews: candidate-reported proctored HackerRank session and loop order. Third-party, checked October 2026.
• Glassdoor, Affirm interview review: candidate-reported question themes including shortest unique substring. Third-party, checked October 2026.
• 1point3acres, Affirm full-time software engineer online assessment: candidate-reported lengthy assessment and Java version note. Third-party, checked October 2026.
• OphyAI, Affirm interview guide: loop context, itself candidate-reported. Checked October 2026.