Senior Manager, Strategy & Operations
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Key content:
- Intro about CAIS: description of org, achievements. Could be "About the role"? Actually "About the role" maybe includes description of role and org. The posting includes "The Center for AI Safety (CAIS) is a leading research and advocacy organization...". That's about org. Could be placed under "About the role" or maybe a separate "About the organization". But only allowed headings are listed. We could put that under "About the role". Or we could omit if not needed? The instruction: include a section ONLY when the posting has real, specific content for it. So we need to decide which sections have content.
We have:
- About the role: description of role, what they do, note about Public Engagement, etc. So we can put that.
- Responsibilities: bullet list of "What You'll Do". That's responsibilities.
- Requirements: maybe "What We're Looking For" (experience, track record). Could be split into Requirements and Qualifications? The posting has "What We're Looking For" with bullet points of experience, track record, etc. Also "Nice to have". Could treat "What We're Looking For" as Requirements/Qualifications. We need to decide.
- Skills: maybe list of skills like data analysis, program management, influencing, etc. Could be extracted.
- Benefits: explicit list: Health insurance, 401K + 4% matching, Unlimited PTO, Lunch and dinner at the office, Annual Professional Development Stipend, Access to top talent.
- Pay: "$150,000 - $200,000 a year"
- Schedule: not mentioned. So we should not include Schedule section.
We must not include sections with placeholder like "commensurate with experience". Not present.
We need to output only HTML fragment, no /. Use for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like achievements, etc.
Let's extract substantive content:
Intro paragraph: "The Center for AI Safety (CAIS) is a leading research and advocacy organization focused on mitigating societal-scale risks from AI. Some of our past achievements include: releasing the most widely used measure of AI capabilities used by all major AI companies, running a large compute cluster to facilitate AI safety research which has been cited over 24,000 times, and publishing a global statement on AI Risk signed by Geoffrey Hinton, Yoshua Bengio and top AI CEOs. CAIS is scaling quickly across Research, Public Engagement, and Policy, and our operational infrastructure needs to keep pace."
That's about org.
Then "The RoleWe're looking for a Senior Manager to join our Special Projects team and work across a variety of high-priority initiatives for CAIS. Special Projects sits close to leadership and takes on the highest-priority, least-defined problems across the organization: the ones without an obvious owner, that span multiple teams, or that need someone to build the plane while flying it.This is a generalist role by design. You might spend a quarter building the operational backbone for a new program, the next helping scope and launch a go-to-market plan for an initiative, and the one after that designing a process that lets a team run a function on its own going forward. What stays constant is the standard: fast, structured, data-informed execution, and full ownership from A to Z. A Note on This OpeningThis particular req is likely to be dedicated to our Public Engagement team, which runs a growing slate of campaigns, programs, and partnerships in service of one mission: make AI safety legible, urgent, and personal for every American. In this capacity, you'd work closely with the Head of Public Engagement to become the operational backbone behind that work, translating ambitious goals into clear workstreams, owners, milestones, and measures of success, and building the mechanisms that let programs repeat and scale so key work doesn't depend on any one person holding all the pieces together. Illustrative scope on this team includes standing up the operating model for a new creator program, turning an emerging opportunity into a cross-functional execution plan, building the systems used to prioritize investments and measure impact, or coordinating a complex initiative spanning researchers, communications, agencies, partners, and leadership.As with all Special Projects roles, the specific focus may shift based on organizational need, but candidates should be excited about the possibility of this placement. What Unites the WorkWhether focused on Public Engagement or another priority area, the core of the job is the same: bring structure to ambiguity, establish accountability, and keep high-priority work moving without requiring close supervision. You should be equally comfortable structuring an ambiguous problem, influencing decisions, and getting into the details required to make a program work."
Then "Who We're Looking ForYou've operated as the connective tissue in a fast-moving organization — someone who can take an ambiguous mandate, build the plan, and pre-wire the decisions that keep research, policy, communications, creative teams, agencies, and outside partners moving in lockstep. You are a strong generalist who can enter an unfamiliar problem space, understand what matters quickly, and build a path from an ambitious goal to a concrete outcome.Your specific background may look different. What matters most is a track record of independently owning complex, multi-stakeholder initiatives end-to-end and building systems that make an organization more effective over time."
Then "What You'll Do" bullet list.
Then "What We're Looking For" bullet list (experience etc). Then "Nice to have:" bullet list.
Then Pay and Benefits.
We need to map to sections.
Potential sections:
- About the role: could include intro about CAIS and role description (the first paragraphs). Might be too long but okay.
- Responsibilities: the "What You'll Do" list.
- Requirements: maybe the "Who We're Looking For" paragraph plus the "What We're Looking For" bullet list (experience). Could split into Requirements and Qualifications but we have both headings allowed. We could put "Requirements" for mandatory experience, and "Qualifications" for nice-to-have? Or "Skills" for skillset.
Better: Use "Requirements" for the bullet list under "What We're Looking For" (mandatory). Use "Qualifications" for the "Nice to have:" list. Use "Skills" for skill-based bullet points like data analysis, program management, influencing, etc. But we need to avoid duplication.
Let's extract skill-based points from the "Who We're Looking For" paragraph and the "What We're Looking For" bullet list.
From "Who We're Looking For": operated as connective tissue, can take ambiguous mandate, build plan, pre-wire decisions, strong generalist, enter unfamiliar problem space, understand what matters quickly, build path from ambitious goal to concrete outcome, track record of independently owning complex multi-stakeholder initiatives end-to-end, building systems that make organization more effective over time.
From "What We're Looking For": 4-6 years experience in management consulting, investment banking, business strategy, GTM strategy, program management, or strategy/operations role at high-growth company; track record of taking projects from ambiguous start to finished outcome with limited guidance, managing complex multi-stakeholder programs and influencing senior stakeholders without direct authority; comfortable moving across very different problems and picking up context quickly, rather than specializing narrowly; strong with data: can structure analysis, build model, use it to drive decision, not just report a number; skilled at turning strategy into concrete processes and execution plans, with demonstrated systems thinking: build repeatable mechanisms, not one-off docs; excellent program management and operational judgment: know how much process a problem needs, and when process will simply slow things down; experience scaling a team, function, or program, and/or launching something into market; bias toward speed and high bar for quality: ship 80%-right plan this week and iterate than wait for perfect next month; communicate excellently, in writing and in person, can distill complexity and trade-offs for leadership and non-specialist audiences; consistently good judgment under uncertainty, making sound decisions with incomplete information and knowing when to move quickly, investigate further, or escalate; care genuinely about AI safety and CAIS's mission, willingness to develop deep domain knowledge.
Nice to have: prior experience in startup, scale-up, or other fast-moving, resource-constrained environment; experience working directly with executive or founder-level stakeholders; SQL or other data-querying experience.
Thus we can categorize:
- Requirements: the bullet list under "What We're Looking For" (mandatory). Could also include the "Who We're Looking For" paragraph as prose.
- Qualifications: Nice to have bullet list.
- Skills: maybe we can extract skill-based bullet points like data analysis, program management, influencing, systems thinking, etc. But we already have those in Requirements. Could still have a Skills section summarizing key skills: data analysis, program management, influencing, systems thinking, communication, judgment under uncertainty, etc. However we must not invent or summarize away detail; we can list them as they appear.
But we have to avoid duplication; but it's okay if same content appears in multiple sections? Probably better to avoid duplication but not strictly prohibited. However we should preserve all substantive information; we can include it in multiple sections if it's naturally part of each. But we risk being redundant. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should aim for clarity.
Simplify: Use sections:
- About the role: include intro about CAIS and role description (the paragraphs before responsibilities). Could be a
with that text.
- Responsibilities:
of "What You'll Do" items.
- Requirements: of mandatory experience/qualifications (the "What We're Looking For" bullet list). Also maybe include the "Who We're Looking For" paragraph as before list.
- Qualifications:
of nice-to-have items.
- Benefits: of benefits.
- Pay: with salary range.
We should not include Schedule.
We need to ensure we don't include boilerplate like EEO etc. Remove that.
Now craft HTML.
We need to be careful with HTML escaping: no special characters that need encoding? We can include apostrophes etc. It's fine.
Let's write.
First, About the role section:
About the role
The Center for AI Safety (CAIS) is a leading research and advocacy organization focused on mitigating societal-scale risks from AI. Some of our past achievements include: releasing the most widely used measure of AI capabilities used by all major AI companies, running a large compute cluster to facilitate AI safety research which has been cited over 24,000 times, and publishing a global statement on AI Risk signed by Geoffrey Hinton, Yoshua Bengio and top AI CEOs. CAIS is scaling quickly across Research, Public Engagement, and Policy, and our operational infrastructure needs to keep pace. We're looking for a Senior Manager to join our Special Projects team and work across a variety of high-priority initiatives for CAIS. Special Projects sits close to leadership and takes on the highest-priority, least-defined problems across the organization: the ones without an obvious owner, that span multiple teams, or that need someone to build the plane while flying it. This is a generalist role by design. You might spend a quarter building the operational backbone for a new program, the next helping scope and launch a go-to-market plan for an initiative, and the one after that designing a process that lets a team run a function on its own going forward. What stays constant is the standard: fast, structured, data-informed execution, and full ownership from A to Z. A Note on This Opening: This particular req is likely to be dedicated to our Public Engagement team, which
- for any list of duties/requirements/benefits. Use
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like achievements, etc. Let's extract substantive content: Intro paragraph: "The Center for AI Safety (CAIS) is a leading research and advocacy organization focused on mitigating societal-scale risks from AI. Some of our past achievements include: releasing the most widely used measure of AI capabilities used by all major AI companies, running a large compute cluster to facilitate AI safety research which has been cited over 24,000 times, and publishing a global statement on AI Risk signed by Geoffrey Hinton, Yoshua Bengio and top AI CEOs. CAIS is scaling quickly across Research, Public Engagement, and Policy, and our operational infrastructure needs to keep pace." That's about org. Then "The RoleWe're looking for a Senior Manager to join our Special Projects team and work across a variety of high-priority initiatives for CAIS. Special Projects sits close to leadership and takes on the highest-priority, least-defined problems across the organization: the ones without an obvious owner, that span multiple teams, or that need someone to build the plane while flying it.This is a generalist role by design. You might spend a quarter building the operational backbone for a new program, the next helping scope and launch a go-to-market plan for an initiative, and the one after that designing a process that lets a team run a function on its own going forward. What stays constant is the standard: fast, structured, data-informed execution, and full ownership from A to Z. A Note on This OpeningThis particular req is likely to be dedicated to our Public Engagement team, which runs a growing slate of campaigns, programs, and partnerships in service of one mission: make AI safety legible, urgent, and personal for every American. In this capacity, you'd work closely with the Head of Public Engagement to become the operational backbone behind that work, translating ambitious goals into clear workstreams, owners, milestones, and measures of success, and building the mechanisms that let programs repeat and scale so key work doesn't depend on any one person holding all the pieces together. Illustrative scope on this team includes standing up the operating model for a new creator program, turning an emerging opportunity into a cross-functional execution plan, building the systems used to prioritize investments and measure impact, or coordinating a complex initiative spanning researchers, communications, agencies, partners, and leadership.As with all Special Projects roles, the specific focus may shift based on organizational need, but candidates should be excited about the possibility of this placement. What Unites the WorkWhether focused on Public Engagement or another priority area, the core of the job is the same: bring structure to ambiguity, establish accountability, and keep high-priority work moving without requiring close supervision. You should be equally comfortable structuring an ambiguous problem, influencing decisions, and getting into the details required to make a program work." Then "Who We're Looking ForYou've operated as the connective tissue in a fast-moving organization — someone who can take an ambiguous mandate, build the plan, and pre-wire the decisions that keep research, policy, communications, creative teams, agencies, and outside partners moving in lockstep. You are a strong generalist who can enter an unfamiliar problem space, understand what matters quickly, and build a path from an ambitious goal to a concrete outcome.Your specific background may look different. What matters most is a track record of independently owning complex, multi-stakeholder initiatives end-to-end and building systems that make an organization more effective over time." Then "What You'll Do" bullet list. Then "What We're Looking For" bullet list (experience etc). Then "Nice to have:" bullet list. Then Pay and Benefits. We need to map to sections. Potential sections: - About the role: could include intro about CAIS and role description (the first paragraphs). Might be too long but okay. - Responsibilities: the "What You'll Do" list. - Requirements: maybe the "Who We're Looking For" paragraph plus the "What We're Looking For" bullet list (experience). Could split into Requirements and Qualifications but we have both headings allowed. We could put "Requirements" for mandatory experience, and "Qualifications" for nice-to-have? Or "Skills" for skillset. Better: Use "Requirements" for the bullet list under "What We're Looking For" (mandatory). Use "Qualifications" for the "Nice to have:" list. Use "Skills" for skill-based bullet points like data analysis, program management, influencing, etc. But we need to avoid duplication. Let's extract skill-based points from the "Who We're Looking For" paragraph and the "What We're Looking For" bullet list. From "Who We're Looking For": operated as connective tissue, can take ambiguous mandate, build plan, pre-wire decisions, strong generalist, enter unfamiliar problem space, understand what matters quickly, build path from ambitious goal to concrete outcome, track record of independently owning complex multi-stakeholder initiatives end-to-end, building systems that make organization more effective over time. From "What We're Looking For": 4-6 years experience in management consulting, investment banking, business strategy, GTM strategy, program management, or strategy/operations role at high-growth company; track record of taking projects from ambiguous start to finished outcome with limited guidance, managing complex multi-stakeholder programs and influencing senior stakeholders without direct authority; comfortable moving across very different problems and picking up context quickly, rather than specializing narrowly; strong with data: can structure analysis, build model, use it to drive decision, not just report a number; skilled at turning strategy into concrete processes and execution plans, with demonstrated systems thinking: build repeatable mechanisms, not one-off docs; excellent program management and operational judgment: know how much process a problem needs, and when process will simply slow things down; experience scaling a team, function, or program, and/or launching something into market; bias toward speed and high bar for quality: ship 80%-right plan this week and iterate than wait for perfect next month; communicate excellently, in writing and in person, can distill complexity and trade-offs for leadership and non-specialist audiences; consistently good judgment under uncertainty, making sound decisions with incomplete information and knowing when to move quickly, investigate further, or escalate; care genuinely about AI safety and CAIS's mission, willingness to develop deep domain knowledge. Nice to have: prior experience in startup, scale-up, or other fast-moving, resource-constrained environment; experience working directly with executive or founder-level stakeholders; SQL or other data-querying experience. Thus we can categorize: - Requirements: the bullet list under "What We're Looking For" (mandatory). Could also include the "Who We're Looking For" paragraph as prose. - Qualifications: Nice to have bullet list. - Skills: maybe we can extract skill-based bullet points like data analysis, program management, influencing, systems thinking, etc. But we already have those in Requirements. Could still have a Skills section summarizing key skills: data analysis, program management, influencing, systems thinking, communication, judgment under uncertainty, etc. However we must not invent or summarize away detail; we can list them as they appear. But we have to avoid duplication; but it's okay if same content appears in multiple sections? Probably better to avoid duplication but not strictly prohibited. However we should preserve all substantive information; we can include it in multiple sections if it's naturally part of each. But we risk being redundant. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." It doesn't forbid duplication, but we should aim for clarity. Simplify: Use sections: - About the role: include intro about CAIS and role description (the paragraphs before responsibilities). Could be a
with that text. - Responsibilities:
- of "What You'll Do" items.
- Requirements:
- of mandatory experience/qualifications (the "What We're Looking For" bullet list). Also maybe include the "Who We're Looking For" paragraph as
before list. - Qualifications:
- of nice-to-have items.
- Benefits:
- of benefits.
- Pay:
with salary range. We should not include Schedule. We need to ensure we don't include boilerplate like EEO etc. Remove that. Now craft HTML. We need to be careful with HTML escaping: no special characters that need encoding? We can include apostrophes etc. It's fine. Let's write. First, About the role section:
About the role
The Center for AI Safety (CAIS) is a leading research and advocacy organization focused on mitigating societal-scale risks from AI. Some of our past achievements include: releasing the most widely used measure of AI capabilities used by all major AI companies, running a large compute cluster to facilitate AI safety research which has been cited over 24,000 times, and publishing a global statement on AI Risk signed by Geoffrey Hinton, Yoshua Bengio and top AI CEOs. CAIS is scaling quickly across Research, Public Engagement, and Policy, and our operational infrastructure needs to keep pace. We're looking for a Senior Manager to join our Special Projects team and work across a variety of high-priority initiatives for CAIS. Special Projects sits close to leadership and takes on the highest-priority, least-defined problems across the organization: the ones without an obvious owner, that span multiple teams, or that need someone to build the plane while flying it. This is a generalist role by design. You might spend a quarter building the operational backbone for a new program, the next helping scope and launch a go-to-market plan for an initiative, and the one after that designing a process that lets a team run a function on its own going forward. What stays constant is the standard: fast, structured, data-informed execution, and full ownership from A to Z. A Note on This Opening: This particular req is likely to be dedicated to our Public Engagement team, which