Program Analyst (Hybrid- Annapolis, Maryland)

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: EEO, etc. Must preserve all substantive info. Let's parse the posting. Content: - Intro paragraph: "Program Analyst Fairwinds Technologies, LLC is looking for a Program Analyst to manage projects, financials and support program managers with large complex program awards and handle the day-to-day activities within the program management office. This position will work directly for the VP of PMO and in parallel with operations, accounting and sales. We are looking for someone who can manage customer expectations, develop/edit reports and schedule work efforts across the business unit. The position will work with internal and external customers requiring them to think on their feet and leverage a proven ability to brief decision makers and support staff alike to develop customer organizational consensus." - Location: "Hybrid, Annapolis Maryland and at Fairwinds facilities, and customer sites" - Compensation: "Base Salary" - Supervisor: "Director of PMO" - Minimum Qualifications: list bullet points. - Responsibilities: list bullet points. - Position Type/Expected Hours of Work: "This is a full time, exempt position." - Work Authorization/Security Clearance: "Must be eligible to work in the US." - AAP/EEO Statement: remove. - Compensation- Salary: "At Fairwinds, we consider many factors when it comes to compensation, including the scope of the position as well as your background and experience. Base pay may vary depending on job-related knowledge, skills, location and experience" We need to decide sections. We have: - About the role: could be the intro paragraph. - Responsibilities: list. - Requirements: maybe Minimum Qualifications. - Qualifications: maybe also Minimum Qualifications? But we can combine? The instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include sections only if we have real specific content. We have content for About the role (intro). Responsibilities (list). Requirements (Minimum Qualifications). Qualifications maybe same as Requirements? Could treat Minimum Qualifications as Requirements. Could also have Skills (list of skills like communication, MS Office, etc). Benefits: none specific (just mention Base Salary but no details). Pay: we have "Base Salary" and statement about compensation varying. That's not specific numbers; but we have some content about compensation. The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Compensation: Base Salary" and later a paragraph about compensation factors. That's enough to include a Pay section? It says base salary but no amount. The rule: never emit a 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 the posting actually states them. The posting states "Compensation: Base Salary" and then a paragraph about compensation factors. That's not a specific number but it's stating compensation exists. Is that considered filler? It's not a specific number but it's stating base salary. The rule says avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The paragraph says "Base pay may vary depending on job-related knowledge, skills, location and experience". That's somewhat vague but still mentions base pay may vary. Might be considered filler? It's not a specific number but it's not "varies" alone; it's a statement that base pay may vary depending on factors. I'd lean to include a Pay section with that paragraph (maybe trimmed). However we must not invent or summarize away detail. We can include the exact sentences. Schedule: we have "Position Type/Expected Hours of Work This is a full time, exempt position." That's schedule info. So we can include Schedule section with that sentence. Benefits: none specific. No mention of health, retirement, etc. So omit Benefits. Skills: we have list of skills: Excellent organizational, communication and presentation skills; Proficient in MS Office; Ability to communicate, present and influence credibly and effectively at all levels; Ability to prioritize, multi-task, perform under pressure; Ability to work remotely and communicate effectively; etc. Could extract into Skills section. But we already have Requirements (Minimum Qualifications) which includes BA/BS, 3 years gov contracting, project based accounting/finance experience, demonstrated ability to communicate, present, influence, ability to prioritize, multi-task, perform under pressure, must be US citizen. That's overlapping with skills. We could separate: Requirements = education/experience/citizenship; Skills = abilities like communication, MS Office, etc. Qualifications maybe duplicate; we could omit Qualifications if we already have Requirements. But we need to follow instruction: include a section ONLY when posting has real specific content. We have content for Requirements (Minimum Qualifications). We have content for Skills (list of abilities). We have content for About the role (intro). We have Responsibilities (list). We have Pay (compensation statement). We have Schedule (full time exempt). We have Location? Not a heading but could be part of About the role or a separate paragraph. The instruction didn't list Location as a heading option; we can just include it in About the role paragraph or as a

after About the role. We must not repeat job title as heading. So we won't have

Program Analyst

. Good. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: EEO, Work Authorization/Security Clearance? Actually "Must be eligible to work in the US." is substantive (work authorization). Should we keep? It's a requirement. Could be part of Requirements. The posting includes "Work Authorization/Security Clearance Must be eligible to work in the US." That's a requirement. We'll keep that as part of Requirements. We must remove AAP/EEO statement. We must remove duplicated lines. Now craft HTML. Structure:

About the role

Program Analyst Fairwinds Technologies, LLC is looking for a Program Analyst to manage projects, financials and support program managers with large complex program awards and handle the day-to-day activities within the program management office. This position will work directly for the VP of PMO and in parallel with operations, accounting and sales. We are looking for someone who can manage customer expectations, develop/edit reports and schedule work efforts across the business unit. The position will work with internal and external customers requiring them to think on their feet and leverage a proven ability to brief decision makers and support staff alike to develop customer organizational consensus. Location: Hybrid, Annapolis Maryland and at Fairwinds facilities, and customer sites.

Responsibilities

• Project planning, budgeting/forecasting, invoicing, and overall project strategy
• Analyzing project data to optimize performance, identify problems and shortfalls and propose solutions
• Review project contracts and financials
• Manage customer expectations, schedule updates, deliveries, tracking, etc.
• Coordinate the activities of the program(s) and set priorities for their execution
• Formulate, organize, and monitor inter-connected projects
• Development of customer and internal briefs as needed
• Apply change, risk, and resource management
• Ability to review customer documents and create reports for submission as required
• Ability to work remotely and communicate effectively
• Excellent organizational, communication and presentation skills
• Proficient in MS Office
• Adheres to company policies, procedures, and practices
• Ability to obtain a security clearance as needed
• Close attention to detail and the ability to plan ahead

But note some of these items are actually skills; but we can keep them in Responsibilities as they appear in the posting under Responsibilities section. The original Responsibilities list includes many items; we should keep them as is. Now Requirements:

Requirements

• BA/BS Degree (or equivalent)
• Minimum 3 years with government contracting / DoD Experience
• Project based accounting/finance experience, managing costs and schedules with customers and vendors
• Demonstrated ability to communicate, present and influence credibly and effectively at all levels of the organization
• Ability to prioritize, multi-task, and perform effectively under pressure
• Must be a US Citizen
• Must be eligible to work in the US

Now Skills: maybe we can extract skills not already in Requirements: Excellent organizational, communication and presentation skills (already in Requirements? Actually that's in Requirements as ability to communicate etc. But we could still include a Skills section for things like Proficient in MS Office, Ability to work remotely and communicate effectively, etc. However to avoid duplication, we could decide not to include Skills if it's too thin. But we have some distinct skills: Proficient in MS Office, Ability to work remotely and communicate effectively, Excellent organizational, communication and presentation skills (some overlap). Might be okay to include Skills. But we must avoid filler. Let's see if we have enough distinct content: The posting includes under Responsibilities: "Excellent organizational, communication and presentation skills", "Proficient in MS Office", "Ability to work remotely and communicate effectively". Also under Minimum Qualifications: "Demonstrated ability to communicate, present and influence credibly and effectively at all levels of the organization." That's similar. We could combine Skills into Requirements or Responsibilities. But the instruction says we can have Skills section if we have real specific content. We have some. Let's include Skills.

Skills

• Excellent organizational, communication and presentation skills
• Proficient in MS Office
• Ability to work remotely and communicate effectively

Now Pay:

Pay

Compensation: Base Salary. At Fairwinds, we consider many factors when it comes to compensation, including the scope of the position as well as your background and experience. Base pay may vary depending on job-related knowledge, skills, location and experience.

Now Schedule:

Schedule

This is a full time, exempt position.

We should not include Benefits. Check for any duplicated lines: Ensure we didn't repeat same bullet. Now ensure we didn't include any boilerplate like EEO, etc. We removed "Work Authorization/Security Clearance Must be eligible to work in the US." but we kept "Must be eligible to work in the US" under Requirements. Good. We removed "Supervisor: Director of PMO". That's substantive; maybe we should include it somewhere. Could be part of About the role or a separate line. The posting includes "Supervisor: Director of PMO". That's a detail we should preserve. Where to put? Could add to About the role paragraph after location or as its own sentence. Let's incorporate into About the role: add "The position reports to the Director of PMO." Actually the posting says "Supervisor: Director of PMO". We'll add a sentence: "The position reports to the Director of PMO." Also we have "Location: Hybrid, Annapolis Maryland and at Fairwinds facilities, and customer sites". Already included. Now check if any other content: "Position Type/Expected Hours of Work This is a full time, exempt position." Already in Schedule. Now ensure we didn't inadvertently include any navigation/legal/EEO/scams. Good. Now output only HTML fragment. Let's craft final HTML. Be careful to close tags. We'll output:

About the role

Program Analyst Fairw