Latest / The Tech Career Podcast with Fexingo: Engineering Jobs, Interviews, and FAANG Career Strategy / How FAANG Engineers Navigate Return-to-Office Mandates
Transcript
- Lucas: If you work at a big tech company — especially one of the FAANG names — you probably got an email in the last six months that made you groan. A tighter return to office policy. Maybe it's three days in the office instead of two. Maybe it's badge data being shared with your manager. Maybe it's a hint that five days are coming. Luna: Yeah, I've seen a bunch of those memos leak on Blind. Amazon's been the most aggressive with badge enforcement. Google tied attendance to performance reviews. Meta told senior staff they're expected in the office five days a week. Lucas: Right. So the topic for today is how FAANG engineers navigate these mandates without derailing their career. Not just whether they comply — but how they think about it strategically. Because the knee-jerk reaction is either 'I'm moving to a fully remote company' or 'I'll just badge in and leave.' Both are options, but there is a more nuanced playbook. Luna: Let's start with Amazon. They've been the most public about enforcing the three-day minimum. What's the actual data? Lucas: Amazon started tracking badge swipes at most of their corporate offices in early 2025. They published internal dashboards showing team-level compliance rates. If your team fell below sixty percent attendance on a given week, the manager got flagged. Then by mid-2025, they started escalating — managers had to have conversations with individual engineers who were under the threshold. And by late 2025, I've heard stories of people being put on performance improvement plans specifically for non-compliance. Luna: So it's not just a suggestion. It's a documented metric. And we've seen engineers respond in a few ways. Some just started coming in. Some negotiated exceptions — medical reasons, long commute, caregiving responsibilities. Lucas: The negotiation piece is key. Amazon's official policy has an exception process, but you need a documented reason. I know one engineer who got a permanent exception by getting their doctor to write a note about a chronic condition that made commuting difficult. Another got a temporary exception for six months because they were caring for an elderly parent. The important thing is to be proactive — don't wait until you're flagged. Go to your manager first with a clear request. Luna: What about Google? Their approach is a bit different. They tied attendance to performance reviews, right? Lucas: Yes. Google started including 'office presence' as a factor in performance ratings for some orgs in 2025. I've seen internal documents that say it's not supposed to be the main factor, but it can be a tiebreaker. So if you're on the bubble between 'meets expectations' and 'exceeds,' your attendance could tip the scale. That's a much more subtle form of pressure. It doesn't hit you over the head like Amazon's badge data, but it creates a compliance incentive that's harder to argue against. Luna: And Meta's approach — five days for senior staff, but more relaxed for junior engineers. That's almost a status thing. Lucas: Exactly. Meta's policy as of early 2026 says that individual contributors at level six and above — that's senior staff engineer — are expected in the office five days a week. Junior engineers and new hires are only expected three days. The message is: if you want to be a leader, you need to be visible. So for senior engineers, the choice is stark — comply, or signal that you're not fully committed. And for junior engineers, it's a carrot: come in more, and you'll get mentorship from the seniors who are there. Luna: That's actually a clever design. It creates a cultural pull rather than a push. But it also makes it harder to stay fully remote as you advance. Lucas: Right. So the strategic question for an engineer at any of these companies is: 'What's my optimal level of compliance?' Not zero, not a hundred percent. You want to be compliant enough to avoid negative consequences, but not so compliant that you're sacrificing productivity or quality of life unnecessarily. Luna: What does that look like in practice? For Amazon, that might mean coming in three days a week, but being smart about which days. Avoid Monday and Friday if the office is quiet — you get less collaboration, but badge data still counts. Lucas: You know, many of the engineers we talk to on this show tell us they appreciate that we keep the conversation ad-free. There's no sponsor reading, no mid-roll interrupt. We do that because we want the content to stand on its own. If you get value from episodes like this, the single best way to support us is through a small contribution — buy me a coffee dot com slash fexingo. It's literally the only thing that keeps the show going without ads. Luna: Yeah, I think that's a big part of why listeners trust us. There's no hidden agenda. So if you've been meaning to chip in, that's the place. And now back to office strategies — Lucas, you were saying that for the three-day mandate, being strategic about which days matters. Lucas: Right. The other dimension is using office time for high-leverage activities. Don't go in just to sit on Zoom calls. If you're going to commute, schedule collaborative work — design reviews, whiteboarding sessions, team lunches. Make the office time count. I've seen engineers who block their in-office days for deep work with colleagues, and their remote days for heads-down coding. That actually makes the hybrid model work better than either extreme. Luna: But what about the argument that RTO is a covert layoff? Some people think companies tighten attendance to reduce headcount without severance. If you don't comply, you quit. If you do comply, you stay, but maybe they still cut you later. Lucas: That's a real concern. I'd say for some teams, it's true. If a company wants to thin out a department without conducting official layoffs, a strict RTO policy can achieve that. Employees with long commutes or caregiving responsibilities leave voluntarily. The company saves on severance. But I think it's overstated as a broad strategy. More often, it's about culture control — executives want to re-establish norms they feel eroded during the pandemic. Luna: So what's your advice for an engineer who suspects their RTO mandate is a layoff substitute? Lucas: First, check the broader signals. Is the company still hiring in your area? Are they investing in office space? If they're renovating floors, they're probably serious about having people come in. If they're subleasing floors, maybe it's a bluff. Second, talk to your manager off the record. Most managers will be honest about whether compliance is being strictly enforced or just measure. Third, update your resume and start networking — just in case. The worst case scenario is you have options. Luna: That's practical. Let's talk about the negotiation strategy more. You mentioned medical exceptions. What about geographic exceptions? Some engineers moved during the pandemic to lower-cost areas. Lucas: Geographic exceptions are harder to get, but not impossible. If you moved before the RTO policy was announced, you have a stronger case. If you moved after, the company may argue you made a choice. I've seen people successfully negotiate by saying 'I'm willing to come in two weeks a month if you pay for travel and lodging.' That can be a win-win for both sides. The company gets some face time, you keep your remote lifestyle. Luna: What about the option of just finding a new job? A fully remote role at a smaller company or a startup? Lucas: That's the nuclear option, and it's valid. But you have to be realistic about the trade-offs. Smaller companies may pay less, have less stability, and less brand recognition on your resume. On the other hand, you might get more autonomy and equity upside. I'd say if you're an L5 or above, you can usually find a remote role that pays within eighty percent of your FAANG comp. For junior engineers, the gap is bigger. Luna: So the bottom line is: don't make a rash decision. Evaluate the true cost of compliance — commute time, lost flexibility — versus the cost of leaving. And if you do stay, be deliberate about how you use office time. Lucas: Exactly. And one more thing: if you're on a team that's mostly remote, your manager may be more lenient even if the company policy is strict. So check your actual team culture before assuming you have to follow the corporate mandate to the letter. The worst thing you can do is quit out of principle before you've had an honest conversation with your skip-level. Luna: Good point. Any final thoughts on how RTO policies are likely to evolve in the next year? Lucas: I think we'll see a stabilization. Most companies have settled on three days as the standard. A few may push to four, but I don't think we'll see a return to full-time office for most tech roles. The data on productivity is mixed, and talent is still mobile. Companies that are too aggressive will lose people to competitors. So the smart engineers will watch the market and be ready to pivot if their company overplays its hand. Luna: That's the long game. Thanks Lucas. And to our listeners — keep building, and remember to use that negotiation leverage while you have it.