Engineering Manager, Infrastructure
San Francisco
$307k–$352k a yearOn-siteLead & above
Job details
- San Francisco
- On-site
- $307k–$352k a year (posted by the company)
- Full-time · Lead & above
- Engineering
- Posted 3 months ago
Sponsorship history
Past filings by Kikoff in public government data. Not a promise of sponsorship.
- Filed 7 H-1B LCAs in FY2025
Full job description
Kikoff: The Fintech Powering Financial Security at Scale
Kikoff is a profitable, pre-IPO fintech company on a mission to empower everyone to achieve financial security. With record revenue growth in 2025 and a unicorn valuation, we've built a suite of products that help millions of people build credit, access liquidity, and save money.
We're scaling fast. Join us if you want to build something meaningful and help millions of people move forward financially.
Why Kikoff:
This is a consumer fintech startup, and you will be working with serial entrepreneurs who have built strong consumer brands and innovative products. We value extreme ownership, clear communication, a strong sense of craftsmanship, and the desire to create lasting work and work relationships. Yes, you can build an exciting business AND have real-life real-customer impact.
About the Role
Kikoff's infrastructure team builds the systems that enable engineering teams to move quickly without sacrificing reliability, security, or cost discipline. The team owns five connected areas: Observability, Developer Productivity, Compute Infrastructure, Networking and Storage, and Data Infrastructure.
As Engineering Manager, you will share leadership of Infrastructure and initially lead a focused group of engineers within the team. You will support their growth, help turn ambiguous problems into durable systems, and run infrastructure as a product for Kikoff engineers. The team works across five connected areas, but you will not be expected to manage every engineer or personally own every domain on day one. You will partner with senior ICs and Infrastructure leadership, taking on broader scope as the team grows.
This is a player-coach role. You will stay close to the code, architecture, incidents, and people while senior ICs retain clear technical ownership in their domains. You should be comfortable reviewing code and designs, helping make architecture decisions, and contributing directly when useful. Strong ICs should respect your technical judgment because you understand the work, not because you report on it. This does not mean being the primary engineer across all five areas.
AI is increasing the amount of code and change moving through our systems. You will help build a platform that can absorb that growth without creating more incidents, unsustainable cost, or a team that depends on heroics.
