Company
Valon interview questions
8 practice questions in the style of Valon's interviews, covering Software Engineering Fundamentals, System Design, Coding & Algorithms.
0 easy6 medium2 hard
Valon interview questions by the numbers
Last updated
Katkat has 8 Valon interview questions. The largest topics are Coding & Algorithms (38%), Software Engineering Fundamentals (38%) and System Design (25%). By difficulty: 75% medium and 25% hard. The most common round is Technical Screen (63%). Frequent concepts include Data Structures, Algorithms, API Design and billing.
Topics
- Coding & Algorithms38% · 3
- System Design25% · 2
Difficulty
- Medium75% · 6
- Hard25% · 2
Interview rounds
- Technical Screen63% · 5
- Onsite38% · 3
Roles
- Software Engineer88% · 7
- Backend Engineer13% · 1
Frequent concepts
- Data Structures25% · 2
- Algorithms13% · 1
- API Design13% · 1
- billing13% · 1
- data-structures13% · 1
- Databases13% · 1
Most mentioned in interview experiences
- 1.Build a staged banking service: ATM cash, statements, transfers, fees, slow transfers1 report
- 2.Design an In-Memory Database1 report
- 3.Design Correct Stateful Services for Irregular Financial Events1 report
- 4.Loan Ledger: Fee-First Payments and Out-of-Order Event Processing1 report
Counted from 3 candidate interview experiences on Katkat. How we collect and count
Showing 1–8 of 8 results
A staged, roughly two-hour coding exercise to build a banking service: ATM balance, deposits and withdrawals, per-account statements that include failed transactions, instant transfers, external transfers that charge a fee, and slow transfers that hold funds until they arrive. It tests exact money handling, ledger design and extensible code.
ValonSoftware EngineerSoftware Engineering FundamentalsOnsiteA systems-design interview about correct stateful processing for sparse records, out-of-order loan events, investor payment allocation, and authenticated APIs. It emphasizes idempotency, ledgers, exact arithmetic, recovery, and auditability.
ValonBackend EngineerSystem DesignOnsiteSystem design question about a loan system in which borrowers make repayments and the investors who own the loans are paid on a schedule. It tests loan and ownership modeling, repayment allocation, exact ledger accounting, idempotent payout runs, cent-level splitting among investors, and handling of payments reversed after a payout.
ValonSoftware EngineerSystem DesignOnsiteThis question evaluates a candidate's skills in data modeling, in-memory data structures, index design, and query/filter semantics for a flexible schema-less record store.
ValonSoftware EngineerCoding & AlgorithmsTechnical ScreenDesign and implement an in-memory query engine capable of ingesting records and executing structured queries with comparison, membership, and logical operators.
ValonSoftware EngineerCoding & AlgorithmsTechnical ScreenThis problem tests your ability to design a flexible, in-memory table structure that supports dynamic schema definition, data storage, and basic relational query operations.
ValonSoftware EngineerCoding & AlgorithmsTechnical ScreenImplement loan accounting handlers in Python where fees increase the fee balance and payments pay down fees before principal, then build a ledger that accepts payment and fee events out of order. It tests keeping events ordered by accounting sequence, updating later balances without reprocessing the whole history, handling ties and overpayments, and analyzing per-call cost.
ValonSoftware EngineerSoftware Engineering FundamentalsTechnical ScreenImplement billing event handlers where credits pay down usage before the subscription fee, then build a ledger that accepts charge and credit events out of chronological order and recomputes only the balances that a backdated event actually invalidates.
ValonSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
Valon interview experiences
All 3 →- Phone Screen on an Out-of-Order Loan LedgerValon · Software Engineer · Technical Screen · Sep 2026
This was the phone screen. It was an OOP coding problem about a bank ledger. I had seen someone mention it on the forum but with no specifics, and if you haven't prepared in advance, time gets a bit tight. The first part is designing a simple dataclass and 2 basic functions, which are just simple addition and subtraction. The second part is the real focus. You design 2 functions that handle the 2…
- Four One-Hour Onsite Rounds in a Single DayValon · Backend Engineer · Senior+ · Onsite · Apr 2026
The recruiter got back to me within a day, really fast. First round, coding — 3 levels, 2 of which were the bar to clear. You write a schemaless database (an in-memory SQL), but you're given each column's type and name. Some rows might be missing certain columns. The first level is figuring out what data structure to use, then basically being able to store and read. The second level does filter a…
- Two-Hour Bank Service Build, Then an HM RoundValon · Software Engineer · Onsite · Jan 2026
Valon's onsite format is pretty unusual: you get 2 hours to implement one problem. The goal is to build a banking service made up of 5 parts. My feeling is that you need to get through at least parts 3-4, but you are not required to finish everything. How the time is split: First 30 minutes: go through the problem with an engineer, discuss the design, and start building. Middle 90 minutes: you wr…
More companies
- Meta666
- Amazon653
- Google486
- OpenAI342
- Capital One268
- Microsoft252
- DoorDash241
- Anthropic225
- Uber217
- Apple177
- TikTok176
- Pinterest161
- ByteDance160
- LinkedIn154
- Stripe139
- Snowflake130
- Databricks122
- Airbnb112
- Rippling106
- Oracle104
- Coinbase99
- Netflix97
- NVIDIA95
- Snapchat94
- Citadel90
- Waymo90
- Instacart87
- Roblox84
- Salesforce77
- Optiver76
- Shopify63
- Robinhood60
- Atlassian55
- Hudson River Trading55
- Two Sigma55
- J.P. Morgan53
- PayPal53
- xAI53
- Lyft52
- Tesla52