Ryan Peterman’s Post

Today I had the chance to experience a day in the life of an Engineering Manager at Meta! 🚀 🚀 I would like to thank my host Greg Vannoni for this amazing experience and for guiding us through this enriching day. We went over the Software Architecture of Meta's system, met with other Software Engineers and Tech Leads, and had the opportunity to ask questions and get valuable insight from them. Here is a brief glimpse of what I learned 💡: - Tech stack of Meta and what new technologies they invest in... (PHP, Hack, Python, SQL, VR) - How new products are built at Meta - from design/strategy to execution and scaling. - Understanding of team dynamics and various career paths within the company. - Mindset/Attitude of a Tech Lead and what their typical day looks like. - An overview of the interview process at Meta and how to get well-versed in technical interviews. Lastly, I would like to credit Nimroz Ortiz, as part of the UA JSP Team for conducting and organizing this program!

The average Meta engineer pushes ~125 commits per half. Back at Meta, I had a rockstar mentee who went from junior [E3] to senior [E5] in just 2 years and pushed a whopping ~500 commits per half. This engineer was the fastest growing talent I have ever mentored, and writing 4x more code than average was a big reason why they got promoted so quickly. So how did they do it? When most people look at this insane number, they immediately assume that quality took a hit and the commits were garbage. However, this was actually the complete opposite for this engineer. This engineer arguably had the highest code quality of any engineer in our 100+ person organization. Every pull request of theirs was a delight to review. Every diff they had was atomic, focused, and reasonably sized. They were diligent about proactively discussing their strategy with senior engineers beforehand, so their code was always clean, optimal, and readable. The big thing that really made engineers feel comfortable accepting their code though was their test plans. This engineer was always so incredibly thorough, testing every possible case and attaching the proof. This is why this engineer got their pull requests approved on the very first try 95%+ of the time. When you're pulling in those numbers, you really are only limited by how fast you can type. When you write some of the best code in the world, your career growth becomes unstoppable. To learn exactly what I taught this engineer to make them so technically strong, take my new 3.5 hour code quality course here: https://lnkd.in/gzkq36Sv #techcareergrowth #seniorengineer #codequality #growthtips #promotion #meta #techlead

IMO, how many times one goes back and forth on their PR/codes and keeps polishing/crafting until it's `perfect`, shows how mature/senior one is and willing to be 🚀

What impact you need to make for $3.2M a year ? E9s are generally the distinguished engineers and probably 0.01% of engineers in Meta reach this level. They don’t just drive complex projects or solve ambiguous problems. The generally - Create Industry Wide Impact - Identifying new technologies or business areas - Ensuring company remains in forefront of tech industry They are ao exclusive that I’ve never met a distinguished engineer at Meta. #softwareengineering

THANK YOU FOR TOP FAN.! With President Joe Biden – I just got recognized as one of their top fans.! ARTICLE: CRYPTOCURRENCY & REYGITONIUM-G. MICHAEL BLOOMBERG FORMER NYC MAYOR Co-FOUNDER BLOOMBERG L.P MIKEBLOOMBERG.com CHAN ZUCKERBERG INITIATIVE CHANZUCKERBERG.com BILL & MELINDA GATES FOUNDATION GATESFOUNDATION.org TENRI CULTURAL INSTITUTE tenri.org https://lnkd.in/e55sRd8b https://lnkd.in/eB98Jnv9 WonderMind.com: CRYPTO-FINANCE & WHAT'S ON THE TABLE. REYGITONIUM-G MR. MS. TEEFEY & SELENA GOMEZ-RARE-SUPERSTAR. TCI GALLERY SPRING 2024 THEMES. CRYPTOCURRENCY & REYGITONIUM-G TO WHOM IT MAY CONCERN: I ABSOLUTELY SEE NOTHING WRONG WITH CRYPTOCURRENCY: REYGITONIUM-G I CAN UNDERSTAND WHY THE INFANT DEMOCRATIC-CAPITALISTIC MINDS OF TODAY BLAME USA GOVERNMENT. THEN IS ANY GOVERNMENT TO BE BLAMED FOR HOMELESS PROBLEMS PLAGUING THE WORLD.? NO. GOD KNOWS HEADACHES USA GOVERNMENT HAVE WITH THE FOREIGN AFFAIRS. THE NEW WORLD PRACTICALLY SHOCK TO WITNESS. PEOPLE ONLY WORKING TOGETHER FOR A COMMON GOAL. "IN THE PURSUIT OF HAPPINESS." THUS DOESN'T THAT ALSO INCLUDE THE HOMELESS. THE HOMELESS ARE OUT THERE. ARE YOU.? HOMELESS.. AN OPPORTUNITY MISUNDERSTOOD. The modern economic system is a market economy, which is a capitalist economy where people, not the government--NOT THE GOVERNMENT--own most businesses. In a capitalist economy, prices allocate capital and labor between competing uses, and capital assets like factories, mines, and railroads can be privately owned and controlled. https://lnkd.in/eB98Jnv9 GOOGLE EXAMPLE, IF YOU NEED TO RAISE MONEY FOR ANY REASON OR MORE SO LETS SAY THE "HOMELESS" PROBLEM WHICH IS BELIEVED TO BE TIME & MONEY CONSUMING BUT IN ONE DIRECTION TOWARD THE HOMELESS. HOWEVER CRYPTOCURRENCY CAN POSSIBLE ALLOWS AN EXPENDITURE OF CURRENCY TO BENEFIT ALL WHO USES THE CRYPTO & REGARDLESS OF HOW IT'S CONSUMED. THEREFORE IF A CRYPTO HOMELESS CURRENCY REYGITONIUM-G EXISTED IT'S MORE HIGHLY LIKELY THAT THE HOMELESS PROBLEM CAN BE VANQUISHED BECAUSE CURRENCY-FINANCES IT'S ALWAYS AVAILABLE TO BE TAPPED INTO FOR HOMELESS RESOLUTIONS. REYGITONIUM-G: EACH COUNTRY GOVERNMENT INITIAL $1-DOLLAR INVESTMENT PORTFOLIO OF 8-BILLION EARTH CITIZENS. THEREAFTER GLOBALLY ANYBODY CAN INVEST IN THE CRYPTOCURRENCY REYGITONIUM-G. OR CONTINUE HIDING THE HOMELESS WHEN A POLITICAL LEADER VISITS AMERICA. CLOSING COMMENT: THE DAMNEDEST CRAZIEST FUNNIEST EMBARRASSING ABOUT THE HOMELESS CHAOS IS ANY EXCUSE AS TO WHY HOMELESS EXIST. HENCEFORTH CONSIDER USA TRILLIONS IN DEBT & 6,120 HOSPITALS SCATTERED AROUND THE USA & MANY COUNTRIES ASKING FOR FOREIGN AID IN THE TRILLIONS & YOU TALKING EXCUSES. MEANWHILE WE WANT TO SETTLE HUMANITY ON OTHER PLANETS. THANK YOU FOR READING.

One thing I learned this month at Meta…don’t be afraid to speak up in meetings, even when you’re *just* a new grad. You might see something others miss. It happened to me just a couple weeks ago. I was in a meeting with senior engineers who were planning a project to reduce latency that was limiting ad performance. To do so, they were discussing optimizing a series of validations for a certain feature. As I listened, I remembered a recent change in the feature that made me question whether the validations were even necessary any more. I briefly wondered, “Should I say anything? I’m sure they know more about this part of the code base than me…” But then I realized, “well even if I’m wrong, I want to learn why, so I should ask anyway.” So I asked: “quick noob question, are we sure we even need to run these validations any more?” And then I mentioned the recent feature change and asked if a more simple solution could just be to remove the validations entirely. It turned out that wasn’t a noob question at all. There was immediate agreement in the room that I was likely right. Most likely, we could remove the validations entirely and the ~2 weeks of eng work required for the original plan could be simplified to just a few simple code changes. Not only would this solve the latency issue, but by removing the now unnecessary validations we would also significantly increase coverage for the feature. That one question ended up changing and simplifying the approach entirely. I also ended up becoming a primary code reviewer and resource for the engineer tasked with the project. That was a great example to me of the power collaboration and a reminder to always speak up and ask questions—especially when something seems off. You might just be right. Anyone else have a similar experience? #softwareengineer #swe #coding

Just had my performance review for my first half at Meta as a new grad software engineer. Here are my takeaways: 1) Write lots of code…and keep writing it High code output is extremely important, but doing so over the course of just one half isn’t terribly impressive. Management looks for sustained high output over multiple halves to prove that you’re not a one hit wonder. 2) Leave behind artifacts Aka don’t just write code, write design docs, tech plans, project proposals, launch summaries, etc. This is all “evidence” for what you’ve accomplished that your manager can use when they advocate for you to get the rating or promo you want. 3) Complexity…and the senior eng who vouch for it… are your best friends The more complex your projects, the better. But there’s really only one way management can know if your project was complex…and that is if a senior engineer says so. This means you need to make sure senior engineers not only know what you're doing, but how hard it is to do it. Prioritize and volunteer for projects that *they* think are complex. (*clarification* this doesn't mean 'chase complexity for complexity’s sake'. That's an awful idea. It means showing enthusiasm for and working with senior eng to tackle the hard problems.) 4) Demonstrate E2E ownership For a new grad to make it to the next level at Meta, they need to show they can take a full project from start to finish. Be the one to design and propose the tech plan, breakdown the tasks, execute, experiment, record and publicize the impact, and ship. Make it clear that you want the ownership and are capable enough to deserve it. Time to put this all into practice in H2.

As I am ramping up at Meta Integrity team, it's rather inevitable that I had to do a number of starter projects. Given that I was expected to define my own destiny to some extent, it triggered a number of very interesting conversations with multiple senior engineers across the org - and even more thoughts that I had while trying to choose the right one. I wanted to share some of them with you - let me know what is your experience of starter project and Big (and small) tech companies alike? What did you enjoy, what did you hate and what you would do differently, with the benefit of hindsight? https://lnkd.in/eknZRszb

Simple reason some engineers at Meta are worth +$3,000,000/yr: Leverage. There are three main ways top engineers have leverage: 1. They write impactful software no one else can. Software at large companies is already high leverage due to the scale. A single change can have a ton of impact ($$$). This impact makes it worth it to pay a lot for their specialized skills. 2. They influence large groups of engineers. Imagine a tech lead among tech leads. They might lead the planning, design, and delivery of initiatives that involve 30+ engineers. This influence gives them leverage and amplifies their impact. 3. They help engineers move faster at scale. They do this by making improvements to tooling or underlying infrastructure everyone uses. Imagine making 1000 engineers 3% faster. That "creates" 30 more engineers' worth of bandwidth out of thin air. Most engineers will not get to these levels, but there's something we can learn from them still. The best way to have more impact is not to invest more time but to think about how to get more out of it through leverage.

I'm thrilled to announce that I've reached a major milestone by successfully completing the "Introduction to Front End Development" course by Meta! This journey has been incredibly rewarding, and I'm excited to apply what I've learned. #meta #frontenddevelopment #coursera