Airbnb · OA
In processAirbnb SWE CodeSignal OA: 19 Experiences
Airbnb SWE CodeSignal OA, July–September 2026: 19 reports, mostly one small system built over four levels, like banking or cloud storage.
At a glance
- Process: a 90-minute CodeSignal OA with an interface, starter code and unit tests; one system grows over four levels, and each level opens only after the last one passes (05, 07, 18). One sitting required the camera (03).
- Asked recently: banking or credit ledgers in 7 of 19 reports, file or cloud storage in 5, task management in 2, worker hours in 2, and a recipe system, a record store and parcel events once each.
- Difficulty: candidates called the logic manageable; the hard part is keeping state right as timestamps, scheduled events, user limits, merging and backups arrive (01, 04, 11, 14, 15). Full scores did not guarantee an interview (03, 04).
- Practise first: Progressive Banking System, In-Memory File System, Task Management System and Worker Management with Full-Shift Double Pay.
Coverage: 19 Airbnb SWE and senior software candidates, mostly full-time, all taking the CodeSignal OA; report dates July 21 to September 24, 2026. Two short reports (09, 13) only confirm an earlier prompt, but each is an independent sitting.
What came up
The names changed, but the shape did not: one stateful program, four test-gated levels. One candidate is counted once per row.
| Topic | Reports | Last seen |
|---|---|---|
| Banking or credit ledger | 7 of 19 | Sep 2026 |
| File or cloud storage | 5 of 19 | Sep 2026 |
| Task management | 2 of 19 | Aug 2026 |
| Worker hours and pay | 2 of 19 | Aug 2026 |
| Record store with TTL | 1 of 19 | Aug 2026 |
| Recipe management | 1 of 19 | Jul 2026 |
| Parcel event tracking | 1 of 19 | Jul 2026 |
Questions we found
All dates are report dates.
Four-level OA systems
| Question | Reports | Last seen |
|---|---|---|
| Progressive Banking System | 6 | Sep 2026 |
| Cloud storage with user backup and restore | 3 | Aug 2026 |
| In-Memory File System | 2 | Sep 2026 |
| Task Management System | 2 | Aug 2026 |
| Worker Management with Full-Shift Double Pay | 2 | Aug 2026 |
| Workspace Credit Ledger | 1 | Aug 2026 |
| In-memory database with prefix scan and TTL | 1 | Aug 2026 |
| Recipe Management System | 1 | Jul 2026 |
| Parcel Event Tracking | 1 | Jul 2026 |
The cloud-backup and in-memory-database tasks have no live FastPrep problem right now, so they are not linked.
19 detailed candidate timelines, loops, and screens
01: Banking, scheduled payments and account merges
Report date: September 24, 2026
- Progressive Banking System: level 1 accounts, deposits and transfers; level 2 top spenders; level 3 scheduled payments in strict timestamp order; level 4 merging accounts while keeping balances and history.
- The candidate did not finish level 3 and scored 440. Their warning: due payments may need to run before every later operation.
02: Banking with offline and deletable transfers
Report date: September 22, 2026
- This banking version asked for user creation, normal transfers, offline transfers and deleting a pending transfer; transfer state got much harder from level 3.
- In the CodeSignal editor, clicking the wrong file could drop you into a test or interface file, so the candidate suggested learning the editor first.
03: Cloud storage with compression, full score, rejected
Report date: September 8, 2026 · Result: rejected a week later
- In-Memory File System: add, get and copy files; search by prefix and suffix; users with storage limits; compress and decompress.
- In Python, the candidate finished all four levels in about 40 of the 90 minutes with a full score. The sitting required the camera.
04: Cloud storage with backup and restore
Report date: August 28, 2026 · Result: rejected the next day
- Level 1 add, delete and look up files; level 2 the largest files under a prefix, ties by name; level 3 users, capacity and merging users; level 4 backup and restore, skipping a restored file when another user already owns that name.
- Full score. The candidate's tip: keep the early data model together, because levels 3 and 4 touch nearly every earlier operation.
05: A record store with prefix scan and TTL
Report date: August 28, 2026 · Result: passed
- An in-memory database of nested hash maps (objects with fields and values): set, get and delete; scan fields by prefix; then timestamps and TTL (time to live), ignoring or cleaning expired fields.
- Detailed but not hard; 90 minutes felt fair. The edge case: a field shorter than the prefix must not match.
06: The fullest cloud-backup prompt
Report date: August 26, 2026 · Status: no follow-up yet
- Cloud storage with user backup and restore: add, get and delete files, top-N ranking, users with capacity, merging users, snapshots, restoring the latest snapshot and resolving name conflicts.
- Full score, but no reply at the time of the update.
07: Banking as one codebase with tests
Report date: August 23, 2026 · Status: waiting
- The candidate stressed that the Progressive Banking System was one codebase with four test-gated levels, not separate LeetCode questions: balances, outgoing totals with tie-breaks, scheduled payments, then merging with history.
- Their design: one central account state plus a shared function that processes due payments.
08: Workspace credits with delayed cashback
Report date: August 22, 2026 · Status: waiting
- Workspace Credit Ledger: create workspaces and move credits; rank by credits spent; a 2% rebate exactly 24 hours after spending, with transaction-status lookup; merge workspaces and answer historical-balance queries.
- The candidate did not finish level 4.
09: Same banking prompt, hard editor
Report date: August 21, 2026
- Same banking prompt as report 15; not finished.
- Red error marks and broken autocomplete made it hard to type the given APIs quickly.
10: Cloud backup with an admin edge case
Report date: August 20, 2026
- Cloud storage with user backup and restore: file operations, top-N by prefix, users and capacity, merging, then backup and restore.
- The last two failing tests were backup and restore for the built-in admin user, which follows different capacity rules but still needs backups.
11: File system with user capacity
Report date: August 18, 2026
- In-Memory File System: add and copy, prefix-and-suffix search, users with capacity, compression.
- Finished level 3 and ran out of time on level 4. The design had to track owner, stored size, original size and used capacity; a level-3 change broke level-2 copy behavior.
12: A banking variant and platform errors
Report date: August 18, 2026 · Result: failed
- A different story with almost the same operations as the Progressive Banking System. The problem felt manageable, but the page kept showing errors and was hard to navigate. Full interfaces were not shared.
13: A second working-hours sighting
Report date: August 17, 2026 · Status: waiting
- The candidate pointed to report 18's Worker Management with Full-Shift Double Pay as the same prompt, with no new rules.
14: Task management with quotas and overdue work
Report date: August 7, 2026
- Task Management System: create, update and read tasks with sequential IDs; case-sensitive name search sorted by priority then creation order; users, quotas, assignments, finish times and auto-expiry; completing assignments and listing those that expired unfinished.
- The key change: stop deleting expired assignments, since level 4 still needs them; an append-only list with status flags worked better.
15: Banking with historical balance
Report date: July 31, 2026
- Progressive Banking System: accounts, deposits, transfers, top spenders, scheduled payments and cancellation, merging and balance-at-time queries.
- Most of level 4 done, a few tests failing at the end. The fix: a shared settlement step run before operations so scheduled payments update balances and totals.
16: Recipe management
Report date: July 29, 2026 · Result: rejected August 5
- Recipe Management System: recipe CRUD with case-insensitive unique names; ingredient search and sorted listing; users who can edit recipes while names stay unique.
- Passed two levels, wrote level 3 with failing tests, never unlocked level 4; debugging ate the clock.
17: Parcel events, from screenshots
Report date: July 27, 2026
- Parcel Event Tracking: count events per parcel, read and remove; rank parcels by events; assign couriers and courier events; undo courier changes and courier sign-out. Only level 1's exact rules were fully visible.
18: Working Hours Register
Report date: July 26, 2026
- A 90-minute, four-level Worker Management with Full-Shift Double Pay system: record entry and exit and total time; top workers by time; promotions on a future entry, with pay at each session's rate; double pay only for a full shift inside an approved bonus period.
- An interface and sample-style tests were provided.
19: A task database for a senior role
Report date: July 21, 2026 · Role: senior
- A four-level Task Management System; time was very tight. Another candidate in the same thread shared a richer version: task CRUD, sorting by priority and timestamp, users with quotas and expiry, and historical assigned-task counts. Our practice page does not fully cover the multi-user history part.
- Several people there finished only two or three levels.
Patterns across the reports
- One system, four gated levels. Every detailed report describes one codebase that grows level by level, unlocked only when tests pass (05, 07, 14, 18).
- Banking repeats the most. Six reports had the banking system or a close variant (01, 02, 07, 09, 12, 15), plus the credit-ledger version in 08.
- Shared helpers save the late levels. Reports 07 and 15 both used one function to process due payments before other operations; 04 and 11 warned that later levels touch or break earlier code.
- Full scores, then silence or rejection. Reports 03 and 04 got full scores and were rejected; 06 had no reply.
- The editor costs time. Reports 02, 09 and 12 all struggled with the CodeSignal page itself.
Common questions
What is the Airbnb CodeSignal OA?
A 90-minute assessment with one system that grows over four test-gated levels (05, 18), such as banking, cloud storage, tasks or worker hours.
Does a perfect score on the Airbnb OA get you an interview?
Not always: reports 03 and 04 had full scores and were rejected, and 06 had heard nothing.
Which Airbnb OA question comes up most?
The banking system: six reports (01, 02, 07, 09, 12, 15), most recently September 2026.
Is the Airbnb OA proctored?
Report 03 said the camera was required for their sitting.
Keep practicing
- Progressive Banking System, In-Memory File System and Workspace Credit Ledger: the banking and storage tasks from reports 01–15.
- Worker Management, Part 3: Promotions and Salary: the level before full-shift double pay in report 18.
- Credit Accounts with Scheduled Transfers and Parcel Attribute Store with TTL: newer Airbnb OA tasks from later reports.
- Airbnb coding question bank (sign-in needed).
- Airbnb interview guide and hiring insights.
- Experience feed: more interview reports from other companies and roles.
Sources: Anywhere useful interview info can be found.
Comments
0No comments yet — be the first to share what you know.