So, I got my first job by going to my local Haskell meetup and chatting with someone who would end up being my boss, and I've stuck with that crew since. I thin

So, I got my first job by going to my local Haskell meetup and chatting with someone who would end up being my boss, and I've stuck with that crew since. I think that's rather serendipitous but it definitely doesn't hurt to go hang out with the Haskellers in your area. There's a regular meetup in many major cities, including Boston, SF, NYC, London and Zurich off the top of my head. Our shop has also hired people who respond to our job postings (on Reddit, for example), as well as people who participate in the community on IRC and Discord either by word of mouth or recommendation. Now, as someone who evaluates resumes and interviews people, the only Haskell specific thing I care about is making sure the candidate knows how to use the core of the language, which is basically Haskell2010 + some indispensable extensions. I expect fancier stuff to require training, and to be honest it's sometimes better to properly contextualize that stuff for someone instead of having them come in already thinking they know how to use the footguns :^). My company asks candidates to attach or link code samples if they have them. If they don't, we ask them to write a small Reflex [0] app, because we're primarily a Reflex shop. Now, every shop is going to be different and expect different things from their candidates. That's one reason why getting involved in the community is so useful. If you hear directly from people who employ Haskellers in your area what they want, then you can build your credentials for that. Besides that, you just gotta apply. If you're a strong candidate in another tech stack, you're a strong candidate for a Haskell stack too if you can demonstrate you can use the language. There's currently a remote job posting on r/haskell if you want to give it a shot. I wish you the best of luck :) [0] https://reflex-frp.org/ https://reflex-frp.org/