Centralized Permit Coordinator

We need to output HTML fragment with sections: headings

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. Remove boilerplate, navigation, legal, EEO, etc. Preserve all substantive info. Include a section only when posting has real specific content. Avoid filler like "commensurate with experience". Pay/Schedule/Benefits only if posting actually states them. We need to parse the posting. Content: - Intro paragraph: "Ready to build your future? We're Groundworks, North America's leading foundation repair and water management specialist. We're more than a company - we're a team driven by purpose. As a Top Workplace, we're looking for top talent to fuel our mission: to protect, repair, and improve our customers’ greatest asset – their home. But what makes us a great place to work? Here, you'll find real career growth, comprehensive and affordable benefits, a culture that values hard work and innovation, and company ownership equity. Whether you’re starting your career or looking for your next big move, we offer hands-on training, advancement opportunities, and the chance to make a real impact every day. Join us and lay the foundation for your success. Apply today!" That's about the company; could be "About the role"? Actually "About the role" is typical heading for description of role. But we have "Job Purpose" heading in posting: "Job Purpose The Centralized Permit Coordinator is responsible for coordinating and executing permitting activities for residential and commercial projects throughout the project lifecycle. This role ensures permits, inspections, revisions, approvals, and closeout documentation are processed accurately and timely while maintaining compliance with municipal and regulatory requirements. The Centralized Permit Coordinator serves as a key liaison between municipalities, engineers, customers, branches, and internal teams to support project progression from permit acquisition through final permit closure." We can treat that as "About the role" or "Job Purpose". The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to those headings. We have: - About the role: could be the Job Purpose paragraph. - Responsibilities: list of duties (the bullet list under "Duties And Responsibilities"). - Requirements: maybe "Qualifications" section. - Qualifications: maybe separate? Actually they have "Qualifications" heading with bullet list of skills. Then "Working Conditions" and "Physical Requirements". Also "What We Provide" with benefits list. We need to decide which sections to include based on actual content. We have: - About the role: Job Purpose paragraph. - Responsibilities: list of duties (multiple sentences, each ends with period). Could be turned into

  • . - Requirements: maybe combine Qualifications and Working Conditions? But they have "Qualifications" heading with list of skills/experience. Also "Working Conditions" and "Physical Requirements". Could be part of "Requirements" or separate "Qualifications". The instruction says we can use headings like Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include. We have explicit "Qualifications" heading with bullet list: Strong organizational..., Excellent communication..., Ability to manage..., Experience with permitting..., Knowledge of municipal..., Proficiency with Microsoft Office... We also have "Working Conditions" paragraph: "The Centralized Permit Coordinator will sit onsite in our Manassas branch. The pay rate for this role is $21.50/h." That's pay info. Then "Physical Requirements": "Prolonged periods of sitting at a desk and working on a computer. Other requirements include standing, walking, and moving, as needed." Then "What We Provide": list: Competitive Pay, Employee Company Ownership Opportunities, Industry Leading Training Programs, Leadership Development and Career Growth Tracks, Comprehensive and Affordable Benefits Package, Top Workplace with Award Winning Culture. Then there is also "The anticipated salary range is the expected hiring range for this role in Virginia is $14.00 - $17.50. Final compensation will be based on an evaluation of each candidate's qualifications, relevant experience, demonstrated capabilities, and work location." We have contradictory pay: earlier says pay rate $21.50/h, then anticipated salary range $14-17.50. Both are substantive. We need to preserve all substantive info. So we need to include Pay section with both pieces? The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include Pay section with the specific pay rate and salary range. Schedule: no mention of schedule (like full-time, part-time, shift). Not present, so we should not include Schedule heading. Benefits: we have "What We Provide" list includes benefits. So we can have Benefits section with those items. Skills: we could have Skills section from Qualifications? But Qualifications already covers skills. The instruction allows Skills heading. We could put skills under Qualifications or Skills. But we need to avoid duplication. Perhaps we put Qualifications heading for the list of qualifications (education/experience) and Skills heading for the list of abilities (organizational, communication, etc). However the posting's Qualifications includes both. To follow instruction, we could create a Qualifications section for the bullet list under "Qualifications". And maybe a Skills section for the same? That would duplicate. Better to follow the headings that match content: we have "Qualifications" heading in posting, so we can use that. We also have "Working Conditions" and "Physical Requirements" which could be part of "Requirements" or separate. But we don't have a heading for Working Conditions in the allowed list; we could put under Requirements or maybe under Qualifications? The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. Thus: - About the role: Job Purpose paragraph. - Responsibilities: list of duties. - Requirements: could include Working Conditions and Physical Requirements? Or maybe Requirements is for mandatory qualifications (like experience, knowledge). But we have Qualifications heading already. So maybe Requirements is for "Working Conditions" and "Physical Requirements". However the instruction says we can use Requirements heading for any list of duties/requirements/benefits. So we can put the working conditions and physical requirements under Requirements as a list. - Qualifications: the bullet list under "Qualifications" heading. - Skills: maybe we could split the Qualifications into Skills and Qualifications? But we already used Qualifications for the bullet list. Could also put Skills as same list? Might be redundant. Better to not include Skills if we already used Qualifications. But we could include Skills for the abilities like organizational, communication, problem-solving, etc. However the Qualifications list includes those. To avoid duplication, we could treat Qualifications as the list of qualifications (experience, knowledge, proficiency) and Skills as the abilities (organizational, time-management, communication, customer service, problem-solving, ability to manage multiple priorities). But the posting lumps them together. However we can still split them logically: The first three bullets are skills: Strong organizational and time-management skills..., Excellent communication..., Ability to manage multiple priorities... The next two are experience/knowledge: Experience with permitting..., Knowledge of municipal..., Proficiency with Microsoft Office... So we could separate. But the instruction says "Prefer a few substantive sections over many thin ones." So maybe better to keep Qualifications as one section containing all bullet points. Then we don't need Skills. Thus sections: About the role, Responsibilities, Requirements (working conditions + physical requirements), Qualifications, Benefits, Pay. We must not include Schedule. Now we need to format. Use

    for each section heading. Under each heading, we need to put content: either

    for prose, or

    • for lists. For About the role: prose paragraph(s). We have the Job Purpose paragraph. Could also include the introductory paragraph about company? The instruction says preserve ALL substantive information; do not invent or summarize away detail. The introductory paragraph about company is substantive? It describes the company and culture. It could be considered part of About the role? But the heading "About the role" is for role description, not company overview. However we could include it as a separate section? Not in allowed headings. Could we put it under About the role as prose? It is about the company, not the role. But we could still include it as part of About the role because it's contextual. The instruction says do not repeat the job title as a heading. It didn't forbid including company overview. So we can include that introductory paragraph as part of About the role. Thus About the role will have two paragraphs: the intro about Groundworks, and the Job Purpose paragraph. We need to ensure we don't include boilerplate like "Apply today!"? That's a call to action; maybe considered boilerplate? It's not legal/EEO, but it's application instruction. The instruction says remove application instructions. So we should remove "Apply today!" and also "Ready to build your future?" maybe not application instruction but marketing. It's substantive? It's about the company. Might be okay to keep. However "Apply today!" is clearly an application instruction; we should remove it. Also "Join us and lay the foundation for your success." is also motivational but not instruction. Might keep. We need to remove duplicated lines. There's no duplication. Now Responsibilities: list of duties. We need to extract each duty sentence from the "Duties And Responsibilities" block. Let's list them: - Prepare, submit, track, and maintain permit applications and supporting documentation. - Coordinate permit approvals, revisions, inspections, and permit closeout activities. - Work with municipalities, inspectors, engineers, utility providers, homeowners, and internal teams to obtain required approvals and information. - Resolve permit blockers, kickbacks, failed inspections, and escalations to keep projects progressing. - Schedule and coordinate inspections as required throughout the permitting process. - Maintain accurate permit records, tracking logs, compliance documentation, and status updates. - Communicate permit status, requirements, and updates to branches, customers, municipalities, and internal stakeholders. - Ensure compliance with all jurisdictional, permitting, and regulatory requirements. - Identify aging or at-risk permits and proactively drive resolution. - Coordinate permit revisions, engineering updates, certifications, and other documentation required to support project completion. - Support the closure of building and trade permits, including coordination with third-party inspectors, engineers, and municipalities as needed. - Assist with process improvement initiatives to increase permitting efficiency and reduce cycle times. - It is an essential function of this position to regularly and reliably report to work each day. - Perform other duties as assigned. We need to keep all. We'll put each as
    • . Now Requirements: we have Working Conditions and Physical Requirements. Working Conditions: "The Centralized Permit Coordinator will sit onsite in our Manassas branch. The pay rate for this role is $21.50/h." Physical Requirements: "Prolonged periods of sitting at a desk and working on a computer. Other requirements include standing, walking, and moving, as needed." We could combine into a list? Or separate paragraphs. Since it's not a list of duties/requirements/benefits, we can use

      for prose. But we have two sentences; could be two paragraphs or one. Better to make a

      • for each? The instruction says use
        • for any list of duties/requirements/benefits. These are requirements (working conditions, physical). So we can make a list. Thus Requirements section:
          • The Centralized Permit Coordinator will sit onsite in our Manassas branch. The pay rate for this role is $21.50/h.
          • Prolonged periods of sitting at a desk and working on a