Sigma Computing Software Engineer interview questions

5 Software Engineers have shared notes from their Sigma Computing interviews, with the questions they were asked in each round. That is 71% of the 7 Sigma Computing interview notes on Screna AI.

5 Software Engineer interview notes

Sigma Computing·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a software engineering role at Sigmacomputing and got a pretty involved coding problem around implementing a pivot table from scratch. Three parts, each building on the last, and I was not fully prepared for how deep it went.
  • Implement a basic 2D pivot table in memory: given a list of row maps with categorical and numeric columns, group by two categorical columns and sum the numeric column, then print the result as a text table.
  • Extend the pivot table to include row totals, column totals, and a grand total in the printed output.
  • Generalize the pivot table so that each axis can be defined by a list of column names rather than a single column, forming composite tuple keys for rows and columns.

“Started okay with a nested map approach, row key to col key to running sum.”

View Post

Sigma Computing·Software Engineer·Onsite - System Design / Architecture

Jun 2026
Interviewed for a software engineering role at Sigmacomputing and got a meaty spreadsheet design problem that went deeper than I expected. The cycle detection piece especially caught me off-guard because I hadn't thought carefully about eager vs lazy evaluation trade-offs in a while.
  • Design a spreadsheet that supports formula cells with dependency tracking. How would you extend a basic get/set cell interface to handle formulas like ADD(cell_a, cell_b), and how do you detect cycles in the dependency graph before accepting a write?
  • Walk through the trade-offs between eager evaluation (recompute formula values whenever a dependency changes) and lazy evaluation (compute only when the cell is read). When would you choose one over the other?
  • How would you propagate or invalidate cached values when an upstream cell in the dependency graph is updated?

“This was the core question and it took a while to even scope properly.”

View Post

Sigma Computing·Software Engineer·Technical Phone Screen

Jun 2026
Interviewed for a software engineer role at Sigmacomputing and got a data aggregation problem that seemed straightforward but had a decent follow-up layer to it. The pivot table framing was a bit unusual compared to typical coding rounds.
  • Implement a function that builds a pivot table from a list of records, where each record has a row key, a column key, and a numeric value. Aggregate by the row/column pair and return a structure that supports efficient lookup. Then explain how you'd extend it to support average and minimum in addition to sum.

“Started with a nested dict keyed by row then column, which felt right.”

View Post

Sigma Computing·Software Engineer·Technical Phone Screen

May 2026
Sigma Computing interview for a software engineer role, one technical round focused on designing a spreadsheet data structure from scratch. The problem was more open-ended than I expected and the discussion about storage trade-offs ended up taking longer than the actual coding.
  • Implement a basic spreadsheet class with a fixed number of columns and dynamic rows. Include methods to get a cell value, set a cell value, and pretty-print the first N rows including empty cells.
  • Walk through the trade-offs between using a list of lists versus a sparse dictionary for the underlying cell storage. Consider memory usage, access time, and how each handles mostly-empty spreadsheets.
  • How would you extend this spreadsheet API to support formula cells, where a cell's value is computed from other cells?

“I started with a list of lists because it felt natural, then the interviewer pushed on what happens when most cells are empty and I had to walk back and pitch a dict keyed on (row, col) tuples instead.”

View Post

Sigma Computing·Software Engineer·Onsite - Coding / Algorithms

May 2026
Coding round at Sigmacomputing for a software engineer role. The main problem was building a pivot table from scratch, which sounds straightforward but has a lot of moving parts once they start asking follow-ups about aggregation, missing cells, and complexity.
  • Implement a basic pivot table: given a list of records with multiple fields, and a pivot specification defining row fields, column fields, and value fields with aggregation functions (sum, count, average, min, max), produce a 2D pivot table with aggregated values per (row-key, column-key) cell. Discuss data structures, missing cell handling, header sorting, multiple aggregations, grand totals, and time/space complexity.

“This is the kind of problem that feels manageable until you start coding and realize how many edge cases you glossed over.”

View Post