As a Software Engineer at Wood Mackenzie, you play a pivotal role in shaping the technology solutions that power our analytics and insights in the energy, metals, and mining sectors. This position is not merely about coding; it is about crafting robust systems that store, process, and analyze vast datasets, enabling clients to make informed decisions. Your work directly impacts the effectiveness of our products and the satisfaction of our users, as you contribute to systems that are integral to our business's decision-making processes. The role offers an exciting blend of challenges, from addressing complex technical problems to collaborating with cross-functional teams to deliver high-quality software solutions. You will have the opportunity to work on innovative projects that leverage cutting-edge technologies, enhancing the efficiency and scalability of our platforms. As a Software Engineer, you will not only write code but also engage in the design and architecture of solutions that drive strategic initiatives across Wood Mackenzie.
Initial Screening Call
reportedA call with a recruiter to assess your background and fit for the role.
What to demonstrate
- A call with a recruiter to assess your background and fit for the role
- Depth in SOLID Principles
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.
Interviews with Managers
reportedInterviews with hiring managers and technical leads to evaluate your skills and cultural fit.
What to demonstrate
- Interviews with hiring managers and technical leads to evaluate your skills and cultural fit
- Depth in SOLID Principles
How to prepare
- Answer aloud and timed: Can you discuss a challenging software project you worked on and the technologies involved?
- Answer aloud and timed: How do you ensure code quality and maintainability?
PracHub editorial advice for the preparation topics above.
Understand the business context
Familiarize yourself with Wood Mackenzie’s role in the energy and resources sectors. This knowledge will help frame your answers effectively.
Prepare for behavioral questions
Use the STAR method to structure your responses, focusing on your contributions and outcomes in team settings.
Practice coding problems
Use online platforms to practice coding challenges, focusing on algorithms and data structures relevant to the role.
Be ready to ask questions
Prepare thoughtful questions about the team, projects, and company culture to demonstrate your interest and engagement.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Write a function to sort an array of integers.
Write a function to sort an array of integers.
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 the time complexity of your solution.
Explain the time complexity of your solution.
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?
Given a binary tree, write a function to traverse it in-order.
Given a binary tree, write a function to traverse it in-order.
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?
Write the update path that detects a concurrent edit
resource carries version INT NOT NULL DEFAULT 1. resource_revision holds revision_id, resource_id, version, actor_user_id, change_kind, patch JSONB, request_id, created_at with UNIQUE (resource_id, version). outbox_event holds aggregate_type, aggregate_id, aggregate_version, event_type, payload, status. A PUT carries the version the client read. Write the exact statements for the single transaction that applies the edit, records the revision and enqueues 'resource.updated', and give the handler's branch on zero affected rows. Then say what PostgreSQL 16 does under READ COMMITTED when two of these updates hit one row at once.
Approach
- One transaction, three writes, no network call inside it: UPDATE resource SET title = $3, version = version + 1, updated_at = now() WHERE resource_id = $1 AND tenant_id = $4 AND version = $2; then INSERT the resource_revision row at version $2 + 1; then INSERT the outbox_event row at the same aggregate_version. The event goes to a table rather than a broker because no transaction spans both.
- Branch on the affected-row count before doing anything else. Zero has three causes — stale version, wrong tenant, row gone — so re-read once and map to 409 carrying the current version, or 404 for an id outside the caller's tenant, which also stops the endpoint confirming that another tenant's id exists.
- State the engine behaviour instead of assuming it. Under READ COMMITTED the second UPDATE blocks on the row lock, and when the first commits PostgreSQL re-evaluates the WHERE clause against the newly committed row, so the version predicate now fails and the statement reports zero rows. Under REPEATABLE READ the identical collision raises SQLSTATE 40001 instead, so the handler must fold both shapes into one conflict response.
- Keep UNIQUE (resource_id, version) even though the predicate already serialises writers. It is what makes a lost update unwritable if any other path ever reaches the revision table, and it converts a logic bug into 23505 rather than into a silently missing history row.
Follow-up
- A client sends the version it read ten minutes ago and the resource has moved three versions. What is in your 409 so it can resolve the conflict without a full re-fetch?
- Two editors, two disjoint fields, no overlap. Does your answer still refuse the second write, and should it?
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?
Explain the SOLID principles and how they apply to your work.
Explain the SOLID principles and how they apply to your work.
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?
Can you discuss a challenging software project you worked on and the technologies involved?
Can you discuss a challenging software project you worked on and the technologies involved?
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 ensure code quality and maintainability?
How do you ensure code quality and maintainability?
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?
Design a system for a real-time data analytics platform. What components would you include?
Design a system for a real-time data analytics platform. What components would you include?
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 would you approach designing a microservices architecture for a large application?
How would you approach designing a microservices architecture for a large application?
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 how you would ensure data consistency in a distributed system.
Explain how you would ensure data consistency in a distributed system.
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?
You are given a dataset with missing values. How would you handle this situation?
You are given a dataset with missing values. How would you handle this situation?
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?
A customer reports a bug in your application. Describe your process for investigating and resolving the issue.
A customer reports a bug in your application. Describe your process for investigating and resolving the issue.
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?
What is your approach to debugging and resolving software issues?
What is your approach to debugging and resolving software issues?
Approach
- Establish what changed and when, before forming any theory.
- Pick a bisection that eliminates candidates whichever way it turns out.
- Check the instrumentation before believing the symptom.
- 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?
Built from the rounds and topics Wood Mackenzie candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Wood Mackenzie loop
- Write out the reported sequence: Initial Screening Call, Interviews with Managers.
- 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 2 reported rounds, with the weakest marked.
02Work SOLID Principles
- Spend the session on SOLID Principles, which Wood Mackenzie candidates report being tested on.
- Write one worked example in SOLID Principles and time yourself on it.
Deliverable: One timed worked example in SOLID Principles.
03Work Software Design / High-Level Design
- Spend the session on Software Design / High-Level Design, which Wood Mackenzie candidates report being tested on.
- Write one worked example in Software Design / High-Level Design and time yourself on it.
Deliverable: One timed worked example in Software Design / High-Level Design.
04Work Object-Oriented Programming (OOP)
- Spend the session on Object-Oriented Programming (OOP), which Wood Mackenzie candidates report being tested on.
- Write one worked example in Object-Oriented Programming (OOP) and time yourself on it.
Deliverable: One timed worked example in Object-Oriented Programming (OOP).
05Answer out loud: Technical / Domain Questions
- Answer aloud, timed: Describe your experience with object-oriented programming and its principles.
- Answer aloud, timed: Explain the SOLID principles and how they apply to your work.
Deliverable: Spoken answers to 2 reported Technical / Domain Questions question(s), under time.
06Answer out loud: System Design / Architecture
- Answer aloud, timed: Design a system for a real-time data analytics platform. What components would you include?
- Answer aloud, timed: How would you approach designing a microservices architecture for a large application?
Deliverable: Spoken answers to 2 reported System Design / Architecture question(s), under time.
07Answer out loud: Behavioral / Leadership
- Answer aloud, timed: Describe a situation where you had to work under pressure. How did you handle it?
- Answer aloud, timed: Can you provide an example of a successful team project and your role in it?
Deliverable: Spoken answers to 2 reported Behavioral / Leadership 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.
Describe your experience with object-oriented programming and its principles.
Describe your experience with object-oriented programming and its principles.
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 work under pressure. How did you handle it?
Describe a situation where you had to work under pressure. How did you handle 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?
Can you provide an example of a successful team project and your role in it?
Can you provide an example of a successful team project and your role in 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?
How do you handle conflicts or disagreements within a team?
How do you handle conflicts or disagreements within a team?
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
Describe your experience with object-oriented programming and its principles.
- 02
Describe a situation where you had to work under pressure. How did you handle it?
- 03
Can you provide an example of a successful team project and your role in it?
- 04
How do you handle conflicts or disagreements within a team?
What is the typical interview difficulty and preparation time?
The interview process for a Software Engineer at Wood Mackenzie can be considered average to difficult, depending on your experience. Candidates typically spend a few weeks preparing, focusing on technical skills and behavioral questions.
Wood Mackenzie Software Engineer candidate reports ↗What differentiates successful candidates?
Successful candidates demonstrate a strong technical foundation, effective problem-solving skills, and the ability to communicate clearly. They also align well with the company's values and culture.
Wood Mackenzie Software Engineer candidate reports ↗What is the culture like at Wood Mackenzie?
Wood Mackenzie fosters a collaborative and innovative environment. Employees are encouraged to share ideas, take initiative, and contribute to collective goals.
Wood Mackenzie Software Engineer candidate reports ↗What is the typical timeline from initial screen to offer?
The timeline can vary, but candidates often report a process lasting several weeks to a few months. Delays in communication can occur, so it's advisable to follow up if you haven't heard back.
Wood Mackenzie Software Engineer candidate reports ↗Are there remote work or hybrid options available?
Wood Mackenzie has embraced flexible work arrangements, including remote and hybrid options. However, specifics may vary by team and location.
Wood Mackenzie Software Engineer candidate reports ↗What topics does Wood Mackenzie test in interviews?
Wood Mackenzie interviews most often cover Stakeholder Management, Problem Solving, Behavioral Interviewing, Python, and Presentation Skills. The exact emphasis depends on the specific role you apply for.
Wood Mackenzie 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.
- 01Wood Mackenzie 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
Explore related engineering environments and compare the preparation focus.
Cognition Software Engineer Interview Guide
What Cognition asks Software Engineer candidates, from reported rounds and questions.
Discord Software Engineer Interview Guide
Database practice for Discord candidates: how an index changes a query plan, and which anomalies survive a given isolation level, since read committed still permits non-repeatable reads.
CoreWeave Software Engineer Interview Guide
Failure-handling practice for CoreWeave software engineer candidates: requests whose outcome a timeout leaves unknown, where a retry is safe, and deduplicating at the receiver instead of assuming exactly-once delivery.
Aerospike Software Engineer Interview Questions & Guide 2026
Aerospike database-engine preparation through an original single-owner Python key-value store with bounded logical index accounting, disk-offset reads, conditional writes, tombstones, process-restart recovery and 3,240 checks. Existing 14 p