| In your opinion, which role is the best to be average at? From compensation, work/life balance, fulfillment, career opportunities, etc? 1. Frontend Engineer 2. Backend Engineer 3. Applied Research Engineer 4. Research Engineer 5. Graphics Engineer 6. Game developer 7. Enterprise SE 8. Fintech Engineer (esp. in trading/algos) 9. Cloud Engineer 10. DevOps 11. System Engineer (compiler, os, browser) 12. Consumer Application Engineer (macos/linux/windows) 13. Machine Learning Engineer 14. Data Engineer It’s always good to be best. I got told best ML engineer would earn a lot compared to best Frontend Engineer. (ofc, it might be wrong). But which role is good to be average at? It would also be awesome to know barrier of entry vs reward. For example entering graphics engineering is extremely hard and reward is also average compared to average frontend roles. Once the profile is built up, the former will be a great deal because the investment pays off! So, what are your opinions? Any idea? |
I've worked with barely average developers and believe me, they frustrate the rest of the team. They'll copy-and-paste the same code 5x instead of asking where they should put a new module. They'll commit untested code into main, and leave it to the next guy to clean it up, just so they can close their ticket. Communication is often poor. We all don't know things. The problem with "average" is they don't ask questions.