Chief of Staff

• Being the right hand to Nat and Cameron — anticipating what they need, taking work off their plates, and making sure nothing falls through the cracks across hiring, admissions, school programming, travel, facilities, and communications.

• Driving the hiring pipeline: posting roles, coordinating with recruiters, scheduling interviews, keeping candidate trackers current, and flagging when follow-ups slip.

• Supporting admissions operations: keeping the pipeline and CRM clean, coordinating scheduling between families and the team, and making sure no prospective family goes cold.

• Owning travel and logistics for the team — flights, hotels, dinners, campus visits — and the facilities and vendor details of standing up an NYC campus.

• Drafting and sending communications — internal updates, family logistics, partner and vendor correspondence — in the team's voice.

• Building lightweight systems and processes as the program scales, and using AI aggressively to do the work of a much larger team.

• Waiting for instructions. If you need to be told what needs doing, this isn't the role. You see it, you handle it, you report it done.

• Making decks about executing. We need someone who executes.

• Staying in your lane. The whole point is that you take on whatever the team needs, including the messy, undefined problems that don't have an owner yet.

• Owning program design or family relationships — those belong to the school heads and enrollment. You make everything around them run.

At 6 months, you're the operational glue the founding team can't imagine working without, and Nat and Cameron have visibly more time for the work only they can do. You've built the first real systems and playbooks for how the program operates, replacing scramble with process, and you've earned enough trust to own entire workstreams end to end, not just tasks.

At 12 months, you're demonstrably running operations — owning domains outright, spotting problems before they surface, and taking on scope well beyond the original role.

As the program scales toward 1,000 students and multiple cities, you grow into a senior operations leader — building and running the functions and teams that keep a multi-campus program moving. For the right person, this is the path to COO.

• You have been the operational backbone of a fast-moving team before — chief of staff, executive assistant to a founder, startup ops, venture, or a founder's right hand. The title matters less than the proof that you kept a complex operation running when there was no playbook.

• You are exceptionally detail-oriented and proactive. Nothing falls through the cracks, and you don't wait to be told.

• You communicate clearly and quickly, in writing and in person, and you can represent the program to families, vendors, and partners.

• You are AI-forward. You use AI tools daily and instinctively reach for them to do more with less. This is non-negotiable.

• You are energized by ambiguity and growth, and you genuinely want to grow into a senior operations or COO role rather than stay an individual contributor forever.

• You are located in or willing to relocate to New York, NY.

• You are legally authorized to work in the United States.

• Experience in a startup, venture, or high-growth environment where you wore many hats.

• Experience with CRM and project-management tools (HubSpot, Notion, Linear, or similar).

• Background in education, edtech, or programs that work with families and students.

• A track record of building processes and systems from scratch, not just running existing ones.