Siepe Software Engineer Interview Guide

The 60-second brief

A Software Engineer at Siepe serves as a cornerstone of the firm’s mission to provide cutting-edge technology solutions for the private credit and syndicated loan markets. You will be responsible for building, maintaining, and scaling the infrastructure that powers complex financial workflows, including CLO (Collateralized Loan Obligation) compliance and cloud infrastructure. Your work directly impacts how financial institutions manage risk, interpret data, and streamline operations in a high-stakes environment. This role requires a unique blend of technical precision and domain curiosity. You aren't just writing code; you are solving structural problems within the financial technology ecosystem.

This guide is scoped to a Software Engineer candidate at Siepe.

Focus areas

• SQL Development
• Cloud Infrastructure Support
• Technical Coding Assessments

The Siepe interview process

Siepe candidates report 4 rounds over 3-5 weeks. The stages below are what candidates describe, not a published process.

Recruiter Screen

Initial screening conducted by a recruiter to assess candidate fit for the role.

What to demonstrate

• Initial screening conducted by a recruiter to assess candidate fit for the role
• Depth in SQL Development

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 Assessment

A coding assessment lasting between 1.5 to 3.5 hours, focusing on problem-solving and coding skills.

What to demonstrate

• A coding assessment lasting between 1.5 to 3.5 hours
• Focusing on problem-solving and coding skills

How to prepare

• Answer aloud and timed: Explain the time and space complexity of your chosen approach.
• Answer aloud and timed: Describe how you handle edge cases in your code.

Team Interview

In-depth discussions with team members about professional experience and methodologies.

What to demonstrate

• In-depth discussions with team members about professional experience and methodologies
• Depth in SQL Development

How to prepare

• Answer aloud and timed: Write a function to parse or transform [specific data structure].
• Answer aloud and timed: Explain the architecture of your most recent project.

Leadership Interview

Final conversational round with senior leadership, including the CEO and CTO.

What to demonstrate

• Final conversational round with senior leadership
• Including the CEO and CTO

How to prepare

• Answer aloud and timed: How do you approach complex SQL queries or database optimization?
• Answer aloud and timed: Describe your experience with cloud infrastructure and deployment pipelines.

Where candidates lose points

Own your answers

When explaining your past projects, be prepared to discuss the "why" behind your technical choices, not just the "how."

Clarify expectations

Given the feedback on communication, treat the interview as a two-way street—ask specific questions about the team's culture and work-life balance.

Prepare for the leadership round

If you make it to the final interview with the CEO and CTO, focus on your ability to contribute to the company's long-term vision.

Practice standard coding

Keep your skills sharp with common algorithmic patterns, as these are a recurring theme in the technical assessments.

Questions & practice

Implement a solution for [LeetCode-style algorithmic challenge].

Medium · Coding and Algorithms

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. 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?

How would you optimize this specific data processing function for performance?

Medium · Coding and Algorithms

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. 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?

Explain the time and space complexity of your chosen approach.

Medium · Coding and Algorithms

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. 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?

Describe how you handle edge cases in your code.

Medium · Coding and Algorithms

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. 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?

Write a function to parse or transform [specific data structure].

Medium · Coding and Algorithms

Approach

1. Restate the input: its shape, its size, and what is guaranteed about it.
2. Name the brute-force solution and its complexity before improving on it.
3. Choose the data structure from the access pattern, not from familiarity.
4. 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?

How do you approach complex SQL queries or database optimization?

Medium · Technical and Domain Knowledge

Approach

1. Name the grain you start from and join outward from it.
2. Check whether any join is one-to-many before aggregating, or the sums inflate.
3. Say which index the query would use, and what makes it unusable.
4. Handle the rows that do not match: that is usually the actual question.

Follow-up

• How does the query change if that join becomes one-to-many?
• What happens to this when the table is ten times larger?

Stop tag and share joins from fanning out a page

Medium · join fan-out · semi-joins · many-to-many

resource_tag is (resource_id, tag_id) with PK (resource_id, tag_id); resource_share is (resource_id, shared_with_user_id, permission). The tagged-and-shared listing inner-joins resource to both, filters tenant_id, tag_id = ANY($2) and shared_with_user_id = $3, orders by updated_at DESC and takes 50. Pages come back with fewer than 50 distinct resources and the total in the header is far too high. Explain the row multiplication, rewrite both the page query and the count query so each is correct, and name the index each one needs. PostgreSQL 16.

Approach

1. Do the arithmetic against the predicates that are actually there. An inner join emits one row per matching child row, and both joins are filtered: tag_id = ANY($2) admits only the requested tags, shared_with_user_id = $3 admits one user's share rows. So a resource holding three of the requested tags and shared with $3 once yields three rows, not one — the multiplier is its count of matching tags times its share rows for that single user, and that second factor is 1 unless the table admits duplicate (resource_id, shared_with_user_id) pairs. LIMIT 50 then limits rows rather than resources, and COUNT(*) counts pairs — the header is the product, not the population.
2. Reject DISTINCT as the fix. It deduplicates after the product has been built, so the planner must materialise and sort the fanned-out set before the LIMIT can apply, and it leaves any SUM or AVG in the same select list wrong.
3. Rewrite both filters as semi-joins, keeping resource as the only row source: AND EXISTS (SELECT 1 FROM resource_tag rt WHERE rt.resource_id = r.resource_id AND rt.tag_id = ANY($2)) and the same shape against resource_share. A semi-join stops at the first match per resource and preserves the driving index order, so ORDER BY updated_at DESC, resource_id DESC LIMIT 50 still stops after 50 rows.
4. Count with the same predicates and no join at all: SELECT count(*) FROM resource r WHERE r.tenant_id = $1 AND r.status = 'active' AND EXISTS (...) AND EXISTS (...). Nothing multiplies a resource, so the number is the population.

Follow-up

• The filter changes from 'any of these tags' to 'all of these tags'. Rewrite it and state what it costs relative to the ANY form.
• A resource can be shared with the same user twice under different permissions. Does your count change, and should it?

Explain the architecture of your most recent project.

Medium · Technical and Domain Knowledge

Approach

1. Fix the scope first: who calls this, how often, and what they do when it fails.
2. Name the read and write paths separately; they rarely have the same bottleneck.
3. Choose a partition key and say what query it makes expensive.
4. 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?

What are the trade-offs between different UI frameworks for data-heavy applications?

Medium · Technical and Domain Knowledge

Approach

1. Clarify what is being asked and what a complete answer contains.
2. State your assumptions explicitly before working the problem.
3. Say what you would check first and why it is the highest-information step.
4. Work from the requirement backwards to the design.

Follow-up

• What assumption would you test first?
• How would you know your answer was wrong?

How do you ensure data integrity in a distributed system?

Medium · Technical and Domain Knowledge

Approach

1. Fix the scope first: who calls this, how often, and what they do when it fails.
2. Name the read and write paths separately; they rarely have the same bottleneck.
3. Choose a partition key and say what query it makes expensive.
4. 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?

Edge instances grow 400 MB per hour until the nightly restart

Hard · memory leak · heap analysis · metric cardinality

Edge API instances start at 700 MB resident and grow about 400 MB/hour; a nightly rolling restart has hidden it for weeks. Growth continues unchanged when request rate halves overnight, p99 degrades in the last hours before an instance is recycled, and heap used immediately after a forced full GC rises monotonically. The service holds no product state. Name the discriminating measurement that separates the plausible causes, give the most likely cause, and give the fix and how you would verify it.

Approach

1. Separate resident memory from live heap first, because they fail differently. Resident size can grow from fragmentation, native buffers or thread stacks while the heap is flat; heap used after a full GC rising monotonically is the measurement that says objects are reachable and not being released. You already have it, so this is retention, not fragmentation, and that closes off half the candidate list.
2. Use the rate's independence from traffic as the discriminator. Growth that continues at half the request rate rules out per-request objects that are merely slow to collect and points at a structure that grows with distinct values observed rather than with call volume. Write the candidates that have that property: a metrics registry keyed on a high-cardinality label, an unevicted cache, an interner, a per-key lock map.
3. Take two heap snapshots an hour apart and diff by retained size, reading the dominator tree, not by allocation count or instance count. Expect one root holding a map with millions of entries, then follow the reference chain to the code that inserts and never removes. Allocation profilers point at churn, which is the wrong signal here.
4. The candidate that fits this service is an observability label carrying an identifier, such as a request path recorded before templating so that /v1/resources/48213 becomes its own metric series. That grows with distinct ids seen, is independent of rate, and explains the late p99 degradation, since GC cost rises with the size of the live set.

Follow-up

• Post-GC heap is now flat but resident size still creeps. What are you looking at, and does it matter?
• How would you have detected this before an OOM, given the nightly restart masked the trend?

Suggested practice checklist

Built from the rounds and topics Siepe candidates report.

Day 1 — Map the Siepe loop

• Write out the reported sequence: Recruiter Screen, Technical Assessment, Team Interview, Leadership Interview.
• 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.

Day 2 — Work SQL Development

• Spend the session on SQL Development, which Siepe candidates report being tested on.
• Write one worked example in SQL Development and time yourself on it.

Deliverable: One timed worked example in SQL Development.

Day 3 — Work Cloud Infrastructure Support

• Spend the session on Cloud Infrastructure Support, which Siepe candidates report being tested on.
• Write one worked example in Cloud Infrastructure Support and time yourself on it.

Deliverable: One timed worked example in Cloud Infrastructure Support.

Day 4 — Work Technical Coding Assessments

• Spend the session on Technical Coding Assessments, which Siepe candidates report being tested on.
• Write one worked example in Technical Coding Assessments and time yourself on it.

Deliverable: One timed worked example in Technical Coding Assessments.

Day 5 — Answer out loud: Coding and Algorithms

• Answer aloud, timed: Implement a solution for [LeetCode-style algorithmic challenge].
• Answer aloud, timed: How would you optimize this specific data processing function for performance?

Deliverable: Spoken answers to 2 reported Coding and Algorithms question(s), under time.

Day 6 — Answer out loud: Technical and Domain Knowledge

• Answer aloud, timed: Explain the architecture of your most recent project.
• Answer aloud, timed: How do you approach complex SQL queries or database optimization?

Deliverable: Spoken answers to 2 reported Technical and Domain Knowledge question(s), under time.

Day 7 — Answer out loud: Behavioral and Professionalism

• Answer aloud, timed: Describe a time you had to resolve a conflict within a technical team.
• Answer aloud, timed: How do you handle changing requirements or shifting project priorities?

Deliverable: Spoken answers to 2 reported Behavioral and Professionalism question(s), under time.

Behavioural preparation

Behavioural rounds judge the decision you made and what it cost.

Describe your experience with cloud infrastructure and deployment pipelines.

Medium · Technical and Domain Knowledge

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. 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?

Describe a time you had to resolve a conflict within a technical team.

Medium · Behavioral and Professionalism

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. 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?

How do you handle changing requirements or shifting project priorities?

Medium · Behavioral and Professionalism

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. 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?

Tell me about a time you received constructive feedback and how you acted on it.

Medium · Behavioral and Professionalism

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. 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?

How do you prioritize tasks when working under tight deadlines?

Medium · Behavioral and Professionalism

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. 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?

Why are you interested in the intersection of finance and software engineering?

Medium · Behavioral and Professionalism

Approach

1. Pick a story where you made the decision, not one where you watched it.
2. State the situation in two sentences and spend the rest on the reasoning.
3. Give the blast radius: what could have broken, and what you measured.
4. 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?