Getting into FAANG isn't enough, or 9 steps to a dream career

Hello,  Gromov is with you . I recently ran a career stream for School 21 students, which turned out to be very intense - and I only managed to touch on about a third of what was planned. Below are his main thoughts if you don't have time to watch an hour-long recording.





Career ≠ work

We often use the terms “career” and “work” interchangeably, but this is not entirely correct. A career, in my opinion, is a professional path that is  planned and in line with your desires and goals . While work is just one of the points along the way.





Just changing jobs every few years in search of a bigger salary or a more interesting project, you will move chaotically. Career needs to be planned, otherwise it will somehow develop without your active participation.





Why isn't getting into FAANG enough?

Technology corporations - FAANG - have become targets for many programmers. Moreover, often alternatives are not considered at all, and a refusal at an interview is perceived as a complete failure. In my opinion, in the eyes of such people, "faangs" are greatly overvalued.





They have  pluses :





  • Many smart and educated people around





  • Relatively high status





  • Salary above the market average





  • Many possibilities (in theory)





But the  disadvantages are  serious:





  • A formal approach to assessing your performance





  • Huge internal competition for interesting projects and opportunities (in practice)





  • Low chances of non-linear career growth





  • A bunch of routine and problems specific only to these companies





To strive for FAANG or not is up to you. I urge you  to reflect now and never forget your personal goals .





Learn to do cool stuff

- , . , . — .





?

  •   . , .





  • . , WebAssembly, , — , /





?

  •    .





  •   , — -.





  •  — , , .





,

. , , , — .





, .





  • - , .





  • , .





 — . , . , .





. , , , .





, , ,   .  , (, , — -), .





?

 — , . , , - , .





, ,  , .





, — IDE, Linux-.





,   , . SSH.





, / , , .





— , . , , . , .





 (« X?») , — .





 — , ( ), . , , - ( , ).





  •   . (hard skills), , , , soft skills .





  • , . ( , ) , . — , — , .





  •   .  , .





- «» — .





  .  , , — , , — .





  •   .  , .





  •   .  — , , , .





  • ,    — FAANG, , .





    . , , . , .





, /-. , , , -, , , -, .





—  ,  . , — . , , .





  •   .  - - scrum, — , .





  • .  2 , , . , , .





, , , , . , ,    — .





-.    , , . , — «» .





,   , .





- . , . , .





. - «» —   () , , user experience , , customer experience.





(, , ), .





, , , , , .





, . ( ), .





( , )   — , . — , .





  •   .





  •   , — .





  •  — , .





  • .





, — , , — , , .





   — , . , , , , .





A map of professional activity from the article "Why should a programmer delve into the brain" (t.me/gromov_com/48)
« » (t.me/gromov_com/48)

,   , .





=

, , — —   . , , , , .





, : , , . , ?





9 5, , . ( ), , , . , .





, . !





  •  «Learning How to Learn»  .





  • «» — , .





  • «Four Favorite Tools»  . , , .





  • «War of Art»  , , . , .





  • « »  (- – Soft Skills). , — .





  • Joel Spolsky on Project Appraisal: Evidence Based Scheduling . Cool article, recommendations from which I would not undertake to apply in practice?












All Articles