The Rise of ADHD-Type Talent in the AI Era

Fast context-switching juniors now outshine deep specialists, while AI-written eighteen-page requirement documents drown the seniors who must verify them.

Share
The Rise of ADHD-Type Talent in the AI Era

Every company runs at a different AI temperature

The surprising part: everyone at the table works at a household-name tech company, and yet the temperature differs this much from company to company.

Company A rolled Claude out company-wide and actively encourages it, wired into the messenger, the issue tracker, and the wiki, with other AI tools open as well, while Company B bans Claude and allows only one specific coding tool. People know that attaching AI to the messenger is a new world, but the company blocks it, so they cannot even have the experience. Content and creative teams resist adoption outright, which complicates things further.

The internal gap is extreme too. A colleague from the next team quietly asked what AI they should use, and it turned out they were only using a chatbot. With almost no internal training, everyone learns alone, so the usage gap between employees is enormous; the higher the title, the more likely someone still works by hand. The best users are too busy with their own work to teach, and their know-how is personal, so it does not spread, which means the gap widens instead of closing.

Company C is entirely team by team, where the customer support team adopted well and handles repetitive work efficiently, while the data team still analyzes everything manually on the grounds that internal data is too unstructured for AI. If this is the spread inside the tech industry, what does the rest look like? And is this temperature gap quietly becoming the future competitiveness gap?

The biggest hurdle is time

The most common line of the night: we know AI is good, but really using it takes three or four hours of deep focus, and that time does not exist.

At Company A, meetings run wall to wall from morning to evening, so the FOMO is huge but there is physically no time to dig in. Meanwhile executives post daily in the leadership channel about how many lines of code they wrote with AI, and when working-level staff say they have no time, the response is: do you have time at home? Internal lectures keep getting scheduled, and nobody has time to attend them either, a vicious cycle of no trigger, no time, no experience. And yet the gap between those who somehow made the time and those who did not is already enormous.

Walking into work feeling covered

The representative power user was from Company B, using a coding tool almost as a secretary. All work data lives in organized local folders; a scheduled job reports each morning only what needs doing that day. When a meeting ends, the notes summarize themselves, get distributed to owners, and update the wiki, fully automated, and that alone cut the workload sharply.

The operations case was striking too, since entering country-by-country data used to be fully manual. Now AI does it, instructed to mark everything one of three ways: certain, estimated, or blank if unknown, color-coded so reliability is visible at a glance.

When I get to work and the tool is open in the side window, I feel so covered.

Like a trustworthy colleague permanently seated next to you. People said earlier that they cannot use AI for lack of time, but invest the time once to set it up, and time is what you get back.

Revenge of the eighteen-page document

Does everything improve as more people use AI well? Not quite, because at Company A juniors now stamp out product requirement documents with AI, and the volume has ballooned into eighteen-page documents that keep arriving. The problem is the senior who has to review and catch everything is drowning.

AI raised productivity and the verification cost exploded, an irony, and reviews could be answered with AI too, but people have not dug deep enough to get there yet. Building with AI and verifying with AI has arrived, and the seniors caught in the middle are suffering most.

The ideal employee profile is shifting

The most memorable story of the meetup came here, when the person from Company A said their strength had always been deep immersion: pick one thing and dig to the bottom. But the deep part is exactly what AI now does better.

Instead, multitasking juniors who switch contexts quickly are standing out: throw things at AI, judge the results fast, move to the next thing. That does not make depth meaningless; it changes where depth goes. The depth of execution moves to AI; the depth that remains for people is deciding what to do and judging what comes back.

Keep reading


Join Bloom

Bloom builds offline rooms where people and technology meet. We run them in Seoul, and now beyond it.

Read more

석양빛을 받은 샌프란시스코 금문교와 그 너머의 도시

샌프란시스코는 한 번 가 보면 안다

Bloom 행사를 하다 보면 유난히 기억에 남는 분들이 있다. 그런 분들은 내가 따로 커피챗을 요청한다. 그렇게 평일 저녁 삼성동 스타벅스에서 마주 앉게 된 사람이, 토스와 뱅크샐러드에서 시니어 개발자로 일하다 나와 창업한 고의성(Abel Ko) 님과 중학교 때부터 그의 친구로 미술 거래 사업을 하다 합류한 김민성(Mark Kim) 님이다. 둘은 Ironact라는

By Bloom
팀별 커밋 순위와 방금 올라온 커밋이 뜬 LED 아래에서 노트북으로 작업하는 해커톤 참가자들

Ambition for Korea 오픈소스로 공개합니다

Ambition for Korea 해커톤 운영 방식을 GitHub에 오픈소스로 공개합니다. https://github.com/patrickhan-coder/bloom-hackathon-kit 현장에서 “운영이 유니크하고 획기적이다”라는 피드백을 정말 많이 들었습니다. 그런데 저는 사실 해커톤에 한 번도 참가해 본 적이 없습니다. Bloom 행사에서 실습은 많이 했지만, 해커톤이라기보다는 빌더톤에 가까웠죠. 이번엔 본선 8팀 모두에게 팀당 5,

By Bloom