3 ms·
> only advertise positions for people who are comically well-decorated; Principal engineers with 10 years of experience, plus the masters degree, plus a bunch o
by Aurornis 3y ago
> only advertise positions for people who are comically well-decorated; Principal engineers with 10 years of experience, plus the masters degree, plus a bunch of specific cloud orchestration, scalable systems, or other devops experience that just seems entirely impractical to accumulate without simply advancing at the same company or FAANG for 15 years, which seems itself to be an unachievable tenure in this millennium.
You don’t need to spend 15 years at the same company or at FAANG to acquire these skills.
One issue that a lot of people face is that their career has been less about accumulating 10-15 years of progressively more complex experience and more about accumulating 1-2 years of experience 7-10 different times. It can take some deliberate planning to work your way upward over time and across companies rather than repeating the same arc over and over again.
Another trap is when people who want to be high-level ICs end up in management for a while, slowly getting further and further from working on the tech.
In this job market it’s hard to go from unemployed in one country to direct hire Principal in another country unless you have an extraordinary skill set. It will make more sense to get your foot in the door at any job that might work, then move up from there.
- bluefirebrand 3y ago> their career has been less about accumulating 10-15 years of progressively more complex experience This is difficult to avoid because most companies don't have a progressively more complex requirements for people to learn from.
- KRAKRISMOTT 3y agoThen either jump jobs or get promoted. This is the nature of tech. High risk, high reward. Work for the public sector e.g. US Digital Service if you just want something boring and stable.
- Anon1096 3y agoFor a lot of people the only option is to jump jobs. At small and mid size companies, it's literally not possible to have the impact of an L6+ Google equivalent most of the time. Rough for people not working in the tech industry and wanting to get in, but that's why you get downleveled and honestly it's usually appropriate even if your previous title was staff and now you're a SWE2 or senior.
- ldjkfkdsjnv 3y ago"One issue that a lot of people face is that their career has been less about accumulating 10-15 years of progressively more complex experience and more about accumulating 1-2 years of experience 7-10 different times." This could also be worded as: "One issue that a lot of people face is that they did not work at prestigious technical companies. Having a long tenure at such companies gives hiring managers confidence in placing them into principal level roles, regardless of what the candidate actually learned at said company. Everything is about the illusion of competence."
- ajkjk 3y agoDisagree. I've worked with engineers who were taking on much more business responsibility after two years than others who are basically moderately proficient code bots after twenty. There is a huge difference in competency at the stuff that scales well, such that some people don't even notice it's a skill at all and others instantly gravitate to it it. Principal roles are for the people who learn to do them (with some error bars of course.. And everyone knows when that happens).
- brailsafe 3y agoCan you provide an example where this has happened both outside of a FAANG and outside of management?
- SenHeng 3y agoI once worked as the sole maintainer of an old legacy product while the company spent 2 years trying to create a new product to replace it. Eventually they abandoned all work and most of the team left. During the transition months, I managed to convince upper management that now would be a good time to update the legacy product with all the knowledge gained over the past years. So I spent about a couple of months or more (fuzzy memory) directing a group of people more skilled and talented than me, converting a coffeescript codebase to typescript, fixing a whole bunch of bugs and performance issues and updated a neglected codebase to something they can actually hire people to work on. After that experience, I was promoted to tech director and leveraged that to become tech lead at future jobs.
- brailsafe 3y agoI suppose the nature of that quote is more about the exaggerated nature of the requirements compared to the rather unlikely ability to fulfill those requirements without gradually climbing at a company with an endless level of advancement in an IC role, but not excluding the possibility it could be done otherwise. That said, I definitely suffer from this problem, but it's in-part a result of both no clear way to advance in most circumstances, and repeated volatility in both the market, world, and my life. Now, there aren't jobs to advance from, even if I could land one, and prior to being laid off, I'd most likely have just continued doing either my regular course of work or eventually being offered a managing role. My impression is that it would be a rare circumstance to be offered a higher level IC position at a different company without making a horizontal move in role and building the trust there. I wouldn't say I've actually repeated the same arc ever, it would just seem that way on the surface, and maybe I should think about how to make it not seem that way.
- j7ake 3y agoDisagree on the country statement. it requires certain achievements, but by no means extraordinary. For example, very common to see European PhD graduates move to usa as their first job as staff or principal.