It depends on the type of a position. If it is a "one-shot"/contract job then you are looking for the concrete skillset/expertise, i.e. "Haskell". For relatively longterm or permanent positions I think it is better to give a priority to smart and "getting things done" type of persons rather than specific skills. But they should have some relevant experience. For instance, if you're looking for the functional programmers, you should consider ML/SML/OCaml, Scheme, Erlang, ... (Well, in case of these two, better to check that person has some grasp of static typing :)) programmers as well. And learning (fun) should be an important aspect of the position. Regards, Zura Paul Johnson-2 wrote:
I'm starting to see job adverts mentioning Haskell as a "nice to have", and even in some cases as a technology to work with.
However right now I'm looking at it from the other side. Suppose someone wants to hire a Haskell developer or three. How easy is this? I'd appreciate replies from people who have actually done this.
* How many applications did you get?
* How many of those applicants knew what a monad is, or how to write FizzBuzz in Haskell?
Thanks,
Paul. _______________________________________________ Haskell-Cafe mailing list Haskell-Cafe@haskell.org http://www.haskell.org/mailman/listinfo/haskell-cafe
-- View this message in context: http://old.nabble.com/How-easy-is-it-to-hire-Haskell-programmers-tp29038634p... Sent from the Haskell - Haskell-Cafe mailing list archive at Nabble.com.