Why I Built HexHire

· 1 min read
Remote Elixir Jobs HexHire

HexHire started from a personal frustration. I kept hearing that “there aren’t many Elixir jobs.” But as someone active in the Elixir ecosystem, I knew that wasn’t true.

The jobs were there — just scattered everywhere. Some appeared on Elixir-specific boards like Elixir Jobs and Elixir Radar, which do a great job curating high-quality roles, but the volume was always limited. Most Elixir opportunities lived elsewhere:

  • LinkedIn posts and company pages
  • Discord and Slack communities
  • X (Twitter) threads
  • General-purpose job boards
  • Elixir Forum discussions

Finding them meant constantly switching platforms, scrolling feeds, and hoping you didn’t miss something. That fragmentation always felt unnecessary.

I wanted one simple thing:

  • A single place focused on remote Elixir jobs
  • No noise from unrelated tech stacks
  • No chasing links across half the internet

So I built HexHire — the place I wished existed when I was searching myself.


What HexHire is (and isn’t)

HexHire is:

  • A focused job board
  • Optimized for clarity and speed
  • Built for a specific community

HexHire is not:

  • A massive marketplace
  • A recruiter platform
  • A general tech job board

The goal is usefulness, not scale for scale’s sake.


How I’m building it

HexHire is built incrementally:

  • Small features
  • Fast feedback
  • Real usage over assumptions

I’m intentionally keeping it simple:

  • Minimal UI
  • Clear job posts
  • No dark patterns

If it helps even a handful of people find the right role or hire the right developer, it’s doing its job.


What’s next

I’m continuing to:

  • Improve the posting flow
  • Listen to feedback from companies and developers
  • Ship small improvements consistently

HexHire is a long-term project, not a launch-day experiment.

You can check it out here:
hexhire.io