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??

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

  1. Can you find and correct a spelling mistake
  2. Could you look at a partially completed unit test and complete it.
  3. Could you filter out a piece of erroneous data.
  4. 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!

5 Likes

Maybe I am misunderstanding you but this sounds like it would be much more effective at assessing dyslexia than programming performance! :slight_smile:

1 Like

:sweat_smile: we did tell you what the correct spelling was!

2 Likes

May I present to you… :drum: :drum: :drum:GitHub - crate-ci/typos: Source code spell checker (I am not the author).

2 Likes

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 “hello in Y module is misspelled as helyo. We’d like to correct the spelling to be hello”.

2 Likes

Yeah I get it, was just messing with you here. :slight_smile:

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.

2 Likes

If you want to practice job interviews, message me. I know a good tool :wink:

2 Likes