Role

Behind EAS are web services and infrastructure that serve both developers and their end users. Developers rely on EAS to build their own apps and making our backend infrastructure for building apps, running CI/CD workflows, serving app updates, and web hosting reliable is one of the ways we build developer trust. We're looking for engineers early in their career to come work with us on EAS's infrastructure and help us let every engineer and agent ship a service safely, from pull request to production.

What You’ll Do

• Join EAS’s infrastructure team as an early-career engineer, working alongside a senior engineer.
• Learn to design, build, and operate the backend infrastructure behind our developer-facing services, including the deploy path, CI, and preview environments.
• Build internal improvements that help us ship services faster, cut CI time and cost, and make Expo a better place to work.
• Write software that runs correctly and efficiently, and own its uptime and performance.
• Own the code you write: add tests and monitoring, and join your team’s on-call rotation.

What You’ll Bring

• You’re curious about containers, CI pipelines, and writing small services, and you have some experience with each.
• You’ve built something real, end to end: a service or pipeline that people actually use.
• You’re comfortable with continuous integration at scale and with deploying to Kubernetes.
• You have cloud experience. We use Google Cloud, but deep experience with AWS, Azure, or a home lab carries over well.
• You have the knowledge taught in courses on operating systems, networks, databases, and distributed systems, whether you learned it in school or on your own.
• You’ve gone deep on at least one low-level area: containers, CI internals, Kubernetes deploys, or infrastructure as code.
• You’re comfortable writing code and want to write a lot more of it.
• Bonus: experience with GitHub Actions internals or Terraform.
• You make sound decisions on your own and bring new, effective ideas to improve how app software is built and distributed.
• You write services that stay healthy long after you’ve moved on to your next project.
• You respond quickly to teammates so Expo keeps making fast, steady progress.
• You get yourself unstuck and help others get unstuck too.
• You know why well-designed tools and APIs matter, and you ship well-designed, well-tested features quickly.
• You communicate ideas and code clearly through documentation, GitHub reviews, blog posts, and other writing.
• You understand the problems and goals of Expo’s users and think about them every day.
• You use agents for real work every day, and you can explain what you checked before you trusted the result.
• You get better every week. You’re curious and focused, and you own what you run.