Page 43 of Secret Heir For The Billionaire Twin

The difference in him is immediate. His voice gains speed, and the reserve I saw in Manhattan loosens as he describes the work. He talks about testing thresholds, failure points, and the way the team rebuilds a design after discovering where it breaks. There is no performance in it. He is not pretending modesty, and he is not reciting a polished founder’s narrative. He knows the systems because he has lived inside the work.

I glance at my notes, then look back at him.

“If reliability depends on eliminating unpredictable variables,” I say, “aren’t you eventually designing for an environment that doesn’t exist?”

Julian goes still for a fraction of a second.

I continue before I can second-guess the question.

“You can model heat and latency,” I say, “but if the system’s most unstable input is human behavior, then the testing architecture has to account for misuse, not just failure. Otherwise, the more intuitive the product becomes, the less control you have over how people push it.”

His gaze sharpens.

“That’s exactly the problem,” Julian says.

The approval in his voice is restrained, but unmistakable.

“I read the technical filings,” I explain.

“I can tell,” he replies.

Something passes between us, too quick to name and too precise to ignore. I look down at my notebook before it can settle.

For the next half hour, the interview moves easily. Julian answers without retreating into company language, and I find myself asking fewer questions from my prepared list. The conversation becomes more specific, more technical, and more honest than I expected.

When the first segment ends, he stands and gestures toward the glass doors.

“You should see the testing floor,” Julian says.

“It’ll make more sense than listening to me explain it from here.”

“I was hoping you’d say that,” I reply as I gather my notebook.

He glances at me. “Were you?”

“I didn’t come to Boston for the conference room.”

His smile is brief but real.

“No,” Julian says. “I suppose you didn’t.”

We step into the corridor together. He moves faster here than he does in Manhattan, greeting engineers by name and stopping without hesitation when someone asks him a question. His posture is looser, his attention immediate. He belongs in the space in a way that has nothing to do with the name on the building.

I follow him onto the testing floor while he explains the sequence of stations. Several members of the staff give short presentations, and Julian adds context when necessary, never speaking over them or claiming credit for their work. He listens closely, asks direct questions, and occasionally reaches for a component or schematic as though his hands remember the work before his mind catches up.

The tour requires us to move through narrow aisles and around crowded workstations. More than once, Julian steps aside to let me pass, his hand hovering near the small of my back without touching me. The restraint is somehow more noticeable than contact would have been. I focus on the equipment. At least, I try to.

His shoulder brushes mine when we stop beside a display, and the faint trace of his scent returns. I keep my eyes on the screen while one of the engineers explains a testing sequence, though I am acutely aware of Julian standing close enough that the warmth of his body reaches me through my blazer.

“Does that answer your question?” the engineer asks.

“It does,” I say, hoping my voice sounds steadier than I feel.

Julian looks down at me, and his gaze lingers for a moment before he turns back to the display.

Forty-five minutes later, we leave the main floor and enter a smaller conference room near the rear of the facility. The space is less formal than the first, with a round table, four chairs, and a wide window overlooking the courtyard.

Julian closes the door behind us.