cswork / libraryOpen practice workspace

Interview guides · CSC

CSC Software Engineer Interview Guide

CSC Software Engineer interview guide: reported rounds, questions and how candidates describe the process.

The 60-second brief

As a Software Engineer at CSC, you are at the heart of the organization’s ability to deliver mission-critical technology solutions. This role is not merely about writing code; it is about architecting scalable systems, navigating complex enterprise environments, and solving real-world challenges for high-stakes clients. You will contribute to projects that require a deep understanding of infrastructure, business logic, and the ability to bridge the gap between technical requirements and client needs. The impact of this position is significant. You will be responsible for building and maintaining the software that powers core business processes, often working within large-scale, distributed environments.

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

Focus areas

  • SAGA Pattern
  • Java Spring Microservices
  • Choreography vs Orchestration

The CSC interview process

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

Application Review

Initial review of candidate applications to assess qualifications and fit.

What to demonstrate

  • Initial review of candidate applications to assess qualifications and fit
  • Depth in SAGA Pattern

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.

Written Assessments

Candidates may complete written assessments to evaluate foundational skills.

What to demonstrate

  • Candidates may complete written assessments to evaluate foundational skills
  • Depth in SAGA Pattern

How to prepare

  • Answer aloud and timed: What are the best practices for implementing SQL joins and stored procedures?
  • Answer aloud and timed: Explain the principles of OOPs and how you apply them to handle specific system scenarios.

Technical Interviews

In-depth technical interviews focusing on competency and past project successes.

What to demonstrate

  • In-depth technical interviews focusing on competency and past project successes
  • Depth in SAGA Pattern

How to prepare

  • Answer aloud and timed: How do you optimize a database query that is performing poorly?
  • Answer aloud and timed: Describe a challenging project you worked on; what was your role and how did you resolve the technical hurdles?

Discussions with Management

Candidates engage in discussions with senior management or project leads.

What to demonstrate

  • Candidates engage in discussions with senior management or project leads
  • Depth in SAGA Pattern

How to prepare

  • Answer aloud and timed: How do you design a system to handle a scenario where one transaction in a series fails?
  • Answer aloud and timed: Can you walk us through the architecture of your most recent application?

Final Decision-Making

Final evaluations and decision-making regarding candidate suitability.

What to demonstrate

  • Final evaluations and decision-making regarding candidate suitability
  • Depth in SAGA Pattern

How to prepare

  • Answer aloud and timed: How do you ensure code quality and maintainability in a large-scale project?
  • Answer aloud and timed: How would you find a missing number in an array of 1 to 100?

Where candidates lose points

Structure your answers

Use the STAR method (Situation, Task, Action, Result) when answering behavioral questions to keep your responses focused and impactful.

Know your resume

Be prepared to answer questions about every bullet point on your resume; interviewers will use it as a roadmap for the conversation.

Ask thoughtful questions

At the end of your interview, ask about the team’s current technical challenges or how the company supports professional development.

Be honest about your limits

If you encounter a technical question you don't know, it is better to explain how you would find the answer rather than guessing.

Questions & practice

How do you manage multithreading and the Collections framework in Java?

Medium · Technical Proficiency and Domain Knowled

Approach

  1. Say what the runtime actually does before reasoning about the code.
  2. Name what is shared across threads and what owns each piece of state.
  3. Identify the window where an invariant is briefly untrue.
  4. 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?

How would you find a missing number in an array of 1 to 100?

Medium · Problem-Solving and Logic

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 reverse a linked list recursively?

Medium · Problem-Solving and Logic

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?

What are the best practices for implementing SQL joins and stored procedures?

Medium · Technical Proficiency and Domain Knowled

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?

How do you optimize a database query that is performing poorly?

Medium · Technical Proficiency and Domain Knowled

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?

Can you explain the SAGA pattern in microservices and the difference between choreography vs. orchestration?

Medium · Technical Proficiency and Domain Knowled

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?

Explain the principles of OOPs and how you apply them to handle specific system scenarios.

Medium · Technical Proficiency and Domain Knowled

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 a challenging project you worked on; what was your role and how did you resolve the technical hurdles

Medium · Project Experience and Practical Applica

Describe a challenging project you worked on; what was your role and how did you resolve the technical hurdles?

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 design a system to handle a scenario where one transaction in a series fails?

Medium · Project Experience and Practical Applica

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?

Can you walk us through the architecture of your most recent application?

Medium · Project Experience and Practical Applica

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 do you ensure code quality and maintainability in a large-scale project?

Medium · Project Experience and Practical Applica

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 designing a solution when requirements are initially vague.

Medium · Problem-Solving and Logic

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 would you approach debugging a complex, intermittent production issue?

Medium · Problem-Solving and Logic

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 CSC candidates report.

Day 1 — Map the CSC loop

  • Write out the reported sequence: Application Review, Written Assessments, Technical Interviews, Discussions with Management, Final Decision-Making.
  • 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 5 reported rounds, with the weakest marked.

Day 2 — Work SAGA Pattern

  • Spend the session on SAGA Pattern, which CSC candidates report being tested on.
  • Write one worked example in SAGA Pattern and time yourself on it.

Deliverable: One timed worked example in SAGA Pattern.

Day 3 — Work Java Spring Microservices

  • Spend the session on Java Spring Microservices, which CSC candidates report being tested on.
  • Write one worked example in Java Spring Microservices and time yourself on it.

Deliverable: One timed worked example in Java Spring Microservices.

Day 4 — Work Choreography vs Orchestration

  • Spend the session on Choreography vs Orchestration, which CSC candidates report being tested on.
  • Write one worked example in Choreography vs Orchestration and time yourself on it.

Deliverable: One timed worked example in Choreography vs Orchestration.

Day 5 — Answer out loud: Technical Proficiency and Domain Knowledge

  • Answer aloud, timed: Can you explain the SAGA pattern in microservices and the difference between choreography vs. orchestration?
  • Answer aloud, timed: How do you manage multithreading and the Collections framework in Java?

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

Day 6 — Answer out loud: Project Experience and Practical Application

  • Answer aloud, timed: Describe a challenging project you worked on; what was your role and how did you resolve the technical hurdles?
  • Answer aloud, timed: How do you design a system to handle a scenario where one transaction in a series fails?

Deliverable: Spoken answers to 2 reported Project Experience and Practical Application question(s), under time.

Day 7 — Answer out loud: Problem-Solving and Logic

  • Answer aloud, timed: How would you find a missing number in an array of 1 to 100?
  • Answer aloud, timed: How do you reverse a linked list recursively?

Deliverable: Spoken answers to 2 reported Problem-Solving and Logic question(s), under time.

Behavioural preparation

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

Tell us about a time you had to explain a technical concept to a non-technical stakeholder.

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 or project managers?

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?

Why are you interested in joining CSC and what are your career goals for the next few years?

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 work under significant pressure or a tight deadline.

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?