[Gardner Analytics Office (Expanded) — March 2015, 9:00 AM]
The second floor smelled like fresh paint and old sandwiches. Manny had finalized the lease three weeks ago — the entire building now belonged to Gardner Analytics, top to bottom, except for the ground-floor sandwich shop that Manny refused to sell because "the pastrami was here before the computers and will be here after." The expansion had tripled their space to forty-two hundred square feet across two levels, connected by a staircase that the construction team had installed through a hole in the floor that Sarah supervised with the exacting attention she normally reserved for training infrastructure.
The second floor held the new hires. Fifteen desks in the first week. Twenty by the end of the second. The hiring sprint that James Wright's board had demanded six months ago was finally happening at a pace that satisfied investors and terrified Sarah.
"Candidate twelve," Sarah said, dropping a résumé on Ethan's desk. They'd developed a rhythm: Sarah screened on paper, Ethan screened in person, Priya handled the technical deep-dive. Twenty interviews per week. Three per day minimum, scheduled in forty-five-minute blocks that left Ethan with exactly enough time between sessions to eat half a sandwich and check the GPT-2 preliminary training metrics on his laptop.
Candidate twelve was a Berkeley PhD with a specialization in natural language processing. Published in ACL and EMNLP. Three years at a major tech company whose name Ethan recognized from the show but whose relevance to his timeline he could no longer predict with any confidence. Talent Resonance: 7.0. Clean signal. Strong in theoretical foundations, modest in practical implementation. The profile of someone who could contribute to research but would need guidance on production engineering.
"Hire," Ethan said. "Research team. Priya supervises."
Sarah made a note. "That's seven this week. Twelve this month. We're at forty-seven. Three more to hit fifty by Friday."
"Who's next?"
"Stanford postdoc. Distributed systems. Sarah-recommended."
"Your recommendation or a different Sarah?"
"My recommendation." She didn't smile, but the air around the sentence carried the particular dryness she reserved for moments where her professionalism absorbed a joke without acknowledging it. "He rates well on paper. You'll tell me the number."
The number. The thing they didn't name. The system they'd built around a supernatural ability that Sarah had documented through twelve months of observation without ever confronting directly. Ethan rated people. The ratings were consistently accurate. The mechanism was unexplained. Sarah had stopped asking how and started using the output, which was either pragmatism or trust or some hybrid of both that didn't have a word in any language she spoke.
The Stanford postdoc arrived at eleven. Tall, quiet, the particular energy of an academic who'd been working on distributed computing problems that nobody outside his research group understood. Ethan's Talent Resonance activated during the handshake: 7.5. Strong. Genuinely strong. The kind of engineer who understood how systems broke at scale because he'd built systems that broke at scale and fixed them without complaining.
"Hire," Ethan told Sarah. "Infrastructure team. Marcus supervises."
By Friday, the team was fifty. The milestone felt different from thirty-five — not just larger but structurally altered. At thirty-five, Ethan knew everyone's name, their project, their daily coffee order. At fifty, faces blurred. Names required effort. The new hires on the second floor were competent strangers — people he'd assessed with Talent Resonance and approved with a word, but whose personalities, ambitions, and anxieties existed outside his awareness.
Middle management had materialized without anyone formally creating it. Sarah ran engineering operations through three team leads she'd promoted from the original hires. Priya managed research through two senior researchers she'd recruited from academia. Marcus handled infrastructure with a growing team of systems engineers who spoke his language of uptime guarantees and failover protocols. Diana's sales team had expanded to four people who spent their days calling enterprise clients and their evenings updating a CRM that Marcus had built because the commercial options were "insufficiently paranoid about data security."
Ethan's role had changed. Not gradually — abruptly, the way a river changes when it hits a waterfall. He'd gone from writing code daily to reviewing code weekly. From designing architecture to approving architecture. From the person who built the thing to the person who decided what thing to build. CEO. The title he'd inherited from a dead man's business cards, now carrying the weight that the title was supposed to carry.
The Breville machine — Sarah's "most important infrastructure investment" — had been supplemented by a commercial espresso system on the second floor, because fifty people consuming coffee at engineering-standard rates required industrial capacity. The new machine produced adequate espresso that nobody praised and everyone consumed, which was the operational definition of successful infrastructure.
A new hire — a junior engineer named Kai, three days into the job, rated 6.5, assigned to the API team — stopped Ethan in the stairwell between floors.
"Excuse me. Do you know where the supply closet is? I need a whiteboard marker."
Ethan directed him. Kai thanked him and continued upstairs. Sarah, who'd been descending behind Ethan, waited until Kai was out of earshot.
"He doesn't know who you are."
"He just asked me for a whiteboard marker."
"He asked a random person in the stairwell for a whiteboard marker. Your own employee doesn't recognize his CEO." The observation was delivered without judgment — Sarah's voice carried the diagnostic flatness of an engineer reporting a system metric. But underneath, something shifted. A recognition that the company had grown past the point where the founder was the center of gravity, and that the shift was both necessary and sad.
"We should do an all-hands," Ethan said. "Introduce myself to the people who think I'm the whiteboard marker guy."
"I'll schedule it for Monday." Sarah continued down the stairs. Paused. "For the record, you are terrible at being a CEO. You're excellent at being a founder. The difference is that founders build things and CEOs manage people who build things, and you'd rather be building."
"I know."
"Good. Because the GPT-2 training configuration needs your review, and I've been holding it for three days because you've been interviewing instead of engineering."
The callback was precise — the tension between scaling the team and maintaining the technical edge that made the team worth scaling. Every hour spent evaluating candidates was an hour not spent on the architecture. Every hire added capability and diluted focus. The company needed fifty people. The technology needed Ethan's attention. Both demands were legitimate, and neither could wait.
He took the GPT-2 configuration from Sarah's desk and carried it upstairs to his office — the glass-walled room in the corner that had been his since the original office, now surrounded by thirty more desks than it had been designed to overlook. Through the partition, the second floor hummed with the particular energy of people who'd been hired in the last month and were still learning where the bathrooms were.
The configuration file was dense. Forty-eight decoder layers. Sixteen attention heads. Embedding dimension 1600. Vocabulary 100,000 tokens. Training data: two billion tokens, curated from the expanded corpus that Priya's research team had assembled. Estimated training time: five hundred GPU-hours on ChronoCloud's V100-equivalents. Estimated cost: $800,000.
Eight hundred thousand dollars. Thirty percent more than the preliminary estimate, because Priya had recommended additional training epochs to ensure the model reached the scaling thresholds where emergent capabilities appeared. The Phase 1 blueprint in Ethan's mind confirmed her instinct — the specific parameter thresholds were visible in the architectural awareness, the points where the model's behavior would shift from "better" to "qualitatively different."
He approved the configuration. Sent it back to Sarah. Opened the next interview file.
Candidate thirteen. The day continued.
Author's Note / Promotion: Your Reviews and Power Stones are the best way to show support. They help me know what you're enjoying and bring in new readers! You don't have to. Get instant access to more content by supporting me on Patreon. I have three options so you can pick how far ahead you want to be: 🪙 Silver Tier ($6): Read 10 chapters ahead of the public site. 👑 Gold Tier ($9): Get 15-20 chapters ahead of the public site. 💎 Platinum Tier ($15): The ultimate experience. Get new chapters the second I finish them . No waiting for weekly drops, just pure, instant access. Your support helps me write more . 👉 Find it all at patreon.com/fanficwriter1