Senior Elixir Engineer - Sequin, San Francisco CA, USA

Intro

Help us build the world’s fastest and most developer-friendly change data capture (CDC) platform. We’re transforming how teams handle real-time data flows, from edge caching to event triggers. While other CDC systems are complex and slow, Sequin is so simple you could set it up in a weekend project, yet robust enough for Fortune 500 companies. And it’s completely open source.

About us

My name: Eric Goldman
My position: Co-founder
Company name: Sequin
Company website: sequinstream.com
Company headquarters: San Francisco, CA USA
Company info and history:

We’re backed by amazing investors like Kleiner Perkins and Craft Ventures. We’re starting the new year by growing from 3 → 4. We’re solving some very hard and classic problems, 100% open source

We are all in on Elixir/Phoenix/LiveView.

About the job

Job title: Senior Software Engineer

Job description:

We’re searching for ambitious engineers to join us at this early stage. This is not a ticket-taking role - you’ll have significant influence over both product and technical direction, often tackling projects with clear outcomes but undefined paths to get there.

  • We’re solving novel distributed systems challenges, not building CRUD apps
  • We’re building open source
  • We move incredibly fast - our users consistently praise our rapid feature delivery and issue resolution
  • It’s a high-energy environment where you get to write a lot of code that directly impacts customers and our bottom-line
  • Speed to product/market fit in 2025 is our priority, making this an exciting time to join
  • We embrace whatever tooling we can to be hyper productive, including AI tooling

Salary range: $170K - $210K + Equity

Qualifications or experience:

You’ll thrive at Sequin if you:

  • Are a self-starter who excels with autonomy
  • Have natural curiosity and eagerly learn new domains
  • Are passionate about programming beyond work hours
  • Have a ship it attitude and a willingness to iterate to the right solution as opposed to build it perfectly upfront
  • Maintain optimism while tackling complex challenges
  • Communicate clearly and frequently
  • Are excited about creating exceptional developer experiences

Skills & Experience

  • 3+ years of full-time software engineering experience
  • Strong distributed and concurrent systems experience (strongly preferred)

Bonus points for

  • Experience working with data-intensive applications
  • Experience with Postgres internals (performance tuning, trigger functions)
  • Cloud infrastructure experience (we use AWS)

Position on remote work

Remote job: No
Any other notes about your position on remote work: We ship from our office in San Francisco. We provide relocation assistance.

About the interview process

To Apply: Email Founders@sequinstream.com

In place of a cover letter:

  • In 2-3 sentences, tell us what excites you about Sequin
  • In 3-4 sentences, tell us about the most impressive thing you’ve built

After you apply, you can expect a quick reply and the following process:

  1. 30-minute phone call: We’ll get introduced and spend 30 minutes learning if we’re both aligned.
  2. 60-minute technical call: Before we ask you to come in to the office, we’ll assess your skills over the phone.
  3. Onsite: We’ll host you in our office and you’ll meet the entire team. We’ll discuss each chapter of your career, write code together, and white board an architecture problem.
  4. References: Talking with your former bosses and colleagues is a crucial part of our process. We’ll want to talk to at least three references.
  5. Offer: We’ll make an offer

Further info

Check out our careers page →

5 Likes

How would define “strong distributed and concurrent systems experience”? Published papers?

1 Like

Not published papers. Have you ever worked on the kinds of applications described by “Designing Data-Intensive Applications”? Worked with message streams? Dealt with distributed data, clustered nodes (and the accompanying challenges), data syncing, or an event-driven system?

In Elixir-speak, used OTP primitives directly?

1 Like

I’m not the best fit but this elaboration will help your search I think. Thank you for clarifying.

1 Like