← Back to Directory

Circle

Large Enterprises

Screna has 9 Circle interview write-ups. The most reported round is the technical phone screen (5).

9 interview notes · updated Jun 2026

Circle·Software Engineer·Technical Phone Screen

Jun 2026
Circle SWE interview, level 3 of a banking system design problem. The whole thing was one extended coding question building on a payment scheduling feature, and it got pretty involved with edge cases around execution ordering and failure handling.
  • Implement a payment scheduling system where schedulePayment takes a timestamp, account ID, amount, and delay, then returns a unique payment ID. cancelPayment should cancel a pending payment for a given account. Critically, every operation must first flush all pending payments whose execute time is at or before the current timestamp before doing anything else.

“The flushing requirement is what trips you up.”

View Post

Circle·Software Engineer·Technical Phone Screen

Jun 2026
Circle technical screen for a software engineering role, focused on a banking system design problem. The question was about implementing a leaderboard-style function on top of an existing account system, which sounds straightforward until you're actually in it.
  • You're building on top of a banking system. Implement a `topSpenders(timestamp, k)` function that returns the top k accounts by total outgoing spend. Only outgoing transfers and outgoing payments count; incoming transfers and deposits are excluded. Results should be sorted by spend descending, with ties broken by account ID lexicographically ascending. Return strings formatted like `'alice(1200)'`. If fewer than k accounts have spent anything, just return all of them.

“The sorting was the part I nearly tripped on.”

View Post

Circle·Software Engineer·Technical Phone Screen

Jun 2026
Circle SWE interview that went deep into extending a banking system, specifically around historical balance queries. The problem built on earlier levels so if you hadn't nailed the transfer logic beforehand, this part got messy fast.
  • Extend a banking system so that you can query an account's balance at any past timestamp. How would you design the data structure and retrieval logic for this?

“The core idea isn't too bad once you see it: keep a per-account list of (timestamp, delta) pairs and precompute prefix sums so each query is just a binary search.”

View Post

Circle·Software Engineer·Online Assessment (OA)

Jun 2026
Circle SWE interview had a CodeSignal-style multi-level banking system problem. Level 1 was more involved than I expected for a first level, covering account creation, deposits, and transfers with a bunch of edge cases to handle.
  • Implement a basic banking system with createAccount, deposit, and transfer operations, each taking a timestamp along with the relevant account IDs and amounts. createAccount should return false if the account already exists. deposit should return the new balance or an error if the account is missing. transfer should move funds between two accounts and return the source's updated balance, failing on missing accounts, same-source-as-target, or insufficient funds.

“The createAccount and deposit parts were pretty mechanical.”

View Post

Circle·Software Engineer·Technical Phone Screen

May 2026
Circle SWE interview, got into the deeper levels of a multi-part banking system design problem. This particular portion was about account merging logic and it got complicated fast.
  • Implement a mergeAccounts function that takes a timestamp, a source account ID, and a target account ID. It should merge the source into the target by combining balances, combining spending statistics used by a top-spenders feature, reassigning all pending scheduled payments from source to target in order of execution time then creation order, and then deleting the source account. Return false if either account doesn't exist or if source and target are the same.
  • Implement a getBalance function that takes a timestamp and an account ID, executes any pending scheduled payments whose execution time is at or before the given timestamp, and returns the resulting balance. Return null if the account does not exist, including accounts that have been merged away.

“The balance and spending stats part felt manageable but the pending payments ordering tripped me up.”

View Post

Circle·Software Engineer·Onsite - Coding / Algorithms

May 2026
Circle SWE interview had a coding round where you basically just had to build a Task class from scratch. Not conceptually hard but it eats up your time if you're not careful with the implementation details.
  • Implement a Task class that supports adding tasks and retrieving the current list of tasks, with formatted output.

“The actual logic is pretty simple.”

View Post

Circle·Software Engineer·Technical Phone Screen

May 2026
Circle had me build out a banking system in three escalating stages during a technical screen. The problem was well-structured and each level genuinely built on the last, which I appreciated, though the transfer expiry logic in level 3 tripped me up more than I expected.
  • Implement basic banking account operations: creating accounts (rejecting duplicates), depositing funds, and processing payments while tracking cumulative outgoing totals per account.
  • Given the account system above, implement a TOP_SPENDERS query that returns the top N accounts by total payment outflow, with ties broken alphabetically by account ID.
  • Extend the system to support transfers between accounts with a pending state: transfers deduct from the source immediately but only credit the target upon explicit acceptance, and expire automatically after 24 hours if not accepted.

“Pretty standard warm-up.”

View Post

Circle·Software Engineer·Online Assessment (OA)

May 2026
Circle OA for a Software Engineer role, one problem, multi-level CRUD design with some sneaky edge cases baked in. The kind of thing that looks like a warmup until you actually read the update rules.
  • Design a Recipe Storage system supporting Create, Read, Update, and Delete operations. Each recipe has a name, ingredients list, and steps list. Add returns an auto-incrementing string ID. Name matching on Add is case-insensitive and duplicates are rejected. Update only succeeds if the new name matches the stored name case-insensitively (no actual renames allowed). All operations return a success or failure indicator.

“The Add and Delete parts were fine.”

View Post

Circle·Software Engineer·Online Assessment (OA)

May 2026
Did an online assessment for a Software Engineer role at Circle. The coding problem wasn't conceptually hard but it ate up more time than expected just dealing with string filtering and sorting mechanics.
  • Given a list of tasks at a specific point in time, filter out tasks whose names contain a given substring, then sort and print the results.

“The logic itself wasn't the issue.”

View Post