Haskell Engineer

We're looking for a Haskell Engineer to architect and build our Haskell backend to help tens of millions of people connect to each other and themselves – through astrology – in real, meaningful ways.

What you’ll do

• Architect and build our Haskell backend with well-documented, easily-tested code that can gracefully scale to tens of millions of users
• Build an elegant system that takes the infinite complexity of human language, gives our writers tools for expressive composition, and delivers relevant horoscopes to users using aggregated contextual & historical signals
• Use machines to automate a wide variety of repetitive tasks, including some (not all) writing
• Work extremely closely with a small, cross-functional team to negotiate, build, and ship new features with the best bang for our buck

What you'll bring

• 3+ years of hands-on experience writing in Haskell or another functional programming language 
• An ability to develop, scale, and maintain complex web apps on cloud infrastructure (we use AWS)
• A disciplined approach to development, testing, documentation, and code structure in a team environment 
• Knowledge or a willingness to learn about ML and NLP, particularly libraries like spaCy, GPT-2, and BERT, is a plus

Our technical interview process

Our interview process is divided into four phases — an initial interview with a recruiter, a secondary interview with a manager, 3–4 virtual onsite interviews (1 hour each, 2 of which are technical screens using CoderPad) with peers and cross-functional coworkers, and lastly, a meeting with our founder.

We realize technical interviews can feel challenging to prepare for, so here’s what we’re interested in seeing from you: 

• Clean, easily-testable code that’s compiled frequently  
• Clear communication around your decision-making process 
• Creative and thoughtful problem-solving 
• Self-reflection around past projects and the ability to articulate what worked, what didn’t work, and what you'd do differently now that you know the outcomes
• Ability to partner with cross-functional coworkers outside of engineering 

We’re not interviewing for: 

• Pure coding skills (we’re a cross-functional company and the ability to collaborate across disciplines is equally as important as coding ability)   
• Memorization of complex algorithms or trivia (we all have access to some form of search engine and use it when we forget) 
• Your ability to know everything (we may ask you a question you don’t know the answer to and that’s ok) 
• “Cracking the Code” / LeetCode-type knowledge