As a Software Engineer at Moody's, you will build and scale the global financial infrastructure that underpins credit ratings, risk analytics, and financial intelligence worldwide. Moody's is actively transforming how global markets evaluate risk by integrating cloud-native architecture, advanced data pipelines, and cutting-edge artificial intelligence into its core product suites. Engineers in this role sit at the intersection of enterprise software engineering and sophisticated financial modeling, building platforms that process massive volumes of market data with absolute precision, security, and low latency. Your work directly impacts global financial institutions, corporations, and government entities that rely on Moody's risk assessments to make high-stakes capital decisions. Whether you join the Corporate Systems group, the Ratings technology team, or specialized enterprise product organizations, you will be responsible for building resilient microservices, designing cloud infrastructure on AWS or Azure, and engineering user-centric web applications. The software you deliver must adhere to strict security, compliance, and performance standards while maintaining high availability across distributed global systems. This position offers a compelling challenge for software engineers who want to solve complex distributed systems problems while developing domain expertise in risk analytics and financial technology.
HR Screening Call
reportedInitial engagement to confirm technical background, role alignment, and salary expectations.
What to demonstrate
- Initial engagement to confirm technical background, role alignment, and salary expectations
- Depth in Data Structures & Algorithms (DSA)
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.
Online Coding Assessment
reportedCandidates complete a coding assessment on HackerRank covering data structures, algorithms, and SQL.
What to demonstrate
- Candidates complete a coding assessment on HackerRank covering data structures, algorithms, and SQL
- Depth in Data Structures & Algorithms (DSA)
How to prepare
- Answer aloud and timed: Perform string manipulation and array filtering tasks with optimal time and space complexity.
- Answer aloud and timed: Implement and traverse binary trees, such as finding the top view or boundary view of a tree.
Interactive Technical Rounds
reportedLive coding sessions, object-oriented design problems, and discussions on cloud infrastructure and system architecture.
What to demonstrate
- Live coding sessions, object-oriented design problems, and discussions on cloud infrastructure and system architecture
- Depth in Data Structures & Algorithms (DSA)
How to prepare
- Answer aloud and timed: Demonstrate bitwise operations and solve algorithmic problems using bit manipulation techniques.
- Answer aloud and timed: How would you design a scalable microservices architecture on AWS using ECS, ECR, Lambda, and Step Functions?
Final Interviews
reportedInterviews with Hiring Manager, Associate Directors, or Vice Presidents to evaluate technical depth and team fit.
What to demonstrate
- Interviews with Hiring Manager, Associate Directors, or Vice Presidents to evaluate technical depth and team fit
- Depth in Data Structures & Algorithms (DSA)
How to prepare
- Answer aloud and timed: Given a data-intensive case study, design a cost-effective cloud architecture diagram and explain your technical tradeoffs.
- Answer aloud and timed: How do you manage service dependencies, API gateway routing, and inter-service communication in a microservices deployment?
4 candidate reports. Individual accounts describe a particular role and hiring cycle.
Moody's Software Engineer interview: interval DSA, AWS, and manager interruptions
My first interview began with a LeetCode-style DSA problem about intervals that felt medium to hard. We also discussed AWS concepts including ECS, ECR, Lambda, and Step Functions, so it was not purely abstract coding. The next stage was with the hiring manager. I expected a normal discussion of my projects, but the manager quickly drove the conversation toward the answers he wanted. He cut me off…
Read full experienceMoody's Software Engineer delayed-feedback interview experience
The interview itself felt productive and well matched to my background. It was scheduled for June 9. Communication afterward fell apart. I had no update for several weeks and tried reaching HR by phone multiple times without a response. After I followed up by text with an HR representative on July 3, I was told that I had not been shortlisted. The result was disappointing, but the lack of timely…
Read full experienceMoody's Software Engineer Interview Experience: unclear AWS-heavy office interview
I was asked to attend an interview at the office, but the questions did not seem relevant to what I understood the role to require. Much of the discussion felt textbook-like, and I could not tell what the interview was actually trying to evaluate. They focused on how AWS works internally and on specific steps, but the phrasing made it hard to connect my answers to the expected skills. I did not g…
Read full experienceMoody's Software Engineer Interview Experience — Onsite System Design for a Product Inventory Service
System Design Design a Product Inventory & Pricing Service for an e-commerce platform Functional requirements: get product details, update product price, update inventory when a user places an order. System requirements: this is a read-heavy system, so we needed to discuss the Consistency vs Availability tradeoff, plus authorization for inventory updates. Technical approach discussion: SQL vs NoS…
Read full experiencePracHub editorial advice for the preparation topics above.
Going into the loop without having done this.
Prepare detailed project narratives: Be prepared to walk through the complete technical stack, data pipeline, and deployment strategy of your past resume projects. Interviewers will dive deep into your direct individual contributions.
Going into the loop without having done this.
Review core computer science definitions: In addition to practical coding, interviewers at Moody's frequently ask conceptual trivia questions regarding OOP principles, Operating System concepts, and database indexing mechanics.
Going into the loop without having done this.
Highlight cloud cost efficiency: When discussing system design or cloud architecture on AWS, explicitly mention cost-effective scaling strategies alongside security and performance.
Going into the loop without having done this.
During live coding and system design rounds, talk through your thought process continuously before writing code or drawing architecture diagrams.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Solve the overlapping intervals problem (e.g., merging or inserting time/data intervals).
Solve the overlapping intervals problem (e.g., merging or inserting time/data intervals).
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?
Search a target element in a 2D sorted matrix using an optimized binary search approach.
Search a target element in a 2D sorted matrix using an optimized binary search approach.
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?
Perform string manipulation and array filtering tasks with optimal time and space complexity.
Perform string manipulation and array filtering tasks with optimal time and space complexity.
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?
Implement and traverse binary trees, such as finding the top view or boundary view of a tree.
Implement and traverse binary trees, such as finding the top view or boundary view of a tree.
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?
Demonstrate bitwise operations and solve algorithmic problems using bit manipulation techniques.
Demonstrate bitwise operations and solve algorithmic problems using bit manipulation techniques.
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?
Explain fundamental Operating System concepts including multithreading, process synchronization, memory manage
Explain fundamental Operating System concepts including multithreading, process synchronization, memory management, and deadlock prevention.
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?
Write SQL queries involving complex joins, aggregations, subqueries, and indexing optimization.
Write SQL queries involving complex joins, aggregations, subqueries, and indexing optimization.
Approach
- Name the grain you start from and join outward from it.
- Check whether any join is one-to-many before aggregating, or the sums inflate.
- Say which index the query would use, and what makes it unusable.
- 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?
Keep soft-deleted accounts from blocking re-registration
app_user holds user_id, tenant_id, email CITEXT, password_hash (NULL for SSO principals), email_verified_at, auth_version, status ('invited','active','suspended','deactivated'), created_at, updated_at, deleted_at. Two live accounts for one address inside a tenant must be impossible, but an address freed by a soft delete must be reusable, and the same tenant may delete and re-register it repeatedly. Write the uniqueness DDL for PostgreSQL 16, then the equivalent for MySQL 8 where partial indexes do not exist, and say what each permits once three deleted rows already hold that address.
Approach
- Start from what is actually unique: not (tenant_id, email), but (tenant_id, email) among live rows. PostgreSQL says that directly — CREATE UNIQUE INDEX app_user_live_email ON app_user (tenant_id, email) WHERE deleted_at IS NULL. A full constraint over the same two columns burns the address permanently the first time someone deletes an account.
- Keep case-insensitivity in the type or the index, never in the application: CITEXT as given, or UNIQUE (tenant_id, lower(email)) as an expression index where the extension is unavailable. A case-sensitive unique column is exactly how two accounts for one human appear.
- For MySQL 8 the predicate has to move inside the key: add a discriminator column that is a constant 0 while the row is live and is set to user_id on delete, with UNIQUE (tenant_id, email, deleted_marker). Live rows share the constant and still collide; deleted rows differ from each other and stop colliding.
- State the NULL variant and its dependency: leaving the marker NULL for deleted rows also works, because a unique index treats NULLs as distinct — true in MySQL, and true in PostgreSQL only under the default NULLS DISTINCT, which PostgreSQL 15 lets you reverse. Check the polarity against the three existing deleted rows: constant-on-live is what preserves the collision you want, and reversing it silently admits duplicate live accounts.
Follow-up
- A deleted account re-registers with the same address the next day. Do the old resource rows follow the new user_id, and how does the API keep the two principals apart?
- How do you honour an erasure request while resource_revision.actor_user_id still references this table?
How would you design a scalable microservices architecture on AWS using ECS, ECR, Lambda, and Step Functions?
How would you design a scalable microservices architecture on AWS using ECS, ECR, Lambda, and Step Functions?
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?
Given a data-intensive case study, design a cost-effective cloud architecture diagram and explain your technic
Given a data-intensive case study, design a cost-effective cloud architecture diagram and explain your technical tradeoffs.
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?
How do you manage service dependencies, API gateway routing, and inter-service communication in a microservice
How do you manage service dependencies, API gateway routing, and inter-service communication in a microservices deployment?
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?
Explain strategies for system containerization, deployment pipelines, and managing container orchestration usi
Explain strategies for system containerization, deployment pipelines, and managing container orchestration using Kubernetes.
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?
Explain core Object-Oriented Programming (OOP) principles (Polymorphism, Encapsulation, Inheritance, Abstracti
Explain core Object-Oriented Programming (OOP) principles (Polymorphism, Encapsulation, Inheritance, Abstraction) with practical examples in Python, Java, or C#.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- 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 structure and secure RESTful APIs using standard HTTP methods, status codes, and JSON payloads?
How do you structure and secure RESTful APIs using standard HTTP methods, status codes, and JSON payloads?
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- 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 how application deployment, configuration packaging, and automated scripting (e.g., PowerShell) work
Describe how application deployment, configuration packaging, and automated scripting (e.g., PowerShell) work in production environments.
Approach
- Clarify what is being asked and what a complete answer contains.
- State your assumptions explicitly before working the problem.
- Say what you would check first and why it is the highest-information step.
- Work from the requirement backwards to the design.
Follow-up
- What assumption would you test first?
- How would you know your answer was wrong?
Walk me through the architecture of a key project listed on your resume, detailing your specific contributions
Walk me through the architecture of a key project listed on your resume, detailing your specific contributions and technical decisions.
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 Moody's candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Moody's loop
- Write out the reported sequence: HR Screening Call, Online Coding Assessment, Interactive Technical Rounds, Final Interviews.
- 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 & Algorithms (DSA)
- Spend the session on Data Structures & Algorithms (DSA), which Moody's 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).
03Work System Design
- Spend the session on System Design, which Moody's candidates report being tested on.
- Write one worked example in System Design and time yourself on it.
Deliverable: One timed worked example in System Design.
04Work NgRx
- Spend the session on NgRx, which Moody's candidates report being tested on.
- Write one worked example in NgRx and time yourself on it.
Deliverable: One timed worked example in NgRx.
05Answer out loud: Data Structures, Algorithms & Problem Solving
- Answer aloud, timed: Solve the overlapping intervals problem (e.g., merging or inserting time/data intervals).
- Answer aloud, timed: Search a target element in a 2D sorted matrix using an optimized binary search approach.
Deliverable: Spoken answers to 2 reported Data Structures, Algorithms & Problem Solving question(s), under time.
06Answer out loud: Cloud Architecture & System Design
- Answer aloud, timed: How would you design a scalable microservices architecture on AWS using ECS, ECR, Lambda, and Step Functions?
- Answer aloud, timed: Given a data-intensive case study, design a cost-effective cloud architecture diagram and explain your technical tradeoffs.
Deliverable: Spoken answers to 2 reported Cloud Architecture & System Design question(s), under time.
07Answer out loud: Backend, Databases & Core Computer Science
- Answer aloud, timed: Write SQL queries involving complex joins, aggregations, subqueries, and indexing optimization.
- Answer aloud, timed: Explain core Object-Oriented Programming (OOP) principles (Polymorphism, Encapsulation, Inheritance, Abstraction) with practical examples in Python, Java, or C#.
Deliverable: Spoken answers to 2 reported Backend, Databases & Core Computer Science 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.
How do you handle security, authentication, authorization, and data encryption in cloud-native applications?
How do you handle security, authentication, authorization, and data encryption in cloud-native applications?
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?
Describe a situation where you had to manage cross-team communication during a high-priority code review or te
Describe a situation where you had to manage cross-team communication during a high-priority code review or technical disagreement.
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?
How do you handle changing product requirements or ambiguous scope in a fast-paced development sprint?
How do you handle changing product requirements or ambiguous scope in a fast-paced development sprint?
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?
Give an example of a time you identified a system bottleneck or architectural defect and how you resolved it.
Give an example of a time you identified a system bottleneck or architectural defect and how you resolved it.
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?
Why are you interested in working at Moody's, and how do your skills align with our financial risk intelligenc
Why are you interested in working at Moody's, and how do your skills align with our financial risk intelligence mission?
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
How do you handle security, authentication, authorization, and data encryption in cloud-native applications?
- 02
Describe a situation where you had to manage cross-team communication during a high-priority code review or technical disagreement.
- 03
How do you handle changing product requirements or ambiguous scope in a fast-paced development sprint?
- 04
Give an example of a time you identified a system bottleneck or architectural defect and how you resolved it.
How difficult is the Software Engineer interview process at Moody's?
The overall technical difficulty is rated as average to challenging. The interview focuses heavily on computer science fundamentals, clear code execution, SQL query design, and practical cloud design rather than obscure algorithmic puzzles.
Moody's Software Engineer candidate reports ↗How long does the hiring process typically take from application to offer?
The process usually takes between 3 to 6 weeks, though timelines can vary depending on candidate location and team schedule. Candidates typically progress through an initial recruiter/HackerRank screen, followed by 2 to 3 technical and managerial rounds.
Moody's Software Engineer candidate reports ↗Does Moody's use automated tools or AI platforms during candidate scheduling?
Yes. Moody's utilizes an automated recruiting system named Sage to facilitate interview scheduling. Ensure you monitor your email notifications closely and confirm interview calendar invites promptly to avoid scheduling conflicts.
Moody's Software Engineer candidate reports ↗What differentiates successful candidates in Moody's engineering interviews?
Successful candidates distinguish themselves by explaining their architectural decisions clearly, demonstrating solid knowledge of cloud services (AWS/Azure), writing optimized SQL queries, and showing strong alignment with collaborative corporate culture.
Moody's Software Engineer candidate reports ↗How important is domain knowledge in finance or credit risk for this engineering role?
While prior experience in fintech or financial risk assessment is advantageous, it is not strictly required for general software engineering positions. Technical excellence, problem-solving ability, and strong software engineering fundamentals are the primary evaluation metrics.
Moody's Software Engineer candidate reports ↗How hard is the Moody's interview?
Candidates most commonly rate Moody's interviews as medium, based on 517 reported interviews. About 38% of candidates who interview go on to receive an offer.
Moody's Software Engineer candidate reports ↗What topics does Moody's test in interviews?
Moody's interviews most often cover SQL, Problem Solving, Python, Stakeholder Management, and Case Study Interviewing. The exact emphasis depends on the specific role you apply for.
Moody's Software Engineer candidate reports ↗Is Moody's a good place to work?
Employees rate Moody's 3.8 out of 5 overall, based on aggregated workplace reviews spanning career growth, work-life balance, compensation, culture, and management.
Moody's Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
Official role evidence, timestamped platform data and clearly labeled preparation advice.
- 01Moody's Software Engineer candidate reports ↗
Company-reported rounds, questions and FAQ.
candidate · Accessed 2026-09-22 - 02PracHub Software Engineer practice ↗
PracHub practice material, not company-reported.
platform · Accessed 2026-09-22 - 03PracHub preparation framework ↗
PracHub preparation guidance.
platform · Accessed 2026-09-22
Explore related engineering environments and compare the preparation focus.
Workiva Software Engineer Interview Guide
What Workiva asks Software Engineer candidates, from reported rounds and questions.
Trader Interactive Software Engineer Interview Guide
What Trader Interactive asks Software Engineer candidates, from reported rounds and questions.
Sander Software Engineer Interview Guide
What Sander asks Software Engineer candidates, from reported rounds and questions.
Ltimindtree Software Engineer Interview Guide
What Ltimindtree asks Software Engineer candidates, from reported rounds and questions.