← Back to Directory

Mithril

Small

Screna has 6 Mithril interview write-ups. The most reported round is the onsite coding round (2).

6 interview notes · updated Jun 2026

Mithril·Software Engineer·Onsite - Behavioral / Leadership

Jun 2026
One round at Mithril for a Software Engineer role, focused entirely on cross-functional collaboration. Pretty behavioral, no coding involved.
  • Tell me about a project where you worked with cross-functional teams. How did you handle communicating requirements, cutting down unnecessary back-and-forth, and keeping things moving?

“This one sounds easy until you realize they're not just asking if you've worked with other teams.”

View Post

Mithril·Software Engineer·Technical Phone Screen

Jun 2026
Mithril had me implement an Operation Triads Parsing system for a software engineering round, basically building a mini compiler IR from scratch. Pretty niche problem, not something you'd prep for on Leetcode.
  • Design and implement a system that parses arithmetic and logical expressions into operation triads (op, operand1, operand2), correctly handling operator precedence, associativity, and parentheses.

“This one took me a minute to even understand what they wanted.”

View Post

Mithril·Software Engineer·Onsite - System Design / Architecture

May 2026
System design round at Mithril for a software engineer role. The prompt was a beast: design a GPU resource manager spanning on-prem and multiple public clouds, covering basically everything from telemetry to cost-aware scheduling. Big scope, not a lot of hand-holding.
  • Design a system that manages and allocates GPU resources across a hybrid cloud environment, covering on-prem infrastructure and multiple public cloud providers. Your design should address GPU inventory tracking and telemetry, multi-tenant scheduling with quota enforcement, job queueing and preemption, fair-share and priority-based scheduling, fault tolerance, and cost-aware placement decisions.

“The scope of this thing is genuinely absurd.”

View Post

Mithril·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Round 4 at Mithril was a debugging exercise, not an algorithm grind. They handed me a small GPU resource manager codebase with logs and failing tests and basically said: figure out what's broken and fix it.
  • Given a small codebase for a GPU resource manager with failing unit tests and logs, identify and fix the bug in the GPU scoring logic.
  • Debug a resource allocation and preemption bug in the same GPU manager codebase, where a unit test is failing due to incorrect preemption behavior.
  • Extend the preemption logic to sort candidates by GPU score before selecting which resource to preempt.

“The root cause was that the scoring function wasn't actually checking the user's preference at all.”

View Post

Mithril·Software Engineer·Hiring Manager Screen

Apr 2026
Had a deep project review with the department head at Mithril for a software engineering role. The whole thing was basically a walkthrough of your resume but with real pressure, they want the full story on every major project, not just what you built.
  • Walk me through a major project you've worked on: why it was built, the technical decisions made, what you personally contributed, and what the outcome was.

“This is the core of the whole interview.”

View Post

Mithril·Software Engineer·Onsite - Coding / Algorithms

Apr 2026
Round 2 at Mithril was a coding round with a single problem, the Bomb Diffusing Problem. State search with backtracking, pretty approachable if you've seen DFS before.
  • Given a system with defined states and legal operations, determine whether a sequence of operations exists that reaches a safe goal state without passing through any unsafe states or revisiting the same state twice.

“Knew pretty quickly it was a DFS with a visited set.”

View Post