Exceeding Expectations as a Meta Intern
Hi Taro Community,
I was really inspired by a recent discussion post on Taro regarding the key behaviors of a 'Greatly Exceeds' (GE) intern. I found Alex's detailed explanations and guidance very helpful, and I gained a much better understanding of the internship expectations.
Following up on that post, I would love to learn more about the key differences between expectations at the various levels for internship(MA, EE, GE). In particular, I was wondering about the main areas in which the expectations for Meets All (MA) and Exceeds Expectations (EE) differ?
The reason why I am asking is that I will be joining Meta this summer as an intern and would like to do my best to grow as much as possible during my time there.
![Senior Software Engineer [E5] at Meta company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fmeta.jpeg%3Falt%3Dmedia%26token%3Da7a5bcc0-e178-4b5b-b71e-09bf6c6aefae&w=48&q=75){kind=small}
![Mid-Level Software Engineer [E4] at Meta company logo](/_next/image/?url=https%3A%2F%2Ffirebasestorage.googleapis.com%2Fv0%2Fb%2Ftech-career-growth.appspot.com%2Fo%2Fcompany_logos%252Fmeta_logo.png%3Falt%3Dmedia%26token%3Db5f837b1-c74f-4e2f-848b-1599f05624c5&w=48&q=75){kind=logo}
Discussion
(1 comment)- 0
30 minutes agoTech Lead @ Robinhood, Meta, Course HeroSimilar to that other post, I recommend going through the L3 to L4 learning path which breaks down the evolution of junior engineers in great detail: Nail Your Promotion: Junior To Mid-Level (L3 -> L4)
Here's how it works in broad strokes:
Meets All
- Solid coding velocity
- Decent code quality that comes together in the last 3-4 weeks of the internship. Will still put out diffs that get roasted pretty bad occasionally
- Can solve tasks independently but needs a little hand-holding sometimes
- Lackluster communication
Exceeds Expectations
- High code velocity
- Good code quality that starts coming together around the midway point of the internship. Rarely puts out low quality diffs
- Solves tasks very independently, rarely needs hand-holding
- Good communication
Greatly Exceeds
- Extremely high code velocity
- Stellar code quality that comes together astonishingly early in the internship (like week 3). Almost never puts out a diff that gets a major amount of comments
- Solves tasks extremely independently, even those with high technical complexity and ambiguity
- Great communication with many well-written project updates
- Takes the initiative, creates some small scope here and there for themselves
