Six Months at Tencent: Big Company, Startup Heart

Six months ago I walked out of campus with a diploma; these days I badge into an office with a Tencent logo on the door. The transition from "incoming engineer" to "actual engineer" happened faster than I could overthink it—which, knowing myself, was probably for the best.

Now that the first stretch is behind me, here's an honest field report from inside the machine. The short version: almost nothing matches what I imagined, and most of the mismatch is good news.

The Atmosphere Is the Real Deal

Let's start with the thing I was most skeptical about. Every company claims to have a great culture; it's the corporate equivalent of "funny and easygoing" on a dating profile. So I arrived with my expectations pre-lowered.

I was wrong, happily. The atmosphere on our team is genuinely warm. People are patient with the new hire's questions—including, and I say this with gratitude, the questions I was embarrassed to ask. There's an inclusiveness to how the team operates: ideas get heard before they get ranked by who said them, and nobody performs seniority at you. Meetings end with someone asking, sincerely, whether anyone disagrees.

I expected to spend my first months learning the org chart. Instead I spent them learning the codebase, and being treated like I already belonged to it.

Less Process Than the Brochure Promised

Here's the confession: I had braced myself for Big Company Process™. Approval chains for everything. A ticket to get a ticket. Six weeks to provision a server.

Reality: our team runs like a startup that happens to have a very large parent. We move fast, we own things end to end, and the gap between "we should try this" and "it's running" is often measured in hours. When I needed to experiment on a GPU server, the onboarding process was essentially: here's the IP, here are your credentials, ssh in as root, don't break anything important, go build.

Root access. Directly. No bastion ballet, no three-layer permission request.

My security-trained reflexes briefly screamed into the void—and then I got to work. There is something deeply clarifying about being trusted with the keys: it makes you careful in a way that a permission slip never does. With great sudo comes great responsibility, and also great nvidia-smi.

To be fair, this cuts both ways. A startup-shaped team inside a big company means fewer guardrails and fewer ready-made answers. The polished internal platform you'd expect sometimes doesn't exist yet—because you're the platform team. Which brings me to the best part.

Zero to One Is a Teacher With No Syllabus

Much of what I'm doing is zero-to-one work: systems that didn't exist before we decided they should. Nobody hands you the architecture; you go find it. Nobody has written the doc; you become the doc.

This is a very different education from graduate school. Research teaches you to go deep on a defined problem until the reviewers are satisfied. Zero-to-one engineering teaches you to define the problem in the first place, to make thirty small decisions a day with incomplete information, and to live with the ones you got wrong long enough to fix them properly. The learning curve is steep enough that some weeks feel vertical. But the compounding is real: things that terrified me in July are Tuesday-afternoon tasks now.

If recruitment season was the crucible that got me here, this is the forge that decides what I'm actually made of.

The Remote-First Team (And the Monthly Pilgrimage)

Here's the twist in my setup: my entire team is based in Chengdu. All of them. I am the only satellite, orbiting from another city, living my work life inside a grid of video-call windows.

Day to day, it works better than I feared. Async habits, written updates, cameras mostly on. But text and tiles can only carry so much, which is why once a month I pack a bag and fly to Chengdu for a few days of being a physical person.

These trips have become my favorite part of the job. There's the work side—whiteboards instead of screen shares, conversations that happen at walking speed, the kind of quick alignment that takes ten minutes in person and two days over chat. And then there's the other side: milk tea runs at 2 PM; fun board games after dinner; discovering that the colleague whose avatar I've stared at for weeks is funnier in three dimensions.

Each trip compresses a month's worth of context and camaraderie into a few days, and then I fly home with a notebook full of decisions. It's a strange rhythm—remote by default, together by appointment—but it has made me unusually deliberate about communication. When you can't tap someone on the shoulder, you learn to write clearly. When you only see your team twelve times a year, you don't waste the twelfth.

What I Know Now That I Didn't in April

Five months is nothing, and I say that with humility—I am still the person most likely to ask where anything is. But a few things have already settled into conviction:

• Trust scales better than process. Being trusted with root access, real ownership, and real deadlines made me more careful and more productive than any approval chain could have.
• Zero-to-one is a privilege. Most engineers spend years maintaining other people's decisions. Getting to make my own—and defend them—this early is an education money can't shortcut.
• Culture isn't the poster in the lobby. It's whether your questions get real answers at 6 PM on a Friday. So far, they do.
• Distance is a constraint, not an excuse. Remote work punishes sloppy communication and rewards good writing. Conveniently, I have a blog for that.

In my 2025 recap, I wrote that the jump from the lab to Tencent would be the steepest learning curve of my life, and that I was bringing my co-pilot with me. Five months in: the curve is real, the co-pilot is earning its seat, and the view from the climb is better than advertised.

More dispatches as the altitude increases.