Infrastructure Engineer

beehiiv is the all-in-one newsletter and creator platform powering the next generation of media companies and independent voices. We help creators and businesses launch, grow, and monetize newsletters-now serving tens of thousands of publishers and reaching hundreds of millions of readers monthly. With $20M+ ARR, 100% YoY growth, and a newly expanded product suite (ad network, website builder, paid tiers), we're entering our next phase of hypergrowth.

We are looking for an experienced infrastructure and dev-ops engineer to build out the core hosting and deployment platform for our main application.

You will work closely with other engineers to migrate our main application from Heroku to a self-hosted platform on AWS. This is a largely greenfield opportunity to build out everything, including Terraform IaC, CI/CD, deployment mechanisms, integration with 3rd-party tools such as CloudFlare and CrunchyData, and monitoring and alerting.

Ideally, you'll have:

• Worked with the following technologies in an engineering role, such as Infrastructure, Site Reliability (SRE), DevOps, or Cloud Engineering.
• Built out projects using these technologies from the ground up, and/or you have supported them while running in production environments at scale.
  You've architected and designed CI/CD pipelines that start with code on a keyboard and end with a container in production.
• Familiar with SOC II and have implemented it in the past using industry best practices.

Technologies you are familiar with: Ranked in order of relative importance

• AWS - Experience provisioning, managing, and automating AWS infrastructure, including: EKS, EC2, ALBs, IAM, VPCs, S3, Route53, SecretsManager, KMS, and more.
• Terraform (or other IaC) - Building, managing, and deploying IaC as the foundation of an organization's infrastructure.
• Kubernetes - Experience provisioning and managing cloud K8s clusters and using standard management tools such as Helm, Helmfile, and more.
  IAM - Writing IAM policies, and provisioning SSO authentication and proper access roles.
  CI/CD - Ideally, you have experience with GitHub Actions, but any CI/CD technology, such as GitLab CI, Jenkins, or CircleCI.
• Networking, VPNs - Building, provisioning, and managing VPNs and network access.
• Observability, Monitoring, and Alerting - You have worked with either DataDog, Prometheus, Grafana,
• CloudWatch, PagerDuty, NewRelic, and others.
• Fault Tolerance, Availability, Scalability, and Disaster Recovery - Ideally, you have worked with architectures that take all of these into consideration. You've built out and tested (and hopefully never run) DR scenarios.

Nice-to-Have's:

• Queue-based job runner systems - You have experience managing, deploying, and monitoring these systems, such as the Ruby-based Sidekiq.
• Microservices - You're comfortable understanding and potentially writing some application code to power microservices. You understand logical and physical boundaries between deployments.
• You're comfortable working with RESTful web applications.
• You have experience with Ruby on Rails.
• Postgres - You've worked with Postgres before and can write SQL and DDL.
• OLAP Databases - You've worked with Columnar OLAP databases before, are comfortable with SQL, can write DDL, and can manage database migration tools. (We use Clickhouse specifically)
• You've self-hosted Clickhouse before
• Kafka Ecosystem - You've managed or even provisioned Kafka Clusters before, created topics, connectors, and schemas. You've troubleshooted and fixed clusters in a bad state.
• You're familiar with Event-Driven Architectures.
• You've worked with Heroku before

What you'll be responsible for:

What you can expect:

First 60 days:

• Develop an understanding of the current application, its deployment mechanisms, and its scaling metrics.
• Take ownership of SRE responsibilities for the existing Heroku Application.
• Contribute to the AWS Infrastructure Stack that is already hosting our Data Infrastructure.
• Develop an understanding of both the physical and business logic boundaries of the current application. For example:
  • Where does it make sense to split the application into microservices deployed separately?
  • Where might it make sense to fork the repo into separate code bases?
  • What protocol should be used to communicate between services?

180 days and beyond:

• Stand up a new hosting platform for the application in AWS using the decided upon deployment and hosting platforms. Begin migrating components of the existing application from Heroku to.the new platform.
• Take on Pager Duty shifts for the Infrastructure stack.
• Build out the appropriate monitoring and alerting.
• Continue iterating on the platform to improve SLAs with a focus on:
  • Improving monitoring and alerting as new features are released
  • Improving scaling reaction times while keeping costs in check.
  • Improved security.
  • Developer experience and acceleration of release times.
• Stand up new infrastructure and deployments as needed for other teams, such as Security and deliverability teams.

Future projects you may work on:

• Stand up a parallel self-hosted Clickhouse deployment to reduce Cloud Costs.
• Stand up an ML Infrastructure for total lifecycle management.

Why this role might be for you:

• You are comfortable working with another Infrastructure Engineer who may have different opinions from you.
• You're comfortable working with a team of other engineers who will not be as familiar with these technologies as you are. You can support them and provide guidance.
• You can take loosely defined objectives and develop appropriate proposals and architectures.
• You have or are excited to work in a fast-paced startup environment.
• You're excited about conducting research and experimenting with new technologies.
• You can disagree and commit.

Why this role might not be for you:

• Not a traditional 9-to-5 position.
• Need to manage multiple priorities and stakeholders.
• Must be comfortable with rapid iteration and frequent context switching.
• High expectations for both speed and quality.
• Must navigate complex organizational dynamics.

Why beehiiv?

• Bias towards action: Our first impulse is to act. We don't get bogged down in unnecessary processes or bullsh**t. Perfection is the enemy of progress.
• Ownership mentality: This company is ours. We go the extra mile because that's what owners do. Every day, people step up to take on tasks outside of their responsibilities and do whatever it takes for us to succeed.
• Building is in our DNA: We are obsessed with improving every aspect of our platform (and ourselves). Whether it's our product, support, or partnerships, we never stop working to improve it.
• We answer to our users: Nothing matters more than serving our users. If our users fail, we fail.
• Ego comes second, but winning comes first: We put our egos aside to work collaboratively and build something special. It doesn't matter who's idea or who's vision, we're here to create the best outcome. We're here to win.

We'll take care of you:

• Competitive salary
• Stock Options
• Health, Dental, and Vision Insurance
• 401(k) employer match
• Unlimited PTO (mandatory 10 days per year minimum)
• Annual in-person team retreat
• Unlimited book budget
• Monthly Wellness Days (every third Friday of the month)

---