YouTube Deep SummaryYouTube Deep Summary

Star Extract content that makes a tangible impact on your life

Video thumbnail

What does it take to work on a platform team as a dev?

The Pragmatic Engineer โ€ข 2025-04-28 โ€ข 1:31 minutes โ€ข YouTube

๐Ÿค– AI-Generated Summary:

What It Takes to Be a Successful Platform Engineer: Insights from an Industry Veteran

Working as an iOS or Android engineer on a platform team is no walk in the park. Itโ€™s a unique role that comes with its own set of challenges and demands a particular mindset. Recently, a seasoned platform engineer shared candid insights about what it truly takes to thrive in such a positionโ€”and why, despite the difficulties, itโ€™s an incredibly rewarding career path.

Why Platform Engineering Is Tough (But Worth It)

The first thing to understand is that platform engineering can be stressful and hard. The engineer humorously admits they stumbled into the role themselves and wonders why anyone would voluntarily choose it. Yet, they also emphasize that given the choice, they wouldnโ€™t want to do anything else.

The core challenge lies in the nature of the work: itโ€™s not just about writing code and moving on. Itโ€™s about owning the long-term health and stability of systems that often live in the codebase for yearsโ€”sometimes five years or more. Unlike feature development, where you ship and move on, platform engineers must "sit in the consequences" of their decisions for a long time.

The Importance of Long-Term Ownership

One of the standout pieces of advice is that aspiring platform engineers need to gain experience working at a tech company for at least a year or two before jumping into platform work. This time allows engineers to see firsthand what happens after they ship a system: assumptions change, requirements evolve, and the job becomes about maintaining and adapting the system over time.

This long-term ownership builds invaluable software design intuition. Platform engineers constantly re-evaluate their assumptions to keep systems running smoothly despite shifting demands. Itโ€™s a mindset that requires patience, resilience, and a willingness to learn from the ongoing impact of your work.

How to Prepare for a Role on a Platform Team

If youโ€™re an engineer looking to move into platform engineering, the advice is clear: take your time and donโ€™t rush into it. Avoid burnout by gradually building the necessary experience and mental models.

One practical tip is to โ€œbefriend your platform team.โ€ If your company has one, engage with them during hackathons, seek mentorship, or collaborate on side projects. These interactions provide insight into the nature of platform work and demonstrate your interest and capability.

Moreover, platform teams highly value strong partnerships with feature teams. Feature engineers who communicate honestly about their real problems become critical allies, helping platform engineers understand where to focus their efforts.

Final Thoughts

Platform engineering isnโ€™t for the faint of heart. It demands a blend of technical skill, long-term thinking, and collaboration. But for those willing to embrace the challenge, it offers a unique opportunity to shape the foundational systems that support entire organizations.

If youโ€™re considering this path, remember: gain solid experience first, nurture relationships with platform engineers, and prepare to own the consequences of your work for years to come. The journey is tough, but the rewardsโ€”both personal and professionalโ€”can be immense.


๐Ÿ“ Transcript (45 entries):

What does it take for an iOS or Android engineer to work at a platform team like this in terms of when you're hiring? What are the traits that you're looking for? My joke answer is that I don't know why someone would choose to do this. I just sort of stumbled into it. It's very stressful and it's very hard. Having said that, I would not choose any other position. I want to talk about what I think is the most important thing for an IC who was trying to have a job on a platform team. You need to sit in the consequences of your decisions. You should try to work at a tech company for a year or two and actually see what happens after you ship a system and then the assumptions change and you have to figure out how to keep this thing going. There are systems that we have, no joke, been in our codebase for 5 years. Most things that I've had to write at Reddit are still in the codebase. I wish they weren't. But you have to understand it. What you get out of that is you get a bunch of software design intuition because you have to re-evaluate your assumptions for an incredibly long time. If you can do that, you're probably ready for platform stuff, but take your time. I don't want to burn you out before you're ready cuz this is hard. I would say that like befriend your platform team is the best way to become a platform engineer someday. If you have a platform team, befriend them during hackathon weeks or do some mentorship and side projects. Almost everyone has done something like that before they end up joining our team. But also we really like having really good partners on the feature teams themselves because they are very honest with us about what their real problems are and they are the best source of that.