At Susquehanna International Group (SIG), a Software Engineer occupies a central role in driving high-frequency quantitative trading, portfolio management, risk analytics, and post-trade execution systems. Engineering at SIG is not an isolated back-office function; software engineers build the very infrastructure, platforms, and proprietary tools that power real-time trading operations worldwide. Whether developing ultra-low latency trading systems in C++, building resilient post-trade and risk platforms using C#/.NET, or writing high-throughput data pipelines in Python, engineers at SIG directly impact the firm's profitability and market efficiency. The technical environment at SIG is defined by extreme scale, high concurrency, and real-time execution constraints. Software engineers tackle domain challenges such as indexing high-velocity market data streams, building in-memory book-matching algorithms, implementing complex financial data structures like dynamic order books, and managing dynamic caching mechanisms. Systems must operate with predictable, sub-millisecond latencies while maintaining strict execution safety and data integrity under high market volatility. Candidates entering the Software Engineer candidate pipeline will find an environment that rewards lower-level computational understanding, data structure mastery, pragmatic object-oriented design, and real-time code optimization.
Online Assessment
reported70-to-90-minute assessment via CodeSignal with 3–4 questions on data structures and algorithms.
What to demonstrate
- 70-to-90-minute assessment via CodeSignal with 3–4 questions on data structures and algorithms
- Depth in Data Structures
How to prepare
- Answer aloud and timed: Movie Catalog Search & Indexing: Given a list of movies with attributes (title, release year, category), implement a catalog and optimize search queries so elements within a specific range can be returned in $O(\log N)$ or $O(1)$ time using appropriate indexing and dynamic maps.
- Answer aloud and timed: News Headline Ticker Search: Given a mapping of company names to stock tickers (e.g., "The Big Company" $\rightarrow$
TBC), write a system to match and return all valid tickers mentioned in a given news headline, correctly handling substring overlap (e.g., matching both "Cool Company" and "My Super Cool Company").
Recruiter Screen
reported30-minute introductory call reviewing resume, background, achievements, and cultural fit.
What to demonstrate
- 30-minute introductory call reviewing resume, background, achievements, and cultural fit
- Depth in Data Structures
How to prepare
- Be able to walk your CV end to end in two minutes, and say why this company specifically.
- Have your salary expectations, notice period and location constraints ready, and ask for the rest of the loop in writing.
Technical Screening
reported60-to-90-minute technical session with software engineers focusing on coding and optimization.
What to demonstrate
- 60-to-90-minute technical session with software engineers focusing on coding and optimization
- Depth in Data Structures
How to prepare
- Answer aloud and timed: Stateful Financial Ledger & Delayed Operations: Implement a bank account simulation class supporting basic
depositandwithdrawoperations, extending it to track and process delayed operations, such as automatically applying a $2%$ cashback credit exactly 24 hours after a withdrawal. - Answer aloud and timed: Grocery Checkout System: Design a Point-of-Sale (POS) and checkout system supporting item inventory, weight/unit pricing, coupon applications, dynamic receipt generation, and extensible membership rewards integration.
Final Round / Superday Onsite
reported2-to-3-hour evaluation including Object-Oriented Design, technical coding, and behavioral interviews.
What to demonstrate
- 2-to-3-hour evaluation including Object-Oriented Design, technical coding, and behavioral interviews
- Depth in Data Structures
How to prepare
- Answer aloud and timed: In-Memory File System: Design an in-memory file system (equivalent to standard memory file management APIs) supporting path creation, directory listing, file reads, and file content appends with clean class abstractions.
- Answer aloud and timed: Order Book & Financial Exchange Simulation: Design an order book data structure handling bid and ask matching, evaluating the performance trade-offs of binary search trees, min/max heaps, vectors, and hash maps for high-speed search and insertion.
2 candidate reports. Individual accounts describe a particular role and hiring cycle.
Susquehanna International Group Software Engineer month-long process
Scheduling was deliberate from the beginning. After recruiter contact, I had a technical screen and then a technical-plus-design round, with recruiter preparation and follow-up calls around the interviews. The in-person stage also included fit and experience conversations, and I appreciated the communication and feedback throughout. The process lasted more than a month, with rounds about one to t…
Read full experienceSusquehanna International Group Software Engineer interview: CodeSignal DSA
The process was compact: a CodeSignal coding assessment, then recruiter and technical interviews. The main technical checkpoint was a DSA-focused CodeSignal set with multiple questions. It felt designed to see how I handled structured algorithm problems within the platform's constraints. After the assessment, I had an HR interview and a technical interview with deeper discussion and coding-style…
Read full experiencePracHub editorial advice for the preparation topics above.
Do not skip complexity analysis during your live coding or code optimization exercises
Interviewers at SIG expect you to articulate the exact time and space complexity (Big-O notation) of your initial code and demonstrate how your optimizations improve performance.
Practice Low-Level OOP Design
Prepare for application-level design challenges (such as grocery store checkouts, file systems, or catalog lookups) rather than high-level distributed systems design (like web crawlers or microservice architectures). Focus on clean interfaces, SOLID design principles, modularity, dynamic updates, and edge case handling.
Master Standard Library Mechanics
Be ready to explain how standard dynamic memory collections, maps, sets, and vectors operate under the hood in your chosen language. Understand memory allocation behavior, growth factors, hashing functions, and iterator mechanics.
Structure Your Communication
During independent 30-minute coding blocks, take 3–5 minutes at the outset to plan your data structures and logic. When the interviewer returns, deliver a clear summary of your solution structure, trade-offs evaluated, and optimizations implemented.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Movie Catalog Search & Indexing: Given a list of movies with attributes (title, release year, category), imple
Movie Catalog Search & Indexing: Given a list of movies with attributes (title, release year, category), implement a catalog and optimize search queries so elements within a specific range can be returned in $O(\log N)$ or $O(1)$ time using appropriate indexing and dynamic maps.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
News Headline Ticker Search: Given a mapping of company names to stock tickers (e.g., "The Big Company" $\righ
News Headline Ticker Search: Given a mapping of company names to stock tickers (e.g., "The Big Company" $\rightarrow$ TBC), write a system to match and return all valid tickers mentioned in a given news headline, correctly handling substring overlap (e.g., matching both "Cool Company" and "My Super Cool Company").
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Trie-Based Prefix Search & String Parsing: Implement an efficient Trie data structure to handle high-speed str
Trie-Based Prefix Search & String Parsing: Implement an efficient Trie data structure to handle high-speed string lookup, prefix matching, and string compression algorithms (e.g., encoding AAABBCC to A3B2C2).
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Matrix and Stack Operations: Solve array and matrix transformation problems, including sliding window algorith
Matrix and Stack Operations: Solve array and matrix transformation problems, including sliding window algorithms over streaming data, min-heap top-$K$ element queries, dynamic programming, and $2\text{D}$ matrix grid manipulation.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Stateful Financial Ledger & Delayed Operations: Implement a bank account simulation class supporting basic `de
Stateful Financial Ledger & Delayed Operations: Implement a bank account simulation class supporting basic deposit and withdraw operations, extending it to track and process delayed operations, such as automatically applying a $2%$ cashback credit exactly 24 hours after a withdrawal.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
In-Memory File System: Design an in-memory file system (equivalent to standard memory file management APIs) su
In-Memory File System: Design an in-memory file system (equivalent to standard memory file management APIs) supporting path creation, directory listing, file reads, and file content appends with clean class abstractions.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Order Book & Financial Exchange Simulation: Design an order book data structure handling bid and ask matching,
Order Book & Financial Exchange Simulation: Design an order book data structure handling bid and ask matching, evaluating the performance trade-offs of binary search trees, min/max heaps, vectors, and hash maps for high-speed search and insertion.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Library & Asset Search System: Model an extensible domain system for cataloging physical or digital assets, en
Library & Asset Search System: Model an extensible domain system for cataloging physical or digital assets, ensuring proper implementation of standard object-oriented design patterns, encapsulation, and interface segregation.
Approach
- Restate the input: its shape, its size, and what is guaranteed about it.
- Name the brute-force solution and its complexity before improving on it.
- Choose the data structure from the access pattern, not from familiarity.
- State the target complexity and say which constraint rules the naive version out.
Follow-up
- How does this change if the input no longer fits in memory?
- What is the worst case, and how likely is it on real data?
Custom Vector Implementation: Re-implement a lightweight version of `std::vector` (or equivalent dynamic array
Custom Vector Implementation: Re-implement a lightweight version of std::vector (or equivalent dynamic array) from scratch. Explain allocation strategy, dynamic resizing logic, dynamic memory allocation costs, and exception guarantees.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Language Trade-Offs (C# vs. Java vs. C++): Compare language runtime execution environments, focusing on Garbag
Language Trade-Offs (C# vs. Java vs. C++): Compare language runtime execution environments, focusing on Garbage Collection (GC) pauses versus manual memory management, Just-In-Time (JIT) compilation, allocation overhead, and execution efficiency in financial trading platforms.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Pointers, References, and Memory Layout: Explain memory alignment, cache line friendliness, cache misses, and
Pointers, References, and Memory Layout: Explain memory alignment, cache line friendliness, cache misses, and pointer-to-hash-map data structures when designing low-latency processing systems.
Approach
- Say what the runtime actually does before reasoning about the code.
- Name what is shared across threads and what owns each piece of state.
- Identify the window where an invariant is briefly untrue.
- Distinguish a value from a reference to it, and say which one you handed out.
Follow-up
- What happens if two callers reach this at the same time?
- Where could this allocate more than you expect?
Hold a per-tenant active cap against concurrent creates
A tenant on the standard plan may hold at most 50 resources with status='active'. The create handler runs SELECT count(*) FROM resource WHERE tenant_id = $1 AND status = 'active', compares to 50, then inserts. Two creates arrive 3 ms apart on different instances and the tenant lands at 51. Name the anomaly, say whether PostgreSQL 16 READ COMMITTED or REPEATABLE READ prevents it and why, then give an implementation that holds the cap at READ COMMITTED with the exact statements. Finally, say what changes when the cap is 'at most one running export per tenant' on job_run.
Approach
- Name it: write skew. The two transactions read an overlapping set and write disjoint rows, so there is no row-level conflict for the engine to detect and each commit is individually legal.
- Rule out the levels precisely. READ COMMITTED takes a fresh snapshot per statement and takes no lock on the counted rows, so both see 49. PostgreSQL's REPEATABLE READ is snapshot isolation: it removes non-repeatable reads and phantoms within the snapshot but still admits write skew, because the anomaly is not a re-read of a changed row, it is a read of a set that a concurrent transaction invalidates. Only SERIALIZABLE closes it, by tracking the read dependency and aborting one transaction with SQLSTATE 40001 — a guarantee that exists only if the application re-runs the whole transaction from the read.
- Convert the set predicate into a single-row conflict: keep tenant.active_resource_count and run UPDATE tenant SET active_resource_count = active_resource_count + 1 WHERE tenant_id = $1 AND active_resource_count < 50 in the same transaction as the INSERT. Zero affected rows is the cap, returned as 409. The row lock serialises the decision at any isolation level, and contention is bounded to one tenant's row — which is also the fair-scheduling unit, unlike a global counter that would convoy every tenant behind one row.
- State the cost you just took on: a counter is a second source of truth that can drift, so every path that changes status must adjust it inside the same transaction, and a periodic reconciliation has to exist, with resource_revision as the authority for what the count should have been.
Follow-up
- A resource moves from archived back to active. Which statements change, and what breaks if the counter update and the status change land in different transactions?
- The cap becomes plan-dependent and a plan can change mid-month. Where does the number 50 live, and who reads it?
Denormalise tenant onto revisions and backfill it live
resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.
Approach
- Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
- Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
- Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
- Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.
Follow-up
- The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
- How do you verify the backfill actually finished, given rows are still being inserted while it runs?
Grocery Checkout System: Design a Point-of-Sale (POS) and checkout system supporting item inventory, weight/un
Grocery Checkout System: Design a Point-of-Sale (POS) and checkout system supporting item inventory, weight/unit pricing, coupon applications, dynamic receipt generation, and extensible membership rewards integration.
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
`std::vector::push_back` and Move Semantics: Walk through the mechanical execution of `std::vector::push_back`
std::vector::push_back and Move Semantics: Walk through the mechanical execution of std::vector::push_back, detailing capacity doubling, amortized $O(1)$ complexity, copy versus move constructors, Rvalue references, and Empty Base Optimization (EBO).
Approach
- Fix the scope first: who calls this, how often, and what they do when it fails.
- Name the read and write paths separately; they rarely have the same bottleneck.
- Choose a partition key and say what query it makes expensive.
- State the consistency you need, and where you are willing to be stale.
Follow-up
- What breaks first when traffic grows ten times?
- How does this behave when that dependency is down for an hour?
Listing latency scales with page size, not with filters
The tenant listing endpoint reads resource filtered by tenant_id and status, ordered by updated_at DESC, and returns each row plus the owner's display name from app_user and the actor of that resource's latest resource_revision. p99 is 55 ms at 10 rows per page and 1.4 s at 200. Database telemetry shows 401 statements per request, each under 1 ms, and nothing in the slow-query log. Diagnose the cause and give the fix, stating the statement count per request and the p99 you expect afterwards.
Approach
- Read the counters before forming a theory. 401 statements for 200 rows is one driver query plus two per row, and sub-millisecond execution with an empty slow-query log rules out a bad plan. The time is round trips, which is why it is invisible in every per-query metric and scales with rows returned rather than with filter selectivity.
- Name the two per-row statements from their normalised text: a single-row app_user lookup by user_id, and a resource_revision lookup by resource_id ordered by version DESC LIMIT 1. Confirm by dropping those two response fields and watching the statement count fall to one. That locates the calls in the serialisation layer, not the repository.
- Check that the arithmetic accounts for the whole gap. Measure one round trip to the replica in isolation; 400 trips at roughly 3 ms of network plus 0.2 ms of execution is about 1.3 s on top of a 55 ms baseline, which matches. If the multiplication had fallen short, the N+1 would only be part of the story and you would keep looking.
- Batch both lookups. Collect owner_user_ids and resource_ids from the driver query, then issue WHERE tenant_id = $1 AND user_id = ANY($2) for the users, and PostgreSQL's SELECT DISTINCT ON (resource_id) ... WHERE resource_id = ANY($2) ORDER BY resource_id, version DESC for the latest revision, which the UNIQUE (resource_id, version) index serves directly. On an engine without DISTINCT ON, use a lateral join or a row_number window. Three statements per request at any page size.
Follow-up
- The page size is capped at 200 today. What breaks first if it is raised to 2,000, and is it still this bug?
- How do you stop the next N+1 from reaching production, given that no individual query is slow and the endpoint's tests pass?
Built from the rounds and topics Susquehanna International Group candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Susquehanna International Group loop
- Write out the reported sequence: Online Assessment, Recruiter Screen, Technical Screening, Final Round / Superday Onsite.
- For each round, write one sentence on what it is judging, from the description above, and mark the one you are least ready for.
Deliverable: A one-page map of the 4 reported rounds, with the weakest marked.
02Work Data Structures
- Spend the session on Data Structures, which Susquehanna International Group candidates report being tested on.
- Write one worked example in Data Structures and time yourself on it.
Deliverable: One timed worked example in Data Structures.
03Work Algorithms
- Spend the session on Algorithms, which Susquehanna International Group candidates report being tested on.
- Write one worked example in Algorithms and time yourself on it.
Deliverable: One timed worked example in Algorithms.
04Work SQL (Coding / Querying)
- Spend the session on SQL (Coding / Querying), which Susquehanna International Group candidates report being tested on.
- Write one worked example in SQL (Coding / Querying) and time yourself on it.
Deliverable: One timed worked example in SQL (Coding / Querying).
05Answer out loud: Data Structures & Algorithmic Optimization
- Answer aloud, timed: Movie Catalog Search & Indexing: Given a list of movies with attributes (title, release year, category), implement a catalog and optimize search queries so elements within a specific range can be returned in $O(\log N)$ or $O(1)$ time using appropriate indexing and dynamic maps.
- Answer aloud, timed: News Headline Ticker Search: Given a mapping of company names to stock tickers (e.g., "The Big Company" $\rightarrow$ `TBC`), write a system to match and return all valid tickers mentioned in a given news headline, correctly handling substring overlap (e.g., matching both "Cool Company" and "My Super Cool Company").
Deliverable: Spoken answers to 2 reported Data Structures & Algorithmic Optimization question(s), under time.
06Answer out loud: Object-Oriented Design & System Architecture
- Answer aloud, timed: Grocery Checkout System: Design a Point-of-Sale (POS) and checkout system supporting item inventory, weight/unit pricing, coupon applications, dynamic receipt generation, and extensible membership rewards integration.
- Answer aloud, timed: In-Memory File System: Design an in-memory file system (equivalent to standard memory file management APIs) supporting path creation, directory listing, file reads, and file content appends with clean class abstractions.
Deliverable: Spoken answers to 2 reported Object-Oriented Design & System Architecture question(s), under time.
07Answer out loud: C++ / Language Internals & Low-Level Mechanics
- Answer aloud, timed: Custom Vector Implementation: Re-implement a lightweight version of `std::vector` (or equivalent dynamic array) from scratch. Explain allocation strategy, dynamic resizing logic, dynamic memory allocation costs, and exception guarantees.
- Answer aloud, timed: `std::vector::push_back` and Move Semantics: Walk through the mechanical execution of `std::vector::push_back`, detailing capacity doubling, amortized $O(1)$ complexity, copy versus move constructors, Rvalue references, and Empty Base Optimization (EBO).
Deliverable: Spoken answers to 2 reported C++ / Language Internals & Low-Level Mechanics question(s), under time.
Expand any day for tasks and deliverables. Your progress is saved on this device.
Behavioural rounds judge the decision you made and what it cost.
Why Susquehanna International Group?: Why are you interested in working at SIG compared to traditional big tec
Why Susquehanna International Group?: Why are you interested in working at SIG compared to traditional big tech software companies or traditional financial institutions?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Navigating Technical & Team Blockers: Describe a situation where a project was delayed or blocked by a co-work
Navigating Technical & Team Blockers: Describe a situation where a project was delayed or blocked by a co-worker or technical impediment. How did you handle the situation and resolve the blocker?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Handling Project Failures & Trade-Offs: Describe the most technically challenging project you led or contribut
Handling Project Failures & Trade-Offs: Describe the most technically challenging project you led or contributed to. What trade-offs did you make, what failed during execution, and what did you learn?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
Maintaining Technical Edge: How do you stay up-to-date with modern engineering tools, low-level language stand
Maintaining Technical Edge: How do you stay up-to-date with modern engineering tools, low-level language standards, and framework improvements?
Approach
- Pick a story where you made the decision, not one where you watched it.
- State the situation in two sentences and spend the rest on the reasoning.
- Give the blast radius: what could have broken, and what you measured.
- Name the disagreement and how you resolved it with evidence.
Follow-up
- What would you do differently if you ran that again?
- How did you know your change caused the improvement?
- 01
Why Susquehanna International Group?: Why are you interested in working at SIG compared to traditional big tech software companies or traditional financial institutions?
- 02
Navigating Technical & Team Blockers: Describe a situation where a project was delayed or blocked by a co-worker or technical impediment. How did you handle the situation and resolve the blocker?
- 03
Handling Project Failures & Trade-Offs: Describe the most technically challenging project you led or contributed to. What trade-offs did you make, what failed during execution, and what did you learn?
- 04
Maintaining Technical Edge: How do you stay up-to-date with modern engineering tools, low-level language standards, and framework improvements?
How difficult is the technical interview process at SIG?
The technical bar is rigorous, focusing heavily on solid computer science fundamentals, code optimization, and clean object-oriented architecture. Rather than relying solely on obscure algorithmic puzzles, SIG emphasizes practical problem solving, code refactoring, complexity analysis, and deep language understanding.
Susquehanna International Group Software Engineer candidate reports ↗Do I need prior experience in finance or quantitative trading to get hired?
No. SIG routinely hires talented software engineers from non-financial backgrounds, including tech firms, gaming companies, and academic environments. Demonstrating raw technical capability, low-level language understanding, dynamic problem solving, and an eagerness to learn financial concepts is what matters most.
Susquehanna International Group Software Engineer candidate reports ↗How does SIG evaluate live coding sessions compared to other tech companies?
A key differentiator is SIG's focus on code optimization. While many tech firms ask candidates to write algorithms from scratch on a blank screen, SIG interviewers often provide existing working code and ask you to analyze performance bottlenecks, refactor data structures, and optimize its runtime while maintaining clean code organization.
Susquehanna International Group Software Engineer candidate reports ↗What is the typical timeframe from initial application to receiving an offer?
The full process typically takes between 3 to 5 weeks. Depending on your location and scheduling preferences, rounds progress steadily through the online assessment, recruiter phone screen, technical evaluation, and superday final interview loop.
Susquehanna International Group Software Engineer candidate reports ↗What topics does Susquehanna International Group test in interviews?
Susquehanna International Group interviews most often cover Python, Combinatorics, Behavioral Interviewing, Probability Theory, and System Design. The exact emphasis depends on the specific role you apply for.
Susquehanna International Group Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
No official company page is cited. Rounds and questions come from candidate reports and PracHub editorial material; each source shows the date it was read.
- 01Susquehanna International Group Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
Candidate reports · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
PracHub page · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
PracHub page · Accessed 2026-09-22