← Chicago Trading Company Interview Insights

Chicago Trading Company·Software Engineer·Technical Phone Screen·Intermediate

IntermediatePrefer not to say
Apr 2026

Summary

C++ debugging round for a software engineer role at Chicago Trading. One question, ten test cases, two bugs to find. Less about writing code and more about reading it carefully.

Questions Asked (1)

Q1

You're given a C++ order book implementation with 10 test cases. Find and fix 2 bugs so all tests pass.

Root Cause AnalysisTechnical Trade-offs
Author's notes

Spent the first few minutes expecting some gnarly algorithmic trap and then realized the bugs were just small stuff, a typo here, a logic condition flipped there.

Create a free account to read the full note

AI HintsAI Generated

Suggested Approach

Start by running the test suite to see which tests fail and how. Then systematically debug each failure by tracing the code, forming hypotheses, and using tools like debuggers or print statements to isolate the root cause. Fix bugs one at a time, re-running tests after each fix to ensure no regressions.

Pro tip: Demonstrate a methodical approach: before fixing, explain your hypothesis and how you'll verify it. This shows you're not just guessing but applying root cause analysis, which is crucial in trading systems where bugs can be costly.

1. Run Tests and Observe Failures

Execute the test suite to identify which tests fail and capture error messages or incorrect outputs. This gives you a starting point and narrows down the problematic areas.

2. Analyze Failing Tests and Code

Examine the failing test cases and the corresponding code paths. Understand the expected behavior versus actual behavior, and identify potential logic errors or edge cases.

3. Form Hypotheses and Debug

Based on your analysis, form hypotheses about the root causes. Use debugging tools (e.g., gdb, print statements) to trace execution and confirm or refute your hypotheses.

4. Fix Bugs and Verify

Implement fixes for the identified bugs, ensuring minimal changes that address the root cause. Re-run the tests to verify the fixes and check for regressions.

5. Reflect and Communicate

Summarize the bugs found, the fixes applied, and any trade-offs considered. Explain how you ensured the solution is robust and efficient.

Key Points to Mention

  • Systematic debugging approach: reproduce, isolate, hypothesize, verify, fix.
  • Use of debugging tools (gdb, valgrind, sanitizers) and logging.
  • Understanding of order book mechanics and common pitfalls (e.g., price-time priority, order matching).
  • Root cause analysis: distinguishing between symptoms and underlying causes.
  • Trade-offs in fixes: performance vs. correctness, simplicity vs. robustness.
  • Testing strategy: unit tests, edge cases, and regression testing.

AI-generated suggestions, not part of the candidate's original notes. May be inaccurate — verify before relying on them.