Greg Has Been Here Four Years. He Is Running Everything. Nobody Has Noticed.

Greg Tinsley has been at Lumenwave for four years and seven months. He does not have a standing desk. He has a regular desk — the kind that doesn't adjust — a second monitor, a Hydro Flask he fills at 8:51 AM when he arrives, and a physical notebook he uses for actual notes. Not for the performance of notes. For notes. The notebook is three-quarters full. There is no copy of Atomic Habits anywhere in his workspace.

He is a senior individual contributor on the platform team. He is, formally, two levels below Manager OTG. He is, functionally, the reason anything works.

This is not an unusual situation. This is, in fact, the standard situation.

The pipeline thing

For six months in 2024, the data pipeline feeding Lumenwave's customer dashboards was failing silently — not crashing, not alarming, just quietly returning stale numbers. Support tickets were arriving at a rate that had begun to appear in Dana's Q2 all-hands slides under the heading "Customer Trust Indicators." Dana flagged it. Her VP of Engineering flagged it to Manager OTG. Manager OTG, at 9:04 AM on a Monday, sent a message to the #platform-eng Slack channel: "Let's sync on the pipeline situation this week 🙏."

Greg did not wait for the sync.

By Wednesday at 6:14 PM, the pipeline was fixed. Greg had located the root cause — a bad join in a query written by an engineer who'd left in 2023 — diagnosed the downstream effects, patched the query, and redeployed. He posted a three-paragraph writeup to #platform-eng with a link to the PR. The post had four readers in the first 24 hours. Manager OTG was not one of them.

Two weeks later, in Dana's Q3 all-hands, Dana said: "The team resolved the pipeline issue — really great work, everyone." Manager OTG, in the Slack thread afterward, replied: "Great work everyone 🙌 — really proud of how we came together on this." Greg did not respond to the thread. He was already working on the next thing.

Greg as a service

The way Manager OTG uses Greg's name in external meetings is a specific and observable phenomenon.

He says "Greg is on it." He says "I've got Greg spinning up on that." He says "I'll have Greg take a look." He uses Greg's name the way you use a name you want to be known for knowing — confidently, like citing a reliable source. The effect is that Greg sounds like a service Manager OTG provides to other stakeholders.

None of these conversations include Greg. Greg learns about them afterward: through a calendar invite he wasn't originally copied on, or through a Slack from Priya that says "Hey — just so you know, Mark told the eng sync you're presenting Thursday." Greg replies: "Thanks for the heads-up." He prepares the presentation. He does not use slides. He says what the data shows and then stops talking. The room is briefly confused by the brevity. Then it moves on.

The 1:1 that keeps getting moved

Greg's 1:1 with Manager OTG happens, in theory, every other Wednesday at 11:00 AM.

In practice it has been rescheduled eleven times since February. The original block was March 4th. It moved to March 18th, then April 2nd, then April 9th, then April 30th, then May 14th, then to a date two weeks from now — which Greg does not expect to happen, either. Manager OTG reschedules via calendar drag-and-drop, without a message. The new invite arrives with no note. This is, they have both apparently agreed, the normal way this works.

Greg has not complained about this. He started, instead, keeping his own record: a Notion page called "Greg's Worklog (Q2–Q3 2025)," updated every Friday, shared to the company-wide engineering channel. It lists what he's been working on, what shipped, what's next. Forty-three people have access. Four have opened it. Manager OTG is not one of the four.

When Manager OTG's 360 review came around in November, Greg rated him 3 out of 5 overall. The form had a comments field. Greg left it blank. This was, as gestures go, almost entirely invisible.

Tuesday, 3:17 PM

Manager OTG posts a link to #general. It's a Harvard Business Review article headlined "The Quiet Contributors You Can't Afford to Lose." His caption: "Thinking about this a lot lately 🙏."

Sixteen people react with the 🙏 emoji. Greg reacts with 👍.

Manager OTG does not register the difference.

Greg closes the Slack tab. He has a PR to review, two bugs to triage, and a question from Marcus in his DMs he hasn't gotten to yet. He fills his Hydro Flask. He gets back to it.

At 11:47 PM, a Slack notification arrives from Manager OTG: "Hey Greg — quick question for you when you have a sec."

Greg's Slack is set to Do Not Disturb from 9:00 PM to 8:00 AM.

The notification will be there in the morning. So will everything else.