As a Software Engineer at Mariana Minerals, you play a vital role in building the technical infrastructure that supports complex industrial, metallurgical, and resource optimization processes. You are responsible for designing, developing, and scaling software systems that bridge modern web architectures with heavy industrial operations. Whether you are building intuitive frontend interfaces or robust backend services, your work directly impacts how engineering teams process data, manage workflows, and scale operations across multiple geographic locations. The role sits at the intersection of modern software development and heavy industry, presenting unique and stimulating technical challenges. You will work on integrating seemingly disparate software systems, building real-time data pipelines, and architecting unified services that act as a single source of truth for the business. This position demands a high degree of technical versatility, system-level thinking, and an ability to collaborate closely with cross-functional teams including process engineers, data modelers, and leadership. Expect an environment that moves fast and values pragmatic problem-solving over rigid adherence to a task list. You will be expected to demonstrate senior-like behavior, taking ownership of features from conception to deployment while actively seeking feedback to ensure your solutions serve the broader team.
Recruiter Screen
reportedIn-depth discussion to explore fit for the role and interest in the industrial-meets-digital space.
What to demonstrate
- In-depth discussion to explore fit for the role and interest in the industrial-meets-digital space
- Depth in System Design
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.
Technical Screen
reportedInitial technical assessment to evaluate hands-on coding skills.
What to demonstrate
- Initial technical assessment to evaluate hands-on coding skills
- Depth in System Design
How to prepare
- Answer aloud and timed: What strategies do you use when building a complex frontend interface that cannot realistically be completed in a single standard sitting?
- Answer aloud and timed: How do you validate and test code generated or assisted by AI-forward development tools before merging it into production?
Hands-on Coding Rounds
reportedPractical coding interviews focusing on real-world engineering scenarios.
What to demonstrate
- Practical coding interviews focusing on real-world engineering scenarios
- Depth in System Design
How to prepare
- Answer aloud and timed: What steps do you take to optimize a web application's frontend performance when dealing with large, continuous streams of industrial data?
- Answer aloud and timed: Tell me about a time when you went out of your way to ensure a technical solution worked seamlessly for the entire team rather than just finishing your assigned task list.
Architecture Design
reportedDiscussion and evaluation of system architecture and design capabilities.
What to demonstrate
- Discussion and evaluation of system architecture and design capabilities
- Depth in System Design
How to prepare
- Answer aloud and timed: How do you approach seeking feedback from cross-functional stakeholders when requirements are ambiguous?
- Answer aloud and timed: Describe a situation where you had to balance tight project timelines with maintaining high code quality and architectural integrity.
Team Fit
reportedAssessment of cross-functional communication skills and team collaboration.
What to demonstrate
- Assessment of cross-functional communication skills and team collaboration
- Depth in System Design
How to prepare
- Prepare two projects you led end to end, each with the decision you owned and what it cost.
- Have three questions about the team's roadmap and how success is measured in the first six months.
Executive Alignment
reportedFinal discussions with team leadership to ensure alignment with company goals.
What to demonstrate
- Final discussions with team leadership to ensure alignment with company goals
- Depth in System Design
How to prepare
- Work System Design until you can explain it without notes
- Work Frontend Development until you can explain it without notes
PracHub editorial advice for the preparation topics above.
Communicate your thought process
Always talk through your reasoning during technical and system design screens so interviewers can evaluate your problem-solving methodology, not just your final output.
Scrutinize AI-generated output
When utilizing AI-enabled tools during coding exercises, never accept outputs blindly; demonstrate critical review and ownership of your code.
Keep presentations concise
During case study or presentation rounds, remember that less is more, ensuring you leave ample time for meaningful Q&A with the panel.
Prioritize team impact
Frame your technical decisions around how they benefit the broader organization, showing that you care about long-term maintainability and peer collaboration.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
How do you approach seeking feedback from cross-functional stakeholders when requirements are ambiguous?
How do you approach seeking feedback from cross-functional stakeholders when requirements are ambiguous?
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?
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?
Canonicalise a request body into a stable idempotency fingerprint
idempotency_key.request_fingerprint is a SHA-256 over the method, path and canonicalised body, and a retry whose fingerprint differs must be rejected with 422 rather than served the stored response. Write the canonicaliser. Bodies are JSON up to 256 KB nested at most 32 levels; clients vary key order, whitespace and unicode escaping, and some send 64-bit ids as JSON numbers. Produce a deterministic byte string such that semantically identical bodies match and any semantic difference does not. State your complexity and name two normalisations you refuse to perform.
Approach
- Parse once into a tree, then re-serialise under fixed rules: object keys sorted, array order preserved, one escaping convention, no insignificant whitespace. Parsing is O(n) and sorting keys is O(k log k) per object, so O(n log n) overall with O(depth) stack, and the 32-level cap is enforced during parsing because hostile nesting is how a canonicaliser becomes a stack overflow.
- Sort keys by their UTF-8 bytes and say why the obvious implementation is wrong in some runtimes: a default string comparison that orders by UTF-16 code units places surrogate pairs, meaning code points from U+10000 up, below U+E000 to U+FFFF, which is not UTF-8 byte order, so two services written in different languages disagree on the same document.
- Do not re-encode numbers through a double. IEEE-754 binary64 represents integers exactly only up to 2^53, so normalising a 19-digit id through a float changes it, and 1 against 1.0 cannot be reconciled without deciding whether they are the same value. Preserve the literal token, and require ids as strings at the API boundary if you want them comparable.
- Reject duplicate keys rather than picking one. JSON permits them and parsers disagree, most keeping the last, so any choice you make ties the fingerprint to a parser detail that the code handling the request does not necessarily share.
Follow-up
- A client sends the same logical request with an extra field your API ignores. Same key, different fingerprint, so you return 422. Is that the right answer?
- Where does the fingerprint get computed relative to request decompression and the body-size limit?
Hold a per-tenant active cap against concurrent creates
A tenant on the standard plan may hold at most 50 resources with status='active'. The create handler runs SELECT count(*) FROM resource WHERE tenant_id = $1 AND status = 'active', compares to 50, then inserts. Two creates arrive 3 ms apart on different instances and the tenant lands at 51. Name the anomaly, say whether PostgreSQL 16 READ COMMITTED or REPEATABLE READ prevents it and why, then give an implementation that holds the cap at READ COMMITTED with the exact statements. Finally, say what changes when the cap is 'at most one running export per tenant' on job_run.
Approach
- Name it: write skew. The two transactions read an overlapping set and write disjoint rows, so there is no row-level conflict for the engine to detect and each commit is individually legal.
- Rule out the levels precisely. READ COMMITTED takes a fresh snapshot per statement and takes no lock on the counted rows, so both see 49. PostgreSQL's REPEATABLE READ is snapshot isolation: it removes non-repeatable reads and phantoms within the snapshot but still admits write skew, because the anomaly is not a re-read of a changed row, it is a read of a set that a concurrent transaction invalidates. Only SERIALIZABLE closes it, by tracking the read dependency and aborting one transaction with SQLSTATE 40001 — a guarantee that exists only if the application re-runs the whole transaction from the read.
- Convert the set predicate into a single-row conflict: keep tenant.active_resource_count and run UPDATE tenant SET active_resource_count = active_resource_count + 1 WHERE tenant_id = $1 AND active_resource_count < 50 in the same transaction as the INSERT. Zero affected rows is the cap, returned as 409. The row lock serialises the decision at any isolation level, and contention is bounded to one tenant's row — which is also the fair-scheduling unit, unlike a global counter that would convoy every tenant behind one row.
- State the cost you just took on: a counter is a second source of truth that can drift, so every path that changes status must adjust it inside the same transaction, and a periodic reconciliation has to exist, with resource_revision as the authority for what the count should have been.
Follow-up
- A resource moves from archived back to active. Which statements change, and what breaks if the counter update and the status change land in different transactions?
- The cap becomes plan-dependent and a plan can change mid-month. Where does the number 50 live, and who reads it?
Denormalise tenant onto revisions and backfill it live
resource_revision (revision_id, resource_id, version, actor_user_id, change_kind, patch, request_id, created_at) has 400M rows and no tenant column; tenant_id lives only on resource. Two reads need it: a tenant-scoped audit feed ordered by created_at DESC, and an offboarding purge. Both join back to resource today. Justify adding tenant_id to resource_revision against those two reads, name the anomaly the copy introduces and the constraint that prevents it, then give the ordered migration for a live table taking 1.2k writes/second — the lock each step takes, how the backfill is batched, and where each step stops being reversible. PostgreSQL 16.
Approach
- Justify from the access path rather than from taste. Without the column, the audit feed either scans resource_revision by created_at and discards other tenants' rows, or resolves the tenant's resource_ids first and probes with them — both proportional to the tenant's whole history rather than to one page. With (tenant_id, created_at DESC, revision_id DESC) it is a seek that stops at 50 rows, and the purge becomes a ranged delete instead of a join.
- Name the cost exactly: a second copy of a fact can disagree with the first. Make the disagreement unwritable rather than documented — add UNIQUE (resource_id, tenant_id) on resource so it can serve as a foreign-key target, then FOREIGN KEY (resource_id, tenant_id) REFERENCES resource (resource_id, tenant_id) on the revision table. A revision can then only ever carry its parent's tenant.
- Step one, expand: ALTER TABLE resource_revision ADD COLUMN tenant_id BIGINT NULL, with no default, so it is a catalogue change and no rewrite. It still needs ACCESS EXCLUSIVE for an instant, and that instant queues behind the longest open transaction on the table while every later query queues behind it — set lock_timeout to 2s and retry rather than wait.
- Step two, dual-write: deploy the writer that populates tenant_id on every new revision while reads still use the join. Reversible by redeploying the previous build, because nothing reads the column yet.
Follow-up
- The backfill is half finished and a rollback is required. What state is the table in, and what does the previous build do with a half-populated column?
- How do you verify the backfill actually finished, given rows are still being inserted while it runs?
How would you design a backend database architecture using PostgreSQL to serve as a reliable source of truth?
How would you design a backend database architecture using PostgreSQL to serve as a reliable source of truth?
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?
Can you walk through how you would integrate multiple seemingly unrelated software systems using APIs and webh
Can you walk through how you would integrate multiple seemingly unrelated software systems using APIs and webhooks into a unified service?
Approach
- Say who the caller is and what they do when the call fails halfway.
- Define the identity of a request so a retry cannot double-apply it.
- Separate accepted, pending, failed and confirmed; they are different facts.
- Design the error taxonomy before the success shape; callers branch on it.
Follow-up
- What happens if the caller retries after a timeout?
- How does a client discover it is on an old version of this contract?
What strategies do you use when building a complex frontend interface that cannot realistically be completed i
What strategies do you use when building a complex frontend interface that cannot realistically be completed in a single standard sitting?
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 validate and test code generated or assisted by AI-forward development tools before merging it into
How do you validate and test code generated or assisted by AI-forward development tools before merging it into production?
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?
What steps do you take to optimize a web application's frontend performance when dealing with large, continuou
What steps do you take to optimize a web application's frontend performance when dealing with large, continuous streams of industrial data?
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?
Describe a situation where you had to balance tight project timelines with maintaining high code quality and a
Describe a situation where you had to balance tight project timelines with maintaining high code quality and architectural integrity.
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 Mariana Minerals candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Mariana Minerals loop
- Write out the reported sequence: Recruiter Screen, Technical Screen, Hands-on Coding Rounds, Architecture Design, Team Fit, Executive Alignment.
- 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 6 reported rounds, with the weakest marked.
02Work System Design
- Spend the session on System Design, which Mariana Minerals 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.
03Work Frontend Development
- Spend the session on Frontend Development, which Mariana Minerals candidates report being tested on.
- Write one worked example in Frontend Development and time yourself on it.
Deliverable: One timed worked example in Frontend Development.
04Work Backend Development
- Spend the session on Backend Development, which Mariana Minerals candidates report being tested on.
- Write one worked example in Backend Development and time yourself on it.
Deliverable: One timed worked example in Backend Development.
05Answer out loud: Technical and System Architecture
- Answer aloud, timed: How would you design a backend database architecture using PostgreSQL to serve as a reliable source of truth?
- Answer aloud, timed: Can you walk through how you would integrate multiple seemingly unrelated software systems using APIs and webhooks into a unified service?
Deliverable: Spoken answers to 2 reported Technical and System Architecture question(s), under time.
06Answer out loud: Behavioral and Cross-Collaboration
- Answer aloud, timed: Tell me about a time when you went out of your way to ensure a technical solution worked seamlessly for the entire team rather than just finishing your assigned task list.
- Answer aloud, timed: How do you approach seeking feedback from cross-functional stakeholders when requirements are ambiguous?
Deliverable: Spoken answers to 2 reported Behavioral and Cross-Collaboration question(s), under time.
07Dry run for Mariana Minerals
- Run one full mock under time, then write down the two questions you most want to ask your interviewers.
Deliverable: A completed timed mock and two questions to ask.
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.
Tell me about a time when you went out of your way to ensure a technical solution worked seamlessly for the en
Tell me about a time when you went out of your way to ensure a technical solution worked seamlessly for the entire team rather than just finishing your assigned task list.
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 situations where communication from leadership or interview coordinators is delayed or lacks
How do you handle situations where communication from leadership or interview coordinators is delayed or lacks clarity?
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 apply your software engineering skills specifically within an industrial and mineral proces
Why do you want to apply your software engineering skills specifically within an industrial and mineral processing environment like Mariana Minerals?
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
Tell me about a time when you went out of your way to ensure a technical solution worked seamlessly for the entire team rather than just finishing your assigned task list.
- 02
How do you handle situations where communication from leadership or interview coordinators is delayed or lacks clarity?
- 03
Why do you want to apply your software engineering skills specifically within an industrial and mineral processing environment like Mariana Minerals?
How difficult is the interview process, and how much preparation time should I plan for?
The interview process is rigorous and multi-layered, often rated as moderately to highly challenging due to its combination of open-ended technical screens, system design deep dives, and extensive behavioral evaluations. Plan for at least two to four weeks of dedicated preparation, focusing heavily on full-stack coding practice and architectural integration patterns.
Mariana Minerals Software Engineer candidate reports ↗What truly differentiates successful candidates during the technical rounds?
Successful candidates stand out by treating coding challenges as collaborative exercises rather than isolated tests. They explain their thought process out loud, critically evaluate automated or AI-assisted code outputs, and make deliberate scoping decisions that prioritize long-term team maintainability.
Mariana Minerals Software Engineer candidate reports ↗How does Mariana Minerals approach work location and office policies?
Role locations can vary across tech hubs and operational centers such as San Francisco, Houston, Ann Arbor, and Moab. It is essential to confirm specific office presence and relocation expectations early in your recruiter screening to ensure absolute alignment.
Mariana Minerals Software Engineer candidate reports ↗What is the typical timeline from the initial recruiter screen to a final offer?
The timeline can span several weeks due to the multi-stage nature of the process, which includes initial screens, multiple technical rounds, cross-functional chats, and leadership interviews. Patience, responsiveness, and clear communication will help you navigate this timeline smoothly.
Mariana Minerals Software Engineer candidate reports ↗How can I best prepare for the cross-collaboration and leadership portions of the loop?
Prepare concrete stories from your past experience where you went beyond your assigned ticket to help your team succeed. Emphasize instances where you actively solicited feedback, bridged communication gaps between technical and non-technical teams, and navigated ambiguous project requirements successfully.
Mariana Minerals Software Engineer candidate reports ↗What topics does Mariana Minerals test in interviews?
Mariana Minerals interviews most often cover Machine Learning Engineering, System Design, Project Controls, Frontend Development, and Data Engineering. The exact emphasis depends on the specific role you apply for.
Mariana Minerals 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.
- 01Mariana Minerals 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.
Vercel Software Engineer Interview Guide
Debugging practice for Vercel software engineer prep built on a reproduction you trust, narrowing to the smallest failing input, and changing one variable per run so the result stays attributable.
Spotify Software Engineer Interview Guide
Timed practice for Spotify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.
Shopify Software Engineer Interview Guide
Timed practice for Shopify software engineer candidates who lose time to the clock: short problems taken end to end, then reviewed against a written rubric rather than a passing test run.
Ramp Software Engineer Interview Guide
Systems practice for Ramp software engineer candidates, weighted toward payments and lending work: the load that actually arrives, the failure modes that matter there, and the invariants a partial outage must not break.