AppleKid7
Any Elixir coding interview tips?
I’ve never interviewed for an Elixir role and was wondering what it would look like to interview in 2025 for such a role. I’m still very much in the process of learning, trying to build some simple things (that I’d want to build anyway, so I’m not really doing it to attract potential employers per se), but might start mixing it up with other things.
I’ve read open source contributions go a long way these days (in the age of AI, this makes sense to me). However, in a past thread about how to find Elixir jobs, consensus seemed to be that this wasn’t the most efficient way due to the nature of most open source projects and how they look very different from the application code most employers want you to write. What projects would you recommend that aren’t extremely macro-heavy?
Besides that, what kinds of coding exercises, if any, would y’all recommend looking into? Are regular DSA questions like writing Linked Lists, Hash Tables, Trees, sorting stuff, etc, common at all in Elixir interviews??
Most Liked
camatcode
I certainly can’t speak for every situation - only from my own experience being a technical interviewer.
Open source work is a way to say “Hey, I know what I’m doing” - as far as projects, honestly, just work on stuff that makes you happy.
If its the right fit, the team has taken a lot of time crafting the technical interview experience. For us, our technical interviews weren’t designed to trick you and assumed you were nervous. The most critical part, for me, is that you worked through the issues, and discussed them, using me as a peer to bounce things off of.
Our interview process had 4 issues to work though, I’ll just describe what each was about
- Can you find and correct a spelling mistake
- Could you look at a partially completed unit test and complete it.
- Could you filter out a piece of erroneous data.
- Would you be able to spot an inefficiency?
- If you didn’t, that’s actually OK. There was a harder way to complete the problem. It just told me what you might need to work on.
And honestly, that’s it. As analytical people, we often overthink things. You’ll do great!
camatcode
we did tell you what the correct spelling was!
dimitarvp
May I present to you… 
… GitHub - crate-ci/typos: Source code spell checker · GitHub (I am not the author).
Popular in Questions
Other popular topics
Latest on Elixir Forum
Sponsor Spotlight
Develop your skills with books, videos, and courses.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #javascript
- #code-sync
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance
Our Sponsors
Build Elixir applications with speed and confidence.
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Real-time error tracking, performance insights, and observability for devs.
Develop your skills with books, videos, and courses.
Enabling companies to succeed by building software people love.
The deployment platform built for Elixir: PaaS ease, VPS control.
Courses that'll move you from confusion to "Aha, now I get it!"