ArcFlow
Company
Managed Services
Markets
  • News
  • LOG IN
  • GET STARTED

OZ brings Visual Intelligence to physical venues, a managed edge layer that lets real-world environments see, understand, and act in real time.

Talk to us

ArcFlow

  • World Models
  • Sensors

Managed Services

  • OZ VI Venue 1
  • Case Studies

Markets

  • Sports
  • Broadcasting
  • Robotics

Company

  • About
  • Technology
  • Careers
  • Contact

Ready to see it live?

Talk to the OZ team about deploying at your venues, from a single pilot match to a full regional rollout.

Schedule a deployment review

© 2026 OZ. All rights reserved.

LinkedIn
  1. Home
  2. Blog
  3. Why Clarity Matters More Than Any Technical Credential

Why Clarity Matters More Than Any Technical Credential

Article December 14, 2025

Share this post

One candidate speaks for ten minutes before arriving at a conclusion. The other states a position in thirty seconds, then backs it with evidence. Both are senior engineers. Both have built real systems. Both can talk about distributed computing, edge inference, and real-time pipelines. Only one gets an offer, and Jagruti Patil, OZ's Head of People Operations, can usually tell which within the first few minutes. The difference is not technical skill. It is what she calls clarity: the ability to think in structure, communicate with precision, and tell a story that does not make the listener do the assembly work. In an everything-as-code organization where every playbook, zone map, and deployment checklist is a structured specification, an unclear thinker doesn't just interview poorly; they write ambiguous specs that become production failures.

The Question Behind the Question#

"When I ask a candidate to explain their most important project," Jagruti says, "I am not testing their memory. I am watching how they think. Do they start with the problem they solved, or do they start with the technology they used? Do they explain why their approach was right, or do they list features? Do they tell me a story I can follow, or do they give me a list I have to assemble myself?"

This is the clarity test. It is not written down on a scorecard. It is not a rubric with numbered criteria. It is a pattern that Jagruti has learned to recognize, and its absence is the single most common reason strong candidates do not advance.

"Clarity is not about speaking perfect English or using big words. Some of our best engineers speak three languages and English is their third. Clarity is about structure. Can you state what you believe, and then explain why you believe it? Can you describe a complex system in a way that someone outside your domain can follow? That is what I am looking for."

Clarity of Thought#

The first dimension is how a candidate thinks.

"I ask a question," Jagruti says. "A good candidate answers the question. A great candidate pauses, thinks, and then gives me an answer that shows they understood not just the question but the reason I asked it. They answer with confidence. They support their answer with reasoning. And their reasoning is easy to follow, not because they simplified it, but because they thought about it clearly before they spoke."

She contrasts this with the pattern she sees most often in experienced engineers. "A senior engineer with ten years of experience sometimes gives me ten minutes of context before arriving at a conclusion. They aren't unclear; they are thorough. But thoroughness without structure is not clarity. If I cannot identify your conclusion within the first thirty seconds, you have not been clear. You have been comprehensive. Those are different things."

At OZ, where every system is defined as a specification before it is built, unclear thinking creates unclear specifications. Unclear specifications create systems that almost work. Almost is not good enough when the system runs at a live venue with an audience watching.

"Our entire engineering culture runs on specifications," Jagruti explains. "A playbook is a specification. A zone map is a specification. A deployment checklist is a specification. If the person writing the specification cannot think clearly, the specification is ambiguous. And ambiguous specifications produce ambiguous results. So when I hire, I am not just hiring someone who can build. I am hiring someone who can think clearly enough to define what should be built."

Clarity of Communication#

The second dimension is how a candidate expresses their thoughts.

"There is a technique I learned early in my career," Jagruti says. "Before you answer a question, imagine you have to write your answer on a single page. First sentence: your conclusion. Next few sentences: your supporting reasons, each backed by a specific example or fact. Last sentence: what this means for the decision at hand. If you can do that out loud, in conversation, you are a clear communicator."

This is not a test of public speaking skill. It is a test of organized thinking expressed verbally. Some candidates speak slowly and deliberately. Some speak quickly with energy. Both can be clear. What matters is structure: conclusion first, then evidence.

"In a distributed team that works across time zones, clarity of communication is not a nice thing to have," she says. "It is essential. When an engineer on one continent writes a specification that a colleague on another will implement, the words on the page are the only channel. There is no hallway conversation to fill in the gaps. There is no whiteboard session to clarify the ambiguity. The specification must be complete. And a specification is only as complete as the communication skills of the person who wrote it."

She pauses, then adds something she considers important.

"This matters even more now. We work with AI agents every day. An agent follows instructions literally. If your prompt is vague, the output is vague. If your specification is ambiguous, the agent builds something ambiguous. The humans who get the most from AI tools are the ones who communicate with the most precision. Clarity of communication is not just a human-to-human skill anymore. It is a human-to-system skill. And in an everything-as-code culture, it is the foundational skill."

In an everything-as-code culture (where playbooks, zone maps, deployment checklists, and production rules are all defined as structured specifications) clarity of communication isn't a soft skill. It is the skill that determines whether the system works correctly. Every ambiguous sentence in a specification becomes a potential failure in production.

Clarity of Story#

The third dimension is the one that surprises candidates.

"At the end of a full day of interviews," Jagruti says, "I ask myself one question about each person I met: what is their story? Not their resume. Their story. Who are they? What drives them? Why do they want to be here? And most importantly, did they make that story clear to me, or do I have to guess?"

A candidate who interviews well leaves a clear picture. Not because they rehearsed a pitch, but because they know who they are and what they want, and they communicated both without making the interviewer work to piece it together.

"Some people arrive at an interview and answer each question in isolation," she says. "Each answer is fine. But there is no thread connecting them. At the end, I have twenty separate answers and no story. Other people arrive and every answer builds on the last. By the end, I know exactly who they are, what they care about, and why they would be the right person for this role. That is clarity of story."

This is not about performance or personality type. Introverts tell clear stories. Extroverts tell clear stories. The distinction is whether the candidate has thought about their own narrative before the conversation, or whether they are constructing it on the spot.

"I tell candidates this directly: think about your story before you walk in. Not a script. A thread. What connects your career decisions? What pattern runs through the work you have chosen? When you know your own thread, every answer you give will feel connected. And when your answers feel connected, the interviewer remembers you."

Jagruti Patil

Jagruti Patil

Head of People Operations

People & Talent Growth

“Clarity is not about speaking perfect English or using big words. It is about structure. Can you state what you believe, and then explain why?”

The Solution Finder#

There is one more quality that the clarity test reveals, and Jagruti considers it the most important.

"Every organization has problems," she says. "Every system has gaps. Every process has friction. The question is not whether a candidate can identify problems. Anyone can identify problems. The question is whether they are the kind of person who walks toward solutions."

She describes the distinction as a state of mind, not a skill. "When I describe a challenge that OZ faces (a deployment bottleneck, a scaling constraint, a workflow that needs improvement) I watch the candidate's reaction. Some people immediately start listing obstacles. 'That will be hard because of X. You should worry about Y. Have you considered the risk of Z?' They are not wrong. But they are problem-finders. Their instinct is to map the difficulty."

"Other people hear the same challenge and their first response is: 'Have you tried this approach?' Or: 'What if you structured it this way?' Or simply: 'I would start here.' They are solution-finders. Their instinct is to move toward an answer. They acknowledge the difficulty, but they do not stop there. They keep going until they reach a path forward."

She is careful to distinguish this from recklessness. "A solution-finder is not someone who ignores problems. They see the problems clearly; that is the clarity of thought I described earlier. But they do not stop at seeing. They use what they see to find a way through. That is a different mode of thinking. And it is the mode we need."

"We are a small team building infrastructure that operates at live venues in multiple countries. Every week brings something new. If a person's response to every new challenge is a list of reasons it will be difficult, the team slows down. If their response is a proposed path forward (even an imperfect one) the team accelerates. The solution-finder creates momentum. And momentum, in a company at our stage, is everything."

Energy#

There is a quality that Jagruti talks about last, because it is the hardest to define and the easiest to recognize.

"Some people create energy," she says. "When they join a meeting, the room moves faster. When they send a message, it creates action. When they present an idea, other people want to build on it. They are not loud. They are not performing. They just have a quality (I call it spark) that makes the people around them more productive."

"And some people absorb energy. They are competent. They are reliable. But every interaction with them takes more energy than it gives. The meeting runs longer. The decision takes more rounds. The project moves a little slower because the human friction is a little higher."

In a small team producing outsized output, energy is not a personality trait. It is a multiplier. One person who creates energy amplifies the entire team. One person who absorbs it drags the entire team.

"This is not about being an extrovert," Jagruti clarifies. "Some of the highest-energy people I know are quiet. They create energy through the quality of their work, the speed of their decisions, and the clarity of their communication. Energy is not volume. Energy is forward motion."

She ties it back to the clarity test. "People who think clearly communicate clearly. People who communicate clearly create alignment quickly. People who create alignment quickly create energy. Clarity and energy are connected. The person who creates the most clarity almost always creates the most energy. That is why I test for clarity first. Energy follows."

What Looking Back Reveals#

At the end of a hiring cycle, Jagruti does a review. Not of the process, but of the people.

"I look at everyone we interviewed. I ask: who created clarity? Who left me with a clear picture of who they are, what they think, and why they belong here? That person always stands out. Not because they were the most experienced. Not because they had the best credentials. Because they were clear."

"In a world where AI agents can write code, debug systems, and execute complex workflows, the human qualities that matter most are the ones that agents cannot replicate. The ability to think through an ambiguous problem and arrive at a clear position. The ability to communicate that position in a way that aligns a team. The ability to tell a story that gives people a reason to follow. The ability to create energy that moves a project forward."

"Those are the qualities I test for. Those are the qualities that predict success at OZ. And those are the qualities that I believe will define the best talent in every organization, not just ours, for the decade ahead."


This interview is part of the OZ Interview Series, profiling the team building the world model for the physical world.

All InterviewsAll with JagrutiLearn more about OZ