A Software Engineer at Xometry plays a pivotal role in powering a global digital marketplace that connects enterprise buyers with manufacturing suppliers. At its core, Xometry is not just an e-commerce platform; it is a highly sophisticated technology company driven by a proprietary, machine-learning-based instant quoting engine. As an engineer here, you will build and scale the software that translates complex 3D CAD models and manufacturing requirements into instant, accurate pricing, while seamlessly routing orders to a massive network of global suppliers. Your work directly impacts the efficiency of supply chains for Fortune 1000 companies and small machine shops alike. Whether you are working on the Buyer Experience team, optimizing the supplier portal, or refining the core quoting algorithms, your code will solve high-complexity problems involving geometry, pricing logic, and real-time marketplace dynamics. You will design and implement fast, reliable, and user-friendly web applications that make custom manufacturing as simple as ordering a consumer product online. Joining the engineering team means operating in a fast-paced, product-driven environment where full-stack proficiency is highly valued. You will collaborate closely with product managers, designers, and business stakeholders to turn strategic ideas into robust software.
Initial Contact
reportedThe process begins with initial communication from recruiters regarding the role.
What to demonstrate
- The process begins with initial communication from recruiters regarding the role
- Depth in Programming Problem Solving
How to prepare
- Answer aloud and timed: Implement a solution to a standard, mid-difficulty algorithmic problem (e.g., string manipulation, array processing, or data structure design) using a browser-based IDE.
- Answer aloud and timed: You are given a Node package or library you have never used before. Take 30 minutes to read its documentation, understand its API, and write a simple script that utilizes it to solve a specific task.
Virtual Screens
reportedCandidates participate in virtual screens to assess their technical skills and fit.
What to demonstrate
- Candidates participate in virtual screens to assess their technical skills and fit
- Depth in Programming Problem Solving
How to prepare
- Answer aloud and timed: Explain the difference between synchronous and asynchronous execution in Python or JavaScript, and describe how you would debug a race condition in a production environment.
- Answer aloud and timed: How does the Document Object Model (DOM) render elements, and what strategies do you use to optimize front-end rendering performance in a heavy React application?
Practical Coding Exercises
reportedCandidates complete practical coding exercises to demonstrate their problem-solving abilities.
What to demonstrate
- Candidates complete practical coding exercises to demonstrate their problem-solving abilities
- Depth in Programming Problem Solving
How to prepare
- Answer aloud and timed: Design a high-throughput API gateway that handles incoming quote requests from enterprise buyers and distributes them to internal microservices.
- Answer aloud and timed: How would you structure a database schema to support a marketplace with complex relationships between buyers, multi-part orders, manufacturing partners, and shipping logistics?
Panel Interviews
reportedComprehensive panel interviews focus on system design discussions and live coding.
What to demonstrate
- Comprehensive panel interviews focus on system design discussions and live coding
- Depth in Programming Problem Solving
How to prepare
- Answer aloud and timed: Describe how you would design a background processing system to handle long-running computations, such as analyzing a 3D CAD file for manufacturing feasibility.
- Answer aloud and timed: What are the trade-offs between using a REST API versus GraphQL or gRPC for communication between internal services in a hybrid Python and Rust backend?
Final Decision
reportedThe final decision is made based on performance throughout the interview process.
What to demonstrate
- The final decision is made based on performance throughout the interview process
- Depth in Programming Problem Solving
How to prepare
- Answer aloud and timed: Describe a time when you had to work with a highly ambiguous requirement. How did you clarify the scope, and what was the outcome?
- Answer aloud and timed: How do you handle a situation where a product manager or business executive pushes for a feature timeline that you believe compromises technical quality?
1 candidate reports. Individual accounts describe a particular role and hiring cycle.
Xometry Senior+ Machine Learning Engineer Interview Experience — A Deploy-Under-200ms Deep Dive
Company: Xometry (March) Round: Round 1 Position: Lead ML Questions/format: 1) Walk through your background and your projects in detail 2) The DS team handed you a model — if you had to deploy it, the requirement is that a single inference call has to come in under 200ms 1) Key points for talking about project background Project goal: the business problem you're solving, and the evaluation metric…
Read full experiencePracHub editorial advice for the preparation topics above.
Going into the loop without having done this.
Prepare for the unexpected: Some candidates have reported unannounced interview stages, such as a surprise 30-minute conversation with a Senior Vice President or Engineering Director at the end of a long panel. Pace your energy accordingly and remain professional throughout.
Going into the loop without having done this.
Over-communicate during live coding: If you are asked to complete a live programming task or learn a new package on the fly, talk through your thought process out loud. Interviewers care more about how you read documentation, structure your logic, and handle errors than whether you write flawless code on the first try.
Going into the loop without having done this.
Bring high-value snacks: Because the final panel interview can last between 3 to 3.5 hours and is highly intensive, make sure you have water and quick snacks nearby if you are interviewing remotely. You may not get substantial breaks between consecutive back-to-back rounds.
Going into the loop without having done this.
If you are interviewing for a hybrid role, verify the exact office address with your recruiter before your onsite day. Candidates have occasionally been sent to incorrect or outdated office locations due to administrative mismatches.
Choose a category, try a prompt, then open its approach, worked solution or follow-up when you need it.
Implement a solution to a standard, mid-difficulty algorithmic problem (e.g., string manipulation, array proce
Implement a solution to a standard, mid-difficulty algorithmic problem (e.g., string manipulation, array processing, or data structure design) using a browser-based IDE.
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 difference between synchronous and asynchronous execution in Python or JavaScript, and describe ho
Explain the difference between synchronous and asynchronous execution in Python or JavaScript, and describe how you would debug a race condition in a production environment.
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?
How does the Document Object Model (DOM) render elements, and what strategies do you use to optimize front-end
How does the Document Object Model (DOM) render elements, and what strategies do you use to optimize front-end rendering performance in a heavy React application?
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?
How would you structure a database schema to support a marketplace with complex relationships between buyers,
How would you structure a database schema to support a marketplace with complex relationships between buyers, multi-part orders, manufacturing partners, and shipping logistics?
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?
You are given a Node package or library you have never used before. Take 30 minutes to read its documentation,
You are given a Node package or library you have never used before. Take 30 minutes to read its documentation, understand its API, and write a simple script that utilizes it to solve a specific task.
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?
Design a high-throughput API gateway that handles incoming quote requests from enterprise buyers and distribut
Design a high-throughput API gateway that handles incoming quote requests from enterprise buyers and distributes them to internal microservices.
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 how you would design a background processing system to handle long-running computations, such as anal
Describe how you would design a background processing system to handle long-running computations, such as analyzing a 3D CAD file for manufacturing feasibility.
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 are the trade-offs between using a REST API versus GraphQL or gRPC for communication between internal ser
What are the trade-offs between using a REST API versus GraphQL or gRPC for communication between internal services in a hybrid Python and Rust backend?
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?
How would you explain Xometry's core business model and the value proposition of our machine learning-based qu
How would you explain Xometry's core business model and the value proposition of our machine learning-based quoting engine to someone outside the tech industry?
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 understanding of different manufacturing processes, such as CNC machining, 3D printing, or inject
What is your understanding of different manufacturing processes, such as CNC machining, 3D printing, or injection molding, and how do these constraints influence software design?
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?
If tasked with optimizing a feature to increase the conversion rate of quotes to completed orders, what techni
If tasked with optimizing a feature to increase the conversion rate of quotes to completed orders, what technical and business metrics would you track?
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?
Edge instances grow 400 MB per hour until the nightly restart
Edge API instances start at 700 MB resident and grow about 400 MB/hour; a nightly rolling restart has hidden it for weeks. Growth continues unchanged when request rate halves overnight, p99 degrades in the last hours before an instance is recycled, and heap used immediately after a forced full GC rises monotonically. The service holds no product state. Name the discriminating measurement that separates the plausible causes, give the most likely cause, and give the fix and how you would verify it.
Approach
- Separate resident memory from live heap first, because they fail differently. Resident size can grow from fragmentation, native buffers or thread stacks while the heap is flat; heap used after a full GC rising monotonically is the measurement that says objects are reachable and not being released. You already have it, so this is retention, not fragmentation, and that closes off half the candidate list.
- Use the rate's independence from traffic as the discriminator. Growth that continues at half the request rate rules out per-request objects that are merely slow to collect and points at a structure that grows with distinct values observed rather than with call volume. Write the candidates that have that property: a metrics registry keyed on a high-cardinality label, an unevicted cache, an interner, a per-key lock map.
- Take two heap snapshots an hour apart and diff by retained size, reading the dominator tree, not by allocation count or instance count. Expect one root holding a map with millions of entries, then follow the reference chain to the code that inserts and never removes. Allocation profilers point at churn, which is the wrong signal here.
- The candidate that fits this service is an observability label carrying an identifier, such as a request path recorded before templating so that /v1/resources/48213 becomes its own metric series. That grows with distinct ids seen, is independent of rate, and explains the late p99 degradation, since GC cost rises with the size of the live set.
Follow-up
- Post-GC heap is now flat but resident size still creeps. What are you looking at, and does it matter?
- How would you have detected this before an OOM, given the nightly restart masked the trend?
Built from the rounds and topics Xometry candidates report.
Prepare, practise & reflect
One practical outcome each day. Spend longer where you need it.
0 / 7 done01Map the Xometry loop
- Write out the reported sequence: Initial Contact, Virtual Screens, Practical Coding Exercises, Panel Interviews, Final Decision.
- 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 Programming Problem Solving
- Spend the session on Programming Problem Solving, which Xometry candidates report being tested on.
- Write one worked example in Programming Problem Solving and time yourself on it.
Deliverable: One timed worked example in Programming Problem Solving.
03Work Coding Interviews (Live/On-the-spot)
- Spend the session on Coding Interviews (Live/On-the-spot), which Xometry candidates report being tested on.
- Write one worked example in Coding Interviews (Live/On-the-spot) and time yourself on it.
Deliverable: One timed worked example in Coding Interviews (Live/On-the-spot).
04Work System Architecture / Architecture Design
- Spend the session on System Architecture / Architecture Design, which Xometry candidates report being tested on.
- Write one worked example in System Architecture / Architecture Design and time yourself on it.
Deliverable: One timed worked example in System Architecture / Architecture Design.
05Answer out loud: Coding & Technical Problem Solving
- Answer aloud, timed: Implement a solution to a standard, mid-difficulty algorithmic problem (e.g., string manipulation, array processing, or data structure design) using a browser-based IDE.
- Answer aloud, timed: You are given a Node package or library you have never used before. Take 30 minutes to read its documentation, understand its API, and write a simple script that utilizes it to solve a specific task.
Deliverable: Spoken answers to 2 reported Coding & Technical Problem Solving question(s), under time.
06Answer out loud: System Design & Architecture
- Answer aloud, timed: Design a high-throughput API gateway that handles incoming quote requests from enterprise buyers and distributes them to internal microservices.
- Answer aloud, timed: How would you structure a database schema to support a marketplace with complex relationships between buyers, multi-part orders, manufacturing partners, and shipping logistics?
Deliverable: Spoken answers to 2 reported System Design & Architecture question(s), under time.
07Answer out loud: Behavioral & Cultural Fit
- Answer aloud, timed: Describe a time when you had to work with a highly ambiguous requirement. How did you clarify the scope, and what was the outcome?
- Answer aloud, timed: How do you handle a situation where a product manager or business executive pushes for a feature timeline that you believe compromises technical quality?
Deliverable: Spoken answers to 2 reported Behavioral & Cultural Fit 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 when you had to work with a highly ambiguous requirement. How did you clarify the scope, and w
Describe a time when you had to work with a highly ambiguous requirement. How did you clarify the scope, and what was the outcome?
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 a situation where a product manager or business executive pushes for a feature timeline that
How do you handle a situation where a product manager or business executive pushes for a feature timeline that you believe compromises technical quality?
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?
Walk me through a complex technical project you led. How did you handle code reviews, mentor junior engineers,
Walk me through a complex technical project you led. How did you handle code reviews, mentor junior engineers, and ensure operational excellence?
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?
Tell me about a time you made a significant technical mistake in production. How did you identify it, resolve
Tell me about a time you made a significant technical mistake in production. How did you identify it, resolve it, and what did you learn from the experience?
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 when you had to work with a highly ambiguous requirement. How did you clarify the scope, and what was the outcome?
- 02
How do you handle a situation where a product manager or business executive pushes for a feature timeline that you believe compromises technical quality?
- 03
Walk me through a complex technical project you led. How did you handle code reviews, mentor junior engineers, and ensure operational excellence?
- 04
Tell me about a time you made a significant technical mistake in production. How did you identify it, resolve it, and what did you learn from the experience?
How difficult is the Xometry software engineering interview?
Candidates generally rate the difficulty as average to easy, but note that the process can feel intense due to its length and the unique nature of some rounds. Success depends heavily on your practical coding speed, system design fundamentals, and your ability to adapt to unfamiliar technical tasks rather than memorizing complex algorithmic puzzles.
Xometry Software Engineer candidate reports ↗How long does the entire interview process take from start to finish?
The timeline can vary widely. While some candidates complete the process and receive an offer within two to three weeks, others have reported a highly drawn-out process lasting several weeks or even months due to scheduling delays, team matching, or internal headcount shifts.
Xometry Software Engineer candidate reports ↗What is Xometry's policy on remote and hybrid work?
Xometry offers a mix of remote, hybrid, and office-based roles depending on the team and location. Many software engineering teams operate in a remote-first or hybrid model, with key engineering hubs located in Rockville/Bethesda, MD, Waltham, MA, and Denver, CO. Be sure to clarify the exact expectations for your specific role with your recruiter early in the process.
Xometry Software Engineer candidate reports ↗How should I prepare for the domain-specific questions about manufacturing?
You do not need to be a manufacturing expert, but showing curiosity and a basic understanding of Xometry's business model is highly advantageous. Spend some time reviewing their website, understanding how their instant quoting engine works, and researching basic concepts of CNC machining, 3D printing, and injection molding. Some candidates have reported being ghosted or experiencing long periods of silence after completing final-round interviews. If you do not hear back within a week of your panel, send a polite, structured follow-up email to your recruiter to request an update on your status.
Xometry Software Engineer candidate reports ↗How hard is the Xometry interview?
Candidates most commonly rate Xometry interviews as medium, based on 97 reported interviews. About 35% of candidates who interview go on to receive an offer.
Xometry Software Engineer candidate reports ↗What topics does Xometry test in interviews?
Xometry interviews most often cover Cross-Functional Collaboration, Risk Management, Stakeholder Management, Data Governance, and Cross-Functional Execution. The exact emphasis depends on the specific role you apply for.
Xometry Software Engineer candidate reports ↗Is Xometry a good place to work?
Employees rate Xometry 3.3 out of 5 overall, based on aggregated workplace reviews spanning career growth, work-life balance, compensation, culture, and management.
Xometry Software Engineer candidate reports ↗Where is Xometry headquartered?
Xometry is headquartered in North Bethesda, MD.
Xometry Software Engineer candidate reports ↗Sources & methodology 3 sources ↗
Official role evidence, timestamped platform data and clearly labeled preparation advice.
- 01Xometry 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.
Life.Church Software Engineer Interview Guide
What Life.Church asks Software Engineer candidates, from reported rounds and questions.
Zipline Software Engineer Interview Guide
What Zipline asks Software Engineer candidates, from reported rounds and questions.
Velozient Software Engineer Interview Guide
What Velozient asks Software Engineer candidates, from reported rounds and questions.
Twitch Interactive Software Engineer Interview Guide
What Twitch Interactive asks Software Engineer candidates, from reported rounds and questions.