Electrical Field Supervisor - Multi-Family
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content.
We have job description: includes description about company, reasons to join, position summary, responsibilities, electrical responsibilities, qualifications, physical demands, benefits and compensation, EEO statement (to be removed). Also schedule: "Standard Work Schedule Monday - Friday 7:00am - 4:00pm. MUST be willing to be flexible as jobs may change." That's schedule info.
Pay: Not explicitly given. There's "Highly Competitive Wage" but no specific number. According to rules, we should not create Pay section unless posting actually states them. "Highly Competitive Wage" is vague, not a specific number. So we should not include Pay section.
Benefits: we have details: "Excellent Benefits Package (Health/HSA/Vision/Dental/Life/STD/LTD/Accident and Critical Illness) $15k Company Paid Life Insurance 401(k) Employee Stock Ownership Plan (We are 100% employee owned) Training and Support Paid Time Off and Paid Holidays Advancement Opportunities Paid Apprenticeship and Educational Reimbursement". Also later: "We provide a comprehensive package of employee benefits including: Medical, Dental, Vision, Life/AD&D; additional voluntary benefits such as STD, LTD, Critical Illness, Accident Insurance, paid vacation, and holidays; 401(k) and company paid Life Insurance, and we are 100% Employee Owned." So we have benefits content.
Schedule: we have standard work schedule Monday-Friday 7:00am-4:00pm, must be flexible.
Qualifications: we have Required: high school diploma or equivalent, 5+ years relevant experience in a leadership role, strong knowledge of Electrical codes, regulations, best practices, strong ability to manage and motivate a team. Also physical demands.
Responsibilities: we have position responsibilities list and electrical responsibilities.
About the role: maybe position summary.
We also have "Great Reasons To Join" list: 10x Employee Voted Top Workplace, Highly Competitive Wage, Excellent Benefits Package, $15k Company Paid Life Insurance, 401(k) Employee Stock Ownership Plan, Training and Support, Paid Time Off and Paid Holidays, Advancement Opportunities, Paid Apprenticeship and Educational Reimbursement. This could be part of Benefits or separate "About the company". But we need to follow headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We can put company overview in About the role (maybe position summary). The "Great Reasons To Join" could be part of Benefits or maybe we can include as part of Benefits. But we should not duplicate.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include all points.
We must not include boilerplate like EEO statement.
We need to use for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to decide which sections to include:
- About the role: could contain position summary and maybe company description? The description about Romanoff Group is company overview; could be part of About the role. We'll include that as prose.
- Responsibilities: combine Position Responsibilities and Electrical Responsibilities into a list.
- Requirements: maybe combine Qualifications and Physical Demands? The heading "Requirements" could be used for required qualifications (education, experience, knowledge, ability). Physical demands could be part of Requirements or maybe separate but we don't have a heading for Physical Demands; we could include under Requirements as a list.
- Qualifications: maybe we could treat as same as Requirements; but we need to avoid duplicate headings. The instructions say use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content. We have qualifications (education, experience, knowledge, ability). We also have skills? Not explicitly listed besides strong ability to manage and motivate a team (skill). Could include under Qualifications.
We could have both Requirements and Qualifications sections, but they'd overlap. Better to have one section for Requirements (including education, experience, knowledge, ability, physical demands). Or we could have Qualifications for education/experience/knowledge/ability and Requirements for physical demands? But the instruction says we can use those headings; we just need to include a section only when posting has real specific content for it. We have content for both Requirements (education/experience/knowledge/ability) and Qualifications (maybe same). To avoid duplication, we could combine into one section called "Requirements" and include all. Or we could have "Qualifications" for education/experience/knowledge/ability and "Requirements" for physical demands. That would be two sections with distinct content. Let's see if that makes sense.
We have: "Qualifications Required: High school diploma or equivalent Required: 5+ years of relevant experience in a leadership role Required: Strong knowledge of Electrical codes, regulations, and best practices Required: Strong ability to manage and motivate a team." That's qualifications.
Physical Demands: list of physical demands.
Thus we can have:
Qualifications
with ul list of those four items.
Requirements
with ul list of physical demands.
But the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those as possible headings. It's okay to use both Requirements and Qualifications.
We also have Skills: not explicitly listed separate; maybe we could treat strong ability to manage and motivate a team as skill, but it's already in qualifications. Could omit Skills section.
Benefits: we have benefits content.
Schedule: we have schedule.
About the role: we have position summary and company description.
Responsibilities: we have responsibilities list.
Now we need to ensure we don't include filler like "commensurate with experience", etc. We have no such.
We need to remove duplicated lines, cookie/navigation/legal/EEO etc. Remove EEO statement.
We also need to remove "Great Reasons To Join" list? It's substantive; we could incorporate into Benefits or About the role. Since we already have Benefits section, we could add those reasons as part of Benefits list. But we must not lose any info. The "Great Reasons To Join" includes: 10x Employee Voted Top Workplace, Highly Competitive Wage, Excellent Benefits Package (Health/HSA/Vision/Dental/Life/STD/LTD/Accident and Critical Illness), $15k Company Paid Life Insurance, 401(k) Employee Stock Ownership Plan (We are 100% employee owned), Training and Support, Paid Time Off and Paid Holidays, Advancement Opportunities, Paid Apprenticeship and Educational Reimbursement.
Many of these overlap with Benefits section. We need to preserve all; we can combine them, ensuring no duplication. We'll create a Benefits section that includes all unique items.
Let's extract unique benefits:
- Medical
- Dental
- Vision
- Life/AD&D (Life insurance)
- STD (Short Term Disability)
- LTD (Long Term Disability)
- Critical Illness
- Accident Insurance
- Paid vacation
- Paid holidays
- 401(k)
- Company paid Life Insurance ($15k)
- Employee Stock Ownership Plan (100% employee owned)
- Training and Support
- Paid Time Off (already covered)
- Paid Holidays (covered)
- Advancement Opportunities
- Paid Apprenticeship and Educational Reimbursement
- 10x Employee Voted Top Workplace (maybe a recognition)
- Highly Competitive Wage (but we said not to include Pay section; but it's a benefit? It's wage; but we cannot create Pay section unless specific. However "Highly Competitive Wage" is a statement about compensation but not a specific number. Should we include it? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, we can include statements about benefits; "Highly Competitive Wage" is about pay, not a benefit. But we could include it in Benefits as a statement? Might be considered pay. Safer to omit it because it's not a specific benefit and we are not creating a Pay section. However we must preserve ALL substantive information. If we omit "Highly Competitive Wage", we are losing substantive info. But we could include it in Benefits as a note? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not forbid mentioning wage in Benefits section; but it's about pay. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we cannot mention wage elsewhere. But we could include it in About the role or Benefits as a prose statement. However the rule about Pay section: we should not create a Pay section unless posting actually states them (specific numbers). Since we are not creating a Pay section, we can still mention wage in other sections. So we could include "Highly Competitive Wage" as a bullet in Benefits or About the role. Let's include it in Benefits as a bullet: "Highly Competitive Wage". That seems okay.
- 10x Employee Voted Top Workplace: could be a bullet under Benefits or About the role. We'll include in Benefits.
Now we need to ensure we don't duplicate items like Paid Time Off and Paid Holidays appear both in Great Reasons and Benefits description. We'll list each unique once.
Now we need to format.
We'll produce:
About the role
... company description and position summary ...
Responsibilities
- ...
...
Qualifications
- High school diploma or equivalent
- 5+ years of relevant experience in a leadership role
- Strong knowledge of Electrical codes, regulations, and best practices
- Strong ability to manage and motivate a team
Requirements
- Must be able to adhere to large amounts of standing, walking, bending, squatting, sitting and lifting
- Must be able to pick up, lift, carry and move up to 50 lbs
- Must be able to work in all weather conditions (including heat, rain, cold and wind) while wearing appropriate PPE
Benefits
- Medical, Dental, Vision, Life/AD&D insurance
- Short Term Disability (STD)
- Long Term Disability (LTD)
- Critical Illness insurance
- Accident Insurance
- Paid vacation and holidays
- 401(k) plan
- Company-paid Life Insurance ($15,000)
- Employee Stock Ownership Plan (100% employee-owned)
- Training and Support
- Advancement Opportunities
- Paid Apprenticeship and Educational Reimbursement
- 10x Employee Voted Top Workplace
- Highly Competitive Wage
Schedule
Standard Work Schedule Monday - Friday 7:00am - 4:00pm. Must be willing to be flexible as jobs may change.
We need
- for any list of duties/requirements/benefits, and
for prose. We need to decide which sections to include: - About the role: could contain position summary and maybe company description? The description about Romanoff Group is company overview; could be part of About the role. We'll include that as prose. - Responsibilities: combine Position Responsibilities and Electrical Responsibilities into a list. - Requirements: maybe combine Qualifications and Physical Demands? The heading "Requirements" could be used for required qualifications (education, experience, knowledge, ability). Physical demands could be part of Requirements or maybe separate but we don't have a heading for Physical Demands; we could include under Requirements as a list. - Qualifications: maybe we could treat as same as Requirements; but we need to avoid duplicate headings. The instructions say use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include based on content. We have qualifications (education, experience, knowledge, ability). We also have skills? Not explicitly listed besides strong ability to manage and motivate a team (skill). Could include under Qualifications. We could have both Requirements and Qualifications sections, but they'd overlap. Better to have one section for Requirements (including education, experience, knowledge, ability, physical demands). Or we could have Qualifications for education/experience/knowledge/ability and Requirements for physical demands? But the instruction says we can use those headings; we just need to include a section only when posting has real specific content for it. We have content for both Requirements (education/experience/knowledge/ability) and Qualifications (maybe same). To avoid duplication, we could combine into one section called "Requirements" and include all. Or we could have "Qualifications" for education/experience/knowledge/ability and "Requirements" for physical demands. That would be two sections with distinct content. Let's see if that makes sense. We have: "Qualifications Required: High school diploma or equivalent Required: 5+ years of relevant experience in a leadership role Required: Strong knowledge of Electrical codes, regulations, and best practices Required: Strong ability to manage and motivate a team." That's qualifications. Physical Demands: list of physical demands. Thus we can have:
Qualifications
with ul list of those four items.Requirements
with ul list of physical demands. But the instruction says "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So they expect those as possible headings. It's okay to use both Requirements and Qualifications. We also have Skills: not explicitly listed separate; maybe we could treat strong ability to manage and motivate a team as skill, but it's already in qualifications. Could omit Skills section. Benefits: we have benefits content. Schedule: we have schedule. About the role: we have position summary and company description. Responsibilities: we have responsibilities list. Now we need to ensure we don't include filler like "commensurate with experience", etc. We have no such. We need to remove duplicated lines, cookie/navigation/legal/EEO etc. Remove EEO statement. We also need to remove "Great Reasons To Join" list? It's substantive; we could incorporate into Benefits or About the role. Since we already have Benefits section, we could add those reasons as part of Benefits list. But we must not lose any info. The "Great Reasons To Join" includes: 10x Employee Voted Top Workplace, Highly Competitive Wage, Excellent Benefits Package (Health/HSA/Vision/Dental/Life/STD/LTD/Accident and Critical Illness), $15k Company Paid Life Insurance, 401(k) Employee Stock Ownership Plan (We are 100% employee owned), Training and Support, Paid Time Off and Paid Holidays, Advancement Opportunities, Paid Apprenticeship and Educational Reimbursement. Many of these overlap with Benefits section. We need to preserve all; we can combine them, ensuring no duplication. We'll create a Benefits section that includes all unique items. Let's extract unique benefits: - Medical - Dental - Vision - Life/AD&D (Life insurance) - STD (Short Term Disability) - LTD (Long Term Disability) - Critical Illness - Accident Insurance - Paid vacation - Paid holidays - 401(k) - Company paid Life Insurance ($15k) - Employee Stock Ownership Plan (100% employee owned) - Training and Support - Paid Time Off (already covered) - Paid Holidays (covered) - Advancement Opportunities - Paid Apprenticeship and Educational Reimbursement - 10x Employee Voted Top Workplace (maybe a recognition) - Highly Competitive Wage (but we said not to include Pay section; but it's a benefit? It's wage; but we cannot create Pay section unless specific. However "Highly Competitive Wage" is a statement about compensation but not a specific number. Should we include it? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. For Benefits, we can include statements about benefits; "Highly Competitive Wage" is about pay, not a benefit. But we could include it in Benefits as a statement? Might be considered pay. Safer to omit it because it's not a specific benefit and we are not creating a Pay section. However we must preserve ALL substantive information. If we omit "Highly Competitive Wage", we are losing substantive info. But we could include it in Benefits as a note? The rule says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does not forbid mentioning wage in Benefits section; but it's about pay. However the instruction says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It doesn't say we cannot mention wage elsewhere. But we could include it in About the role or Benefits as a prose statement. However the rule about Pay section: we should not create a Pay section unless posting actually states them (specific numbers). Since we are not creating a Pay section, we can still mention wage in other sections. So we could include "Highly Competitive Wage" as a bullet in Benefits or About the role. Let's include it in Benefits as a bullet: "Highly Competitive Wage". That seems okay. - 10x Employee Voted Top Workplace: could be a bullet under Benefits or About the role. We'll include in Benefits. Now we need to ensure we don't duplicate items like Paid Time Off and Paid Holidays appear both in Great Reasons and Benefits description. We'll list each unique once. Now we need to format. We'll produce:
About the role
... company description and position summary ...
Responsibilities
- ... ...
Qualifications
- High school diploma or equivalent
- 5+ years of relevant experience in a leadership role
- Strong knowledge of Electrical codes, regulations, and best practices
- Strong ability to manage and motivate a team
Requirements
- Must be able to adhere to large amounts of standing, walking, bending, squatting, sitting and lifting
- Must be able to pick up, lift, carry and move up to 50 lbs
- Must be able to work in all weather conditions (including heat, rain, cold and wind) while wearing appropriate PPE
Benefits
- Medical, Dental, Vision, Life/AD&D insurance
- Short Term Disability (STD)
- Long Term Disability (LTD)
- Critical Illness insurance
- Accident Insurance
- Paid vacation and holidays
- 401(k) plan
- Company-paid Life Insurance ($15,000)
- Employee Stock Ownership Plan (100% employee-owned)
- Training and Support
- Advancement Opportunities
- Paid Apprenticeship and Educational Reimbursement
- 10x Employee Voted Top Workplace
- Highly Competitive Wage
Schedule
Standard Work Schedule Monday - Friday 7:00am - 4:00pm. Must be willing to be flexible as jobs may change.
We need