New Grad to Principal Engineer (IC8) at Meta (Career Story)

Navigating the path from a new graduate to a Principal Engineer (IC8) at a tech giant like Meta is rarely a linear journey. It requires more than just technical brilliance; it demands a strategic shift in mindset, the ability to manufacture your own luck, and the courage to take calculated risks. In a candid breakdown of his career, Adrian, a Principal Engineer at Meta, details how he evolved from a data scientist with a PhD into a product-focused engineering leader driving experiences for Meta’s smart glasses.

His story offers a masterclass in career agency. From "hacking" A/B testing systems into Instagram before anyone asked for them, to building internal developer tools that revolutionized workflows, Adrian’s trajectory proves that software engineers hold immense power when they choose to wield it effectively.

Key Takeaways

• Agency beats permission: The most significant career jumps often come from identifying a gap and filling it without waiting for a directive, as seen in Adrian’s initiative to bring A/B testing to early Instagram.
• Manage risk through communication: Taking on high-reward, high-risk projects requires explicit alignment with your manager to "carve out" expectations and protect your performance rating.
• Promotion at the top is a consensus game: Unlike early promotions, moving to Principal Engineer (IC8) requires months of pre-socializing your case, building alliances, and ensuring key decision-makers are aligned before the calibration room.
• Generalists thrive in ambiguity: Adopting a "product hybrid" mindset—balancing engineering, data, and product sense—allows you to tackle complex, cross-domain problems that specialists might avoid.
• Relationships maximize luck: Career longevity and opportunities often come from a "surface area of luck" created by simply being a helpful, trustworthy colleague over many years.

The Mindset Shift: Owning the "Software Engineer" Identity

Early in his career, Adrian joined Facebook’s data science team, a group comprised largely of PhDs and statisticians. At the time, he viewed himself strictly as a researcher, hesitating to claim the title of engineer. A pivotal conversation with his manager, Cameron Marlow, changed his trajectory entirely.

"Software engineers have power at this company. You are a software engineer. Don't pigeonhole yourself into a category that is not the most important job at the company."

This realization—that engineering is the lever for product impact—fueled his first major success. While consulting for Instagram shortly after its acquisition, Adrian noticed a critical gap: the team had no infrastructure for measuring impact or running A/B tests. They were flying blind on product changes.

Despite being told that measuring tools were a low priority during a massive infrastructure migration, Adrian demonstrated unusual agency. He didn't wait for a roadmap. He hacked together a solution by routing Instagram log exposures through a custom Facebook API endpoint. He recruited a mobile engineer to help with the client-side code and proved the value of the system with a simple server-side test.

This initiative wasn't just a technical win; it was a career-defining move that secured his promotion to Senior Engineer (IC5). The lesson was clear: don't wait for permission to solve the problems that everyone else is ignoring.

Scaling Impact: Building Tools and Taking Calculated Risks

Moving from Senior to Staff and Senior Staff (IC6/IC7) requires shifting focus from individual contribution to force multiplication. For Adrian, this manifested in the creation of "Bento," a Jupyter notebook platform that streamlined data workflows across Meta.

Identifying Friction

Adrian noticed that data scientists and engineers were wasting massive amounts of time on boilerplate code and environment setup. They were toggling between different frameworks for data pipelining and machine learning, creating a disjointed developer experience. He saw an opportunity to build a unified library that reduced 300 lines of configuration code to 20 lines of defaults.

The "Save the Half" Strategy

Building a new internal platform is risky. If adoption fails, you have little to show for months of work. Adrian mitigated this by having a transparent conversation with his manager. He proposed a "calculated risk" model:

1. He would deviate from his standard team duties for two to three months to build the prototype.
2. If it didn't gain traction by mid-cycle (April), he would pivot back to standard projects to "save the half" and ensure a Meets Expectations rating.
3. If it succeeded, it would become his primary focus.

This approach allowed him to pursue high-variance work without jeopardizing his standing. Bento eventually scaled to become the standard notebook platform for the company, leading to his transition into a Tech Lead Manager (TLM) role.

The Road to Principal: Consensus and Domain Switching

Reaching the Principal Engineer (IC8) level represents a significant leap in scope and political complexity. After a brief departure to attempt a startup and a tenure at Clubhouse, Adrian returned to Meta with a desire to pivot from data infrastructure to consumer hardware, specifically Ray-Ban smart glasses.

The path to IC8 differed significantly from his previous promotions. While his move to Senior Engineer was a pleasant surprise, his Principal promotion was a meticulously engineered campaign.

The "Campaign" for IC8

At the Principal level, technical impact alone is insufficient. You need organizational buy-in. Adrian and his manager treated the promotion as a project with its own roadmap:

• Pre-socialization: They spent two cycles (a full year) building the case. In the first half, they didn't officially push for the promo but "tested the waters" with leadership to identify gaps.
• Identifying Champions: Adrian explicitly asked a Director in his org to mentor him, securing a powerful advocate who could vouch for his readiness during calibration.
• Writing the Packet: The promotion packet was a collaborative effort, ensuring the narrative clearly demonstrated IC8-level scope—in this case, coordinating experiences across dozens of teams and over 30 Product Managers.

"You need to have the impact in the underlying work, but it is also way easier to build the consensus ahead of time. So that when you go to a performance calibration session, you don't have a debate in the room."

Defining the "Uber TL" Role

One of the challenges of large organizations is finding a role that supports Principal-level scope. Adrian didn't wait for a job description. He observed that while there was an overall engineering lead for the hardware program, the "Experiences" layer (AI, music, photo capture, companion app) lacked a unified technical owner.

He stepped into this vacuum, initially just by helping the existing lead offload work. Over time, he became the de facto "Uber TL" for Experiences. Eventually, he formalized the role by asking leadership to "bless" the title, making it easier for external teams to understand his authority. This reinforces a recurring theme in his career: do the job first, get the title later.

Generalization as a Superpower

A defining characteristic of Adrian’s career is his rejection of hyper-specialization. He references a Robert Heinlein quote: "Specialization is for insects." throughout his tenure, Adrian cultivated a "product hybrid" persona, balancing deep technical skills with product intuition and design sensibility.

This breadth became a competitive advantage when moving into hardware. Despite having no background in firmware or circuitry, his willingness to ask "dumb questions," read code outside his domain, and build non-production prototypes allowed him to bridge the gap between hardware constraints and software experiences.

For engineers looking to grow, this suggests that mastering adjacent domains (e.g., a backend engineer learning product design, or a data scientist learning frontend) can open doors to higher-leverage roles that require cross-functional orchestration.

Conclusion: Maximizing the Surface Area of Luck

Looking back on a journey that spans big tech, startups, and boomerangs, Adrian attributes much of his success to relationships. However, he reframes "networking" not as transactional interactions, but as the cumulative result of being a decent person.

By consistently helping others succeed—whether by maintaining legacy systems so others didn't have to, or helping junior engineers grow into roles he was vacating—he built a reservoir of trust. This trust is what allowed him to boomerang back to Meta, secure referrals to Clubhouse, and gain the mentorship necessary for the Principal level.

The advice for the next generation of engineers is simple but profound: increase your surface area for luck. Take more shots, ask for what you want, and over-communicate your intentions. If you combine high agency with a reputation for reliability, the "luck" of finding the right project or the right promotion tends to find you.