Senior Storage Infrastructure Engineer: Career Walkthrough and a Difficult Problem Solved

In a short recruiter screen for a senior core infrastructure engineer role on a storage team at a cloud infrastructure provider, the recruiter asked two questions: tell me about your experience, and tell me about a difficult problem you solved. The call lasted about 15 to 20 minutes, also covered the next steps of the process, and was mainly a basic check of communication and fit before the technical rounds. Answer both questions as you would on that call. ### Constraints and Clarifications - Both answers and the recruiter's own wrap-up fit into about 15 to 20 minutes, so each answer has a few minutes at most. - Assume the recruiter is not a storage specialist: technical depth is assessed in later rounds, but the answers should still show that your background fits storage infrastructure work. ### Clarifying Questions - How much time is there for these questions, and would the recruiter prefer a full overview or a focus on the most recent role? - Which part of storage does the team work on, for example block, object or file storage, or the metadata and control-plane services around them, so you can choose the most relevant example? - Should the difficult problem be a technical one, or is a people or process problem equally welcome? ### Part 1 — Walk through your experience Tell the recruiter about your experience. ```hint Point the story at storage Order your background so that it ends on the work closest to core infrastructure and storage, and make clear at each step what you personally owned. ``` #### What This Part Should Cover - A short arc through your roles that fits in about two minutes - Seniority signals: the systems you owned, their scale, your production responsibility and the people you influenced - A clear link from your background to a senior storage infrastructure role ### Part 2 — A difficult problem you solved Tell the recruiter about a difficult problem you solved. ```hint Make the difficulty concrete Choose one problem whose cause or solution was not obvious, and be ready to say what made it hard, what you did yourself, and how you knew it was fixed, in words a non-specialist can follow. ``` #### What This Part Should Cover - A problem with real stakes for an infrastructure system, such as availability, data integrity, performance or a risky migration - Your own diagnosis and decisions, including the options you rejected - A measurable outcome and the change you made so that it would not happen again ### What a Strong Answer Covers - Answers sized for a 15 to 20 minute screen, leaving room for the recruiter's questions and the next steps - A consistent story in which the experience overview sets up the difficult-problem example - Senior-level signal: ownership, judgment under ambiguity and impact beyond your own code - Plain language with one or two precise technical details instead of jargon - Honest attribution of what the team did and what you did ### Follow-up Questions - Which system you mentioned is closest to what this storage team builds, and what exactly was your part in it? - Looking back at the difficult problem, what would you do differently now? - How did you confirm the fix worked, and what did you put in place so that it would not recur? - Why move toward storage and core infrastructure at this point in your career?