As a Software Engineer at Newmont, you play a vital role in bridging cutting-edge technology with the world’s leading gold mining operations. This position is responsible for designing, developing, and maintaining robust software solutions, automation pipelines, and data systems that optimize mining processes, improve operational efficiency, and drive digital transformation across global sites. Your code and architecture directly impact industrial operations, asset reliability, and enterprise-wide technical infrastructure. The scale and complexity of work at Newmont mean that your contributions extend far beyond standard application development. You will collaborate with cross-functional teams comprising mining engineers, data scientists, and operations personnel to build solutions for complex operational challenges. Whether you are developing control systems software, building infrastructure networks, or creating reliability analytics tools, your work directly supports safety, sustainability, and productivity on a massive global scale. Expect an environment that demands both technical excellence and deep situational awareness. Because operates in safety-critical industrial settings, engineering solutions must prioritize reliability, security, and rigorous compliance standards. Successful candidates will find themselves in a forward-thinking culture that values continuous improvement, robust problem-solving, and collaborative innovation. Newmont
Online Application
reportedSubmit your application for the Software Engineer position.
What to demonstrate
- Submit your application for the Software Engineer position
- Depth in Safety hazard identification
How to prepare
- Answer aloud and timed: Describe a time you identified a safety hazard and what actions you took to address it.
- Answer aloud and timed: Explain the various things you will do to protect yourself and your colleagues at work.
Initial Screening
reportedParticipate in an online assessment that includes behavioral questions and safety scenarios.
What to demonstrate
- Participate in an online assessment that includes behavioral questions and safety scenarios
- Depth in Safety hazard identification
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.
Panel Interview
reportedAttend a formal panel interview via Microsoft Teams with HR and senior engineers.
What to demonstrate
- Attend a formal panel interview via Microsoft Teams with HR and senior engineers
- Depth in Safety hazard identification
How to prepare
- Answer aloud and timed: It is end of shift handover; what information do you provide to the next crew to ensure safety and continuity?
- Answer aloud and timed: How would your coworkers describe you?
Technical Deep-Dives
reportedEngage in discussions on technical topics, system architecture, and behavioral questions.
What to demonstrate
- Engage in discussions on technical topics, system architecture, and behavioral questions
- Depth in Safety hazard identification
How to prepare
- Answer aloud and timed: Describe the worst conflict you had with a coworker while working for a company and how you acted ethically with the person.
- Answer aloud and timed: How do you see yourself in five years?
Presentation (if applicable)
reportedPrepare and present a previous project or technical topic to demonstrate skills.
What to demonstrate
- Prepare and present a previous project or technical topic to demonstrate skills
- Depth in Safety hazard identification
How to prepare
- Answer aloud and timed: Why do you want to work here at Newmont?
- Answer aloud and timed: What situations would make you decide not to labor with a company?
PracHub editorial advice for the preparation topics above.
Prioritize Safety First
Always frame your technical solutions and past project stories through the lens of safety, reliability, and risk mitigation.
Use the STAR Method
Structure your behavioral answers using Situation, Task, Action, and Result, especially when answering questions about conflicts or tight deadlines.
Prepare for Panel Interviews
Expect to speak with a mix of HR representatives, technical peers, and engineering managers simultaneously. Tailor your communication to resonate with both technical and operational audiences.
Highlight Collaboration
Emphasize how you support your teammates and handle shift handovers, as teamwork is critical in industrial engineering environments.
Be Honest About Mistakes
When asked about past conflicts or failures, focus heavily on what you learned and how you adapted your professional behavior moving forward.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Find overlapping job attempts and peak concurrency from lease records
A day of job_run history yields about 50,000,000 attempt records: (job_run_id, job_type, attempt, started_at, finished_at which is NULL when the worker died, lease_expires_at). Leases expire on a clock, so a job that outran its lease ran twice. Produce (a) every job_run_id whose attempts overlapped in wall-clock time and (b) the peak number of simultaneously running attempts per job_type with the minute it occurred. Target O(n log n). State how you treat a NULL finished_at and what clock skew does to your answer.
Approach
- Define the interval before sorting anything: an attempt occupies [started_at, COALESCE(finished_at, lease_expires_at)). finished_at is observed and lease_expires_at is only a promise, so every attempt without a finish contributes an estimate and the whole result is a lower bound on overlap rather than an exact count.
- For peak concurrency, sweep: emit 2n endpoints, sort by (timestamp, kind) with ends ordered before starts at equal timestamps, then walk the sequence maintaining a counter per job_type and record each type's maximum with its timestamp. O(n log n) dominated by the sort, O(n) space, or O(1) extra if the sort is external and the walk streams.
- For overlap detection, do not compare attempts pairwise. A single global sort by (job_run_id, started_at) gives both the grouping and the order; within a group, keep the maximum end seen so far and report an overlap exactly when the next start is less than that running maximum, which is one linear pass after the sort.
- Half-open intervals matter and are easy to get wrong: with closed intervals an attempt ending at the same millisecond another begins reads as concurrency two, and across 50,000,000 records that artefact swamps the real signal.
Follow-up
- A handler is not idempotent and you have found 400 overlapping jobs. Which of them actually caused damage, and what would you query to find out?
- Peak concurrency for one job_type is 4 against a configured cap of 4. Is the cap working, or is the data hiding attempts that never started?
Track a rolling failure rate per destination for circuit decisions
The egress service delivers about 1,500 webhooks per second across roughly 40,000 destinations, each call bounded by a 10 second timeout. Maintain, per destination, the failure rate over the trailing 60 seconds so a caller can ask before dispatch whether the circuit should open. Attempts arrive as (destination_id, finished_at_ms, outcome). Requirement: amortised O(1) per attempt, with total memory bounded by the destination count rather than by traffic. Give the structure, its exact memory, and the rule that stops a destination with three attempts from opening a circuit.
Approach
- Name the exact-deque version and then reject it as the default. Holding timestamps and advancing a tail pointer past anything older than now minus 60 seconds is a correct two-pointer window at amortised O(1) per attempt, but its memory tracks in-window traffic, so one destination in a retry storm holds hundreds of thousands of entries while thousands of quiet destinations hold none.
- Use a ring of 60 one-second buckets per destination, each bucket a pair of counters for attempts and failures. On an attempt, advance the ring by the elapsed whole seconds, zeroing at most min(elapsed, 60) buckets, then increment the head. That is amortised O(1) with a fixed footprint per destination.
- State the footprint: 60 buckets times two 4-byte counters is 480 bytes of payload per destination, so 40,000 destinations is roughly 20 to 25 MB with per-entry overhead, bounded by the catalogue rather than by the rate. The cost is granularity, since the oldest bucket ages out in whole seconds, which is far tighter than the decision needs.
- Require a minimum sample before the circuit may open. A destination with three attempts and three failures reads as 100 percent and is not evidence; a floor of roughly 20 attempts in the window makes the ratio meaningful, and below that floor use a run of consecutive failures as the trigger instead.
Follow-up
- The fleet is 30 instances and each sees roughly a thirtieth of a destination's traffic. Where does the rate actually live, and what does a per-instance answer get wrong?
- A destination answers in 9.5 seconds and succeeds. It is not failing but it is consuming your per-destination concurrency. What signal should open the circuit here?
Collapse a redelivered event batch into per-aggregate high-water marks
You drain a batch of up to 5,000,000 events, each (aggregate_id BIGINT, aggregate_version INT, event_type, payload). The log guarantees order within one aggregate only; the batch merges 64 partitions, and a relay failover has redelivered a range, so an older version for an aggregate can appear after a newer one. Given a map of last_applied_version per aggregate, produce the events worth applying, at most one per (aggregate_id, version), plus the count discarded. Target O(n) time. State the memory for 2,000,000 distinct aggregates and what you do when it does not fit.
Approach
- One pass, one hash map from aggregate_id to the highest version kept, and a discard counter. An event whose version is at or below last_applied_version for its aggregate is dropped without further work, which is the whole reason the event carries its version rather than a delta. O(n) expected time, O(d) space in distinct aggregates.
- Keep the maximum, never the last occurrence. The redelivered range means the final appearance of an aggregate in the batch can be an older version than one seen earlier in the same batch, so last-wins applies stale state over newer state and the projection regresses with no error anywhere.
- Cost the memory instead of calling it large: an 8-byte key plus a 4-byte version is 12 bytes of payload, and an open-addressed table held at a 0.7 load factor costs roughly 17 bytes per entry before per-slot metadata, so 2,000,000 aggregates is tens of megabytes in a native layout and several times that in a runtime that boxes both key and value.
- If the distinct set exceeds memory, partition on hash(aggregate_id) mod P and reduce each partition independently. Every event for one aggregate hashes to the same partition, so the per-partition result is exact and the merge is concatenation rather than a second reduction.
Follow-up
- The payload is a patch rather than a snapshot, so applying only the highest version loses the intermediate changes. What changes in your reduction?
- How do you detect that version 7 arrived while version 6 was never delivered, and what should the consumer do about the gap?
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?
Stop tag and share joins from fanning out a page
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
- 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.
- 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.
- 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.
- 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 various things you will do to protect yourself and your colleagues at work.
Explain the various things you will do to protect yourself and your colleagues at 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?
Describe a situation where you were unsafe and how did you go about it, and what did you learn?
Describe a situation where you were unsafe and how did you go about it, and what did you learn?
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?
Watch this video and describe two safety hazards on the mine site.
Watch this video and describe two safety hazards on the mine site.
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?
It is end of shift handover; what information do you provide to the next crew to ensure safety and continuity?
It is end of shift handover; what information do you provide to the next crew to ensure safety and continuity?
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?
Technical questions was asked and also some questions on safety and systems engineering.
Technical questions was asked and also some questions on safety and systems engineering.
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?
Name a specific project or task that had a deadline that you were not sure if you were able to meet. How would
Name a specific project or task that had a deadline that you were not sure if you were able to meet. How would you overcome it?
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 the worst thing you ever did while working and how did you resolve the professional consequences?
What is the worst thing you ever did while working and how did you resolve the professional consequences?
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 through your process for handing over technical documentation and project artifacts to a secondary engine
Walk through your process for handing over technical documentation and project artifacts to a secondary engineering team.
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 approach troubleshooting complex technical systems in high-stakes environments?
How do you approach troubleshooting complex technical systems in high-stakes environments?
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 Newmont candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Newmont loop
- Write out the reported sequence: Online Application, Initial Screening, Panel Interview, Technical Deep-Dives, Presentation (if applicable).
- 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.
02Work Safety hazard identification
- Spend the session on Safety hazard identification, which Newmont candidates report being tested on.
- Write one worked example in Safety hazard identification and time yourself on it.
Deliverable: One timed worked example in Safety hazard identification.
03Work Safety hazard mitigation actions
- Spend the session on Safety hazard mitigation actions, which Newmont candidates report being tested on.
- Write one worked example in Safety hazard mitigation actions and time yourself on it.
Deliverable: One timed worked example in Safety hazard mitigation actions.
04Work Workplace safety procedures
- Spend the session on Workplace safety procedures, which Newmont candidates report being tested on.
- Write one worked example in Workplace safety procedures and time yourself on it.
Deliverable: One timed worked example in Workplace safety procedures.
05Answer out loud: Safety and Compliance
- Answer aloud, timed: Describe a time you identified a safety hazard and what actions you took to address it.
- Answer aloud, timed: Explain the various things you will do to protect yourself and your colleagues at work.
Deliverable: Spoken answers to 2 reported Safety and Compliance question(s), under time.
06Answer out loud: Behavioral and Interpersonal Dynamics
- Answer aloud, timed: How would your coworkers describe you?
- Answer aloud, timed: Describe the worst conflict you had with a coworker while working for a company and how you acted ethically with the person.
Deliverable: Spoken answers to 2 reported Behavioral and Interpersonal Dynamics question(s), under time.
07Answer out loud: Technical and Project Execution
- Answer aloud, timed: Technical questions was asked and also some questions on safety and systems engineering.
- Answer aloud, timed: Name a specific project or task that had a deadline that you were not sure if you were able to meet. How would you overcome it?
Deliverable: Spoken answers to 2 reported Technical and Project Execution 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 a time you identified a safety hazard and what actions you took to address it.
Describe a time you identified a safety hazard and what actions you took to address 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 would your coworkers describe you?
How would your coworkers describe you?
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 the worst conflict you had with a coworker while working for a company and how you acted ethically wi
Describe the worst conflict you had with a coworker while working for a company and how you acted ethically with the person.
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 see yourself in five years?
How do you see yourself in five years?
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 do you want to work here at Newmont?
Why do you want to work here at Newmont?
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?
What situations would make you decide not to labor with a company?
What situations would make you decide not to labor with a company?
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 a time you identified a safety hazard and what actions you took to address it.
- 02
How would your coworkers describe you?
- 03
Describe the worst conflict you had with a coworker while working for a company and how you acted ethically with the person.
- 04
How do you see yourself in five years?
How difficult is the interview process, and how much preparation time is typical?
The interview process is considered moderately rigorous, with a strong emphasis on behavioral and situational judgment alongside technical capabilities. Most candidates benefit from dedicating 2 to 3 weeks to review core engineering principles and practice situational storytelling.
Newmont Software Engineer candidate reports ↗What differentiates successful candidates from others?
Successful candidates combine solid technical competence with a genuine, demonstrable commitment to safety, teamwork, and operational excellence. Showing that you care about the real-world impact of your software on people and processes sets you apart.
Newmont Software Engineer candidate reports ↗What is the culture like for engineering teams at Newmont?
The engineering culture is collaborative, safety-focused, and global. Teams operate with a high degree of mutual respect, valuing practical problem-solvers who can communicate effectively across technical and non-technical disciplines.
Newmont Software Engineer candidate reports ↗What is the typical timeline from initial screen to offer?
The timeline can vary, but generally spans from 3 to 6 weeks from initial application submission through online assessments, panel interviews, and final resolution.
Newmont Software Engineer candidate reports ↗Are there remote or hybrid work options available?
Work arrangements depend heavily on the specific team and location, with some roles requiring site-based presence near operations (such as Perth, Boddington, or regional mining hubs) while others offer flexible or hybrid corporate arrangements.
Newmont Software Engineer candidate reports ↗What topics does Newmont test in interviews?
Newmont interviews most often cover Business Requirements Gathering, Safety hazard identification, Project Management Fundamentals, Business Process Improvement (Process Optimization), and Safety hazard mitigation actions. The exact emphasis depends on the specific role you apply for.
Newmont 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.
- 01Newmont 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