Deputy Chief of Staff, Founders Office

This is not a standard Operations or Executive Assistant to a Founder or role, nor is it a strategic think tank role. It is an execution role.

Our client is an AI-powered services company in the financial data space. They build content-curation and data systems for US-based unicorn fintechs and Mag-7 data infrastructure providers. The stakes are high. The pace is unreasonable for most. The standards are binary: the system works, or it doesn't.

This is not an Operations role. This is not an Executive Assistant role. This is not a think tank role. It is an execution role that builds.

We are looking for a Force Multiplier Who Builds. Your job is to take the intent of the CEO and Chief of Staff and convert it into operational infrastructure — systems, workflows, dashboards, and reporting cadences that make the business run.

You don't just manage projects. You build the machine.

The Trade-Off

What you give:

• Your full focus, 6 days a week, including weekend coverage. Flexible schedule, no fixed shifts — but the work doesn't stop Friday.
• Your ego. You will be corrected often. Your systems will be rebuilt. Your assumptions will be challenged daily.
• Your comfort zone. You will architect solutions for problems you've never seen before, across departments you've never worked in.

What you get:

• A PhD in Scaling. You will sit in executive meetings, see how technical and operational decisions drive business outcomes, and learn how a high-growth services business is built from the inside.
• Operational and strategic skill growth in 12 months that would take 5 years at a normal job.
• Direct feedback loops with the CEO and Chief of Staff. If your aspiration is to lead a department or company someday, this is where you learn how — by doing, not observing.

The Scope (What You Will Actually Build)

1. Systems Architect & Ops Infrastructure (80%)

• This is your core. When the CEO says Fix Recruitment, you don't make a Trello board. You build the pipeline — the intake form, the automated routing, the status dashboard, the reporting cadence, the Slack notifications. You ship it in days, not weeks.
• Workflow Infrastructure: Build operational systems from scratch — CRM pipelines, lead routing logic, forecasting frameworks, tracking dashboards, reporting cadences. If it doesn't exist and it should, you create it.
• Tool Integration & Automation: Connect Notion, Slack, Airtable, Google Sheets, Salesforce, HubSpot, and whatever else the business runs on. If a process is manual and repeatable, you automate it — using Zapier, Make, Google Apps Script, Python, or whatever ships fastest.
• Data Ops & Reporting: Build dashboards executives actually use. Write SQL when needed. Work with finance on revenue realization, pipeline forecasting, and P&L visibility. You don't wait for the data team — you are the data layer for the executive office.
• Cross-Departmental System Building: Every department has goals. Most don't have systems that track them. You build the tracking, the cadence, and the accountability infrastructure — then connect them so the Founders Office has a single view across all departments.

2. The Operator (20%)

• Meeting ROI: You own the agenda and the follow-up. No meeting ends without distinct owners, deadlines, and deliverables logged into the system you built.
• Shadow & Synthesis: You sit in high-level discussions. Your output is not notes — it's a synthesized Action Plan with dependencies mapped and blockers flagged. You translate Executive Vision into Staff Orders.
• Department Tracking: Track every department against their one focus metric — daily, weekly, quarterly. If they're behind and haven't flagged it, you flag it. If they're blocked, you unblock them.

The DNA (Who Survives Here)

• Builder, Not Maintainer: You see an undefined problem and your instinct is to build the system that solves it — not to ask for a playbook. You default to creation over coordination.
• High Speed, Low Drag: You don't ask How do I do this — you say I built three versions, which one ships
• Data Over Feelings: Direct feedback is a gift. You don't take correction personally; you take it professionally and fix the system.
• Tech-Native & AI-Fluent: You use Claude, ChatGPT, Perplexity, Cursor, and Copilot as daily force multipliers — not buzzwords on your CV. You use different LLMs for different jobs. You're pragmatic about technology, not religious. If a tool doesn't exist, you build it. If an API is garbage, you wrap it.
• Cross-Functional Operator: You've worked across sales, marketing, finance, ops, or delivery — and you're comfortable jumping into any department's problems. You don't live in one silo.
• Discretion is Currency: You will see sensitive data — cap tables, client contracts, internal performance data. A single breach of trust is a single-strike exit.

The Profile (Two Archetypes Thrive Here)

1. The Ops Person Who Builds Systems. You've been running revenue operations, growth, GTM strategy, or business ops — but you taught yourself to code or automate because you got tired of waiting for engineering. You see business problems first, then build technical solutions. You've set up CRM pipelines, forecasting frameworks, lead routing, compensation tracking, or demand-gen engines. Your stack: Salesforce, HubSpot, Google Apps Script, Python, SQL, plus whatever no-code/low-code platform gets the job done.

2. The Strategy Consultant Who Executes. You come from management consulting, strategy, or FP&A — but you're bored of decks and want to ship the systems you used to recommend. You have the structured thinking, the analytical rigor, and the executive communication skills — now you want to apply them in a company that moves at startup speed.

Both share this: You are the person your friends call when they need to figure something out. You are in a season of life where building skills and impact matters more than a comfortable title. You want ownership, not comfort. You want to see the systems you build get used by hundreds of people — not sit in a slide deck.

What You've Done Before (Evidence, Not Titles)

We care about what you built, not what you were called. At least 3 of these should describe you:

• Built a CRM pipeline, reporting dashboard, forecasting model, or operational workflow from zero — not optimized one that already existed
• Set up a new department, function, or team's operational infrastructure from scratch
• Worked across 3+ functional areas (sales, marketing, finance, ops, delivery) in the same role
• Reported to or worked directly with C-level executives or Founders
• Built automations or integrations between business tools (Zapier, Make, AppsScript, APIs)
• Used SQL, Python, or BI tools to build reporting that executives used for decisions
• Thrived in a high-growth or early-stage company (2x–10x scaling in headcount or revenue)
• Created executive-level reports, one-pagers, or briefings that drove resource-allocation decisions

The Filter (Do Not Apply If...)

• You have only maintained or optimized existing systems — you have never built one from scratch
• You describe yourself as detail-oriented but have never shipped an operational system
• You are looking for a 9-to-5 with clear boundaries
• Your technical skills are limited to Microsoft Office Suite
• You need to be told what to do — this role requires you to figure out what needs doing.
• You are uncomfortable with direct, frequent feedback and having your work rebuilt