Manager, Operations
for each section: About the role, Responsibilities, Requirements, Qualifications?, Skills?, Benefits, Pay. The instructions: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose appropriate headings based on content.
We have "About Us" but that's boilerplate? It's about the organization; maybe we can include as a brief intro? The instruction: do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. The "About Us" is not a heading per the list; but we could include as a
before sections? The instruction: Output ONLY the HTML fragment — no /, no markdown code fences. We can include a
for the About Us description? It's not required but we could include as introductory paragraph. However they said preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the About Us description. It's not a heading but we can put it as a
before sections. Then we have "About The Role" heading; we can make that a
About the role.
Then "What You'll Own" is responsibilities; we can make Responsibilities and list bullet points.
Then "Who You Are: Required" is requirements; we can make Requirements and list bullet points.
Then "Preferred" we could make Preferred Qualifications or just include under Requirements? Better to have separate Preferred Qualifications.
Then "First 90 Days - What Success Looks Like" could be a section maybe "First 90 Days" but not in list; we could treat as part of Responsibilities? But it's substantive; we could make a First 90 Days.
Then Pay: "$85,000 - $97,000 a year" => Pay with
Requirements and list bullet points.
Then "Preferred" we could make Preferred Qualifications or just include under Requirements? Better to have separate Preferred Qualifications.
Then "First 90 Days - What Success Looks Like" could be a section maybe "First 90 Days" but not in list; we could treat as part of Responsibilities? But it's substantive; we could make a First 90 Days.
Then Pay: "$85,000 - $97,000 a year" => Pay with
Preferred Qualifications.
Then "First 90 Days - What Success Looks Like" could be a section maybe "First 90 Days" but not in list; we could treat as part of Responsibilities? But it's substantive; we could make a First 90 Days.
Then Pay: "$85,000 - $97,000 a year" => Pay with
Pay with
. Benefits: list =>
Benefits with .
We should not include Schedule.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes an EEO statement and scam warning at the end; we should remove those. Also the "We understand that not everyone will match..." paragraph is maybe okay to keep? It's not boilerplate; it's encouraging applications; but could be considered application instructions? It's not instructions to apply; it's a statement. Might keep. However the instruction: remove duplicated lines, application instructions. The paragraph "We understand that not everyone will match the above qualifications 100%..." is not an instruction to apply; it's encouraging. I'd keep it as part of maybe a under Requirements or separate.
We also need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the bullet points exactly as given.
Let's extract content.
About Us: "CALSTART is now Catalyst Mobility. We are a mission-driven industry organization focused on transportation decarbonization and clean air for all. For over 30 years, it’s been Catalyst Mobility’s mission to develop, assess, and implement large-scale, zero-emission transportation solutions to mitigate climate change and support economic growth. Catalyst Mobility works with businesses, organizations, governments, and communities to create real-life impact toward clean air and equitable access to clean transportation for all. Catalyst Mobility provides scientific, technical and policy support for regulatory development and clean technology and infrastructure acceleration."
We'll put that as a
.
About The Role: paragraph(s). We'll put as
under About the role heading.
What You'll Own: bullet list. We'll convert each line starting with a bold heading? Actually the text includes headings like "Project Execution & Tracking:" then description. We'll treat each as a list item with maybe sub-bullets? Simpler: each line as
- containing the heading and description.
We need to preserve all detail. Let's copy the bullet points exactly as they appear:
- Project Execution & Tracking: Take ownership of assigned internal projects and programs from intake through close-out, keeping each one moving without daily direction
- Translate the Head of Operations' initiatives into fully structured Monday.com projects - defined phases, tasks, owners, dependencies, and milestones — not just status trackers
- Break ambiguous or loosely defined asks into clear tasks, owners, and deadlines
- Map dependencies and identify critical-path milestones so plans reflect how the work actually has to sequence, not just a task list
- Flag risks, blockers, and dependencies early, and know what belongs in the tracker versus what needs to be raised immediately
- Keeping The Head Of Operations Organized Support with meeting prep, recaps, and follow-through on action items
- Consolidate the status of multiple in-flight projects into a clear, regularly updated view
- Keep all operations projects tracked in Monday.com and connected to the operations dashboard
- Draft correspondence, meeting agendas, status updates, and internal communications as needed
- Keep Microsoft Teams and shared workspaces organized — channels, files, and follow-ups — so nothing gets lost between meetings
- Support with the new Operations SharePoint site creation and keep the information continuously up to date
- Support with optimizing Microsoft tools for collaboration and efficient workflows such as Loop, Teams, and copilot
- Cross-Functional Coordination Serve as a point of coordination across the department's functional areas, making sure handoffs between teams don't stall
- Help prepare and run recurring check-ins and status reviews with functional leads
- Use Teams effectively for day-to-day collaboration — chats, channels, meetings, and file sharing — across a fully remote team
- Process & Documentation Maintain a central library of SOPs, templates, and process documentation
- Apply consistent, repeatable steps for how projects are initiated, tracked, and closed out
- AI-Enabled Efficiency Use Claude and Copilot as working tools, not novelties — applying real prompt engineering skill to draft, analyze, automate, and problem-solve faster
- Identify where AI tools can remove manual steps from recurring operational work, and build those efficiencies rather than waiting to be asked
- Write clear, structured prompts that produce usable output on the first or second pass, for both self-service work and tools built for others
We need to keep the formatting but as list items.
Who You Are: Required bullet list:
- 5+ years of experience managing projects or programs in a professional services, GovCon, or grant-funded environment - building project plans, sequencing dependencies, and driving execution, not just tracking status
- Proven ability to execute independently - you take a task or project with minimal instruction, find your own answers, and get it done without waiting to be told what's next
- Strong Microsoft 365 skills (Excel including pivot tables/formulas, PowerPoint, Teams, SharePoint)
- Hands-on experience building project plans in Monday.com (or a comparable platform) from scratch - phases, dependencies, milestones, and owners — not just updating an existing tracker
- Experience in, or strong working knowledge of, the clean transportation, clean energy, or related mission-driven program space - or comparable program/project delivery in a similarly structured environment - so this person can support client program work if organizational need requires it
- Demonstrated use of AI tools (Claude, Copilot, or similar) for real work product - drafting, analysis, automation, or research - with the prompt engineering skill to get reliable results
- Excellent written and verbal communication - comfortable drafting correspondence and updates for an executive audience and presenting to a large group and leading meetings.
- High discretion and ability to handle confidential organizational information
- Comfortable working in a fully remote environment, with strong self-management and asynchronous communication habits
Preferred bullet list:
- PMP, or equivalent or 3+ years’ direct experience as a PM or PMO in an agile environment
- Lean Six Sigma certification
- Experience supporting an executive or department lead directly
- Experience with dashboarding/BI tools (Power BI or similar)
- Prior program or project management experience within clean transportation, clean energy, sustainability, or a federally/grant-funded program environment
Working Style - This Matters As Much As the Credentials: bullet list (maybe treat as part of Requirements or separate). Could be a section "Working Style". But not in the list of headings; but we could include as
Working Style. It's substantive.
First 90 Days - What Success Looks Like bullet list:
- Independently managing a full slate of assigned operations projects with minimal oversight
- Building and running fully structured Monday.com project plans - dependencies and milestones included - for the Head of Operations' active initiatives
- Operations SharePoint site developed and greater organizational foundation set for the department’s workflows
- Trusted to take a loosely defined problem and turn it into a tracked, moving project on their own
- Actively using Claude and Copilot to speed up drafting, analysis, and routine operational work
Pay: "$85,000 - $97,000 a year"
Benefits bullet list:
- 100% company paid comprehensive health benefits for Medical, Dental, Vision, Short Term Disability, Long Term Disability and Life Insurance
- Retirement plan with generous company contributions
- FSA for Health and Dependent Care
- 3 weeks of vacation time in the first year of employment
- 11 paid company holidays
- paid sick time
- paid family leave
- and more!
We should keep "and more!" as part of last bullet maybe.
We need to exclude EEO statement and scam warning etc.
Now produce HTML.
Structure:
About Us paragraph.
About the role
About The Role paragraph(s).
Responsibilities
- ...
...
Requirements
- ...
...
Preferred Qualifications
- ...
...
Working Style
- ...
...
First 90 Days
- ...
...
Pay
$85,000 - $97,000 a year
Benefits
- ...
...
We should not include Schedule.
Make sure no extra blank lines? It's fine.
Now craft final HTML.
Check for any duplicated lines: we have not included the "We understand that not everyone will match..." paragraph. Should we keep? It's not boilerplate; it's encouraging. Might be considered part of the posting but not a heading. Could be placed as a after Requirements maybe. But the instruction: remove application instructions. This is not an instruction to apply; it's a statement encouraging applications. I'd keep it as a
after Preferred Qualifications maybe under a heading like "Encouragement". But not in list. Safer to keep it as a
after Preferred Qualifications without a heading. However the instruction: "Prefer a few substantive sections over many thin ones." Adding a stray paragraph without heading might be thin. Could incorporate into Requirements as a final paragraph. But it's not a requirement. Might be okay to drop? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Dropping that paragraph would lose substantive information (the encouragement). So
under Requirements or separate. We also need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep the bullet points exactly as given. Let's extract content. About Us: "CALSTART is now Catalyst Mobility. We are a mission-driven industry organization focused on transportation decarbonization and clean air for all. For over 30 years, it’s been Catalyst Mobility’s mission to develop, assess, and implement large-scale, zero-emission transportation solutions to mitigate climate change and support economic growth. Catalyst Mobility works with businesses, organizations, governments, and communities to create real-life impact toward clean air and equitable access to clean transportation for all. Catalyst Mobility provides scientific, technical and policy support for regulatory development and clean technology and infrastructure acceleration." We'll put that as a
. About The Role: paragraph(s). We'll put as
under About the role heading. What You'll Own: bullet list. We'll convert each line starting with a bold heading? Actually the text includes headings like "Project Execution & Tracking:" then description. We'll treat each as a list item with maybe sub-bullets? Simpler: each line as
Working Style. It's substantive. First 90 Days - What Success Looks Like bullet list: - Independently managing a full slate of assigned operations projects with minimal oversight - Building and running fully structured Monday.com project plans - dependencies and milestones included - for the Head of Operations' active initiatives - Operations SharePoint site developed and greater organizational foundation set for the department’s workflows - Trusted to take a loosely defined problem and turn it into a tracked, moving project on their own - Actively using Claude and Copilot to speed up drafting, analysis, and routine operational work Pay: "$85,000 - $97,000 a year" Benefits bullet list: - 100% company paid comprehensive health benefits for Medical, Dental, Vision, Short Term Disability, Long Term Disability and Life Insurance - Retirement plan with generous company contributions - FSA for Health and Dependent Care - 3 weeks of vacation time in the first year of employment - 11 paid company holidays - paid sick time - paid family leave - and more! We should keep "and more!" as part of last bullet maybe. We need to exclude EEO statement and scam warning etc. Now produce HTML. Structure:
About Us paragraph.
About the role
About The Role paragraph(s).
Responsibilities
- ... ...
Requirements
- ... ...
Preferred Qualifications
- ... ...
Working Style
- ... ...
First 90 Days
- ... ...
Pay
$85,000 - $97,000 a year
Benefits
- ... ...
after Requirements maybe. But the instruction: remove application instructions. This is not an instruction to apply; it's a statement encouraging applications. I'd keep it as a
after Preferred Qualifications maybe under a heading like "Encouragement". But not in list. Safer to keep it as a
after Preferred Qualifications without a heading. However the instruction: "Prefer a few substantive sections over many thin ones." Adding a stray paragraph without heading might be thin. Could incorporate into Requirements as a final paragraph. But it's not a requirement. Might be okay to drop? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Dropping that paragraph would lose substantive information (the encouragement). So