Executive Assistant to the Chief Financial Officer
Software Engineering Institute | Carnegie Mellon University · Pittsburgh, PA · 1 mo ago
AdministrativeFull-time
We need to output HTML fragment with sections: About the role? The posting includes Position Summary, What You'll Do, Who You Are, Work Arrangement, Why SEI, Location, Job Function, Position Type, Pay Basis, More Information (benefits link). We need to use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to map content to these headings.
We have Position Summary: could be About the role. What You'll Do: Responsibilities. Who You Are: Requirements/Qualifications/Skills? Could split: Requirements (education, experience), Qualifications (traits), Skills (tools). But we should prefer few substantive sections over many thin ones. We can combine into Requirements and Skills maybe. However we need to follow instruction: Use headings only for those listed. We can decide which sections have content.
We have Work Arrangement: could be Schedule? It mentions full-time, on-site, five days per week. That's schedule info. Could also be Pay? Not given. Pay Basis Salary is mentioned but no amount. That's not specific; we should not create Pay section if only "Salary" with no amount. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. For Schedule, we have specifics: full-time, on-site, five days per week. That's specific enough to include Schedule section. For Benefits, there is a link to benefits but no details; we should not create Benefits section unless posting actually states them. It says "Click here to view a listing of employee benefits" but not listing. Likely we should not include Benefits section because no specific benefits listed. Pay Basis Salary is not specific amount, so we should not include Pay section.
Thus sections: About the role (Position Summary), Responsibilities (What You'll Do), Requirements (Who You Are - education/experience), Skills (tools/proficiency), Schedule (Work Arrangement). Possibly also Qualifications? Could combine Requirements and Qualifications but we have both. We could put Requirements for education/experience, Qualifications for traits, Skills for tools. That's three sections plus About and Responsibilities and Schedule = 5 sections. That's okay.
We must not repeat job title as heading. No Job ID etc.
We need to preserve all substantive information, not invent or summarize away detail. Must include all details from posting.
Let's extract details:
Position Summary paragraph: "Are you someone who anticipates what needs to happen next rather than waiting to be asked? Do you enjoy bringing structure to competing priorities and following things through to completion? Are you comfortable building relationships across an organization to find answers, solve problems, and keep things moving? Do you exercise good judgment and know when to take something on independently and when to ask for help? The Software Engineering Institute (SEI) is seeking an experienced Executive Assistant to support our Chief Financial Officer and help manage the priorities, commitments, and daily rhythm of the CFO's Office and broader Finance and Business Services division. This role is a great fit for someone who takes ownership, asks thoughtful questions, and enjoys being at the center of a busy organization. You'll work closely with the CFO while building relationships across the SEI and Carnegie Mellon University, helping connect people and information, anticipating needs, and making the CFO's Office and broader division more effective."
What You'll Do bullet list (actually sentences separated by periods). Need to convert to
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to map content to these headings.
We have Position Summary: could be About the role. What You'll Do: Responsibilities. Who You Are: Requirements/Qualifications/Skills? Could split: Requirements (education, experience), Qualifications (traits), Skills (tools). But we should prefer few substantive sections over many thin ones. We can combine into Requirements and Skills maybe. However we need to follow instruction: Use headings only for those listed. We can decide which sections have content.
We have Work Arrangement: could be Schedule? It mentions full-time, on-site, five days per week. That's schedule info. Could also be Pay? Not given. Pay Basis Salary is mentioned but no amount. That's not specific; we should not create Pay section if only "Salary" with no amount. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. For Schedule, we have specifics: full-time, on-site, five days per week. That's specific enough to include Schedule section. For Benefits, there is a link to benefits but no details; we should not create Benefits section unless posting actually states them. It says "Click here to view a listing of employee benefits" but not listing. Likely we should not include Benefits section because no specific benefits listed. Pay Basis Salary is not specific amount, so we should not include Pay section.
Thus sections: About the role (Position Summary), Responsibilities (What You'll Do), Requirements (Who You Are - education/experience), Skills (tools/proficiency), Schedule (Work Arrangement). Possibly also Qualifications? Could combine Requirements and Qualifications but we have both. We could put Requirements for education/experience, Qualifications for traits, Skills for tools. That's three sections plus About and Responsibilities and Schedule = 5 sections. That's okay.
We must not repeat job title as heading. No Job ID etc.
We need to preserve all substantive information, not invent or summarize away detail. Must include all details from posting.
Let's extract details:
Position Summary paragraph: "Are you someone who anticipates what needs to happen next rather than waiting to be asked? Do you enjoy bringing structure to competing priorities and following things through to completion? Are you comfortable building relationships across an organization to find answers, solve problems, and keep things moving? Do you exercise good judgment and know when to take something on independently and when to ask for help? The Software Engineering Institute (SEI) is seeking an experienced Executive Assistant to support our Chief Financial Officer and help manage the priorities, commitments, and daily rhythm of the CFO's Office and broader Finance and Business Services division. This role is a great fit for someone who takes ownership, asks thoughtful questions, and enjoys being at the center of a busy organization. You'll work closely with the CFO while building relationships across the SEI and Carnegie Mellon University, helping connect people and information, anticipating needs, and making the CFO's Office and broader division more effective."
What You'll Do bullet list (actually sentences separated by periods). Need to convert to - . List items:
- Proactively manage the CFO's complex calendar, anticipating conflicts, priorities, sequencing needs, and preparation requirements.
- Help the CFO stay ahead of upcoming commitments, deadlines, meetings, and follow-up activities.
- Coordinate leadership meetings, quarterly financial reviews, and other key activities, ensuring the right people, objectives, materials, and information are in place.
- Track commitments and follow-up items and help ensure they move forward to completion.
- Serve as a key point of coordination between the CFO's Office, Finance and Business Services teams, administrative staff, and other groups across the SEI.
- Build strong relationships across the organization and proactively find the information and resources needed to get things done.
- Help coordinate division communications, shared information and reference resources, leadership activities, and division events.
- Identify opportunities to improve administrative processes, information flow, and coordination.
- Coordinate travel, expense reports, purchase requests, meeting logistics, space needs, and other administrative and operational activities.
- Handle sensitive executive, financial, personnel, and organizational information with discretion and sound judgment.
Who You Are: list:
- You have an associate's degree and 5–8 years of progressively responsible experience in executive support, senior administrative support, or administrative coordination.
- You're highly organized and detail-oriented, but able to adapt quickly as priorities change.
- You take initiative and can work independently without losing sight of when collaboration or escalation is needed.
- You build relationships easily and are comfortable working with people across all levels of an organization.
- You're an excellent written and verbal communicator with strong judgment and follow-through.
- You're proficient with office and collaboration tools such as Outlook, Teams, and SharePoint.
- Experience directly supporting a senior leader or working in higher education, research, government, defense, nonprofit, or another mission-driven environment is a plus.
Work Arrangement: "This is a full-time, on-site position in Pittsburgh, Pennsylvania, with an expectation of working in the office five days per week. Consistent in-person presence is important to the role given the close interaction with the CFO, division leadership, administrative partners, and teams across the organization."
Why SEI: "At the SEI, you'll support an organization with a unique national mission while being part of the Carnegie Mellon University community. You'll work closely with senior leadership, build relationships across a complex organization, and have a visible impact on how the CFO's Office and Finance and Business Services division operate."
Location: "Pittsburgh, PA"
Job Function: "Executive Administrative Support"
Position Type: "Staff – Regular Full time/Part time Full time"
Pay Basis: "Salary"
More Information: link to benefits and EEO statement (we should remove boilerplate EEO etc). The More Information includes: "Please visit “Why Carnegie Mellon” to learn more about becoming part of an institution inspiring innovations that change the world. Click here to view a listing of employee benefits Carnegie Mellon University is an Equal Opportunity Employer/Disability/Veteran. Statement of Assurance"
We should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the EEO line and Statement of Assurance. Also drop the "Click here to view a listing of employee benefits" maybe? That's a link to benefits but not listing specifics. Since we are not including Benefits section, we could keep that sentence as part of More Information? But we are not including a Benefits section; we could include a short paragraph under About the role? Probably better to omit that line as it's just a link to benefits, not substantive detail. The instruction: remove boilerplate, duplicated lines, and application instructions. The "Click here to view a listing of employee benefits" is not boilerplate but it's a referral; but we are not including Benefits section, maybe we can keep it as a short paragraph under About the role? However it's not about the role; it's a link to benefits. Might be considered navigation? Safer to omit it.
Also "Please visit “Why Carnegie Mellon” to learn more about becoming part of an institution inspiring innovations that change the world." That's also generic; could be considered boilerplate? It's not about the role specifics. Might be okay to keep as part of Why SEI? Actually Why SEI already covers mission. This line is similar. Could be omitted.
Thus we keep core content: Position Summary, What You'll Do, Who You Are, Work Arrangement, Why SEI, Location, Job Function, Position Type. Pay Basis we omit because not specific. Benefits we omit.
Now map to headings:
About the role: Position Summary paragraph.
Responsibilities: What You'll Do list.
Requirements: education and experience (associate's degree and 5–8 years...). Could also include "Experience directly supporting a senior leader or working in higher education, research, government, defense, nonprofit, or another mission-driven environment is a plus." That's a qualification/plus; could go under Requirements or Qualifications. We'll put under Requirements.
Qualifications: traits (organized, detail-oriented, adaptable, initiative, relationship building, communication, judgment). Could be separate.
Skills: proficiency with Outlook, Teams, SharePoint.
Schedule: Work Arrangement (full-time, on-site, five days per week, Pittsburgh location? Actually location is separate; schedule is about time commitment. We'll include schedule details: full-time, on-site, five days per week. Location we could include in a separate paragraph maybe not under any heading; but we could include location under About the role? Might be better to add a short paragraph after About the role? But we cannot create new headings not listed. We could include location in a
under About the role or Schedule? Probably better to add a
after About the role? But we must not invent headings. We can just include location as a paragraph within About the role or Schedule? The location is not schedule. Could add a separate
without heading? The instruction says output ONLY the HTML fragment; we can have multiple
and
etc. Headings only for sections we choose. So we can have a for location after About the role before Responsibilities. That's fine.
Similarly Job Function and Position Type could be included as
under About the role or maybe as a separate short paragraph without heading. But we could also incorporate them into About the role? Might be better to add a
after About the role summarizing job function and position type.
We must preserve all substantive information; we can't lose location, job function, position type.
Thus structure:
About the role
Position Summary text...
Location: Pittsburgh, PA
Job Function: Executive Administrative Support
Position Type: Staff – Regular Full time
Responsibilities
...
Requirements
... education/experience and plus...
Qualifications
... traits...
Skills
... proficiency with Outlook, Teams, SharePoint.
Schedule
This is a full-time, on-site position in Pittsburgh, Pennsylvania, with an expectation of working in the office five days per week. Consistent in-person presence is important to the role given the close interaction with the CFO, division leadership, administrative partners, and teams across the organization.
But note we already included location in About the role; we might duplicate location if also in Schedule. Better to keep location only once. Schedule section should focus on work arrangement: full-time, on-site, five days per week. We can mention location again? Might be redundant but okay. However we already have location in About the role; we could keep schedule without location. Let's put schedule: "This is a full-time, on-site position with an expectation of working in the office five days per week. Consistent in-person presence is important to the role given the close interaction with the CFO, division leadership, administrative partners, and teams across the organization."
We already have location in About the role; fine.
Now ensure we don't include any boilerplate like EEO, etc.
Now produce HTML fragment.
Let's craft the text precisely.
About the role paragraph: combine the Position Summary sentences exactly as given.
Position Summary: "Are you someone who anticipates what needs to happen next rather than waiting to be asked? Do you enjoy bringing structure to competing priorities and following things through to completion? Are you comfortable building relationships across an organization to find answers, solve problems, and keep things moving? Do you exercise good judgment and know when to take something on independently and when to ask for help? The Software Engineering Institute (SE
under About the role or Schedule? Probably better to add a
after About the role? But we must not invent headings. We can just include location as a paragraph within About the role or Schedule? The location is not schedule. Could add a separate
without heading? The instruction says output ONLY the HTML fragment; we can have multiple
and
- etc. Headings only for sections we choose. So we can have a
for location after About the role before Responsibilities. That's fine. Similarly Job Function and Position Type could be included as
under About the role or maybe as a separate short paragraph without heading. But we could also incorporate them into About the role? Might be better to add a
after About the role summarizing job function and position type. We must preserve all substantive information; we can't lose location, job function, position type. Thus structure:
About the role
Position Summary text...
Location: Pittsburgh, PA
Job Function: Executive Administrative Support
Position Type: Staff – Regular Full time
Responsibilities
- ...
Requirements
- ... education/experience and plus...
Qualifications
- ... traits...
Skills
- ... proficiency with Outlook, Teams, SharePoint.
Schedule
This is a full-time, on-site position in Pittsburgh, Pennsylvania, with an expectation of working in the office five days per week. Consistent in-person presence is important to the role given the close interaction with the CFO, division leadership, administrative partners, and teams across the organization.
But note we already included location in About the role; we might duplicate location if also in Schedule. Better to keep location only once. Schedule section should focus on work arrangement: full-time, on-site, five days per week. We can mention location again? Might be redundant but okay. However we already have location in About the role; we could keep schedule without location. Let's put schedule: "This is a full-time, on-site position with an expectation of working in the office five days per week. Consistent in-person presence is important to the role given the close interaction with the CFO, division leadership, administrative partners, and teams across the organization." We already have location in About the role; fine. Now ensure we don't include any boilerplate like EEO, etc. Now produce HTML fragment. Let's craft the text precisely. About the role paragraph: combine the Position Summary sentences exactly as given. Position Summary: "Are you someone who anticipates what needs to happen next rather than waiting to be asked? Do you enjoy bringing structure to competing priorities and following things through to completion? Are you comfortable building relationships across an organization to find answers, solve problems, and keep things moving? Do you exercise good judgment and know when to take something on independently and when to ask for help? The Software Engineering Institute (SE