Clover Health
Technical Chief of Staff to the CTO
Remote · posted 2026-11-16 · listed from another job board
Source: REMOTE_RSS
At a glance
- Workplace
- Remote
- Location
- Remote
- Seniority
- Executive
- Skills
- AI
- Posted
- 2026-11-16
About the job
At Clover, the Business Enablement team leads our technological advancement while ensuring robust security and compliance. We deliver user-friendly corporate applications, manage complex data ecosystems, and provide efficient tech solutions across the organization. Our goal is simple: we make it easy for the business to do what’s right for Clover.
We’re hiring a Technical Chief of Staff with a background in software engineering who has expanded into product, consulting, or organizational leadership. You’ve shipped production software and still read code, investigate systems, and form independent technical opinions. You’ll spend about 10–20% of your time on hands-on technical work, using that experience to inform decisions across Clover’s technology organization.
You’ll help teams turn requests from across the business into practical next steps: understand the underlying need, assess existing capabilities, narrow the scope, and find the right owner. You’re outgoing and gregarious. You seek people out, build relationships, and earn trust by explaining priorities and constraints and following through.
You’ll lead and develop a small team of portfolio managers, technical program managers, and delegated intake owners. Working with product and engineering leaders, you’ll make decisions within agreed authority and bring consequential or unresolved choices to the CTO with a clear recommendation.
As a Technical Chief of Staff, you will:
- Draw on your engineering experience to test assumptions: read code, inspect an API, trace a data flow, or build a prototype. Make decisions within agreed authority and bring consequential or unresolved choices to the CTO with evidence and a recommendation. Partner with the CEO’s office when business priorities affect technology commitments.
- Work as the public face of technology. Help business partners, managers and directors turn requests into work worth doing. Understand the outcome they need, examine existing capabilities, and find the smallest useful solution. Combine, narrow, defer, or advance requests, giving people a clear owner and next step.
- Seek out collaborators and stakeholders across the business, listen to their concerns, and build trust through candid conversations about priorities, capacity, and constraints. Offer practical options and follow up before they need to chase you.
- Develop portfolio managers, TPMs, and delegated intake owners by giving them meaningful decisions to make, coaching their judgment, and helping them take ownership of their areas.
- Work with engineering leaders and TPMs to keep commitments grounded in capacity, dependencies, and vendor readiness. Step in when a delivery needs help, resolve the immediate problem, and establish an owner who can carry it forward.
- Connect engineers with the people who use their systems. Bring in Product for discovery, partner with Special Project Leads on business transformation, and work with other technical leaders on shared dependencies.
- Use AI to pull together evidence from the work underway, helping leaders see progress, blockers, and decisions that need their attention. Check the conclusions against source material and automate repetitive reporting.
Success in this role looks like:
- First 30 days: You’ve resolved or advanced real requests and delivered an early improvement for a business partner. You and the CTO have agreed on decision boundaries, your team knows its responsibilities, and you’ve established a baseline for request turnaround and unresolved ownership.
- First 90 days: You and your team handle agreed intake areas with less CTO intervention. You can point to improvements accepted by business owners, faster request resolution, and fewer requests stalled without an owner or decision. Partners know where their requests stand and what happens next.
- Longer term: Your team makes more decisions independently, and recurring gaps have enduring owners. Delivery owners meet agreed commitments more consistently, stakeholders spend less time chasing updates, and the CTO spends less time reconstructing context or coordinating follow-through.
You should get in touch if:
- You’ve shipped production software as an engineer and expanded into product, consulting, operations, or leadership. You still enjoy digging into unfamiliar systems and use that technical depth to make better decisions.
- You’re outgoing and gregarious and known to collect allies and partners. You seek people out, listen to operators, and build relationships across teams and levels.
- You can show how you turned an ambiguous request into a practical result, whether you narrowed the scope, reused an existing capability, or uncovered a problem that needed more investigation.
- You’ve developed people by delegating meaningful decisions and helping them build the judgment to work with greater independence.
- You’ve maintained trust through difficult priority or resource decisions. You explain the reasoning, offer alternatives,