AppleKid7
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??
Where Next?
Trending in Questions
Other Trending Topics
Latest on Elixir Forum
Sponsor Spotlight
Deploy Phoenix to your own VPS with PaaS ease: push-to-deploy, zero downtime, auto SSL, managed Postgres. 14-day free trial at potions.io
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #ai
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #blog-post
- #elixirconf-us
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #security
- #hex
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.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
Producing high quality Elixir screencasts since 2017.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 8- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
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
And honestly, that’s it. As analytical people, we often overthink things. You’ll do great!
garrison
Maybe I am misunderstanding you but this sounds like it would be much more effective at assessing dyslexia than programming performance!
camatcode
dimitarvp
May I present to you…
… GitHub - crate-ci/typos: Source code spell checker · GitHub (I am not the author).
camatcode
I should give some more context around it. Genuinely, IDC how you solved it. I just wanted you to open your IDE of choice or tool of choice to show me you know how to find something.
The issue goes something like “
helloin Y module is misspelled ashelyo. We’d like to correct the spelling to behello”.dimitarvp
Yeah I get it, was just messing with you here.
I’ve gotten a good amount of compliments for knowing a lot of tooling which as you point out is just one more way to solve problems. The idea is to be able to solve the problems, mostly regardless of how.
egze
If you want to practice job interviews, message me. I know a good tool
Null-logic-0
I’m relatively new to the Elixir ecosystem, coming from a Ruby on Rails and JavaScript background, but over the past few months, I’ve built around 8 production-ready demo projects with Phoenix and LiveView systems with real architectural complexity, not just CRUD applications.
One thing I’ve noticed is that the Elixir community seems to value different signals compared to more mainstream ecosystems, so I wanted to ask from an interviewer’s perspective:
When evaluating Elixir candidates, what tends to carry more weight: high-quality personal projects that demonstrate OTP/distributed systems thinking, or meaningful open-source contributions to the ecosystem?
I’m especially interested in understanding what separates someone who simply uses Phoenix from someone companies would consider a strong Elixir engineer.