numeric

Small

Numeric is a financial technology company that builds AI-powered accounting software to help finance teams automate the month-end close process, reconciliations, and financial reporting. It is known for streamlining accounting workflows for high-growth companies and modern finance departments.

3 interview notes · updated Jul 2026

numeric·Software Engineer·Technical Phone Screen

Jun 2026

Coding round at Numeric for a software engineer position. One algorithmic problem, greedy with a heap, the kind of question that looks clean on paper but has a few subtle edge cases that can trip you up mid-interview.

A spaceship travels from a start position toward a target along a 1-D axis, with a fixed starting fuel and a list of refueling stations (each with a position and fuel amount). Every unit of distance costs one unit of fuel. What is the minimum number of stops needed to reach the target, or -1 if it's impossible?

“My first instinct was DP and I started going down that road before catching myself.”

View Post

numeric·Software Engineer·Technical Phone Screen

May 2026

Got a coding round at Numeric for a software engineer role. One problem, graph-based, took up the whole session. Not the hardest thing I've ever seen but the details trip you up if you're not careful.

You're given a list of translators, each defined as a directed edge from one language to another, and an API call for each edge that performs the actual translation. Given a source language and a target language, find a translation path if one exists and apply each translation in sequence to convert the input text.

“My first instinct was to reach for Dijkstra but there's no weights here so BFS is cleaner and finds the shortest chain.”

View Post

numeric·Software Engineer·Technical Phone Screen

Apr 2026

Numeric had me work through a paginated API aggregation problem that sounds straightforward until you start thinking about all the ways it can fall apart in production. The conversation went pretty deep into failure handling and I wasn't fully prepared for how much they cared about the retry logic.

You have a paginated server endpoint that returns a page of records and a continuation token. Write code to consume all pages and group the results by a 'planet' field. Then walk through how you'd handle rate limits, transient failures with retry/backoff, and merging partial state if something fails mid-way.

“My loop logic was fine, the grouping was fine, but I stumbled when they asked about partial state merging.”

View Post