# Haskell Interview Prep Resources

**URL:** <https://discourse.haskell.org/t/haskell-interview-prep-resources/1331>\
**Category:** Links\
**Created:** [July 23, 2020, 3:12pm UTC](https://discourse.haskell.org/t/haskell-interview-prep-resources/1331 "2020-07-23T15:12:33Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jaspervdj](https://sea2.discourse-cdn.com/flex002/user_avatar/discourse.haskell.org/jaspervdj/32/586_2.png) [@jaspervdj](https://discourse.haskell.org/u/jaspervdj)\
**Post date:** [July 24, 2020, 10:37am UTC](https://discourse.haskell.org/t/haskell-interview-prep-resources/1331/2 "2020-07-24T10:37:20Z")

</div>

When interviewing for Haskell jobs in the past, I’ve usually asked interviewees to implement a parser combinator library from scratch. I still like that question because it can be adjusted to the level of the interviewee – if it’s more of a beginner Haskeller, I can offer them some guidance and maybe we’ll end up with a simple list based monadic parser similar to [Graham Hutton’s famous functional pearl](https://www.cs.nott.ac.uk/~pszgmh/pearl.pdf). If it’s someone with more experience, we can talk about performance and maybe do a CPS based parser, or talk about how to return good error messages.

This was for a compiler-related job though, so if you’re interviewing for a e.g. a mostly web-based company, I’d recommend looking into that area a bit more.

---

_[View the full topic](https://discourse.haskell.org/t/haskell-interview-prep-resources/1331)._