Engineering Plans Leader I
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
From job description: There's a description paragraph about role, then "What You'll Do" list, then "Requirements" list, then "Benefits" list with subpoints. There's no explicit Pay or Schedule. There's no separate "Qualifications" vs "Requirements"? The posting has "Requirements" and also mentions "Associate's degree ... preferred", "Surveyor-in-Training (SIT) preferred; Professional Land Surveyor (PLS) a plus", "Experience with LiDAR or 3D scan data a plus". Those could be considered Qualifications or Skills. But we have headings: Requirements, Qualifications, Skills, Benefits. We need to avoid duplicate or thin sections. We can combine qualifications and skills under Requirements? But we need to follow instruction: include a section ONLY when posting has real, specific content for it. So we need to decide which headings have content.
We have content for:
- About the role: The initial paragraph describing role: "Rodriguez Consulting is hiring an Engineering Plans Leader I to lead AutoCAD Civil 3D survey drafting production for our Philadelphia infrastructure work. You'll oversee existing conditions surveys and base plans, including boundary and right-of-way surveys and ALTA/NSPS Land Title Surveys, that support water, sewer, stormwater, roadway and ADA design for the Philadelphia Water Department, the Streets Department and other public and private clients. This is a leadership role. You'll direct and review the work of our Engineering Technicians, Engineering Aides, and Project Coordinators, bring new drafting staff up to our CADD standards, and work closely with our licensed surveyor, field survey team, and design engineers."
That's substantive.
- Responsibilities: The "What You'll Do" list: bullet points.
- Requirements: The list under "Requirements" heading: bullet points.
- Benefits: The "Benefits" section with subpoints: Lifestyle & Perks, Career & Growth, Financial & Security. Those are specifics.
- Qualifications: Could be the education and certifications preferences (Associate's degree, SIT, PLS, LiDAR). Those could go under Qualifications. But we already have Requirements covering experience and skills. The posting lumps them under "Requirements". However we could split: Requirements (experience), Qualifications (education/certifications), Skills (technical skills). But we need to avoid thin sections. Let's see if we have enough for each.
Qualifications content: "Associate's degree or equivalent technical training in surveying, geomatics, civil engineering or a related field preferred Surveyor-in-Training (SIT) preferred; Professional Land Surveyor (PLS) a plus Experience with LiDAR or 3D scan data a plus". That's specific enough for a Qualifications section.
Skills content: "Advanced Civil 3D skills, including COGO point management and surface creation Working knowledge of deeds, record plans, legal descriptions, title commitments and the ALTA/NSPS Minimum Standard Detail Requirements Ability to evaluate survey data and base plans prepared by others, including control, topographic and utility survey Experience directing and reviewing the work of other drafters Strong written and verbal communication skills PWD, City of Philadelphia or PA One Call experience strongly preferred". Those could be Skills.
But the posting already has a "Requirements" heading that includes many of those bullet points. Actually the "Requirements" section includes: "8+ years of AutoCAD Civil 3D survey drafting experience, including boundary, right-of-way and ALTA/NSPS plans Advanced Civil 3D skills, including COGO point management and surface creation Working knowledge of deeds, record plans, legal descriptions, title commitments and the ALTA/NSPS Minimum Standard Detail Requirements Ability to evaluate survey data and base plans prepared by others, including control, topographic and utility survey Experience directing and reviewing the work of other drafters Strong written and verbal communication skills PWD, City of Philadelphia or PA One Call experience strongly preferred Associate's degree or equivalent technical training in surveying, geomatics, civil engineering or a related field preferred Surveyor-in-Training (SIT) preferred; Professional Land Surveyor (PLS) a plus Experience with LiDAR or 3D scan data a plus". So the Requirements section lumps experience, skills, qualifications. So we could just have one Requirements section and not split further. That would avoid thin sections.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
We need to output HTML fragment with headings and appropriate
or
- . Ensure we preserve all substantive information. Remove boilerplate: EEO etc. Also remove duplicated lines. Also remove application instructions (none). Also remove cookie/navigation/legal etc. We need to include all content from description, responsibilities, requirements, benefits. Let's extract. About the role paragraph: Combine sentences. Rodriguez Consulting is hiring an Engineering Plans Leader I to lead AutoCAD Civil 3D survey drafting production for our Philadelphia infrastructure work. You'll oversee existing conditions surveys and base plans, including boundary and right-of-way surveys and ALTA/NSPS Land Title Surveys, that support water, sewer, stormwater, roadway and ADA design for the Philadelphia Water Department, the Streets Department and other public and private clients. This is a leadership role. You'll direct and review the work of our Engineering Technicians, Engineering Aides, and Project Coordinators, bring new drafting staff up to our CADD standards, and work closely with our licensed surveyor, field survey team, and design engineers. That's the About the role. Responsibilities: bullet list from "What You'll Do": - Lead production of topographic, existing utility, boundary, right-of-way, ALTA/NSPS, subdivision and as-built plans - Prepare boundary and right-of-way work for the licensed surveyor's review and signature, including deed and record plan research, City Plan lines and legal descriptions - Coordinate ALTA/NSPS surveys against the current standards, the client's Table A items and the title commitment - Review drafting work for accuracy and consistency before it goes to final QA/QC - Set daily production priorities for drafting staff and train new team members - Work with clients and agency reviewers to address plan comments - Help improve our CADD standards and bring automation and AI-assisted tools into production Make each as
- . Requirements: bullet list from "Requirements" heading: - 8+ years of AutoCAD Civil 3D survey drafting experience, including boundary, right-of-way and ALTA/NSPS plans - Advanced Civil 3D skills, including COGO point management and surface creation - Working knowledge of deeds, record plans, legal descriptions, title commitments and the ALTA/NSPS Minimum Standard Detail Requirements - Ability to evaluate survey data and base plans prepared by others, including control, topographic and utility survey - Experience directing and reviewing the work of other drafters - Strong written and verbal communication skills - PWD, City of Philadelphia or PA One Call experience strongly preferred - Associate's degree or equivalent technical training in surveying, geomatics, civil engineering or a related field preferred - Surveyor-in-Training (SIT) preferred; Professional Land Surveyor (PLS) a plus - Experience with LiDAR or 3D scan data a plus Make each
- .
Benefits: The posting has "Benefits" then subheadings Lifestyle & Perks, Career & Growth, Financial & Security with bullet points.
We need to preserve all substantive information. Should we keep subheadings? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid subheadings inside sections, but we could just treat the benefits as a section with subpoints maybe using
- and include the subheadings as part of list items? Better to keep subheadings as plain text inside
or ? But we must output only HTML fragment, no markdown. We could embed for subheadings inside the
- items? However the instruction says use
- for any list of duties/requirements/benefits. So we can have a
- for benefits, and each
- can contain the subheading text and details. Or we could have nested lists? Simpler: create a
- with each benefit category as a
- containing a subheading and then a
- inside? That might be okay but could be considered nested list. The instruction didn't forbid nested lists. But to keep simple, we can just make each benefit bullet as a
- with the subheading and details separated by a colon.
Let's extract benefits:
Lifestyle & Perks:
- Prime Fishtown location with free parking, bike-friendly facilities and easy access to public transportation
- Modern amenities, including on-site gym access and a café
Career & Growth:
- Leadership of a skilled drafting team on high-visibility public infrastructure work
- Professional development, including company-sponsored training and continuing education
- Support for surveying licensure, from SIT to PLS
- A defined career path within the Engineering Support track
Financial & Security:
- Comprehensive insurance: health, dental, vision, life, AD&D and disability coverage
- Retirement planning with employer matching contributions
- Generous time off, including 15 PTO days and 8 PDO days annually
We'll output as
- each bullet. Could include the category as part of the
- text: e.g., "
- Lifestyle & Perks: Prime Fishtown location with free parking, bike-friendly facilities and easy access to public transportation; Modern amenities, including on-site gym access and a café. " But that merges two bullets. Better to keep each bullet separate, but we need to indicate category. Could do: "
- Lifestyle & Perks: Prime Fishtown location with free parking, bike-friendly facilities and easy access to public transportation " then another
- for Modern amenities. Similarly for Career & Growth: each bullet preceded by Career & Growth:. That repeats category but okay.
Alternatively we could have a
inside benefits but not allowed? Only
for section headings. Could use
Lifestyle & Perks:
then- . But that adds extra elements. Might be okay but risk of being considered filler? Probably fine.
Simpler: Keep benefits as a
- and include the category in the text. Let's list all benefit items: - Prime Fishtown location with free parking, bike-friendly facilities and easy access to public transportation - Modern amenities, including on-site gym access and a café - Leadership of a skilled drafting team on high-visibility public infrastructure work - Professional development, including company-sponsored training and continuing education - Support for surveying licensure, from SIT to PLS - A defined career path within the Engineering Support track - Comprehensive insurance: health, dental, vision, life, AD&D and disability coverage - Retirement planning with employer matching contributions - Generous time off, including 15 PTO days and 8 PDO days annually We'll output each as
- .
Now ensure we didn't miss any substantive info: The "What You'll Do" includes all bullet points. The "Requirements" includes all bullet points. The "About the role" paragraph we captured.
Check for any other content: The job title is already shown, we don't repeat as heading. No Job ID. No Pay or Schedule.
Now produce HTML:
About the role
Rodriguez Consulting is hiring an Engineering Plans Leader I to lead AutoCAD Civil 3D survey drafting production for our Philadelphia infrastructure work. You'll oversee existing conditions surveys and base plans
- with each benefit item as
- with the subheading and details separated by a colon.
Let's extract benefits:
Lifestyle & Perks:
- Prime Fishtown location with free parking, bike-friendly facilities and easy access to public transportation
- Modern amenities, including on-site gym access and a café
Career & Growth:
- Leadership of a skilled drafting team on high-visibility public infrastructure work
- Professional development, including company-sponsored training and continuing education
- Support for surveying licensure, from SIT to PLS
- A defined career path within the Engineering Support track
Financial & Security:
- Comprehensive insurance: health, dental, vision, life, AD&D and disability coverage
- Retirement planning with employer matching contributions
- Generous time off, including 15 PTO days and 8 PDO days annually
We'll output as
- containing a subheading and then a
- can contain the subheading text and details. Or we could have nested lists? Simpler: create a
- for any list of duties/requirements/benefits. So we can have a
- and include the subheadings as part of list items? Better to keep subheadings as plain text inside