Project Control Analyst
About the role
then...
. - Responsibilities: "Key Responsibilities" list. Should beResponsibilities
then- each bullet.
- Required Qualifications: list of qualifications. Could be
Qualifications
orRequired Qualifications
. The instruction says use headings like Qualifications. We'll useQualifications
. Provide- .
- Preferred Qualifications: maybe also under Qualifications? Could combine? But we have separate Preferred Qualifications. Could include as another
Preferred Qualifications
or just include under Qualifications. The instruction: Prefer a few substantive sections over many thin ones. Might combine required and preferred into one Qualifications section with sub-bullets? But we need to preserve all info. Could do two subsections? But headings only allowed as listed; we could still have Qualifications and then maybe Preferred Qualifications as separate heading? Not in list but could be considered Qualifications. Safer to have one Qualifications section containing both required and preferred, maybe with notes. But we must preserve all info; we can include both required and preferred as separate- under same heading? Could do
Qualifications
thenRequired:
- ... then
Preferred:
- . That preserves.
- Skills: maybe include Excel, ERP, etc. Could be part of Qualifications. But we have a Skills heading; we could extract skills: Intermediate Excel, familiarity with ERP, curiosity to learn Gov contracting, attention to detail, organization, etc. Could put under Skills.
- Benefits: there is "Comprehensive Benefits Package" and "Flexible Leave Benefits". So we have Benefits section.
- Pay: Salary range $75,000 - $85,000. So include Pay.
- Schedule: Not mentioned. No schedule info. So we should NOT include Schedule section.
- Also there is "About Being a Part Of Team AVIAN" and "Why Join Us?" which could be part of Benefits or maybe separate sections like Culture? Not in allowed headings. Could fold into About the role or Benefits? Probably incorporate into About the role or maybe a separate section like "About the company" but not allowed. So we can include that content under About the role or maybe under Benefits? Better to add to About the role as additional paragraphs.
We must not include boilerplate like EEO statement. Remove that.
We must not include application instructions.
Now craft HTML.
Structure:
About the role
...
Responsibilities
- ...
Qualifications
Required:
- ...
Preferred:
- ...
Skills
- ...
About the role
... combined paragraphs ...
Responsibilities
- ...
Qualifications
Required:
- ...
Preferred:
- ...
Benefits
- ...
Pay
Salary range $75,000 - $85,000 (The offered rate will be based on the selected candidate’s knowledge, skills, abilities, and/or experience and in consideration of internal parity.)
No Schedule. Now craft the About the role paragraph(s). We'll combine into maybe twoelements for readability. First paragraph: The Project Control Analyst (Career Level 2) is a member of the contracts team, reporting to the Director of Quality. This role supports a subsidiary of a large contractor support services company, working closely with Government customers, Prime contractors, Contracts Manager(s) (CM), Program Managers (PM), Sector leads and other relevant Operations personnel to ensure effective contract financial management and performance of projects. Second paragraph: Join a Company Where You Can Make a Real Impact - and Own a Piece of the Future Are you energized by the idea of helping a company grow smarter, serve our customers better, and connect more deeply? Do you thrive in an environment where your ideas matter, your voice is heard, and your work drives real results? If so, we’d love to meet you. We’re a mid-sized, employee-owned company on a mission to create meaningful value for both our employees and our customers. That means we’re not just looking for someone to fill a seat — we’re looking for someone who wants to build, innovate, and evolve with us. Our company primarily serves the Navy and other Department of Defense clients, offering a dynamic environment where your expertise will make a difference. Third paragraph: As an employee-owner, you’ll be a catalyst for progress — helping us find new opportunities with current or new customers, company efficiencies, streamline processes, and bring people and ideas together in smarter ways. Whether it’s helping us optimize workflows, enhancing the employee experience, or delivering more impactful solutions to our customers, your inputs will have reach and relevance across the organization. Taking care of each other is a cornerstone of our AVIAN philosophy. Being part of the AVIAN team means being part of a team that takes pride in being expansive in our community because our impact doesn’t stop in the workplace. We actively engage in community initiatives, empowering our employees to make a meaningful difference. Fourth paragraph: Why Join Us? Employee Ownership: We’re not just building a company — we’re building a legacy. As an employee-owner, you’ll share in our success and have a direct stake in our future. Real Growth: We’re expanding, evolving, and exploring new ways to serve. Your contributions will shape our direction and help us grow stronger. Purpose-Driven Work: Every improvement you help make is one that adds value — not just for us, but for the people and missions we support. Culture of Collaboration: We’re big enough to take on meaningful challenges, but small enough that everyone still knows your name. Comprehensive Benefits Package: Designed to support your health, financial security, and overall well-being, our health and wellness benefits include medical, dental, and vision coverage, along with telemedicine services and a TRICARE supplement for veterans. Flexible Leave Benefits: we prioritize a balanced, supportive environment that allows you to thrive both personally and professionally and offer flexible and paid time off, 11 paid holidays, paid sick leave, maternity and bonding leave, and military training leave. We should avoid repeating benefits details that will be in Benefits section; but it's okay to have some overview. However to avoid duplication, maybe keep brief. But instruction