Protium Software Engineer Interview Guide

The 60-second brief

As a Software Engineer at Protium, you are at the core of a high-growth fintech ecosystem. You will be responsible for building, scaling, and maintaining the robust digital infrastructure that facilitates credit and financial solutions. Your work directly impacts the efficiency of our lending platforms and the experience of our end-users, requiring a blend of technical precision and product-oriented thinking. The role is both challenging and rewarding, as you will contribute to systems that demand high availability and reliability. You will work alongside a team of engineers who prioritize clean code, scalable architecture, and iterative development. Whether you are optimizing database queries or designing new features, your contributions will be fundamental to the company's growth and technical excellence.

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

Focus areas

• Data Structures & Algorithms (DSA)
• Problem Solving
• Coding Interview Preparation

The Protium interview process

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

Online Assessment

Candidates complete an online assessment to evaluate their technical skills.

What to demonstrate

• Candidates complete an online assessment to evaluate their technical skills
• Depth in Data Structures & Algorithms (DSA)

How to prepare

• Answer aloud and timed: Solve a medium-difficulty array manipulation problem.
• Answer aloud and timed: How would you optimize a search algorithm for a large dataset?

Technical Screenings

Candidates participate in technical screenings to further assess their coding abilities.

What to demonstrate

• Candidates participate in technical screenings to further assess their coding abilities
• Depth in Data Structures & Algorithms (DSA)

How to prepare

• Answer aloud and timed: Implement a linked list or tree-based data structure from scratch.
• Answer aloud and timed: Explain the time and space complexity of your solution.

Managerial Round

Final discussions with managerial staff to evaluate cultural fit and overall alignment.

What to demonstrate

• Final discussions with managerial staff to evaluate cultural fit and overall alignment
• Depth in Data Structures & Algorithms (DSA)

How to prepare

• Answer aloud and timed: Given a string, find the longest substring without repeating characters.
• Answer aloud and timed: Explain the difference between ACID properties and BASE.

Where candidates lose points

Structure your thoughts

Before writing code, explain your approach. This demonstrates your ability to think before you act.

Think about real-world constraints

When designing systems, mention scalability, security, and error handling.

Be honest about your knowledge

If you don't know an answer, explain how you would go about finding it rather than guessing.

Research the company

Understand our position in the fintech market; it shows genuine interest in our mission.

Questions & practice

Solve a medium-difficulty array manipulation problem.

Medium · Data Structures 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 a search algorithm for a large dataset?

Medium · Data Structures 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?

Implement a linked list or tree-based data structure from scratch.

Medium · Data Structures 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 solution.

Medium · Data Structures 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?

Given a string, find the longest substring without repeating characters.

Medium · Data Structures 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 the impact of normalization on database performance.

Medium · Database Management Systems (DBMS)

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?

Why do you want to join a fast-paced fintech environment like Protium?

Medium · Behavioral and Leadership

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?

Explain the difference between ACID properties and BASE.

Medium · Database Management Systems (DBMS)

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?

What are the common types of joins, and when should you use each?

Medium · Database Management Systems (DBMS)

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?

Describe your process for building a RESTful API.

Medium · Development and System Design

Approach

1. Say who the caller is and what they do when the call fails halfway.
2. Define the identity of a request so a retry cannot double-apply it.
3. Separate accepted, pending, failed and confirmed; they are different facts.
4. Design the error taxonomy before the success shape; callers branch on it.

Follow-up

• What happens if the caller retries after a timeout?
• How does a client discover it is on an old version of this contract?

Explain the request-response lifecycle in a web browser.

Medium · Development and System Design

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?

How would you design a URL shortening service?

Medium · Development and System Design

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 key differences between monolithic and microservices architectures?

Medium · Development and System Design

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?

How would you handle a deadlock in a transaction-heavy system?

Medium · Database Management Systems (DBMS)

Approach

1. Establish what changed and when, before forming any theory.
2. Pick a bisection that eliminates candidates whichever way it turns out.
3. Check the instrumentation before believing the symptom.
4. Separate the trigger from the cause; the deploy is rarely the bug.

Follow-up

• What would you look at first, and what would it rule out?
• How would you tell a cause from a coincidence here?

Suggested practice checklist

Built from the rounds and topics Protium candidates report.

Day 1 — Map the Protium loop

• Write out the reported sequence: Online Assessment, Technical Screenings, Managerial Round.
• 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 3 reported rounds, with the weakest marked.

Day 2 — Work Data Structures & Algorithms (DSA)

• Spend the session on Data Structures & Algorithms (DSA), which Protium candidates report being tested on.
• Write one worked example in Data Structures & Algorithms (DSA) and time yourself on it.

Deliverable: One timed worked example in Data Structures & Algorithms (DSA).

Day 3 — Work Problem Solving

• Spend the session on Problem Solving, which Protium candidates report being tested on.
• Write one worked example in Problem Solving and time yourself on it.

Deliverable: One timed worked example in Problem Solving.

Day 4 — Work Coding Interview Preparation

• Spend the session on Coding Interview Preparation, which Protium candidates report being tested on.
• Write one worked example in Coding Interview Preparation and time yourself on it.

Deliverable: One timed worked example in Coding Interview Preparation.

Day 5 — Answer out loud: Data Structures and Algorithms

• Answer aloud, timed: Solve a medium-difficulty array manipulation problem.
• Answer aloud, timed: How would you optimize a search algorithm for a large dataset?

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

Day 6 — Answer out loud: Database Management Systems (DBMS)

• Answer aloud, timed: Explain the difference between ACID properties and BASE.
• Answer aloud, timed: How do you handle database indexing to improve performance?

Deliverable: Spoken answers to 2 reported Database Management Systems (DBMS) question(s), under time.

Day 7 — Answer out loud: Development and System Design

• Answer aloud, timed: Describe your process for building a RESTful API.
• Answer aloud, timed: How do you handle authentication and authorization in a web application?

Deliverable: Spoken answers to 2 reported Development and System Design question(s), under time.

Behavioural preparation

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

How do you handle database indexing to improve performance?

Medium · Database Management Systems (DBMS)

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 authentication and authorization in a web application?

Medium · Development and System Design

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 faced a significant technical challenge.

Medium · Behavioral and Leadership

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 disagreements with team members regarding technical choices?

Medium · Behavioral and Leadership

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 situation where you had to learn a new technology quickly.

Medium · Behavioral and Leadership

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?

Give an example of how you contributed to a team's success.

Medium · Behavioral and Leadership

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?