← Back to Directory

Current

Small

Current is a US-based financial technology company offering mobile banking services, including checking accounts, debit cards, and features aimed at younger consumers and those seeking early access to their paychecks. It is known for its consumer-friendly digital banking experience and no-hidden-fee model.

4 interview notes · updated Jul 2026

Current·Software Engineer·Technical Phone Screen

Jul 2026
Interviewed for a software engineering role at Current. Three questions, mix of a custom data problem and two classic LeetCode-style ones. Nothing too wild but the range sum query one tripped me up a bit.
  • Given a list of transactions where each entry has a userId and an amount (positive for credit, negative for debit), compute the final balance for each userId.
  • Find the minimal length of a contiguous subarray whose sum is at least a given target. Return 0 if no such subarray exists. (LeetCode 209)
  • Design a data structure that supports both point updates and range sum queries on an integer array. (LeetCode 307)

“Pretty approachable.”

View Post

Current·Software Engineer·Onsite - Coding / Algorithms

Jul 2026
Coding round at Current for a software engineer role, three back-to-back algorithm problems with a clear emphasis on complexity analysis alongside the actual code. Nothing too wild but the segment tree discussion at the end caught me a bit flat-footed.
  • Given a list of transactions where each entry has a userId and an amount (positive for credits, negative for debits), compute the final balance per userId and return a map. You also need to discuss time and space complexity for large inputs.
  • Given an array of positive integers and a list of target values, for each target find the shortest prefix length k such that the sum of the first k elements is at least the target. Return -1 if no such k exists. Implement this using a prefix-sum array combined with binary search and analyze the complexity.
  • For an immutable array with only a few range-sum queries and no updates, write a recursive divide-and-conquer function to answer a single query. Then explain when you would build a segment tree instead and compare the trade-offs between the two approaches.

“Pretty standard aggregation problem.”

View Post

Current·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
One big behavioral question for a software engineering role at Current. The whole thing was basically a single deep-dive into a past project, and they wanted everything: context, decisions, results, regrets. More thorough than I expected for what I thought would be a lighter round.
  • Walk me through a project you owned from start to finish: what problem you were solving, your role, how you measured success, the technical decisions you made and why, risks you saw and how you handled them, who else you worked with, the timeline, and what actually shipped. Also what you'd change.

“This is a lot to cover in one answer and I did not pace myself well.”

View Post

Current·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Current for a software engineering role. The whole thing was basically one giant question about building a metrics monitoring platform from scratch, and they wanted you to go deep on pretty much every layer of it.
  • Design a metrics monitoring system that collects numeric metrics (counters, gauges, histograms) from many services using labels and tags, and supports both pull-based and push-based ingestion with high throughput and backpressure handling.
  • How would you store time-series data efficiently, including compression strategies and tiered storage with hot and cold data separation?
  • What query language or interface would you expose for aggregations, downsampling, and label-based filtering on the stored metrics?
  • How would you design the alerting layer, including threshold-based alerts, SLO tracking, silencing, deduplication, and alert routing?
  • How do you ensure high availability and horizontal scalability, and how would you handle multi-tenant isolation in this system?
  • How would you control cardinality explosion from label combinations and enforce per-tenant or per-service quotas?
  • Walk through the write path and read path in detail, including how you handle failures and what consistency guarantees you'd offer.

“This is where I spent most of my time and probably where I lost points.”

View Post