HPC Systems Engineer
Posted Aug 14, 2026 · We last checked this listing on Oct 6, 2026
Likely interview questions for this role
Written from this job description, not a generic list. Each one notes what the interviewer is really checking.
About your past
Describe a time you had to profile or debug an application that a researcher or user handed you without much context about what it was supposed to do.
What they are checking: ability to work across unfamiliar codebases and collaborate with non-infrastructure people
How do you approach root cause analysis after an incident is resolved, when the pressure to just move on is high?
What they are checking: whether root cause discipline is a real habit or something they only do when forced
Tell me about a maintenance window you ran that touched a large chunk of production infrastructure. What went wrong, and what would you do differently?
What they are checking: experience coordinating high-stakes, high-blast-radius operations
This role involves rotating on-call and occasional weekend maintenance. Tell me about how you've handled sustained on-call responsibility in the past.
What they are checking: honesty about tolerance for unpredictable hours and whether their track record backs it up
Describe a situation where you had to work with an outside hardware or software vendor to resolve a problem you couldn't fix yourself.
What they are checking: ability to manage vendor relationships and advocate for the company's technical needs
What would you do
Say Slurm jobs across the cluster start failing intermittently but the nodes look healthy. How would you go about isolating the cause?
What they are checking: structured troubleshooting approach across a distributed batch scheduling system
If a researcher tells you their job is running slower on the cluster than they expect, but nothing in your monitoring looks abnormal, what do you check first?
What they are checking: whether they know how to bridge the gap between infrastructure metrics and researcher-perceived performance
How do you decide when documentation is worth writing versus when it's just going to rot, given how fast these systems change?
What they are checking: practical judgment about sustaining institutional knowledge in a fast-moving environment
About the work
Walk me through a time you had a parallel filesystem, like Lustre or GPFS, degrade under load in production. How did you find the bottleneck and what did you fix?
What they are checking: whether they have real hands-on debugging experience with large-scale storage systems, not just textbook knowledge
Tell me about a piece of tooling you built to compile, package, or upgrade software at scale across a large fleet of Linux machines.
What they are checking: depth of automation and config management experience versus one-off scripting
Which configuration management tool have you used most, Salt, Ansible, or Puppet, and what is something that tool handled badly that you had to work around?
What they are checking: real operational scars versus surface familiarity with the tool
What's your go-to language for systems tooling, Go, Python, or C, and can you describe something you built that would have been painful in the other two?
What they are checking: genuine language proficiency and judgment about tool fit, not just resume keywords
Tell me about a distributed system you designed or maintained that had a lot of interdependent parts. What made it fragile, and how did you make it less so?
What they are checking: experience with complex system architecture and understanding of failure modes, not just operating someone else's design
How do you decide what belongs in monitoring versus alerting, on a system this large, so people aren't drowning in noise?
What they are checking: judgment about signal versus noise in fault and performance monitoring at scale
Practice this interview out loud.
Offer builds a real interview for this exact role at Jump Trading from your resume and this job description, asks the questions one at a time, and tells you what landed. The first one is free.
Practice this out loudThe full job description
As published by Jump Trading.