Assistant Project Manager Building Code

We need to output HTML fragment with sections only if real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: disclaimer, EEO, etc. Keep substantive info. We need to parse the posting. Key info: - Title: Assistant Project Manager, Building Code Code Compliance NYC US Salary Range: $55,000 - $85,000 (but we shouldn't repeat title as heading; we can include salary in Pay section if present). Salary range is given. - Overview paragraphs: "Are you ready to drive growth..." etc. That's about the role. - Overview: "At CodeGreen, our Compliance teams help clients navigate..." etc. - "CodeGreen is looking for a detail-oriented and proactive Assistant Project Manager, Building Code to help guide our clients..." etc. - "We welcome applications from candidates at all experience levels..." - Impact section: bullet list of duties (Manage end-to-end filing..., Prepare proposals..., Lead standard Alteration Filings..., Maintain ongoing communication...). Those are responsibilities. - "What You'll Bring To CodeGreen": bullet list of qualifications/skills: Strong communication..., Proficient in Microsoft Office..., Knowledge of NYC permit..., Experience working..., 1-3 years of building code project management experience... - "Compensation And Assessment": Pay ranges listed as required by law. Final compensation reflects each candidate’s education, experience, qualifications, and work location. As part of our recruitment process, we use AI technology... (maybe not needed). Then "What makes CodeGreen different? We offer competitive salaries and great benefits. What sets us apart is our commitment to people and purpose..." Then benefits description: "CodeGreen offers a competitive total compensation package. We offer a comprehensive Benefit package including medical, dental, and vision coverage, a Health Savings Account, an employer funded Health Reimbursement Account, as well as a Dependent Care FSA ensuring flexible options. With a strong 401(k) plan and employer matching, we help you secure your financial future. Additionally, we back your professional growth by reimbursing association fees and providing ample resources for ongoing development—all to keep you leading in your field." - Additional Information: Some positions may involve online testing... No agency phone calls... etc. Also EEO boilerplate to remove. Thus sections: - About the role: could combine the introductory paragraphs about role and overview. Use

for prose. - Responsibilities: the bullet list under "Your Impact as Assistant Project Manager, Building Code". Use

• . - Requirements / Qualifications / Skills: The "What You'll Bring To CodeGreen" includes skills and experience. Could split into Requirements (experience) and Skills (proficiency). But we can combine into one section maybe "Qualifications". However we need to follow instruction: Use headings only if real content. We can have multiple sections: Responsibilities, Qualifications, Skills, Benefits, Pay. But we must avoid thin sections. Let's see. We have: - Responsibilities: clear list. - Qualifications: maybe "1-3 years of building code project management experience..." plus "Strong communication, organization, and attention to detail; able to manage multiple priorities across clients and projects". That's more like skills. - Skills: "Proficient in Microsoft Office (Word, Excel, Project); Knowledge of NYC permit application processes, city filing platforms (DOB Now, BIS, E-filing, Inspection Ready), and strategies around submission timing and approval sequencing is a plus; Experience working with commercial/residential owners, tenants, developers, and architects, and familiarity with construction plans is a plus". That's skills. We could combine Qualifications and Skills into one section "Requirements". But we have separate headings allowed: Requirements, Qualifications, Skills. We need to decide. Better to have: - About the role (intro paragraphs) - Responsibilities (bullet list) - Requirements (bullet list of experience and maybe education? Not given explicit education but we can include "1-3 years of building code project management experience..." as requirement) - Skills (bullet list of technical proficiencies) - Benefits (bullet list of benefits) - Pay (salary range) We should not include Schedule (no info). Avoid empty sections. Now we need to preserve all substantive information, not invent or summarize away detail. So we need to keep the exact phrasing? We can keep the substance but not necessarily verbatim? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Safer to keep the original sentences/phrases but we can format as list items. We need to remove boilerplate like disclaimer, EEO, etc. Let's extract content. Intro paragraphs: - "Are you ready to drive growth and build lasting client relationships as a key leader in business development for CodeGreen? If you’re passionate about making a real impact and advancing your career, we want to hear from you!" - "CodeGreen, a Pinchin company, makes buildings and environments better. We are a multidisciplinary engineering and consulting firm with offices across North America. Our teams bring together expertise in environmental services, compliance, building science and resiliency, sustainability, special inspections, and fire & life safety. We help clients create safe, healthy, and higher performing places through solutions that reflect innovation, care, and deep technical insight. At CodeGreen, we empower our people to uphold unwavering principles and work with purpose to create better outcomes for our clients, communities, and environments." - "CodeGreen is seeking a Assistant Project Manager, Building Code to join our Code Compliance team in New York. The role reports to the Senior Technical Director." - Overview: "At CodeGreen, our Compliance teams help clients navigate the increasingly complex regulatory requirements that shape the built environment. Through expertise in code compliance, inspections, fire and life safety, and related advisory services, we help organizations reduce risk, maintain compliance, and make informed decisions that protect their assets and operations. This work supports safer, more resilient, and higher-performing buildings while helping clients adapt to evolving regulatory expectations and long-term business goals." - "CodeGreen is looking for a detail-oriented and proactive Assistant Project Manager, Building Code to help guide our clients through the complex world of building code and regulatory approvals. As a key member of our Code Compliance team, you’ll play a hands-on role in moving high-profile projects forward - ensuring filings, permits, and approvals are completed accurately, efficiently, and with a strong customer focus. If you thrive on navigating city agency processes, solving regulatory challenges, and being part of a collaborative, fast-paced team, we’d love to meet you." - "We welcome applications from candidates at all experience levels, including recent graduates and career changers" We can combine these into About the role section. Now Responsibilities bullet list: From "Your Impact as Assistant Project Manager, Building Code": - Manage end-to-end filing and permitting services across city agencies (DOB, LPC, FDNY, DOT, etc.), including Application Approvals, Permit Issuance, Signoffs, Violations, and Tracking - Prepare proposals, monitor project budgets, issue Change Orders, and develop project schedules and milestones with internal teams and clients - Lead standard Alteration Filings (ALT-2) and the full TCO/FCO process from filing through approval, proactively resolving DOB objections and ensuring timely Certificates of Occupancy - Maintain ongoing communication with clients, design consultants, and construction managers to advance projects and remove roadblocks; conduct site visits and in-person meetings as needed Now Requirements: maybe "1-3 years of building code project management experience, including exposure to DOB processes, TCO/FCO filings, inspections, and sign-off requirements is preferred but not required". Also "Strong communication, organization, and attention to detail; able to manage multiple priorities across clients and projects". That could be requirement/skill. But we can treat "Strong communication, organization, and attention to detail; able to manage multiple priorities across clients and projects" as a skill. Let's decide: Section Requirements: include the experience requirement: "1-3 years of building code project management experience, including exposure to DOB processes, TCO/FCO filings, inspections, and sign-off requirements is preferred but not required". Also maybe "For Current Employees Current employees are encouraged to speak with HR for information on the application process." That's not a requirement, it's a note; we can drop as boilerplate? It's not EEO but it's internal note. Might be considered minor metadata; we could drop or include in a short p. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." This is minor metadata; we can drop. Now Skills: list: - Proficient in Microsoft Office (Word, Excel, Project) - Knowledge of NYC permit application processes, city filing platforms (DOB Now, BIS, E-filing, Inspection Ready), and strategies around submission timing and approval sequencing is a plus - Experience working with commercial/residential owners, tenants, developers, and architects, and familiarity with construction plans is a plus Also maybe "Strong communication, organization, and attention to detail; able to manage multiple priorities across clients and projects" could go here as skill. But we already used that in Requirements? Let's move it to Skills. Now Benefits: list from benefits paragraph: - Comprehensive Benefit package including medical, dental, and vision coverage - Health Savings Account - Employer funded Health Reimbursement Account - Dependent Care FSA ensuring flexible options - Strong 401(k) plan with employer matching - Reimbursement of association fees - Ample resources for ongoing professional development We could also include "competitive salaries and great benefits" but we have Pay section. Now Pay: Salary range: $55,000 - $85,000. Also mention "Pay ranges are listed as required by law. Final compensation reflects each candidate’s education, experience, qualifications, and work location." That's substantive; we can include that as prose. Now we need to avoid sections with filler like "commensurate with experience". We have actual range. Now we need to output only HTML fragment, no /, no markdown. We'll produce:

  About the role

  ... paragraphs ...

  Responsibilities

  • ...
  ...

  Requirements

  • 1-3 years of building code project management experience, including exposure to DOB processes, TCO/FCO filings, inspections, and sign-off requirements is preferred but not required

  Skills

  • Strong communication, organization, and attention to detail; able to manage multiple priorities across clients and projects
  • Proficient in Microsoft Office (Word, Excel, Project)
  • Knowledge of NYC permit application processes, city filing platforms (DOB Now, BIS, E-filing, Inspection Ready), and strategies around submission timing and approval sequencing is a plus
  • Experience working with commercial/residential owners, tenants, developers, and architects, and familiarity with construction plans is a plus

  Benefits

  • Comprehensive Benefit package including medical, dental, and vision coverage
  • Health Savings Account
  • Employer funded Health Reimbursement Account
  • Dependent Care FSA ensuring flexible options
  • Strong 401(k) plan with employer matching
  • Reimbursement of association fees
  • Ample resources for ongoing professional development

  Pay

  Salary range: $55,000 - $85,000. Pay ranges are listed as required by law. Final compensation reflects each candidate’s education, experience, qualifications, and work location.

  We should not include Schedule section. Check for any leftover