Neurodivergent Interviewing: I vs. We, When “I” Feels Dishonest

An early-career story, and an honest way to tell it in an interview

I’ve spent 20 years learning to lead. A big part of that was learning to talk about the team. “We” hit the goal. I helped get us there. I trained myself to talk that way on purpose, because that’s what good leaders do.

Then I walk into an interview, and every “we” costs me a point. After two decades of giving credit away, I’m suddenly expected to speak a whole new vocabulary.

It’s harder than it sounds. I’m hard of hearing and have ADHD, and like a lot of neurodivergent people, I’m a facts person. If other people helped, “I did it” feels dishonest. So I say “we,” and I lose the point anyway.

Why I picked this story

It’s not the biggest program I’ve run. Years later I’d lead a CI/CD rollout across 22 Scrum teams and chair an architecture review board. But this is the project that took me from tech support into program management, and it’s the one I’ve always struggled to tell without either taking too much credit or hiding behind “we.”

How it started

Around 2011, I was a remote Technical Support Engineer at EMC. Customers kept telling us our case updates were hard to follow, and that it wasn’t clear where each case stood.

Part of the problem was the system itself. Every team managed its own update templates in our Oracle case management system, and they’d grown to well over 1,000. The interface couldn’t be changed. Engineers had to remember to set several fields and flags by hand on every update, which was clunky and easy to get wrong.

I had a habit of trying to fix our internal processes, and it got me invited to a Lean Six Sigma Kaizen event on customer communication. I was there to represent the support engineer’s view. I was one of only two support engineers in the room. Most people there had about 10 more years of experience than me, plus organizational leaders and program managers.

SET came out of that event, and our manager, MaryAlice, came up with it. I can’t take credit for SET itself. My part was making it real across a global organization that was known for resisting change. Some colleagues told me building a tool was a waste of time and I should just work my cases.

What SET is

SET stands for Summary, Evidence, Timetable. Every case update followed the same three parts:

  • Summary: a short explanation of the issue
  • Evidence: errors, logs, and what was found
  • Timetable: the action plan and next steps

It worked because anyone reading a case could jump straight to the part they needed. An escalation manager could check the Timetable to see if the case was current. An engineer joining the case could read the Summary and Evidence.

What I built

My colleague Adam had built a small tool for our front-line intake team. I partnered with him, then took it over and made it my own.

I used AutoHotkey, a macro and automation program, to prototype an app that ran on every support engineer’s computer. It gave engineers SET as a simple 3-field form, so the design itself showed them how to use it. When they hit submit, it filled in the case and set all the right fields and flags automatically. The complexity stayed behind the scenes. It also had a timer for logging time on a case and an auto-update feature.

I had it track usage too, so we could see which templates were used most and when. That told us whether the program was working, and it meant we weren’t deleting templates blindly.

Then I worked with each product group on what SET could replace and what had to stay. Hardware dispatches needed their own variations so the case system could send the right parts to the field. Support limited to US citizens needed its own handling too.

I demoed it early and often, took feedback, and kept iterating. Adoption had to come from the bottom up (engineers) and the top down (leadership), not just town halls and an executive sponsor. I ran training in the US and Ireland and delivered about 50 presentations around the world: town halls, technical summits, roundtables, and executive briefings.

Who else made it happen

  • MaryAlice, our manager, came up with SET.
  • Adam built the original tool.
  • Courtney handled logistics so I could stay on the critical path, and she crunched the numbers, including the adoption figure.
  • Judy, our executive sponsor, fought hard for a global change that surely ruffled some feathers.
  • Brendan laid the groundwork for the online support app I later moved off the old Oracle system.

The results

  • 69% training adoption in the first 30 days after launch
  • 85% of remote customer service engineers coached to compliance within 2 months
  • Effective communication rating at a historic high of 80% in Q4 2011, up 5%, from customer survey data
  • About 1,000 case templates audited and consolidated down to about 25
  • A random inspection process as the quality check on case notes
  • The EMC GTS SCP 2011 Audit Report named the SET practice a “Demonstrated Area of Excellence”
  • The EMC Lean Six Sigma Cup in 2013

A gain like that usually took a year or more and several projects. This did it in one, and it made a bigger dent in global customer support than any project before it.

What it led to

The tool became the main driver for automating a lot of support tasks, and other parts of the company copied it. SET became the foundation for handing off cases, whether to the back line, the next shift or region, or another product group.

It also became the cornerstone of EMC’s new web-based support platform, support.emc.com, which replaced the old Oracle interface we couldn’t change. I became that platform’s Product Owner and Technical Program Manager. That’s where my career in program management started.

Two answers

So how do I tell all of that in an interview?

The “we” answer: “We built a case-notes tool and won the Six Sigma Cup.”

The honest answer: “Our manager came up with SET at a Kaizen event I was invited to as a support engineer. A colleague had built a small tool, and I took it over. I turned SET into a simple form that set every case field automatically, tracked which templates got used, worked with each product group, and ran the training in the US and Ireland. A teammate handled logistics and the numbers, and our executive sponsor fought for the change. We hit 69% adoption in 30 days and a record 80% communication rating, and it won the Lean Six Sigma Cup.”

The first is true but empty. The second is just as true, and the interviewer knows exactly what I did.

Why “I” feels dishonest

When your brain is wired for accuracy, “I” can feel like overclaiming. You remember who did what. Leaving them out feels like rewriting history.

Hearing loss adds a layer for me. For years, I wasn’t fully sure I’d caught everything said in a meeting. When you live with that doubt, you get careful about claiming things. “We” felt safer.

And after 20 years of leading teams, my vocabulary is built around “we” on purpose. None of this means my contribution was small. I put in the hours and was critical to the outcome. I just never learned to say so in a room built to hear “I.”

The simple version

Nobody builds a perfect answer on the spot. Interviews are already high pressure, and for neurodivergent candidates there’s more to juggle in real time. You need something simple enough to remember when your mind goes blank:

“It started with ___. My part was ___. I had help from ___.”

Filled in: “It started with a Kaizen event and our manager’s SET idea. My part was building it into a tool every engineer used, cutting about 1,000 templates to 25, and training engineers in two countries. I had help from a teammate on logistics and the numbers, and an executive sponsor who fought for the change.”

Where it came from, what you did, who helped. You stay honest, and the interviewer hears your part.

A practice drill

  1. Pick the story you tell most often.
  2. Write the three lines: where it started, your part, who helped.
  3. Say it out loud until it feels natural.
  4. Do the same for three or four more stories.

Writing it down first helps if you’re a facts person. Once it’s on paper, saying “I” is just reading the record.

Phrases to try

Instead ofTry
“We came up with the idea.”“My manager came up with the idea. I turned it into a working tool.”
“We cleaned up the templates.”“I tracked which templates got used and worked with each product group on what to keep.”
“We trained everyone.”“I ran the training sessions in the US and Ireland.”
“We hit 69% adoption.”“We hit 69% adoption in 30 days. A teammate tracked the numbers, and I drove the training.”

This isn’t only on the candidate

Candidates can practice, but interviewers carry part of this too. Many very capable people, especially good leaders, will struggle with “I” vs. “we” in real time, and that struggle says nothing about the work they did.

  • Ask the follow-up. If someone keeps saying “we,” ask “What was your part?” Many will tell you exactly. They just won’t volunteer it.
  • Judge the answer, not the pronouns. A precise “we” with clear ownership is a good answer.
  • Share themes ahead of time. Telling candidates the topics you’ll cover lets them prepare real examples instead of building them under pressure.

Balance cuts both ways. Candidates can learn a simple way to own their part. Interviewers can make room for people who give credit by instinct.


I write about interviewing and working in tech with a hidden disability. If this helped, connect with me on LinkedIn.

The Interview Doesn’t End When the Call Does

My last post was about a small moment that turns out to be a big one. The interviewer asks, “Do you have any questions for us?” and you answer, “No, I think you covered everything.”

I expected a few people to relate. Instead, dozens of you wrote back with your own version of it. You did the research, listened closely, and had every question answered before the call ended. Then you were marked down for having nothing left to ask.

One reply stayed with me more than the rest, because the story didn’t end in the interview. It ended in an inbox.

Two follow-ups, two outcomes

A candidate (I’ll keep him anonymous) had a first-round interview, then got an email from the employer. It included this line: “You didn’t have any questions for me either, which in a field this strong did make the difference.”

So he replied in writing, and his reply was honest. He explained that it wasn’t arrogance or disinterest. The interviewer had already described their vision for the team, which would have been his only real question. In his words:

“I’d rather be honest and say I don’t have questions than ask the generic ‘what’s your favourite thing about the role’ just for the sake of asking. Again, I am neurodivergent, so I can’t always just think up stuff on the spot in the heat of the moment.”

He also pointed out that it had been billed as a first-stage, informal chat, so he wasn’t expecting to be asked for questions at the end. Then he made a clear case for why he wanted the job.

That was August. He never got a reply.

Now the other side. I once interviewed for EMC’s product lifecycle team, the group that oversaw the lifecycle, quality, and development of EMC’s flagship products. After the interview, I sent the hiring manager a 30-60-90 day plan showing how I’d spend my first three months. I got the job, and I later found out that plan was what sealed it. Then Dell bought EMC in the biggest tech merger ever at the time, and that same team rewrote the product lifecycle for the combined company. I helped create it and train both companies on it.

We both followed up in writing and got opposite results. The difference was on the other end: whether someone treated the follow-up as part of the interview.

Why the follow-up matters more for neurodivergent candidates

Interviews reward speed. You get a question, you’re expected to have a polished answer in seconds, and you’re expected to close with a smart question of your own.

That’s not how a lot of us think. I’m hard of hearing and I have ADHD. After any meeting, I replay it for hours, sometimes days. That’s when the dots connect. I spot the gaps, come up with the questions I wish I’d asked, and often sketch out a whole solution. Many neurodivergent people describe the same thing.

So the moment an interview ends is often the moment our best thinking starts. The follow-up is where that thinking finally gets to show up. Writing gives us time to process, organize, and say exactly what we mean.

One commenter on my last post put it well: asking a question just to have one feels insincere, and saying no is not a lack of interest. The real questions usually come later.

An interview is really just a glorified meeting. In the actual job, nobody expects you to solve everything in the room. They expect you to follow through.

What a strong follow-up looks like

Here’s a simple structure that works:

  1. Thank them for something specific. Skip the generic “thanks for your time” and name one thing they said that stuck with you.
  2. Answer better. If there’s a question you’d answer differently now, give the short, clear version.
  3. Ask the real question. The one you thought of on the drive home is often your best one.
  4. Say why you want the role, in a sentence or two.
  5. If you’re near the final round, add a 30-60-90 day plan.

The plan doesn’t need to be fancy. One page is enough:

  • First 30 days, learn: who you’d meet, what you’d read, and what you’d want to understand first.
  • Days 31 to 60, contribute: where you’d start adding value, based on what they told you.
  • Days 61 to 90, lead: one or two outcomes you’d aim to own.

A plan like this shows how you think, how you plan, and that you were listening. No single interview answer can show all three.

For hiring teams

If you’re hiring, three small changes go a long way:

  • Tell candidates that follow-ups count. Say it at the end of the interview. It costs nothing and takes the pressure off the closing question.
  • Read them before you decide. If the decision is already made by the time the email arrives, you’re judging people on speed instead of substance.
  • Reply, even with a no. Candidates remember the silence.

And don’t be shy. If a follow-up raises something interesting, ask more questions and dig into the answers. You may find out who is truly skilled at the work, at communicating, and at collaborating, and not just good at telling a story on the spot.

The fair counterpoint

Some interviewers will say a candidate with no questions just wasn’t engaged. And it’s true that asking about something covered fifteen minutes earlier can look like you weren’t listening. A few people raised exactly that in the comments.

That’s the trap. If the closing question can count against you either way, the follow-up is the better place for the real questions, the ones that only show up after you’ve had time to think.

The bottom line

You’re hiring someone to do the job. Treat the interview like the job and not an improv session. If you want to know who truly cares about the role and is still thinking about it, look at the follow-up.

And if you’re the candidate, send it.

The Most Respectful Answer in the Room

“Do you have any questions for us?”

“No, I think you covered everything.”

If you’ve interviewed for anything, you’ve probably been on one side of that exchange. Maybe you said it and then replayed it on the drive home, wondering if it cost you. Maybe you heard it and quietly marked the candidate down.

Every few weeks I see the same advice from hiring managers on LinkedIn: “no questions” is a red flag. A good question shows how you think. No question leaves them guessing.

I understand where that comes from. I also think it can punish some of the most prepared people in the room, and I want to explain why from where I sit.

Where I’m coming from

I’ve been hard of hearing since birth, and I have ADHD. For a long time I saw both as negatives. Interviews are still the hardest part of my job search. More than once I’ve logged off a call knowing I could do the job and hadn’t shown it.

But the same two things made me good at my work. In nearly 19 years at EMC and Dell, much of it in program management, my hearing pushed me toward habits I still rely on. I write everything down. I confirm decisions in writing. I run meetings with a clear agenda, and I make sure nobody leaves with a different version of the plan.

Put simply, I’ve trained my whole career to make other people’s time count. That matters for what happens at the end of an interview.

What “no questions” can actually mean

Experienced candidates do their homework. Before a final round, I’ve read the job description several times, looked up the team, read what the company has published, and sometimes talked with someone who works there. I walk in with a list.

Then a good interview answers most of it. By the time they ask if I have questions, my list is crossed off.

Now I have to choose. I can ask something I already know the answer to, so the box gets checked. Or I can be honest and say they covered it.

The first option feels wrong to me. It asks two busy people to spend time on something neither of us needs. If I did that in a meeting at work, I’d be wasting the room’s time. In an interview, it’s somehow expected.

The same moment through a different lens

Now picture a candidate who’s autistic. For many autistic people, asking a question you already know the answer to feels like acting. It can feel dishonest, and like a real waste of everyone’s time. They may be the most direct and prepared person you talk to all week, and this one ritual marks them down for exactly that.

Senior people often land in the same place for different reasons. After enough years, you know how most companies work. The questions that would have mattered early in a career got answered long ago.

None of these candidates lack curiosity. Their curiosity got answered early, through preparation and through the interview itself. Scoring them down for it means scoring them down for a strength.

For candidates who feel this way

You don’t have to fake a question. A few honest options:

  • Name what they covered. “You answered most of what I came with, especially how the team plans releases.” It shows you were listening, which is what the question is really testing.
  • Keep one question that’s always useful. Mine is “Is there anything in my background you’d like me to clear up?” I genuinely don’t know the answer, it works no matter what the interview covered, and it brings any doubts into the open while I can still address them.
  • Ask to follow up in writing. “If something comes to me tonight, is it okay if I email you?” Many of us think better after the call ends. Then actually send it.

For interviewers

The idea behind the question is good. You want to know how someone thinks and whether they care about the role. You can get there without the ritual.

  • Weigh the whole hour. If someone showed real depth for 45 minutes and their track record backs it up, one closing answer shouldn’t undo that.
  • Ask one more of your own. If “no questions” bothers you, try “What stood out to you from your research on us?” You’ll get the curiosity you were looking for.
  • Invite written follow-up. Tell candidates they’re welcome to email questions later. You’ll often get better ones.

Ask yourself who a rule like this screens out. Often it’s the people who prepared the hardest, or the ones whose brains work a little differently from yours.

Why I’m writing about this

More and more, I see my hearing and my ADHD as the reason I work the way I do. The habits that make me say “no questions” at the end of an interview are the same ones that make me good at the job.

If you’ve ever walked out of an interview wondering whether your honesty cost you, I’d like to hear about it. And if you hire, I’d like to hear how you handle those last two minutes.

If you missed it, last week I wrote about the gap between a strong resume and a rough interview.

Sean Feeney is a disability advocate and program leader who spent nearly 19 years at EMC and Dell, where he led a CI/CD transformation across 22 Scrum teams and ran the Architecture Review Board for Dell NativeEdge. He has been hard of hearing since birth and is neurodivergent.

The Interview Gap: What Hiring Misses About Hidden Disabilities

I get interviews. That part of my job search works. After nearly 19 years at EMC and Dell, leading a CI/CD transformation across 22 Scrum teams and running the Architecture Review Board for Dell NativeEdge, my resume opens doors at companies I’d be proud to work for.

Then I get on a Zoom call, and things get harder.

I’ve been hard of hearing since birth, and I have ADHD. Both are invisible until they aren’t. I want to write about the gap between a strong resume and a rough interview, because I don’t think hiring teams see it, and I don’t think enough of us talk about it.

What a video interview actually asks of me

From the outside, an interview looks simple. One person asks questions and the other answers. For me it’s several jobs at once.

I’m listening through compressed audio and filling in words I didn’t quite catch from context. I’m holding the question in my head while I pick which story fits. I’m watching the clock. And with ADHD, working memory is the first thing to go when I’m nervous, so a detail I knew cold an hour ago can disappear mid-sentence.

When the audio drops, someone turns away from the mic, or two people talk at once on a panel, I lose the thread. Then I have a choice. I can ask them to repeat the question, which feels fine once and awkward the third time. Or I can guess at what they meant, and sometimes answer a question nobody asked.

Either way, the interviewer leaves with an impression. It doesn’t always match the person on the resume, and they don’t know why.

Why the gap closes once I’m on the job

Here’s the part that frustrates me most. Almost none of this is a problem at work.

At work there’s a meeting recap, a Slack thread, a Jira ticket. If I miss something, I follow up an hour later and nobody thinks twice. Over the years I’ve built habits around my hearing. I write everything down, I confirm decisions in writing, and I make sure nobody leaves a meeting with a different version of the plan. Those habits made me good at program management. They’re a big reason the processes I built held up after I handed them off.

The interview format strips all of that away. No follow-up, no notes, no second pass. It tests the exact conditions where I’m weakest and skips the ones where I’m strongest.

The disclosure question

Every candidate with a hidden disability runs the same calculation. Do I mention it?

If I don’t, I risk being judged on a performance that doesn’t reflect me. If I do, I risk it sounding like an excuse, or someone quietly deciding I’ll be “a lot of work.” Neither feels safe, and a lot of people default to silence.

I’ve landed somewhere in the middle. Disclosure is a choice I make company by company, and I’ve found a couple of ways to bring it up that feel normal instead of apologetic.

The first is the accommodation request, sent when the interview gets scheduled. It’s short and practical:

“I’m hard of hearing, so a video call with live captions turned on would work much better for me than a phone call. Could we set it up that way?”

If I’d rather not name it, there’s a version that skips the reason:

“Could we do this as a video call with captions on, and could questions also be typed in the chat? That helps me give you better answers.”

The second is how I talk about it in the room, if I choose to. I frame it as where my strengths come from, instead of something I’m working “despite”:

“I’ve been hard of hearing since birth, and it’s made me very deliberate. I write things down, I confirm decisions, and I make sure nobody leaves a meeting with a different version of the plan. That habit is a big part of why the things I built actually stuck.”

That tells them something true about how I work, and it gives them a reason to remember me.

What’s helped me as a candidate

  • Captions, every time. Zoom, Teams, and Google Meet all have them built in. Windows 11 also has system-wide Live Captions (Win + Ctrl + L) that work with any app.
  • Scripting the edges. I prepare my intro, my close, and lines for the hard moments, like “I want to make sure I answer the right question. Could you say that one more time?” Only the middle gets improvised.
  • Headline first. I put the answer in my first sentence, then the story. If I wander, the point already landed.
  • Asking what’s unclear. Near the end I ask, “Is there anything in my background you’d like me to clear up?” It brings doubts into the room while I can still address them.
  • The same-day follow-up. If an answer didn’t land, I fix it in the thank-you email. That’s the version of me they’d actually be hiring.
  • Warm introductions. Referrals get me into one-on-one conversations with people who already know my work, and that’s the format where I do best.

What hiring teams can do

None of these cost much, and they help every candidate.

  1. Turn on captions by default. Don’t wait for someone to ask. Asking is the hard part.
  2. Share the topics ahead of time. You’ll get better answers from everyone.
  3. Type key questions in the chat, especially the multi-part ones.
  4. Choose one-on-ones over big panels when you can. Crosstalk is brutal when you can’t hear well.
  5. Let candidates follow up in writing, and read what they send. Most real work happens in writing anyway.
  6. Weigh references from people who watched someone work. A former VP who saw two years of delivery knows more than one hour on Zoom can show.
  7. Train interviewers on what a disclosure means. It’s information. Treat it that way.

The Job Accommodation Network has free guidance on interview accommodations for employers and candidates.

Why I’m writing this

Being hard of hearing has shaped my career and my confidence in ways most of my coworkers never saw. I’m done staying quiet about it. Disability advocacy needs more voices from people who are in the middle of it right now, and I’d like to be one of them.

If you’re a candidate dealing with this, you’re not imagining the gap. If you’re a hiring manager, keep the bar where it is. Just make sure your interview is measuring what the job needs.

I’d love to hear what’s worked for you, on either side of the table.

Are Personal LLMs Becoming the New Resume?

I have been thinking about a question that feels slightly uncomfortable, mostly because it might be true.

Are we approaching an age where someone’s value in the job market is less about raw experience, and more about the quality and effectiveness of their personal large language models (LLMs)?

Not “who uses artificial intelligence,” because at this point, that is like asking who uses search or spreadsheets.

I mean this instead: who has built a personal system that reliably turns messy inputs into clear outputs, faster decisions, better communication, and fewer dropped balls?

Experience still matters, but the leverage is changing

Experience used to be a strong proxy for a few things:

  • Pattern recognition
  • Knowing what questions to ask
  • Knowing what good looks like
  • Communicating clearly when things get chaotic

Now we have tools that can supply patterns instantly, draft strong first passes, and help structure thinking.

And the data is starting to show meaningful productivity gains when people use these tools well. In controlled studies, access to generative artificial intelligence has improved speed and quality on certain professional writing tasks. In real workplace settings, generative assistants have shown measurable output gains, with the biggest lift often showing up for less experienced workers (because the tool helps them “close the gap” faster).

But there is a catch that most headlines gloss over.

The tool alone is not the advantage. The system around it is.

Even at Davos this month, one theme was blunt: companies do not get value from artificial intelligence unless they redesign work and invest in training.

That maps to what I see personally. The people getting the most out of LLMs are not the ones who found the cleverest prompt on social media.

They are the ones who treat it like an operating system.

A personal LLM is not a chatbot. It is a workflow.

When I say “personal LLM,” I mean something more specific than “I ask ChatGPT questions.”

I mean a setup that is:

  • Tuned to how you think
  • Organized by context (so it does not turn into one giant junk drawer)
  • Consistent in output format (so you can reuse results, not rewrite them)
  • Guardrailed (so it does not confidently make things up and send you on a goose chase)

If you do this well, you get a multiplier effect on your actual experience.

You still need judgment. You still need domain knowledge. You still need taste.

But your throughput goes up, and your cognitive load goes down.

That is a real advantage in a world where the work never stops piling up.

What I do (practical strategies that actually stick)

I am going to keep this concrete. Here are a few habits that have made the biggest difference for me.

1) One project per reality

I separate my LLM work by context. Work projects, career projects, personal projects. If it has different rules, different output needs, or different “what good looks like,” it gets its own space.

This prevents context bleed, and it helps the model stay consistent. It also makes it easier for me to find things later, which is half the battle.

2) I start each project with a “contract”

At the top of a project, I write a short set of rules like I am onboarding a new teammate:

  • What I care about (speed, accuracy, tone, depth)
  • What to avoid (fluff, invented details, vague advice)
  • The format I want back (headings, bullets, action items)

This one step is boring, but it pays off every single time.

3) I force structured outputs

If I want a meeting summary, I do not ask, “Summarize this.”

I ask for the exact structure I need, every time. Example:

  • Summary (5 bullets max)
  • Decisions
  • Risks and open questions
  • Action items (owner, due date in mm/dd/yyyy, no weekend dates)

When the output is predictable, I move faster. I can paste it into an email, a document, a tracker, or a status update without reformatting everything.

4) I explicitly separate facts from assumptions

I regularly ask for two sections:

  • What you know (based on what I provided)
  • What you are assuming (and how to verify it)

This is a guardrail against confident nonsense, and it trains me to keep a healthy skepticism.

5) I use the model to reduce switching costs

I treat it like a “translator” between modes:

  • Brain dump → clean plan.
  • Chaos → crisp status update
  • Long thread → short executive summary
  • Vague idea → testable hypothesis + next step

Most knowledge work is not hard because the tasks are impossible.

It is hard because we constantly pay the mental tax of switching contexts and formats.

6) I keep reusable templates

This is the part that feels like cheating, but it is just process.

I keep a small set of prompts I reuse, like:

  • “Turn this into a one-page plan with risks and dependencies.”
  • “Rewrite this for a director-level audience, no extra words.”
  • “Give me three options, recommend one, and tell me what you would do first.”

The goal is consistency, not creativity.

Why this is showing up in the job market

Hiring is a pattern-matching game.

If two candidates have similar experience, the tie-breaker is often:

  • Communication quality
  • Speed to clarity
  • Ability to operate across ambiguity
  • Evidence of strong systems thinking

A well-built personal LLM workflow amplifies all of those.

It also creates a new kind of “proof of capability.” Not a certification. Not a buzzword.

A repeatable way of working.

And yes, hiring is being reshaped by automation too. The tools evaluating candidates are changing, and that raises fairness and transparency questions that we are going to have to deal with in the open.

The part we need to be honest about

There are real risks here:

  • Privacy and confidentiality (do not paste sensitive data into tools that are not approved for it)
  • Hallucinations (the model can be wrong with confidence)
  • Overreliance (you still need to think)
  • Inequality of access (not everyone has the same tools, time, or support)

So my take is not “personal LLMs replace experience.”

My take is simpler:

We are moving into a world where experience is the foundation, and your personal LLM workflow is the leverage.

The new baseline skill: building your own leverage

If you are early in your career, this can be a rocket booster. If you are senior, it can keep you from drowning in meetings and context switching.

Either way, the advantage is not the model.

It is how you set it up, how you guide it, and how you validate it.

If you are a hiring manager, you might start asking candidates a new question:

“Show me how you work with an LLM, and how you keep it reliable.”

If you are a candidate, you might want to treat your personal LLM like a professional toolchain, not a toy.

Because the job market is already rewarding people who can turn tools into systems.

Question for you: what is one workflow you would immediately improve if you had a reliable personal LLM setup?