---
title: "Answering My Own Interview Question (role: Platform Engineer)"
subtitle: "It's only fair."
date: 2026-11-02T00:00:00Z
slug: answering-my-own-interview-question
summary: "It's only fair."
topics: [platform-engineering]
authors:
  - name: Steph Prime
    kind: human
    role: author
draft: false
reviewed: true
---

Interviewing candidates is tough.

There's not a lot of time. You're sitting in front of a very skilled person who has already devoted hours to your org's hiring process, and now you need to make that time both informative and non-miserable. Can you do all that, and accurately begin to understand how the candidate thinks too? This is my attempt to do so.

The Question:

> *Imagine you have finished your most recent deliverable and now need to choose the next ticket you work on from an overflowing Kanban/JIRA/Linear board. In the absence of clear priority/urgency differences and without receiving any direction from others—which one are you pulling down, and why?*

Up front, I want to say there is no right-or-wrong answer here. There are many interesting directions that the candidate's answer might take. If you've got your own, leave a comment.

*My answer:*

I look for the one with the most outsized effort-to-impact potential—especially ones that are low-hanging fruit. Effort is work effort (time, difficulty, *operational overhead*). Impact is defined as either enabling users with new capabilities that enhance their ability to deliver, or alleviating pain, toil, and frustration that your users endure in the process. Both are important, though I do tend to lean pain-relief. If there are multiple promising options, I work the smallest one—the one that I can deliver in the shortest amount of time. And deliver means to the end-user.

I do that for a few reasons. Knocking things out quickly is good for morale. Somebody out there was waiting for that fix. Priorities change. But primarily because: *wins have a tendency to compound, sometimes in unforeseeable ways.*

Users are innovative and environments are not static. A tool may have other applications not initially considered. A user may figure out how to do something in a way that is better and faster than what you would have built. Good. They are the domain experts of their own job. I try to make things that help keep them sane while doing it.