Articulating at a Staff Level
15 November 2026 · career
I spoke with three people — Fuse, who works in Spain, Sifan at LinkedIn, and Jordan from Hartman Clark, for Serta — about my work, and I came away thinking about the gaps in how I speak about it: whether I can explain my work at a staff level, showing my thinking process and how I apply the same knowledge in different places. The first conversation, with Fuse, showed me the clearest gap.
Fuse asked me to explain the entire architecture: what my role and responsibility had been in running the service, and how critical the work was. And I found myself leaning so generalist that I was explaining it in a non-technical way — for a technical opportunity. That is the gap. I have to be able to map non-technical language into something a technical person can understand, and that takes a deeper understanding of the concepts themselves, and real comfort with the mental models I have actually used: my working picture of how a system behaves, built up in design reviews, in mentorship, in the decisions I have made.
The second thing is understanding what the other person understands, and expects, and tuning what I say to that. People can sense when you are not confident. So you have to double down on being comfortable with yourself while you explain. The way to get there, I think, is to be more comfortable with design itself — design considerations — because that, I think, is what we are judged on.
That is what articulating at a staff level means to me. It is showing my thinking process, and my learning process: the technical work I am doing, why I am doing it, where I have seen the same thing before, and writing it down consistently, so the other person can see me applying the same knowledge in different places. I need to understand the levels staff engineers talk at, so I can tune the level of detail up or down based on the response I am getting — go deeper into one concept, or go broader across them. To do that I have to go through the notes I took from those conversations. I don’t think I can skip that.
It also takes real examples. Covering all the services, and the foundational ones, seeing how they differ, questioning and cross-questioning my own understanding — that is critically needed. And then mapping the same concepts into a story from my own experience. What matters is the examples that show how I think. I can’t just say what a system is and stop there. If someone asks what problem I actually solved, I will stumble. That is the fear.
Because when someone asks, “it’s a big issue, what exactly do you do?”, I can talk about it. I can talk about staging transactions, about dynamic routing, about business profiles for tenant association, about adaptive throttling. I can talk about the incremental infrastructure migration we did for Spark, and about invoice generation at scale — doing it with a distributed job, so how many invoices we could generate depended on cost, not on the limits of one machine. All of that is there. What I need is the mindset: that my responsibility is designing and calibrating the direction of the organization, keeping it flexible but steady toward the goal we are reaching. The little details don’t really matter, as long as we meet the end goal.
I can only get into that mindset if I am actually comfortable with the concepts — whether it is AWS services and products, or Databricks, or the mental models I have. I need to drill down into those mental models, and then work backwards from them when I explain.
The third thing is explanations. I am getting hesitant about practicing for interviews, and the only thing I can do is practice out loud. When I was talking, I was lacking words — the technical nuances and terminologies that prove I know. Going through the mental models should help with that, I believe. And I have been reading database documentation, the way they put the technical angles, the way they talk through things. The more I read, the better I get at articulating those same thoughts.
So that is the plan for the next couple of weeks: read things out loud, and practice explaining them out loud — being able to answer the questions that might come, being able to handle the pressure and the hard questions, and being transparent about not having done something, and about how I would react when I don’t know something. But none of that helps unless I am actually comfortable with the concepts when I am under pressure.
Related posts
- 14 Nov 2026 Sell the Outcome, Not the Way to Get It agents
To hear about new posts, follow me on LinkedIn or subscribe to the RSS feed.