← Back to Directory

Valon

Small

Screna has 10 Valon interview write-ups. The most reported round is the technical phone screen (10).

10 interview notes · updated Jun 2026

Valon·Software Engineer·Technical Phone Screen

May 2026
Valon SWE interview had me extending a basic in-memory database with ORDER BY support. The problem itself was well-scoped but the follow-up discussion on edge cases is where things got interesting.
  • Given an in-memory SQL-like database that supports INSERT and a basic SELECT with filtering, extend SELECT to support ORDER BY with a specified column and direction. Ties in the sort should be broken by insertion order.
  • How does sort stability apply here, and what happens if the ORDER BY column contains mixed types or null values?
  • What is the time complexity of the full query pipeline including filtering, projection, and sorting?

“The base implementation was straightforward enough, rows as a list of dicts, filter by equality, project columns.”

View Post

Valon·Software Engineer·Technical Phone Screen

May 2026
Valon software engineer interview that was essentially a mini database engine problem. You start with a basic in-memory table structure and have to bolt on filtered selects, then talk through how you'd extend it further with indexing and richer operators. Pretty focused session, no fluff.
  • You have an in-memory database with INSERT and SELECT already working. Extend SELECT to support a filter argument that matches rows using equality conditions on one or more columns. Rows should come back in insertion order, projected onto the requested columns.
  • How would you generalize your filter implementation to support comparison operators like greater than, less than, IN, and BETWEEN, and what are the trade-offs involved?
  • How would a per-column hash index improve filter performance, and what are the costs of maintaining one?

“The core part wasn't bad.”

View Post

Valon·Software Engineer·Technical Phone Screen

May 2026
Valon software engineer interview that focused on OOP design fundamentals. The question was deceptively involved once you got into the weeds of equality semantics and how the class fits into a bigger system.
  • Design an Employee class with id, name, and email fields. Cover the constructor, getters/setters, equality based on id, email validation, immutability of id, hash consistency, and how this class would fit into a broader Company or manager/report hierarchy.

“Started fine with the basic fields and constructor, but the equality and hashCode piece tripped me up a bit.”

View Post

Valon·Software Engineer·Technical Phone Screen

May 2026
Short coding interview at Valon for a software engineer role, second part of what sounds like a multi-part SQL parsing exercise.
  • Extend your SQL parser to support IN clauses, for example: SELECT name IN some_table.

“This was a follow-up to an earlier part so I was already mid-flow, which helped.”

View Post

Valon·Software Engineer·Technical Phone Screen

Apr 2026
Valon SWE interview focused on object-oriented design, specifically building a company employee management system. Pretty standard OOP/data structure territory but the follow-up questions on secondary indexes caught me a bit off guard.
  • Design a Company class that manages a collection of Employee objects. Employees have an id, name, and email, where id is the unique immutable key. Implement get by id, update email, and delete. How do you handle lookups by name or email, and what happens when an id doesn't exist or an email is already taken?

“Started with a hash map keyed by id, which felt obvious, and they nodded along.”

View Post

Valon·Software Engineer·Technical Phone Screen

Apr 2026
Valon SWE interview had me building a mini in-memory database from scratch, which I wasn't expecting to be as tricky as it turned out. The dynamic schema part especially caught me thinking harder than I'd like to admit.
  • Design and implement an in-memory SQL-like database that supports INSERT and SELECT operations, where each table's schema grows dynamically based on what columns have been inserted, and missing columns are treated as NULL.

“The core structure wasn't too bad once I landed on a map from table name to a list of row maps.”

View Post

Valon·Software Engineer·Technical Phone Screen

Apr 2026
Valon software engineer interview, part three of what sounds like a multi-stage coding session. The task was to add filter-by functionality to an existing problem. No AI tools allowed, screen sharing required, Google only. Candidate didn't pass.
  • Extend an existing solution to support filter-by functionality.

“This was part three of a longer coding problem, so by the time we got here I was already a bit fried.”

View Post

Valon·Software Engineer·Technical Phone Screen

Apr 2026
Valon SWE interview had me building an in-memory database from scratch, DynamoDB-style schema and all. No LeetCode judge, you write your own tests, which sounds freeing until you realize you have no safety net.
  • Design and implement an in-memory database with a flexible schema, where each row is a set of key-value pairs and different rows can have different columns. Implement insert, find_by_column, and find_by_column_value operations.
  • Extend the query API to support filtering by multiple column predicates simultaneously, like filter({col1: v1, col2: v2}) returning rows that match all conditions. Discuss the data structures, index design, tradeoffs between insert cost and query cost, and how you'd handle range queries or missing columns.

“The flexible schema part tripped me up more than the code itself.”

View Post

Valon·Software Engineer·Technical Phone Screen

Apr 2026
Valon SWE interview had me building an in-memory file system from scratch. Pretty much a database design problem dressed up as a file system. They pushed Python over Java, which I appreciated.
  • Design an in-memory file system, starting with implementing a basic SELECT operation.

“The file system framing threw me at first but it's really just a mini database.”

View Post

Valon·Software Engineer·Technical Phone Screen

Mar 2026
Interviewed for a software engineer role at Valon and got a coding round that asked me to implement a file system from scratch, full test cases included. I'd been leaning on AI tools too much at work and it showed.
  • Implement a file system. Your code must run correctly and be accompanied by comprehensive test cases.

“This wasn't a 'talk me through the design' question.”

View Post