03

Chapter 1.2: War Room

The first rule of a production incident was simple.

Nobody joined on time. Some arrived because Microsoft Teams had actually notified them, some arrived because Priya had called them directly, and some arrived because another engineer had texted, "Check Teams. Everything's on fire."

And a surprising number appeared five minutes late, breathless, apologising to people who hadn't even noticed they were missing.

The participant counter climbed steadily.

24 participants.

It would reach thirty-two before midnight.

Aditya joined with his camera off, not because he disliked cameras. Because nobody wanted to watch an engineering manager wearing an old black T-shirt with Ctrl + Z Is My Spirit Animal printed across the front while recovering from dinner.

He switched his microphone on.

"I'm here."

Before anyone acknowledged him, another voice cut across the bridge.

"Excellent."

Rocky Bhatia.

"Our Engineering Manager has joined."

Aditya resisted the urge to sigh. Rocky always spoke as though narrating a documentary.

Everything sounded important, even attendance.

"Let's remain solution-oriented, everyone."

There it was; Priya's prediction had taken exactly six seconds to come true.


Rocky occupied the largest tile on the screen.

Not because Teams had pinned him, but because he'd pinned himself.

His camera angle was immaculate, eye level, perfect lighting, bookshelves behind him and Company awards carefully visible. A framed certificate reading Leadership Excellence 2024 occupied just enough of the background to appear accidental.

Nothing in Rocky's frame happened by chance. Even his polo shirt carried the Solstice logo, neatly embroidered over the pocket. He looked like the corporate brochure had learned to breathe.

At forty-five, Rocky genuinely believed in organisations, not cynically, not politically coz he simply trusted the process. If there was a checklist, he followed it, and if there was a dashboard, he believed it. If an AI-generated deployment score said Low Risk, then somewhere, somehow, reality had obviously misunderstood the spreadsheet.

People often mistook him for arrogant. Aditya knew better than to think Rocky was arrogant; he was sincere. That made him infinitely harder to argue with.


"Aditya."

Rocky nodded.

"Quick status."

Aditya opened the dashboard.

"EU Returns API is returning HTTP 500 for new return requests."

"Since?"

"Approximately eleven minutes."

"Customer impact?"

"Still calculating."

Before Rocky could ask another question, another voice answered.

"Twenty-eight thousand failed requests."

Everyone turned toward the speaker.

Priya Anand.


Unlike Rocky, Priya had clearly made no effort to look professional. Her camera framed the corner of a small apartment dining room. An oversized IIT Bombay hoodie hung loosely from her shoulders. Her dark hair was tied into a hurried bun using what looked suspiciously like a pencil. Behind her, a pressure cooker rested on the kitchen counter. Beside her laptop sat half a masala dosa wrapped in foil and beside that a coffee mug.

The coffee inside had almost certainly achieved room temperature hours ago. She never remembered to finish coffee; she merely forgot it more slowly than everyone else.

Her mechanical keyboard clattered through the microphone with enough force that newcomers often assumed construction work was happening nearby.

It wasn't; that was simply how Priya typed.

Fast…violently.

As though every bug had personally insulted her family. She was, in Aditya's opinion, the finest engineer at Solstice Systems. She would also have been the worst possible politician.

Diplomacy required pretending nonsense deserved consideration. Priya had never acquired that skill.


"Twenty-eight thousand?"

Rocky frowned.

"Confirmed?"

Priya didn't even look up.

"Twenty-eight thousand three hundred and twelve."

Pause.

"Now fourteen."

Another pause.

"...Fifteen."

Her fingers never stopped moving.

"The dashboard refreshes every five seconds."

Rocky cleared his throat.

"Right."

"Let's avoid quoting live numbers unless…"

"They're accurate?"

Priya asked pleasantly in a dangerous tone.

Aditya recognised it immediately, and he knew Priya only became this polite when someone was about to regret speaking.

Rocky smiled.

"I'm simply saying we should communicate verified metrics."

"I did."

Another burst of keyboard clicks.

"They're now twenty-eight thousand five hundred."

Silence.

Aditya quietly muted himself before anyone heard him laugh.


A timid voice interrupted.

"Sorry..."

Everyone looked toward a young engineer wearing enormous headphones.

Dev Solanki.

Six months into his first job, still apologised before asking questions, thanked people for reviewing pull requests and believed managers knew what they were doing.

The industry hadn't corrected that assumption yet.

"I..."

Dev swallowed.

"I think the deployment package I approved might be involved."

Nobody spoke.

The silence grew heavier.

"I mean..."

he continued quickly,

"...only if I missed something during validation..."

"I could have…"

"Dev...", Aditya interrupted gently. The young engineer froze.

"Take a breath."

"...Sorry."

"You don't need to apologise."

"I just..."

"I know."

Aditya smiled reassuringly.

"We're investigating."

"If the deployment caused it, we'll find out."

"If it didn't..."

He shrugged.

"We'll still find out."

Around the call, several experienced engineers exchanged knowing glances. That was classic Aditya; nobody left one of his incidents feeling abandoned. No matter how messy the night became.

Dev visibly relaxed.

"...Okay."

"Thanks."

Priya smiled without looking away from her monitor. That tiny exchange explained why half the graduate engineers requested transfers onto Aditya's team whenever internal openings appeared.

He taught people; he didn't interrogate them.


Another participant joined.

Rahul Mehta – Release Management

Rahul always looked like he'd sprinted into every meeting; tonight was no exception.

Tie loosened, his laptop balanced precariously on one arm, and two mobile phones were visible beside him.

"I've informed Change Management,"

He announced before anyone asked.

"The CAB wants an estimated restoration time."

Nobody answered, and Rahul looked around awkwardly.

"So..."

"Any ETA?"

Twenty-seven engineers simultaneously avoided eye contact.

Every incident featured one impossible question; tonight...it had arrived early.

Priya finally looked up. "We don't know what's broken."

Rahul nodded.

"Right."

"So..."

"Approximate ETA?"

This time even Rocky closed his eyes briefly.


Aditya leaned back in his chair and let his gaze drift across the gallery view. The organisation chart insisted they belonged to different business units, different reporting managers and different cost centres. Reality had never cared much for organisation charts. This was his team not because Solstice Systems said so, but because years of midnight deployments, impossible deadlines and production fires had quietly erased those boundaries.

They were scattered across Mumbai, Pune, Bengaluru, Hyderabad and Chennai, each sitting in a different apartment, speaking different languages at home and carrying lives that rarely overlapped beyond office hours. Yet, somehow, the moment production stumbled, geography stopped mattering. Within minutes, they appeared on the bridge, some still in office clothes, others in faded college T-shirts, someone balancing a dinner plate beside the keyboard, another apologising for a barking dog in the background. One engineer had muted a crying toddler before returning to discuss log files as if nothing had happened.

The complaints always came later. They would grumble about management, threaten to resign after every appraisal cycle and mock the latest corporate buzzwords with almost religious consistency. Tomorrow, they would argue over sprint velocity, story points and release timelines. Tonight, none of that mattered. A production incident had a way of stripping away hierarchy, politics and titles until only one question remained: How do we fix this? And somehow, every single one of them always showed up to answer it.

Aditya had often thought there was something quietly beautiful about that.

Most people would never see this side of software engineering. They saw the failed payment, the crashed website or the delayed order. They rarely thought about the thirty engineers who sacrificed their sleep so those problems disappeared before breakfast. The profession was at its best when nobody noticed it at all.

Perhaps that was the strange bargain every engineer unknowingly accepted. If they did their job perfectly, millions of people would wake up the next morning believing nothing had gone wrong.


Priya's fingers, which had been flying across the keyboard since the call began, suddenly stopped. That, more than anything else, caught Aditya's attention.

She stared at the Kibana logs, her brow knitting together. Without saying a word, she enlarged the window and leaned closer to the screen. A few seconds passed before a quiet, almost absent-minded, "Huh," escaped her.

"What?" Aditya asked.

She didn't answer immediately. Her eyes remained fixed on the scrolling logs as if they were trying to tell her something they hadn't yet put into words.

"I don't like this."

"What don't you like?"

She zoomed in further, studying the stack traces line by line. "The errors," she said finally. "They're... too consistent."

The conversation on the bridge faded almost instinctively. Engineers who had been discussing deployment timelines and rollback strategies fell silent and turned their attention to Priya's screen. Years of working together had taught them one simple rule: when Priya said she didn't like something, it was worth paying attention.

Before she could explain what she had noticed, the participant count in the corner of the Teams window ticked up once more.

31 participants.

A new name appeared at the bottom of the gallery.

Kavya D. (Guest).

No department, no employee ID, no profile picture, just a single initial and the word Guest.

For a heartbeat, nobody spoke. Rocky frowned at the unfamiliar name. "I don't believe we've met."

A camera flickered to life in the corner of the screen.

The image sharpened slowly, not into another apartment or a carefully arranged home office, but into the softly lit reception lobby of Solstice Systems. A woman sat alone in one of the grey visitor chairs, a charcoal laptop resting across her knees. Behind her, Mahadev, the night security guard, glanced up from his phone. The moment he realised the camera was live, he straightened instinctively and adopted the expression of a man who had definitely not been scrolling through cricket highlights thirty seconds earlier.

The woman looked up. Her gaze settled on the gallery view, then stopped on Aditya.

It wasn't a searching glance, nor the polite acknowledgement of someone joining a meeting late. It carried the quiet certainty of someone who had finally found the person she'd been waiting for. For reasons Aditya could neither explain nor dismiss, the feeling was unsettlingly mutual.

Write a comment ...

Sachchin Annam

Show your support

As a writer, my goal is to create stories that resonate with narratives rooted in everyday realities, emotions, and moments people often overlook. I want readers to see a reflection of themselves in my characters, to feel understood, and to take something meaningful away from each story, it can be a thought, a lesson, or simply a feeling that lingers. Writing, for me, is not just about storytelling; it’s about connection, finding an audience that feels, reflects, and grows along with the words.

Write a comment ...