Latest / The Tech Career Podcast with Fexingo: Engineering Jobs, Interviews, and FAANG Career Strategy / How FAANG Engineers Build a Personal Brand Without Leaving Their Job
Transcript
- Lucas: We've talked a lot on this show about the mechanics of getting promoted inside FAANG — performance reviews, project selection, that kind of thing. But there's a parallel track that a lot of engineers don't take seriously until it's too late, and that's building a personal brand while you're still in the job. Luna: I think some engineers hear 'personal brand' and immediately think influencer, or side hustle, or something that distracts from the day job. But I've seen it pay off in really concrete ways. Lucas: Right. And I want to be specific about what we mean, because this isn't about becoming a social media personality. It's about making sure the people who matter — your skip-level, recruiters at other companies, conference organizers — know what you're capable of, independent of your current job title. Luna: Yeah. There's actually a Netflix engineer — I won't name them because they keep a low profile — who started breaking down streaming algorithms on Twitter maybe four years ago. Nothing flashy, just clear technical threads. They now have around fifty thousand followers, and they've told me it directly led to two job offers they weren't even looking for. Lucas: Fifty thousand is substantial for a niche technical audience. And the interesting part is they did it while staying fully employed at Netflix, which is notoriously protective of its intellectual property. So how do you thread that needle? Let's talk about the guardrails first. Luna: Because the biggest fear is getting in trouble with legal or your manager. Lucas: Exactly. Every FAANG company has a publication review process. At Google, it's called the 'Google-wide external communications policy.' At Meta, you need to submit blog posts to a legal reviewer. But here's the thing — these processes exist to catch trade secrets and forward-looking statements, not to stop you from being a thought leader. If you're writing about patterns you've observed in public codebases or architecture decisions that have been open-sourced, you're usually fine. Luna: What about conference talks? I know some managers discourage it because they see it as time away from coding. Lucas: That's a real dynamic, but the smart play is to make your talk directly relevant to your team's work. Suppose you're an Android engineer at Google working on battery optimization. You pitch a talk at Droidcon about 'Reducing Wakelock Drain in Large-Scale Apps.' Your manager can't easily object because that knowledge helps Google's recruitment brand and your team gets a free external validation of their approach. I've seen engineers get promoted precisely because their conference talk generated recruiting leads. Luna: That's a good point — it reframes personal branding as a form of company marketing. But let's talk about something more internal, because not everyone wants to be public. I know engineers who built a huge reputation just by writing detailed design review comments on internal wikis. Lucas: Yes, internal brand is often overlooked. At Amazon, people call it 'earning a reputation for good judgment.' One engineer I know at AWS started writing weekly 'architecture highlights' emails to their org. Just two paragraphs summarizing a tricky design decision they'd seen that week. Within six months, their director started cc'ing them on cross-team design reviews. Luna: That's a low-effort, high-visibility tactic. And it's completely within your job scope. Lucas: Compare that to the engineer who only communicates through code reviews and Jira comments. Their brand is invisible. When reorgs happen — and they happen every eighteen months at most of these places — invisible engineers get assigned to the least interesting projects. Luna: So personal branding, in that sense, is a hedge against reorgs. And layoffs, frankly. Lucas: Hundred percent. Let's talk about open source as a branding vehicle, because that's the most durable form. When you contribute meaningfully to a project like Kubernetes, PyTorch, or React, your contributions are public forever. Recruiters search for those. But there's a trap: you don't want to compete with your employer. Luna: What does that look like in practice? Lucas: If your company sells a product that directly monetizes your open-source project, you're in conflict. For example, if you work at Databricks and you're the lead contributor to Apache Spark, that's fine because Spark is foundational to Databricks' business. But if you work at Snowflake and you start a competing open-source query engine on the side, that's a problem. The rule of thumb: contribute to projects your company already uses or supports, not projects that could replace your company's product. Luna: That's smart. Another angle I've seen work well is the 'lunch and learn' series. An engineer at Uber started a monthly session called 'Bugs That Cost Us a Million Dollars.' They'd walk through one high-severity incident, what went wrong, and how it was fixed. It became so popular that HR asked to record it for new hire onboarding. Lucas: That's brilliant because it positions the engineer as a subject-matter expert without them having to claim expertise. The stories do the work. And that kind of internal visibility translates directly to promotion packets. When your promo doc says 'gave twelve well-attended tech talks this year,' that's a signal of scope and influence. Luna: But let's address the elephant in the room: some managers see personal branding as a threat. They worry you're building a parachute out of their team. Lucas: And that's a legitimate perception. The way to neutralize it is to make your manager look good. When you write a blog post, thank your team and your manager by name. When you speak at a conference, mention that you learned the techniques from your current project. If your manager sees that your brand reflects well on them, they'll become your biggest advocate. Luna: I've also seen engineers use their brand to get promoted from within. One engineer at Apple used their public technical blog to build such a strong reputation that when a staff-level position opened, the hiring manager had already read their posts. They didn't need to do a cold interview. Lucas: That's the ideal outcome. Let's talk about a concrete plan. I've got a four-step framework for someone who wants to start building a brand in the next ninety days without quitting their job or spending more than two hours a week. Luna: I'm listening. Lucas: Step one: pick one public platform. Don't try to do Twitter, LinkedIn, a blog, and YouTube all at once. Choose LinkedIn if you want recruiters to find you. Choose Twitter if you want peer recognition. Choose a personal blog if you want a permanent portfolio. Step two: publish one piece of technical content every two weeks. It doesn't have to be long. A thousand words on a bug you fixed or a pattern you discovered. Step three: for every piece, tag two people inside your company whose work you respect. That forces visibility. Step four: after six posts, compile them into a short talk proposal for an internal tech forum or a local meetup. Luna: That's really actionable. And the two-hour-a-week commitment is realistic. Lucas: The hardest part is consistency. Most engineers post once, get ten views, and quit. But if you do it for six months, you'll have a body of work that's searchable. And when the next reorg happens or the next layoff rumor circulates, you're not just a name on an org chart. Luna: I want to push back on one thing, though. There's a risk of burnout if you're doing this on top of a demanding FAANG job. How do you prevent that? Lucas: Build it into your learning process. Instead of reading a tech book quietly, write a summary as you go. Instead of debugging a tricky issue silently, write up the root cause analysis. You're already doing the work; the branding is just packaging it. If it feels like a separate chore, you're doing it wrong. Luna: That's a good reframe. So the key is to make it a byproduct of your job, not an addition. Lucas: Exactly. And one last thing: don't be afraid to start small. An engineer at Stripe gained a following just by tweeting one SQL optimization tip every week. By the end of the year, they had a book deal. It doesn't have to be grandiose. Luna: That's the kind of story that makes it feel achievable. Lucas: And speaking of making things achievable, if today's conversation gave you something usable, that's the whole point of what we do here. This show stays ad-free because of listeners who chip in at buy me a coffee dot com slash fexingo. It's a small way to keep these conversations going without commercial breaks. Luna: Yeah, it really does help. And it means we can keep diving into specific, tactical topics like this one. Lucas: So to wrap up: pick your platform, start small, make your manager part of your story, and use the work you're already doing. Your brand is just your reputation made visible. And in an industry where job tenure is shrinking, that visibility matters more than ever. Luna: Great advice. I'm going to go update my LinkedIn. Lucas: And I'll see you next time.