[dwrodri]

What are you trying to get out of a new job? Are you worried your tech skills have atrophied due to your current employer's tech stack? What space are you interested in heading into?

I think answering these questions might help the rest of HN provide more relevant insight. If you're just chasing a larger paycheck, I think the best bet is still MANGA/FAANG. No lack of documentation out there about landing jobs at those companies.

[peregren]

Thanks for this.

In terms of a new Job, I am looking for work I find engaging, with a mission that I think is worthwhile (Which for me could be anything from useful business enabling tech like Stripe. Uni / Training websites like Udacity / Coursera, or a non-profit. I don't particularly care about tech stack as long as its in some way used across the industry.

I am worried that my tech skills have atrophied mostly because I find the projects that I have been working on for the last 3 years have been very low velocity due to a massive development team (1000+) and a lot of bureaucracy. I have written <1000 SLOC this year. A lot of time is spent doing devops work (which i never wanted but thats how my position evolved) and documentation/process design and execution.

Regarding paycheck - for me personally that't not a motivation. Tech salaries where I live are universally more than enough.

[ipaddr]

If someone was looking to change stacks how does one go about it? Say I know someone who has been going through tutorieals, reviewing the docs, creating a personal project. Technically they feel like a solid intermediate at times but still beginners with the ecosystem. They are at a senior level in another stack.

What's the next step? Apply for new stack with existing resume? Do you try to work in new stack at current role?

How does one acual transition?

For some details this friend has 20 years with php/jquery experience.. a year as an angularjs developer along the way and wants to be part of a react / vue ecosystem but has a hard time of letting go of php.

[Hermitian909]

One option is to choose companies that let you learn on the job and stress fundamentals, usually larger companies in SV. I've been in quite a few front end interviews where all questions involved only questions about native methods, CSS, and general browser knowledge.

In terms of becoming skillful enough to pass interviews testing stack specific knowledge I've seen two strategies be broadly successful:

1. Take 1-2 months full time to work on a serious project in the stack. 2. Spend 1-2 years just being in the ecosystem and absorbing the collective groupthink, doing a few tutorials and occasionally hacking together small projects. A couple hours of your time per week throughout the process.

[JasonCannon]

Every hiring manager is different. Some have some bullshit "requires 3 years in this stack" kind of requirements. Personally I feel like the important thing is knowing how to program period. I think knowing paradigms is what's more important than stacks. Id take someone who knows how to build a oop backend with a spa front end for my position I'm hiring for even if they don't have specifically .net/angular experience. You can always ramp up on the specifics while learning paradigms can be much harder.

[avmich]

What if "larger paycheck" is only one of goals, with others being something like "bringing benefits to humanity" or "pursuing long-term hard problems while being software engineer, not researcher"?