Five years into intentional remote-first engineering (2021-2026), I want to share what I’m seeing from the mobile engineering trenches at Uber. We’ve gone from emergency remote to strategic remote, and the landscape has changed dramatically.
What’s Working in 2026
1. Async-First By Default
The best remote engineering teams are async-first by design. Communication that doesn’t require both parties to be available at the same time. This is table stakes now, not innovative.
Tools: Notion for docs, Linear for tasks, Loom for walkthroughs, Slack with clear norms.
2. AI Pair Programming
GitHub Copilot, Cursor, and similar tools are normalized. Junior engineers can be productive much faster. The productivity gains are real - I estimate 20-30% for routine coding tasks.
3. Global Talent Access
At Uber mobile, we’ve built teams across 15 countries. We can hire the best mobile engineers regardless of location. This would have been impossible in 2019.
4. Outcome Metrics
Activity monitoring is mostly dead at tech companies. We measure what ships, not how many commits. This is healthier for everyone.
5. Virtual HQ Tools
Spatial audio, virtual offices for ambient connection. Still early, but better than 2021’s flat Zoom grid.
What’s Still Broken in 2026
1. Tool Fragmentation
The average team uses 15+ tools. The cognitive overhead is real. We spend too much time context switching between Slack, Notion, Linear, GitHub, Figma, Zoom, etc.
2. Time Zone Exhaustion
Global teams still struggle with overlap. Someone is always working outside their prime hours. We try to rotate the burden, but it’s still hard.
3. Junior Engineer Growth
This is THE unsolved problem. It’s harder to learn by osmosis remotely. Junior engineers miss the informal learning that happens in offices. We’re trying structured mentorship, but it’s not the same.
4. Innovation Collaboration
Breakthrough ideas still seem to happen better in-person. The random hallway conversation that sparks something new - we haven’t replicated that remotely.
5. Culture Drift at Scale
Companies over 500 people struggle with remote culture. The sense of “we’re all in this together” fragments. Every team develops its own subculture.
Emerging Trends I’m Watching
1. Hybrid 2.0
Not “Tuesdays and Thursdays in office.” Instead: Quarterly in-person intensives. Teams get together for a week, do deep collaboration, then return to distributed async work.
2. Regional Hubs
Small offices for social connection, not work. Places where people can grab coffee, but the actual work happens remotely.
3. Async Video
Loom-style communication replacing some Slack. More thoughtful than text, less intrusive than meetings.
4. AI Meeting Summaries
Finally useful. Reduces FOMO for people who couldn’t attend. Makes async participation viable.
5. VR Collaboration (Maybe)
Early but promising for design reviews and spatial work. Still too clunky for daily use, but improving.
The Trade-Offs Crystallizing
Speed vs Inclusion: Fast decisions exclude time zones. Inclusive decisions take longer.
Flexibility vs Alignment: Too much autonomy creates fragmentation. Too much structure kills flexibility.
Cost vs Culture: Remote saves money but costs culture investment. You can’t cheap out on in-person time.
Growth vs Mentorship: Scale globally but junior growth suffers. Haven’t solved this trade-off yet.
My Prediction for 2027
The future is “remote-first with intentional in-person.”
Specifically:
- Daily work is async by default
- Weekly team syncs for connection and complex discussions
- Quarterly in-person gatherings for strategy, brainstorming, and culture
- Annual company-wide events for alignment
Companies that try to be fully remote OR fully in-person will struggle. The hybrid model that works is temporal (mostly remote, occasionally together) not spatial (some days in office).
Mobile Engineering Specific Insights
What works for mobile:
- Async code reviews are actually better (more thoughtful feedback)
- Loom demos of UI changes beat static screenshots
- TestFlight/Firebase dashboards give shared visibility
- Release coordination is possible with good handoffs
What’s hard for mobile:
- Real-time debugging sessions across time zones
- App Store emergencies at 3am
- Coordinating iOS + Android + Backend releases
- Teaching mobile architecture patterns remotely
My Biggest Open Question
How do we solve junior engineer growth remotely?
Structured mentorship helps. Pairing helps. Documentation helps. But there’s still something missing. The informal learning that happens when you overhear a senior engineer thinking through a problem, or you watch someone debug a tricky issue.
If we don’t solve this, we’ll create a two-tier system: senior engineers who learned in offices and can work remotely, and junior engineers who struggle to level up.
I don’t have the answer yet. But it’s the most important problem to solve for remote engineering’s future.
What are you seeing in 2026? What’s your prediction for 2027?