About this role
Why Join AngelList
We’re solving some of the hardest problems in venture capital and private markets. You’ll work with a team that values precision, urgency, and long-term thinking. If you want to shape how startups are funded and built, this is the place.
About AngelList
We exist to accelerate innovation by increasing the number of successful startups in the world. We do this by building the financial infrastructure that makes it easier for more people to invest in world-changing companies.
AngelList is the nexus of venture capital and the startup community. We support $171B+ in assets and have powered investments into over 13,000 startups—over 300 of which are unicorns. Today, 57% of top-tier U.S. VC deals involve investors on AngelList. While our scale is large, our ambition is larger.
If you're excited to build the future of private markets, come build with us.
Responsibilities:
- Hire, coach, and grow a small team of high-performing engineers, and develop the staff and principal engineers who carry technical standards into other teams.
- Build the platform the whole engineering org runs on: developer platforms, deployment pipelines, observability, and developer tooling.
- Automate infrastructure as code on Kubernetes and AWS, using Pulumi, cdk8s, and ArgoCD.
- Build the harnesses agents execute inside, including sandboxing, audit trails, and rollback against systems that move real money.
- Set the engineering standards for reliability, operability, and architectural coherence, and sequence the quality work that keeps teams shipping quickly over time.
What we’re looking for:
- 12+ years in engineering, including 5+ leading teams.
- A builder who leads. You write clean, well-tested code and have designed and shipped systems end to end, and you want to keep doing that while growing a team.
- Leverage through senior engineers. You've developed staff and principal ICs who make other teams better.
- Systems judgment. You've operated consequential infrastructure before. Kubernetes, AWS, and infrastructure-as-code experience helps, but judgment matters more than familiarity with our exact stack.
- Developer experience as a product. You design infrastructure for the engineers using it rather than just operating it.
- You author the standard. You have a clear point of view on what good infrastructure looks like and set it rather than inheriting it.