Can you add list of resources or a roadmap to follow to be an expert in Hack & React+JS Programming language?
I believe this will really enable me to be very productive at Meta since this is my team's tech stack. And, I'm an E3 working on getting promoted to E4 for transparency.
I sincerely appreciate your contribution.
![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
(5 comments)- 0
2 days agoI just work here @ RobinhoodTake whatever # of diffs you're averaging in a day and 2x the volume. A lot of code you're writing will be specific to Meta & learning outside of your codebase won't be as valuable.
- 02 days agoEntry-Level Software Engineer [E3] [OP]Meta
This make sense, but I believe having a great understanding of the programming language I use will help
- 02 days agoI just work here @ Robinhood
The best to understand a programming language is to write more code in it. Your diff count is the main metric used to guage your skill level. To repeat: just write more code. Anything else you can potentially try to do provides negligible value compared to getting better at writing code and landing diffs.
The main heuristic for junior engineers is diff count. If your count is low, you will not get anything above meets all. If you are an expert, it will show in your diffs (volume and quality will be examined, but volume is an easier step forward & more quantifiable).
- 0
15 hours agoTech Lead @ Robinhood, Meta, Course HeroIt is extremely hard to find external tactical resources that help you move faster at Big Tech as everything is so custom. If you have extra time, it's much better just digging deeper into the code in your team's codebase, not the code that some outside course will make you write. This is why Taro's overall goal is to focus more on mindset, not individual tactics (right mindset helps you derive the tactics).
As an E3, one of your biggest blockers is your diffs getting rejected. I highly recommend looking through other diffs on your team and see how they're rejected so you can not make the same mistakes in your diffs. This was a huge level-up I taught to all my mentees, especially E3s.
- 015 hours agoTech Lead @ Robinhood, Meta, Course Hero
A new Meta E3 just reached out to me and told me her first rating was Greatly Exceeds Expectations (GE), largely thanks to Taro. I shared a lot of resources with her, but the main one was this: [Course] Level Up Your Code Quality As A Software Engineer
On top of that, I recommend the overall junior to mid-level learning path here: Nail Your Promotion: Junior To Mid-Level (L3 -> L4)
Promotions are much harder at Meta now than 4 years ago, but fast promotions are definitely still possible, especially if you champion the Taro advice well. I think if you do everything in the learning path, you'll go from E3 -> E4 in 2 halves.
Best of luck!
