Comment

Comment by mdcds

> I’ve had little luck of going for roles that do not directly correlate with my current experience. It seems that recruiters have very little interest in talking about any roles other than ones that fit my current stack exactly (node/react/python).

Yes! so frustrating! this is the reason why I left SF Bay Area circa 2016. No one wanted to talk about what I wanted to do next and my prof interests. Only about past experience and existing skills that I could immediately contribute.

I started my career as a fullstack dev doing crud at startups. Eventually I got interested in FP and learned Haskell in my free time. Then little bit of Scala. After I got laid off from a startup, I knew that FP and/or large scale systems was what I wanted to work on next and wasn't willing to compromise.

Eventually a F500 company with an office in Portland OR agreed to hire me as a contractor because they were looking for strong FPers to program in Scala and local programmer market was almost non-existent.

That's how I pivoted to working on distributed systems and products with millions of users, and never looked back.

Generalized advice: learn a skill with a high barrier to entry that is also in demand.

parent mdcds 4 years ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton