subj
non-obvious strategies that help candidates break through
๐น ๐๐จ๐งโ๐ญ ๐ฃ๐ฎ๐ฌ๐ญ ๐๐ฉ๐ฉ๐ฅ๐ฒ ๐จ๐ง๐ฅ๐ข๐ง๐. Referrals and warm connections make sure your resume gets seen.
๐น ๐๐ฌ๐ค ๐๐จ๐ซ ๐๐๐ฏ๐ข๐๐, ๐ง๐จ๐ญ ๐ ๐ฃ๐จ๐. Conversations often unlock opportunities you wouldnโt find otherwise.
๐น ๐๐ข๐ฏ๐ ๐ญ๐ก๐๐ฆ ๐ ๐ซ๐๐๐ฌ๐จ๐ง ๐ญ๐จ ๐ฌ๐๐ฒ ๐ฒ๐๐ฌ. Shared experiences and passions create connection.
๐น ๐ ๐ข๐ง๐ ๐ญ๐ก๐ โ๐ฒ๐จ๐ฎ-๐ฌ๐ก๐๐ฉ๐๐ ๐ก๐จ๐ฅ๐.โ Highlight the fit only you can fill. Show, donโt just tell.
๐น ๐๐๐ ๐ข๐ญ ๐๐ซ๐จ๐ฆ ๐ญ๐ก๐ ๐ก๐ข๐ซ๐ข๐ง๐ ๐ฆ๐๐ง๐๐ ๐๐ซโ๐ฌ ๐๐ฒ๐๐ฌ. Your job is to de-risk their decision and make choosing you easy.
๐น ๐๐จ ๐ญ๐ก๐ ๐ฃ๐จ๐ ๐๐๐๐จ๐ซ๐ ๐ฒ๐จ๐ฎ ๐ ๐๐ญ ๐ญ๐ก๐ ๐ฃ๐จ๐. Show you are already invested in their product or success.
๐น ๐๐๐ข๐ฅ๐จ๐ซ ๐ฒ๐จ๐ฎ๐ซ ๐ซ๐๐ฌ๐ฎ๐ฆ๐ ๐๐ง๐ ๐ฌ๐ญ๐จ๐ซ๐ฒ. Speak the language of the role and show clearly how you will add value.
๐น ๐๐ฌ๐ค ๐๐จ๐ซ ๐๐๐ฏ๐ข๐๐, ๐ง๐จ๐ญ ๐ ๐ฃ๐จ๐. Conversations often unlock opportunities you wouldnโt find otherwise.
๐น ๐๐ข๐ฏ๐ ๐ญ๐ก๐๐ฆ ๐ ๐ซ๐๐๐ฌ๐จ๐ง ๐ญ๐จ ๐ฌ๐๐ฒ ๐ฒ๐๐ฌ. Shared experiences and passions create connection.
๐น ๐ ๐ข๐ง๐ ๐ญ๐ก๐ โ๐ฒ๐จ๐ฎ-๐ฌ๐ก๐๐ฉ๐๐ ๐ก๐จ๐ฅ๐.โ Highlight the fit only you can fill. Show, donโt just tell.
๐น ๐๐๐ ๐ข๐ญ ๐๐ซ๐จ๐ฆ ๐ญ๐ก๐ ๐ก๐ข๐ซ๐ข๐ง๐ ๐ฆ๐๐ง๐๐ ๐๐ซโ๐ฌ ๐๐ฒ๐๐ฌ. Your job is to de-risk their decision and make choosing you easy.
๐น ๐๐จ ๐ญ๐ก๐ ๐ฃ๐จ๐ ๐๐๐๐จ๐ซ๐ ๐ฒ๐จ๐ฎ ๐ ๐๐ญ ๐ญ๐ก๐ ๐ฃ๐จ๐. Show you are already invested in their product or success.
๐น ๐๐๐ข๐ฅ๐จ๐ซ ๐ฒ๐จ๐ฎ๐ซ ๐ซ๐๐ฌ๐ฎ๐ฆ๐ ๐๐ง๐ ๐ฌ๐ญ๐จ๐ซ๐ฒ. Speak the language of the role and show clearly how you will add value.
subj
The code is the documentation -- yep
At Meta, we didn't waste our time writing documentation about how our codebase worked for a simple reason: The code itself was documentation.
Actually readable, concise, and detailed commit messages were the first step.
On top of that, every pull request had a detailed body explaining the code's business context and approach, making blames super informative.
Every pull request had a test plan section. This is where we attached logs, screenshots, and video demos to make it dead obvious what our code did.
We also required a JavaDoc style header on every file, often linking deeper resources like system design docs there.
If an engineering organization needs to write a series of O' Reilly books to explain how their own code works, they have already failed miserably.
Documentation is something that should be naturally generated as part of the culture, not an explicit extra effort. Learn more about Meta's genius approach to documentation here: https://lnkd.in/ggcqr6pK
Actually readable, concise, and detailed commit messages were the first step.
On top of that, every pull request had a detailed body explaining the code's business context and approach, making blames super informative.
Every pull request had a test plan section. This is where we attached logs, screenshots, and video demos to make it dead obvious what our code did.
We also required a JavaDoc style header on every file, often linking deeper resources like system design docs there.
If an engineering organization needs to write a series of O' Reilly books to explain how their own code works, they have already failed miserably.
Documentation is something that should be naturally generated as part of the culture, not an explicit extra effort. Learn more about Meta's genius approach to documentation here: https://lnkd.in/ggcqr6pK
express, not stress