Prevailing Wage Administrator
Honeywell Technologies · Costa Mesa, CA · 3 wk ago
Information Technology$55k–$69k/yrFull-time
We need to output only HTML fragment, using for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We need to parse the job description.
We have:
- Job Description: main function... (some prose). Could be "About the role". We'll put that under
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only if posting has real specific content. We need to parse the job description.
We have:
- Job Description: main function... (some prose). Could be "About the role". We'll put that under About the role
with
. - Responsibilities: list of duties. We'll put
Responsibilities
with- items.
- Qualifications: includes Basic Qualifications and Preferred Qualifications. Could be under
Qualifications
with- maybe separate? The instruction: Use
- for any list of duties/requirements/benefits. So we can list qualifications as list items.
- Skills: maybe not explicit separate; but we have "Strong communications skills", "Microsoft Office Suite", "SAP", etc. Could be under Skills section. However we can also include them under Qualifications. But we need to decide: The posting includes qualifications and skills mixed. We could create a Skills section for items like "Microsoft Office Suite", "SAP", "Strong communications skills (both written and verbal)", "Ability to communicate with both internal and external stakeholders", "Self‑driven", "Adaptable to changing requirements". But we also have Basic Qualifications: High School Diploma or GED, 3 years experience in administrative support role. Preferred Qualifications: Experience working with virtual teams, Demonstrated working proficiency in Microsoft Office Suite, 3 years’ experience with SAP, Strong communications skills, Ability to communicate..., Self‑driven..., Understand importance..., Adaptable...
Thus we could have Qualifications section for education/experience, and Skills section for skills. But we must only include sections if posting has real specific content. It does.
- Benefits: The posting includes a Benefits paragraph with details. So we include
Benefits
with- list.
- Pay: The posting includes "The annual base salary range for this position is $55,200- $69,000." So we include Pay section.
- Schedule: Not mentioned. No schedule info. So we should NOT include Schedule section.
- About Honeywell Technologies: Could be "About the role"? Actually there is an "About Honeywell Technologies" paragraph describing company. Could be considered "About the role"? But we already have About the role for job description. There's also "About Us" repeated later. We could treat that as "About the role"? But the instruction: Use
- .
Qualifications: Basic Qualifications:
- High School Diploma or GED Diploma
- 3 years’ experience in administrative support role
Preferred Qualifications:
- Experience working with virtual teams
- Demonstrated working proficiency in Microsoft Office Suite
- 3 years’ experience with SAP
- Strong communications skills (both written and verbal)
- Ability to communicate with both internal and external stakeholders
- Self‑driven with the ability to work independently, as well as within the team
- Understand the importance of delivering a high level of service to your customers
- Adaptable to changing requirements
We could separate Basic and Preferred but we can just list all as qualifications.
Skills: Could extract skills from Preferred Qualifications: Microsoft Office Suite, SAP, Strong communications skills, Ability to communicate..., Self‑driven, Adaptable to changing requirements, Understand importance of delivering high level of service. But these are already in qualifications. To avoid duplication, we could put skills section separate but ensure not duplicate content. However instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we split, we still preserve all info, just in different sections. That's okay as long as we don't lose any. But we risk duplication if we list same items in both sections. Better to keep Qualifications section for education/experience, and Skills section for skills like Microsoft Office Suite, SAP, Strong communications skills, Ability to communicate..., Self‑driven, Adaptable..., Understand importance... However some of those also appear as qualifications. But we can treat them as skills. The Basic Qualifications are education/experience. Preferred Qualifications include both experience and skills. We could split: Basic Qualifications under Qualifications, and Preferred under Skills. But the instruction says use headings like Qualifications, Skills. So we can have Qualifications for Basic Qualifications (education/experience) and Skills for Preferred Qualifications (skills). Let's do that.
Thus:
Qualifications
- High School Diploma or GED Diploma
- 3 years’ experience in administrative support role
Skills
- Experience working with virtual teams
- Demonstrated working proficiency in Microsoft Office Suite
- 3 years’ experience with SAP
- Strong communications skills (both written and verbal)
- Ability to communicate with both internal and external stakeholders
- Self‑driven with the ability to work independently, as well as within the team
- Understand the importance of delivering a high level of service to your customers
- Adaptable to changing requirements
- Employer subsidized Medical, Dental, Vision, and Life Insurance
- Short-Term and Long-Term Disability
- 401(k) match
- Flexible Spending Accounts
- Health Savings Accounts
- EAP (Employee Assistance Program)
- Educational Assistance
- Parental Leave
- Paid Time Off (for vacation, personal business, sick time, and parental leave)
- 12 Paid Holidays
- maybe. But we can incorporate into a
before list. However instruction: Use
- for any list of duties/requirements/benefits. So we should list benefits as list items. The introductory sentence could be a
. We'll do:
In addition to a competitive salary, leading-edge work, and developing solutions side-by-side with dedicated experts in their fields, Honeywell employees are eligible for a comprehensive benefits package.
then- list.
Pay: We have salary range and note. We'll do
Pay
The annual base salary range for this position is $55,200
- for any list of duties/requirements/benefits. So we should list benefits as list items. The introductory sentence could be a
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role section describing the role. The company description could be placed under About the role or maybe omitted as boilerplate? It's not boilerplate; it's about the company. But we have no specific heading for company. Could include it in About the role as part of description. However we must not repeat job title as heading. It's fine. We also need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out EEO statement, "Learn more" links, "Application Deadline Language Also Needs To Be Included", "Posting Date: September 24, 2026", "About Us" duplicate maybe? Actually "About Us" repeats the same as earlier "About Honeywell Technologies". We should keep only one instance? The instruction: remove duplicated lines. So we should keep only one copy of the company description. We'll keep the first "About Honeywell Technologies" paragraph and discard the later "About Us" duplicate. Also remove "Learn more" links and maybe the "Learn more" after Benefits? The Benefits paragraph ends with "Learn more". That's likely a link; we should remove that phrase. Also remove "Learn more" after company description. Also remove "This Application Deadline Language Also Needs To Be Included" etc. That's boilerplate. Also remove "Please note that this salary information serves as a general guideline..." That's part of Pay description; we can keep the salary range but maybe remove the note? It's not boilerplate but it's extra commentary. The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The note about salary being a guideline is substantive? It's still about salary. I'd keep it as part of Pay section. Also remove "The annual base salary range for this position is $55,200- $69,000." Keep that. Also remove "The application period for the job is estimated to be 40 days from the job posting date; however, this may be shortened or extended depending on business needs and the availability of qualified candidates." That's application instruction/boilerplate; remove. Also remove "Posting Date: September 24, 2026." That's metadata; we can drop. Also remove "Learn more" after Benefits and after company description. Also remove "Honeywell is an equal opportunity employer..." EEO boilerplate; remove. Also remove "Qualified applicants will be considered without regard to..." etc; remove. Now we need to structure. Let's extract substantive content: Job Description (main function): "The main function of this position encompasses the management of Honeywell Technician and Subcontractors’ Prevailing Wage compliance, including but not limited to the wage determinations, on ‐ time Certified Payroll submissions and record keeping according to policy. You will report directly to the Prevailing Wage Supervisor and work with a team of HBS US Project Managers and Subcontractors. You will be based at the Atlanta, GA or Costa Mesa, CA location." That's About the role. Responsibilities: list: - General understanding of Public Works projects related to Federal and State Prevailing Wage laws and policies and processing, coordinating, and executing of Certified Payroll submission - Compute Prevailing Wage calculations based on project specific Prevailing Wage schedule against Technician time sheets collected, benefit data calculated; also verify correct wages are paid for counties worked in based of wage schedules - Review weekly Technician time sheets for accuracy, making sure breaks, time worked, overtime – are all in accordance with Prevailing Wage Laws, and work orders placed to correct jobs/ contracts for certified payroll documents - Working closely with multiple US Districts to review and log benefit data – 401K, Life, Disability, Vacation, Sick, - calculate correct amounts to be used on a biweekly pay period for each employee individually - As an Approved Payroll Specialist enter PTOP adjustments for coordinating pay cycles - Working with project managers and other professionals in Payroll, Benefits and Administration on Certified Payroll submissions - Complete all applicable certified payroll forms that Public Works contracts require. Making sure these are processed with 100% accuracy as well as in compliance with all time restrictions - Manage Honeywell subcontractor certification forms to all hired subs, along with appropriate wage schedules, track receipt of these - Audit all Subcontractor Certified Payroll for compliance We need to ensure each bullet is a
- .
Qualifications: Basic Qualifications:
- High School Diploma or GED Diploma
- 3 years’ experience in administrative support role
Preferred Qualifications:
- Experience working with virtual teams
- Demonstrated working proficiency in Microsoft Office Suite
- 3 years’ experience with SAP
- Strong communications skills (both written and verbal)
- Ability to communicate with both internal and external stakeholders
- Self‑driven with the ability to work independently, as well as within the team
- Understand the importance of delivering a high level of service to your customers
- Adaptable to changing requirements
We could separate Basic and Preferred but we can just list all as qualifications.
Skills: Could extract skills from Preferred Qualifications: Microsoft Office Suite, SAP, Strong communications skills, Ability to communicate..., Self‑driven, Adaptable to changing requirements, Understand importance of delivering high level of service. But these are already in qualifications. To avoid duplication, we could put skills section separate but ensure not duplicate content. However instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. If we split, we still preserve all info, just in different sections. That's okay as long as we don't lose any. But we risk duplication if we list same items in both sections. Better to keep Qualifications section for education/experience, and Skills section for skills like Microsoft Office Suite, SAP, Strong communications skills, Ability to communicate..., Self‑driven, Adaptable..., Understand importance... However some of those also appear as qualifications. But we can treat them as skills. The Basic Qualifications are education/experience. Preferred Qualifications include both experience and skills. We could split: Basic Qualifications under Qualifications, and Preferred under Skills. But the instruction says use headings like Qualifications, Skills. So we can have Qualifications for Basic Qualifications (education/experience) and Skills for Preferred Qualifications (skills). Let's do that.
Thus:
- for any list of duties/requirements/benefits. So we can list qualifications as list items.
- Skills: maybe not explicit separate; but we have "Strong communications skills", "Microsoft Office Suite", "SAP", etc. Could be under Skills section. However we can also include them under Qualifications. But we need to decide: The posting includes qualifications and skills mixed. We could create a Skills section for items like "Microsoft Office Suite", "SAP", "Strong communications skills (both written and verbal)", "Ability to communicate with both internal and external stakeholders", "Self‑driven", "Adaptable to changing requirements". But we also have Basic Qualifications: High School Diploma or GED, 3 years experience in administrative support role. Preferred Qualifications: Experience working with virtual teams, Demonstrated working proficiency in Microsoft Office Suite, 3 years’ experience with SAP, Strong communications skills, Ability to communicate..., Self‑driven..., Understand importance..., Adaptable...
Thus we could have Qualifications section for education/experience, and Skills section for skills. But we must only include sections if posting has real specific content. It does.
- Benefits: The posting includes a Benefits paragraph with details. So we include