Electrical Operations Manager - Multi-Family
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to decide which sections to include based on content.
We have:
- Company description (Romanoff Group of Companies...). Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for the company description and position summary.
- "Great Reasons To Join" list: includes bullet points: 11x Employee Voted Top Workplace, Highly Competitive Wage, Excellent Benefits Package (list), $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 is benefits and perks. Could be placed under Benefits section. Also there is a separate "Benefits And Compensation" section later with similar info. We need to avoid duplication. We should combine benefits info into one Benefits section, preserving all details.
- Position Summary: description of role.
- Position Responsibilities: list of duties.
- Qualifications: required and preferred.
- Physical Demands: maybe could be part of Requirements? Not a standard heading but we could include under Requirements or maybe a separate section? The instruction only lists certain headings; we can add others if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. Physical Demands could be placed under Requirements or Qualifications? Probably under Requirements (physical demands). Could be a
within Requirements.
- Benefits And Compensation: we already have benefits.
- Pay: Not explicitly stated except "Highly Competitive Wage" but no specific number. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. "Highly Competitive Wage" is vague but it's stating that there is a competitive wage. Is that enough to include a Pay section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Highly Competitive Wage" which is a statement about pay, albeit not a number. That could be considered stating pay info. However they also say avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Highly Competitive Wage" is somewhat vague but not exactly filler; it's a claim. I'd lean to include a Pay section with that statement.
- Schedule: "Standard Work Schedule Monday - Friday 7:00am - 4:00pm. MUST be willing to be flexible as jobs may change." That's specific schedule info, so we can include Schedule section.
Thus sections: About the role (company description + position summary?), Responsibilities, Requirements (maybe combine qualifications and physical demands?), Qualifications (maybe separate?), Benefits, Pay, Schedule.
But we need to avoid thin sections. Could combine Requirements and Qualifications into one? The instruction lists both as possible headings. We could have Requirements for mandatory items, Qualifications for preferred? But we have both required and preferred. Could split: Requirements for required items, Qualifications for preferred items. That seems reasonable.
Physical Demands could go under Requirements as a paragraph.
Skills: Not explicitly listed; we have "Excellent time management, organizational skills, and attention to detail." That's skills. Could be a Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
Now we need to extract content.
About the role: Should include company description and position summary. The company description: "The Romanoff Group of Companies, headquartered in Columbus, Ohio, with offices in eleven markets covering eight states, are a blend of commercial and residential, electrical, heating & cooling, and plumbing companies primarily serving the new housing construction market. Since our founding in 1982, our growth has been fueled by the pride and craftsmanship of our team, supported by exceptional project management and industry-leading expertise. As a 100% employee-owned company, we are deeply committed to the success of our team. This sense of ownership is reflected in the professionalism, integrity, and dedication we bring to every project — and in the positive impact we strive to make in the communities we serve." Then position summary: "The Electrical Operations Manager will oversee and manage operations and project activities by leading a team of Project Managers and/or Field Management to achieve division objectives. Responsible for customer service, high level problem-solving, personnel development, project performance, and team accountability to organizational expectations."
We can combine into a few paragraphs.
Responsibilities: list of duties from "Position Responsibilities". We need to put each as
- . The list includes many items; we need to preserve all. Let's extract them:
- Provide leadership and coaching to the operations team, ensuring alignment with company processes and standards.
- Review and interpret project documents such as drawings, specifications, and contracts to guide project approach and execution.
- Create a collaborative, high-performance environment that encourages continuous learning, professional growth, and performance improvement.
- Lead performance reviews, providing unbiased feedback to support employee development.
- Plan, execute, and monitor projects from inception to completion, ensuring adherence to schedules, budgets, and quality standards.
- Troubleshoot and resolve obstacles or challenges to ensure projects stay on track.
- Develop and communicate accurate project plans, ensuring clarity on project scope, timelines, and responsibilities.
- Develop and manage operations, including forecasting, cost control, financial reporting, and budget adherence. (Original: "Develop and manage operations, including forecasting, cost control, financial reporting, and budget adherence.")
- Identify cost-saving opportunities and implement strategies for operational efficiencies, waste reduction, and process improvements.
- Approve invoices, review job costs, and track purchase order and project history to ensure accurate and timely billing.
- Actively participate in monthly contract status reviews to ensure financial targets are being met.
- Collaborate across all departments ensuring smooth daily operations.
- Foster strong relationships with customers, vendors, suppliers, and other stakeholders to enhance communication and project success.
- Represent the company in meetings and activities, maintaining the company's reputation and ensuring alignment with project goals.
- Establish and enforce safety protocols, ensuring a positive safety culture across all projects.
- Monitor project performance to maintain compliance with local codes, industry standards, and organizational safety policies.
- Manage relationships with all stakeholders to ensure timely and quality deliveries.
- Ensure client satisfaction and address concerns/issues to maintain strong partnerships.
- Additional duties as assigned.
We need to ensure we didn't miss any.
Now Requirements: required items:
- 10+ years in related field and Project Management construction experience.
- High school diploma or GED.
- Thorough understanding of relevant industry practices, theory, and code involved in the business.
- 1+ year of managerial experience.
- Proficient in Microsoft Office Suite or related software.
Also maybe "Must be able to pass a pre-employment drug screen and background check." That is a requirement but could be placed under Requirements as well.
Physical Demands: "Prolonged periods of sitting at a desk and working on a computer. Periodic exposure to outdoor conditions. May occasionally lift and/or move up to 25 lbs." Could be a paragraph under Requirements.
Qualifications (preferred):
- College education in construction management.
- Professional Certifications or Licenses.
Also maybe "Excellent time management, organizational skills, and attention to detail." That's skills.
Skills: "Excellent time management, organizational skills, and attention to detail."
Benefits: Need to combine from "Great Reasons To Join" and "Benefits And Compensation". Let's list:
From Great Reasons To Join:
- 11x 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
From Benefits And Compensation:
- 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.
We need to avoid duplication but preserve all substantive info. We can combine into a Benefits section with bullet points, ensuring we don't repeat same thing. Let's create a comprehensive list:
- 11x Employee Voted Top Workplace
- Highly Competitive Wage
- Comprehensive Benefits Package: Medical, Dental, Vision, Life/AD&D; voluntary benefits: STD, LTD, Critical Illness, Accident Insurance
- $15,000 Company Paid Life Insurance
- 401(k) plan
- Employee Stock Ownership Plan (100% employee-owned)
- Training and Support
- Paid Time Off and Paid Holidays
- Advancement Opportunities
- Paid Apprenticeship and Educational Reimbursement
We should also mention "Paid vacation, and holidays" already covered by Paid Time Off and Paid Holidays.
Now Pay: The posting states "Highly Competitive Wage". That's the only pay info. We'll put that in Pay section as a paragraph.
Schedule: "Standard Work Schedule Monday - Friday 7:00am - 4:00pm. MUST be willing to be flexible as jobs may change."
Now we need to output HTML fragment with
headings and - for lists,
for prose.
We must not include any boilerplate like EEO statement. Remove that.
We must not include duplicated lines.
We must not include application instructions.
We must not include minor metadata like Job ID.
Now produce HTML.
Structure:
About the role
... company description ...
... position summary ...
Responsibilities
- ...
...
Requirements
... required items ... maybe as list? The instruction says use
- for any list of duties/requirements/benefits. So requirements list should be
. Physical demands could be a inside Requirements after list? Or we could include physical demands as a list item? Better to keep as
after list.
Thus:
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. We have: - Company description (Romanoff Group of Companies...). Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for the company description and position summary. - "Great Reasons To Join" list: includes bullet points: 11x Employee Voted Top Workplace, Highly Competitive Wage, Excellent Benefits Package (list), $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 is benefits and perks. Could be placed under Benefits section. Also there is a separate "Benefits And Compensation" section later with similar info. We need to avoid duplication. We should combine benefits info into one Benefits section, preserving all details. - Position Summary: description of role. - Position Responsibilities: list of duties. - Qualifications: required and preferred. - Physical Demands: maybe could be part of Requirements? Not a standard heading but we could include under Requirements or maybe a separate section? The instruction only lists certain headings; we can add others if needed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those as examples. Safer to stick to those headings. Physical Demands could be placed under Requirements or Qualifications? Probably under Requirements (physical demands). Could be a
within Requirements. - Benefits And Compensation: we already have benefits. - Pay: Not explicitly stated except "Highly Competitive Wage" but no specific number. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. "Highly Competitive Wage" is vague but it's stating that there is a competitive wage. Is that enough to include a Pay section? It says "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Highly Competitive Wage" which is a statement about pay, albeit not a number. That could be considered stating pay info. However they also say avoid filler like "commensurate with experience", "not specified", "N/A", "varies", "TBD". "Highly Competitive Wage" is somewhat vague but not exactly filler; it's a claim. I'd lean to include a Pay section with that statement. - Schedule: "Standard Work Schedule Monday - Friday 7:00am - 4:00pm. MUST be willing to be flexible as jobs may change." That's specific schedule info, so we can include Schedule section. Thus sections: About the role (company description + position summary?), Responsibilities, Requirements (maybe combine qualifications and physical demands?), Qualifications (maybe separate?), Benefits, Pay, Schedule. But we need to avoid thin sections. Could combine Requirements and Qualifications into one? The instruction lists both as possible headings. We could have Requirements for mandatory items, Qualifications for preferred? But we have both required and preferred. Could split: Requirements for required items, Qualifications for preferred items. That seems reasonable. Physical Demands could go under Requirements as a paragraph. Skills: Not explicitly listed; we have "Excellent time management, organizational skills, and attention to detail." That's skills. Could be a Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Now we need to extract content. About the role: Should include company description and position summary. The company description: "The Romanoff Group of Companies, headquartered in Columbus, Ohio, with offices in eleven markets covering eight states, are a blend of commercial and residential, electrical, heating & cooling, and plumbing companies primarily serving the new housing construction market. Since our founding in 1982, our growth has been fueled by the pride and craftsmanship of our team, supported by exceptional project management and industry-leading expertise. As a 100% employee-owned company, we are deeply committed to the success of our team. This sense of ownership is reflected in the professionalism, integrity, and dedication we bring to every project — and in the positive impact we strive to make in the communities we serve." Then position summary: "The Electrical Operations Manager will oversee and manage operations and project activities by leading a team of Project Managers and/or Field Management to achieve division objectives. Responsible for customer service, high level problem-solving, personnel development, project performance, and team accountability to organizational expectations." We can combine into a few paragraphs. Responsibilities: list of duties from "Position Responsibilities". We need to put each as
headings and - for lists,
for prose.
We must not include any boilerplate like EEO statement. Remove that.
We must not include duplicated lines.
We must not include application instructions.
We must not include minor metadata like Job ID.
Now produce HTML.
Structure:
About the role
... company description ...
... position summary ...
Responsibilities
- ...
...
Requirements
... required items ... maybe as list? The instruction says use
- for any list of duties/requirements/benefits. So requirements list should be
. Physical demands could be a inside Requirements after list? Or we could include physical demands as a list item? Better to keep as
after list.
Thus:
for prose. We must not include any boilerplate like EEO statement. Remove that. We must not include duplicated lines. We must not include application instructions. We must not include minor metadata like Job ID. Now produce HTML. Structure:
About the role
... company description ...
... position summary ...
Responsibilities
- ... ...
Requirements
... required items ... maybe as list? The instruction says use
- for any list of duties/requirements/benefits. So requirements list should be
- . Physical demands could be a
inside Requirements after list? Or we could include physical demands as a list item? Better to keep as
after list. Thus: