Interdisciplinary Research Program Manager
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them.
We need to parse the posting.
Company Description: includes description of Harvard, GSD. That could be "About the role"? Actually "Company Description" is about the organization. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly.
We have:
- Company Description: description of Harvard, GSD. Could be placed under "About the role" maybe? Or maybe we could have a section "About the role" describing the role and organization. The posting includes "Job Description" with details about role. So we could have "About the role" summarizing the role and maybe the organization.
But we must not invent content; we must preserve all substantive information. So we need to include the company description text as is, maybe within a
under a heading like "About the role". However "About the role" might be more about the role itself, but we can include the company description there as part of role context. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which sections to include based on content.
We have:
- Job Description: includes NOTE about term appointment, reporting line, duties, typical duties and responsibilities broken down with percentages, supervisory responsibilities, physical requirements, work environment, additional information (health, vaccine, cover letter/resume required). Also includes "Additional Information" with Standard Hours/Schedule: 17.5 hours per week, expected annual salary range $45,000–55,000, Visa Sponsorship Info, Pre-Employment Screening, Work Format Details, Salary Grade and Ranges, Benefits.
- Qualifications: BASIC QUALIFICATIONS list, ADDITIONAL QUALIFICATIONS AND SKILLS list.
- Benefits: description of benefits.
Thus we can create sections:
- About the role: could combine Company Description and Job Description overview (maybe the first paragraph of Job Description). But we must not duplicate. We'll include the company description as a paragraph under About the role.
- Responsibilities: typical duties and responsibilities (the bullet list with percentages). Also maybe include supervisory responsibilities (none) and physical requirements, work environment? Those could be under Responsibilities or maybe separate but we only have limited headings. Could put them under Responsibilities as part of duties.
- Requirements: could include BASIC QUALIFICATIONS and ADDITIONAL QUALIFICATIONS AND SKILLS (maybe combine as Requirements). Or we could have Requirements and Qualifications separate. The instruction list includes both Requirements and Qualifications as possible headings. We need to decide.
We have BASIC QUALIFICATIONS and ADDITIONAL QUALIFICATIONS AND SKILLS. Those are qualifications. So we could put them under Qualifications heading. Requirements could be things like "must have employment authorization to work in the US, cannot sponsor visa", "must be able to perform typical office tasks", etc. Those are more like requirements. So we can have a Requirements section for those.
- Skills: maybe we could extract skills from qualifications (leadership, facilitation, organizational skills, written/verbal communication, grant writing, etc.) but we already have qualifications. Could also have Skills section for things like "Strong leadership, facilitation, and organizational skills; experience managing collaborative teams and meetings. Excellent written and verbal communication skills, including grant writing and report preparation." But that's already in qualifications. Might be redundant. Better to follow the instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have headings list; we can choose to include only those with real content. We could have:
- About the role
- Responsibilities
- Qualifications (includes basic and additional qualifications)
- Benefits
- Pay (salary range)
- Schedule (hours per week)
We must not create Pay/Schedule/Benefits unless posting actually states them. It does state salary range and hours, and benefits description. So we can include those.
We must not include filler like "commensurate with experience". Not present.
We must remove boilerplate: EEO/Non-Discrimination Commitment Statement, etc. Also remove "Pre-Employment Screening: Identity." maybe not needed? It's not boilerplate but it's a requirement? It says "Pre-Employment Screening: Identity. Work Format Details ..." Might be considered metadata; we could drop it as minor metadata. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can drop Pre-Employment Screening line, Work Format Details, Salary Grade and Ranges maybe? But Salary Grade is metadata; we already have salary range. Could drop Salary Grade line.
We also need to drop "Additional Information Standard Hours/Schedule: 17.5 hours per weekThe expected annual salary range for this position is: $45,000–55,000Visa Sponsorship Information: Harvard University is unable to provide visa sponsorship for this positionPre-Employment Screening: Identity. Work Format Details ..." We'll extract the needed pieces: Standard Hours/Schedule, salary range, visa sponsorship (maybe we can note as requirement). But visa sponsorship info is a requirement: cannot sponsor visa. So we can include that under Requirements.
We also need to drop duplicated lines, application instructions (cover letter and resume required) - that's application instruction, should be removed per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we need to remove the line about cover letter and resume required. Also remove "Please note that to be considered for this position, a cover letter and resume are required with the submission of your application." That's application instruction, remove.
Also remove "EEO/Non-Discrimination Commitment Statement" entirely.
Also remove "Learn more about these and additional benefits on our Benefits & Wellbeing Page." maybe considered boilerplate? It's a link; could be considered navigation; better to remove.
Also remove "For more information about Harvard GSD see: https://www.gsd.harvard.edu/" maybe considered navigation; but it's part of company description; could keep as part of description? It's a link; maybe we can keep it as part of company description but it's a URL; not sure if considered navigation. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That link is navigation; maybe we should drop it. However it's part of company description; but we can drop it as it's just a reference. The company description text before that is fine.
We must preserve all substantive information. So we need to keep the description of Harvard, GSD, etc. We'll keep the textual description but drop the URL.
Now let's extract substantive content.
Company Description paragraph:
"By working at Harvard University, you join a vibrant community that advances Harvard's world-changing mission in meaningful ways, inspires innovation and collaboration, and builds skills and expertise. We are dedicated to creating a diverse and welcoming environment where everyone can thrive. Why join the Harvard Graduate School of Design? The Harvard Graduate School of Design (GSD) educates design, research, and scholarship leaders to make a resilient, just, and beautiful world. The GSD offers degree programs across a range of design disciplines—architecture, landscape architecture, urban planning, urban design, design engineering, and real estate—as well as advanced research programs that cut across these disciplines and a robust public program of lectures, exhibitions, and publications. The immense variety of people, programs, and ideas at the School sustains a vibrant and rich environment for learning, inquiry, and collaboration, unlike any other design school."
We'll keep that as a paragraph under About the role.
Job Description overview (first paragraph before TYPICAL DUTIES):
"NOTE: This position is a Term appointment for up to two years depending on funding. Reporting to the Director of the Center for Green Buildings and Cities, who serves as the project's Principal Investigator, the Interdisciplinary Research Program Manager supports the coordination and success of this interdisciplinary research initiative, working closely with the project's co-PIs. The Program Manager organizes weekly meetings to ensure regular progress updates, cross-team alignment, and timely course corrections, and serves as a central point of communication across the project's three integrated research thrusts: advanced thermal materials, intelligent building-scale systems, and cooperative urban-scale energy management. The Program Manager tracks project metrics and sponsor reporting deadlines, and is responsible for the project's major written outputs, including the annual report to sponsors. In addition to supporting integration across disciplines, the Program Manager supports the PI and co-PIs in developing and maintaining relationships with industry partners, ensuring that practical insights from the field inform the design and scalable deployment of project innovations. The role also coordinates the preparation and submission of proposals for extramural funding, helping to sustain and expand the project's research and implementation efforts. This role is essential to advancing the project's mission of scaling HouseZero®-inspired innovations into interconnected, energy-efficient communities and delivering impactful, real-world solutions to climate challenges."
We can keep that as prose under About the role or Responsibilities? It's more about role description; maybe we put it under About the role as well.
Then we have TYPICAL DUTIES AND RESPONSIBILITIES with bullet points and percentages. We'll make a Responsibilities section with a
- for each duty.
List:
- Cross-Team Coordination (35%): Organize and lead weekly meetings across the project's three research thrusts, and coordinate meetings with the PI and co-PIs three to four times per year; collect progress updates from team members, track deliverables against project timelines, and escalate issues requiring PI and co-PI decisions.
- Stakeholder and Industry Engagement (20%): Support the PI and co-PIs in developing and maintaining relationships with industry partners and external stakeholders; manage ongoing communications and follow-up, coordinate partner meetings and site visits, and channel practical field insights into research and deployment planning.
- Metrics and Progress Tracking (20%): Develop and maintain metrics for project success; monitor performance against milestones and communicate progress to the PI, co-PIs, and other stakeholders; manage sponsor reporting deadlines and compliance requirements.
- Annual Report and White Paper (15%): Write the annual report to project sponsors, collecting contributions from across the research teams and integrating them into a unified document with an overall synthesis of the year's findings; coordinate the project's overall white paper by collecting input from research teams and managing contributors through drafting and review.
- Proposal Development (10%): Coordinate preparation and timely submission of proposals for extramural funding, including managing internal deadlines, assembling contributor materials, and liaising with the Office for Sponsored Programs.
- Perform other related duties as assigned.
We'll keep each as
- .
Supervisory responsibilities: "There are no supervisory responsibilities associated with this position" - could be included under Responsibilities as a note, but it's not a duty; maybe we can include a short paragraph under Responsibilities: "Supervisory responsibilities: None."
Physical requirements: "Applicants must be able to perform typical office tasks, including sitting for extended periods, using
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. We need to parse the posting. Company Description: includes description of Harvard, GSD. That could be "About the role"? Actually "Company Description" is about the organization. Could be "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. We have: - Company Description: description of Harvard, GSD. Could be placed under "About the role" maybe? Or maybe we could have a section "About the role" describing the role and organization. The posting includes "Job Description" with details about role. So we could have "About the role" summarizing the role and maybe the organization. But we must not invent content; we must preserve all substantive information. So we need to include the company description text as is, maybe within a
under a heading like "About the role". However "About the role" might be more about the role itself, but we can include the company description there as part of role context. The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which sections to include based on content. We have: - Job Description: includes NOTE about term appointment, reporting line, duties, typical duties and responsibilities broken down with percentages, supervisory responsibilities, physical requirements, work environment, additional information (health, vaccine, cover letter/resume required). Also includes "Additional Information" with Standard Hours/Schedule: 17.5 hours per week, expected annual salary range $45,000–55,000, Visa Sponsorship Info, Pre-Employment Screening, Work Format Details, Salary Grade and Ranges, Benefits. - Qualifications: BASIC QUALIFICATIONS list, ADDITIONAL QUALIFICATIONS AND SKILLS list. - Benefits: description of benefits. Thus we can create sections: - About the role: could combine Company Description and Job Description overview (maybe the first paragraph of Job Description). But we must not duplicate. We'll include the company description as a paragraph under About the role. - Responsibilities: typical duties and responsibilities (the bullet list with percentages). Also maybe include supervisory responsibilities (none) and physical requirements, work environment? Those could be under Responsibilities or maybe separate but we only have limited headings. Could put them under Responsibilities as part of duties. - Requirements: could include BASIC QUALIFICATIONS and ADDITIONAL QUALIFICATIONS AND SKILLS (maybe combine as Requirements). Or we could have Requirements and Qualifications separate. The instruction list includes both Requirements and Qualifications as possible headings. We need to decide. We have BASIC QUALIFICATIONS and ADDITIONAL QUALIFICATIONS AND SKILLS. Those are qualifications. So we could put them under Qualifications heading. Requirements could be things like "must have employment authorization to work in the US, cannot sponsor visa", "must be able to perform typical office tasks", etc. Those are more like requirements. So we can have a Requirements section for those. - Skills: maybe we could extract skills from qualifications (leadership, facilitation, organizational skills, written/verbal communication, grant writing, etc.) but we already have qualifications. Could also have Skills section for things like "Strong leadership, facilitation, and organizational skills; experience managing collaborative teams and meetings. Excellent written and verbal communication skills, including grant writing and report preparation." But that's already in qualifications. Might be redundant. Better to follow the instruction: prefer a few substantive sections over many thin ones. So we could combine Requirements and Qualifications into one section? But we have headings list; we can choose to include only those with real content. We could have: - About the role - Responsibilities - Qualifications (includes basic and additional qualifications) - Benefits - Pay (salary range) - Schedule (hours per week) We must not create Pay/Schedule/Benefits unless posting actually states them. It does state salary range and hours, and benefits description. So we can include those. We must not include filler like "commensurate with experience". Not present. We must remove boilerplate: EEO/Non-Discrimination Commitment Statement, etc. Also remove "Pre-Employment Screening: Identity." maybe not needed? It's not boilerplate but it's a requirement? It says "Pre-Employment Screening: Identity. Work Format Details ..." Might be considered metadata; we could drop it as minor metadata. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can drop Pre-Employment Screening line, Work Format Details, Salary Grade and Ranges maybe? But Salary Grade is metadata; we already have salary range. Could drop Salary Grade line. We also need to drop "Additional Information Standard Hours/Schedule: 17.5 hours per weekThe expected annual salary range for this position is: $45,000–55,000Visa Sponsorship Information: Harvard University is unable to provide visa sponsorship for this positionPre-Employment Screening: Identity. Work Format Details ..." We'll extract the needed pieces: Standard Hours/Schedule, salary range, visa sponsorship (maybe we can note as requirement). But visa sponsorship info is a requirement: cannot sponsor visa. So we can include that under Requirements. We also need to drop duplicated lines, application instructions (cover letter and resume required) - that's application instruction, should be removed per instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we need to remove the line about cover letter and resume required. Also remove "Please note that to be considered for this position, a cover letter and resume are required with the submission of your application." That's application instruction, remove. Also remove "EEO/Non-Discrimination Commitment Statement" entirely. Also remove "Learn more about these and additional benefits on our Benefits & Wellbeing Page." maybe considered boilerplate? It's a link; could be considered navigation; better to remove. Also remove "For more information about Harvard GSD see: https://www.gsd.harvard.edu/" maybe considered navigation; but it's part of company description; could keep as part of description? It's a link; maybe we can keep it as part of company description but it's a URL; not sure if considered navigation. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. That link is navigation; maybe we should drop it. However it's part of company description; but we can drop it as it's just a reference. The company description text before that is fine. We must preserve all substantive information. So we need to keep the description of Harvard, GSD, etc. We'll keep the textual description but drop the URL. Now let's extract substantive content. Company Description paragraph: "By working at Harvard University, you join a vibrant community that advances Harvard's world-changing mission in meaningful ways, inspires innovation and collaboration, and builds skills and expertise. We are dedicated to creating a diverse and welcoming environment where everyone can thrive. Why join the Harvard Graduate School of Design? The Harvard Graduate School of Design (GSD) educates design, research, and scholarship leaders to make a resilient, just, and beautiful world. The GSD offers degree programs across a range of design disciplines—architecture, landscape architecture, urban planning, urban design, design engineering, and real estate—as well as advanced research programs that cut across these disciplines and a robust public program of lectures, exhibitions, and publications. The immense variety of people, programs, and ideas at the School sustains a vibrant and rich environment for learning, inquiry, and collaboration, unlike any other design school." We'll keep that as a paragraph under About the role. Job Description overview (first paragraph before TYPICAL DUTIES): "NOTE: This position is a Term appointment for up to two years depending on funding. Reporting to the Director of the Center for Green Buildings and Cities, who serves as the project's Principal Investigator, the Interdisciplinary Research Program Manager supports the coordination and success of this interdisciplinary research initiative, working closely with the project's co-PIs. The Program Manager organizes weekly meetings to ensure regular progress updates, cross-team alignment, and timely course corrections, and serves as a central point of communication across the project's three integrated research thrusts: advanced thermal materials, intelligent building-scale systems, and cooperative urban-scale energy management. The Program Manager tracks project metrics and sponsor reporting deadlines, and is responsible for the project's major written outputs, including the annual report to sponsors. In addition to supporting integration across disciplines, the Program Manager supports the PI and co-PIs in developing and maintaining relationships with industry partners, ensuring that practical insights from the field inform the design and scalable deployment of project innovations. The role also coordinates the preparation and submission of proposals for extramural funding, helping to sustain and expand the project's research and implementation efforts. This role is essential to advancing the project's mission of scaling HouseZero®-inspired innovations into interconnected, energy-efficient communities and delivering impactful, real-world solutions to climate challenges." We can keep that as prose under About the role or Responsibilities? It's more about role description; maybe we put it under About the role as well. Then we have TYPICAL DUTIES AND RESPONSIBILITIES with bullet points and percentages. We'll make a Responsibilities section with a
- for each duty. List: - Cross-Team Coordination (35%): Organize and lead weekly meetings across the project's three research thrusts, and coordinate meetings with the PI and co-PIs three to four times per year; collect progress updates from team members, track deliverables against project timelines, and escalate issues requiring PI and co-PI decisions. - Stakeholder and Industry Engagement (20%): Support the PI and co-PIs in developing and maintaining relationships with industry partners and external stakeholders; manage ongoing communications and follow-up, coordinate partner meetings and site visits, and channel practical field insights into research and deployment planning. - Metrics and Progress Tracking (20%): Develop and maintain metrics for project success; monitor performance against milestones and communicate progress to the PI, co-PIs, and other stakeholders; manage sponsor reporting deadlines and compliance requirements. - Annual Report and White Paper (15%): Write the annual report to project sponsors, collecting contributions from across the research teams and integrating them into a unified document with an overall synthesis of the year's findings; coordinate the project's overall white paper by collecting input from research teams and managing contributors through drafting and review. - Proposal Development (10%): Coordinate preparation and timely submission of proposals for extramural funding, including managing internal deadlines, assembling contributor materials, and liaising with the Office for Sponsored Programs. - Perform other related duties as assigned. We'll keep each as
- . Supervisory responsibilities: "There are no supervisory responsibilities associated with this position" - could be included under Responsibilities as a note, but it's not a duty; maybe we can include a short paragraph under Responsibilities: "Supervisory responsibilities: None." Physical requirements: "Applicants must be able to perform typical office tasks, including sitting for extended periods, using