Engineering Manager

Cboe Global Markets•Chicago, IL

15d•Hybrid

About The Position

At Cboe Global Markets, we inspire our people to solve complex challenges together because what we do matters. We provide the financial infrastructure that powers the global economy. As a leading provider of market infrastructure and tradable products, Cboe delivers cutting-edge trading, clearing and investment solutions to market participants around the world. We’re building meaningful ways to support professional and personal development while strengthening the trust we’ve earned as a global market leader. Our teams are empowered to share ideas, actively pursue them and bring on a challenge. As champions of internal mobility and access to opportunity, we encourage our people to “go for it” and equip our managers with the training to coach their teams to the next level. We strive to provide employees a safe space to network, share ideas and create opportunities. To support strong partnership and team connection, this role follows a four day in office work model. Cboe Clear U.S. (CCUS) is a regulated clearinghouse. We clear the event contracts and prediction markets listed on Cboe's exchanges, and we are building toward tokenized collateral, 24x7 operation, and the infrastructure that carries traditional finance onto DeFi rails. CCUS Software Engineering is a high trust environment. Failure leads to inquiry rather than blame. Working across team boundaries is expected rather than tolerated. We solve the problem, then we write the code. Design documents and architecture decision records come first. The engineers we value most close their feedback loop. They write tests, and they instrument what they ship so it fails fast, explains itself in production, leaves an audit trail and rolls back cleanly. The Engineering Manager leads the software engineers who build our clearing systems. You would lead an existing team, help shape the larger one it becomes, and how the work is divided. The systems your teams own are what let Cboe list and clear new products, so delivery dates here move business dates. We expect our managers to carry real domain knowledge in clearing and to stay close to system design.

Requirements

Owning delivery across the full software lifecycle, from design and code review standards through production support
Experience managing software engineers, including direct performance management and hiring
A record of making the people around you better, with specific engineers you can point to
Delivering complex work on a date that mattered
Partnering with product management on roadmap, scope and sequencing
Working knowledge of clearing, post-trade processing or capital markets
Architecture judgment and a written-first working style, with the depth to guide a design, challenge a proposal, and author the decision records behind both
Minimum Work Experience: 10+ years in engineering, with 3+ years managing engineers
Minimum Education: Bachelor's in Computer Science or a related discipline, or equivalent practical experience
Candidates must be legally authorized to work in the United States without the need for employer sponsorship now or in the future.

Nice To Haves

Experience establishing code review practices and coding standards across more than one team
Hands-on development depth in Java
Shaping team boundaries to get the architecture you want rather than the one the org chart hands you
Designing developer tooling and measuring delivery health with metrics such as change lead time and change failure rate
A habit of hiring for range rather than for a single language, since Java is our stack choice but we hire polyglots
The FIX messaging protocol
Cloud platforms including AWS, Azure or GCP
JVM languages such as Clojure, Scala or Kotlin

Responsibilities

Leading and growing a team of software engineers, including performance management and hiring.
Minimizing cognitive load on your team leads and engineers so their attention stays on solving domain problems in code.
Partnering with the quality engineering organization, which owns QA and test engineering, on shared delivery goals.
Applying domain knowledge of clearing and post-trade processing to guide design decisions rather than delegating them.
Aligning the roadmap with product management against real delivery capacity.
Reducing friction between your engineers and the product, operations and partner teams they depend on.
Shaping team boundaries and ownership so the organization produces the architecture we intend, applying Conway's law deliberately rather than inheriting its side effects.
Owning the architecture decision records for your teams' services and keeping them current as designs change.
Ensuring code review practices and coding standards are enforced consistently across teams.
Improving deployment frequency, change lead time, change failure rate and time to restore service.
Running the on-call and production support model for your teams' services.