Multi-Family - Operations Manager I
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We need to include sections only when posting has real, specific content for it. So we need to parse the posting.
Let's extract:
Company description: "Franklin Energy is redefining the clean energy future as the only integrated provider of comprehensive solutions, combining unmatched expertise in strategic consulting, program delivery, product solutions, and design/build services. Powered by our advanced AI-driven technology platforms, we deliver seamless, tech-driven support across the entire energy service ecosystem to accelerate impactful change and ensure an unmatched customer experience. Since 1994, Franklin Energy has been a trusted partner in protecting communities and our planet, paving the way for a sustainable future for all. Learn more at www.franklinenergy.com and join us in leading the clean energy revolution."
That's about the company, could be "About the role"? Actually "About the role" is for role description. The posting includes "Position Summary". So we can have a section "About the role" maybe with the Position Summary. Or we could have "Position Summary" as a paragraph. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content.
We have:
- Position Summary: description of responsibilities.
- Essential Duties And Responsibilities: list of duties.
- Position Requirements: Education and Experience.
- Required Skills, Knowledge And Abilities: list of skills.
- Licenses & Certifications: Valid driver’s license.
- Travel Requirements: Willingness to travel more than 60%
- Compensation & Benefits: salary range and benefits description.
We also have some notes: "Note: Reasonable accommodations may be made..." etc. That's boilerplate? It's about accommodations, maybe keep? It's not EEO but it's a note about accommodations. Might be considered boilerplate but it's substantive? Probably we can keep as part of Requirements? But it's not a list. Might be okay to keep as a paragraph under Requirements.
Also "The above information describes the general duties..." etc. That's boilerplate; we should remove.
"An Equal Opportunity Employer Safety -Sensitive Role Addendum..." That's EEO and safety; remove.
"Notice Regarding Automated Tools..." remove.
Thus we need to produce sections:
Maybe:
About the role
Position Summary ...
Responsibilities
- ...
Requirements
Education and Experience ...
Skills
- ...
Licenses & Certifications
maybe not a standard heading but could be under Requirements? But we can include as separate section if content present. The instruction says use those example headings but not limited to them? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. Licenses & Certifications could be part of Requirements or Qualifications. Travel Requirements maybe part of Schedule? Travel is not schedule. Could be under Requirements. Compensation & Benefits: we have Pay and Benefits sections. So we can split: Pay heading for salary range, Benefits heading for benefits description.
Schedule: maybe not present; we have travel requirements but not schedule. So we may omit Schedule.
Qualifications: maybe we can combine Education and Experience under Qualifications. But we already have Requirements heading. The instruction says we can use Requirements, Qualifications, Skills, etc. We need to decide.
We need to preserve all substantive info. Let's map:
- About the role: Position Summary paragraph.
- Responsibilities: Essential Duties And Responsibilities list.
- Requirements: Education and Experience (Bachelor's degree, previous operations experience, 1-3 years progressive team management experience). Also Licenses & Certifications (Valid driver's license). Travel Requirements (Willingness to travel more than 60%). Also maybe the note about reasonable accommodations? Could be included as a paragraph under Requirements.
- Skills: Required Skills, Knowledge And Abilities list.
- Pay: Compensation & Benefits salary range.
- Benefits: Compensation & Benefits benefits description.
We should not include Qualifications if we already have Requirements; but we could also have Qualifications separate for education/experience. However to avoid thin sections, we can combine education/experience under Requirements and maybe call it Requirements. That's fine.
We need to output only HTML fragment, no /, no markdown.
Let's craft.
First, About the role:
Franklin Energy is redefining the clean energy future as the only integrated provider of comprehensive solutions, combining unmatched expertise in strategic consulting, program delivery, product solutions, and design/build services. Powered by our advanced AI-driven technology platforms, we deliver seamless, tech-driven support across the entire energy service ecosystem to accelerate impactful change and ensure an unmatched customer experience. Since 1994, Franklin Energy has been a trusted partner in protecting communities and our planet, paving the way for a sustainable future for all. Learn more at www.franklinenergy.com and join us in leading the clean energy revolution.
But that's company description, not exactly role summary. The Position Summary is: "The Operations Manager is primarily responsible for management of the day to day operation of components of the program portfolio/department under the direction of the program/department Manager. These tasks may include management and reporting of staff and program/department performance, forecasting, reporting tracking and reporting of program/department metrics. The position is also responsible for establishing, execution, and reporting of all proactive quality assurance processes."
We should include that as About the role. The company description could be considered introductory but not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep company description as well. Where to put? Could be a preceding paragraph before About the role? But we cannot have extra headings not requested. We could include it as a before the first heading. That's allowed: output only HTML fragment, can have paragraphs and headings. So we can start with a
containing the company description. Then
About the role
with Position Summary.
Let's do that.
Now Responsibilities: we need to extract list items from Essential Duties And Responsibilities.
The list:
- Manage and lead Operations team including Operations Analysts, Field Operations Auditors, Project Specialists, and Project Coordinators.
- Support delivery of operations team goals towards program and portfolio Key Performance Indicators
- Support and deliver payment reviews, application intake, customer service calls, and operations team scheduling
- Program/Project forecasting, tracking, invoicing, and reporting
- Oversight for weekly and monthly departmental/program reporting
- Work with the program teams to identify opportunities for process improvement that would improve customer/client satisfaction
- Work directly with internal functional teams and/or program teams on process and QA projects
- Ensure all documentation on contracts, SOWs, Cost Allocation Agreements, KPIs, etc. are up to date and readily available on SharePoint
- Support the organization of financial, legal, and budget tracking responsibilities in relation to portfolio programs compliance
- Manage and track the compliance requirements for contracts, addendums, proposals, and subcontracts for the portfolio
- Complete special ad-hoc projects and reporting for program, program manager, operations manager, and regional director
- Act as a technical resource/consultant to develop systems, processes, and process improvements for the portfolio
- Manage operations team staffing, budgets, goals, productivity, and provide analysis, solutions and recommendations on the operations team to Operations Manager and Regional Director
- Coordinate the internal support team efforts across the portfolio including reporting, meetings, leadership team coordination, and portfolio wide training and events
- Coordinate portfolio resource sharing inside and outside of the portfolio
- Work with internal customers to support the reporting needs of the portfolio, program, and business
We need to put each as - .
Now Requirements: Education and Experience:
- Bachelor’s degree in Business, Finance, Engineering or related field from an accredited college or university.
- Previous operations experience including thorough understanding of energy efficiency or demand response program operations and processes
- 1 – 3 years of progressive team management experience including managing and directing the work of direct reports and teams (preferred)
Also Licenses & Certifications: Valid driver’s license.
Travel Requirements: Willingness to travel more than 60%
Also note about reasonable accommodations: "Note: Reasonable accommodations may be made for individuals with disabilities to perform the essential functions of this position." This is substantive; we can include as a
under Requirements.
We could also include "The above information describes the general duties..." but that's boilerplate; remove.
Now Skills: list from Required Skills, Knowledge And Abilities.
Let's extract each bullet:
- Ability to maintain confidentiality
- Ability to analyze financial data and prepare financial reports and statements
- Ability to analyze program performance data and reports
- Proficient in data analysis and programmatic database management, ticketing, reporting, and dashboards
- Data entry skills in entering, tracking, maintaining, and querying databases
- Ability to communicate effectively both verbally and in writing.
- Ability to communicate to customers, clients, employees, and supervisor effectively
- Ability to analyze and interpret data and solve practical program problems
- Ability to add, subtract, multiply and divide. Knowledge of mathematical concepts such as fractions, percentages, and ratios
- Proficient in Microsoft Office, Word, PowerPoint, Excel, Visio
- Ability to identify and resolve project, program, or application issues with customers, clients, trade allies, and internal stakeholders
- Exhibits concern for personal goal attainment, team goal attainment, and programmatic goal attainment
- Committed to diversity and inclusion
- Reliable transportation
We need to keep each as
- . Some sentences have multiple abilities; we can keep as is.
Now Pay: salary range: "Franklin Energy reasonably expects the starting salary for this position to fall between $85,000.00 and $110,000.00 Annually. The final offer will be determined based on relevant experience, skills, qualifications, internal equity, geographic location, and business needs."
We can put that as
under
Pay
.
Benefits: "Franklin Energy offers a comprehensive benefits package, including medical, dental, and vision coverage; retirement benefits; paid time off; paid holidays; and other company-sponsored benefits and programs."
Put under Benefits
.
We should not include Schedule heading because no schedule info.
We should not include Qualifications heading if we already have Requirements; but we could also have Qualifications separate for education/experience. However to avoid thin sections, we can keep Requirements as above and maybe rename to Requirements (includes education/experience, licenses, travel). That's fine.
Now ensure we don't repeat job title as heading. We haven't.
Now output HTML fragment.
Let's construct:
Franklin Energy is redefining the clean energy future as the only integrated provider of comprehensive solutions, combining unmatched expertise in strategic consulting, program delivery, product solutions, and design/build services. Powered by our advanced AI-driven technology platforms, we deliver seamless, tech-driven support across the entire energy service ecosystem to accelerate impactful change and ensure an unmatched customer experience. Since 1994, Franklin Energy has been a trusted partner in protecting communities and our planet, paving the way for a sustainable future
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Preserve all substantive info. Remove boilerplate like EEO, legal, etc. Also remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We need to include sections only when posting has real, specific content for it. So we need to parse the posting. Let's extract: Company description: "Franklin Energy is redefining the clean energy future as the only integrated provider of comprehensive solutions, combining unmatched expertise in strategic consulting, program delivery, product solutions, and design/build services. Powered by our advanced AI-driven technology platforms, we deliver seamless, tech-driven support across the entire energy service ecosystem to accelerate impactful change and ensure an unmatched customer experience. Since 1994, Franklin Energy has been a trusted partner in protecting communities and our planet, paving the way for a sustainable future for all. Learn more at www.franklinenergy.com and join us in leading the clean energy revolution." That's about the company, could be "About the role"? Actually "About the role" is for role description. The posting includes "Position Summary". So we can have a section "About the role" maybe with the Position Summary. Or we could have "Position Summary" as a paragraph. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose headings that match content.
We have:
- Position Summary: description of responsibilities.
- Essential Duties And Responsibilities: list of duties.
- Position Requirements: Education and Experience.
- Required Skills, Knowledge And Abilities: list of skills.
- Licenses & Certifications: Valid driver’s license.
- Travel Requirements: Willingness to travel more than 60%
- Compensation & Benefits: salary range and benefits description.
We also have some notes: "Note: Reasonable accommodations may be made..." etc. That's boilerplate? It's about accommodations, maybe keep? It's not EEO but it's a note about accommodations. Might be considered boilerplate but it's substantive? Probably we can keep as part of Requirements? But it's not a list. Might be okay to keep as a paragraph under Requirements.
Also "The above information describes the general duties..." etc. That's boilerplate; we should remove.
"An Equal Opportunity Employer Safety -Sensitive Role Addendum..." That's EEO and safety; remove.
"Notice Regarding Automated Tools..." remove.
Thus we need to produce sections:
Maybe:
About the role
Position Summary ...
Responsibilities
- ...
Requirements
Education and Experience ...
Skills
- ...
Licenses & Certifications
maybe not a standard heading but could be under Requirements? But we can include as separate section if content present. The instruction says use those example headings but not limited to them? It says usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should stick to those headings. Licenses & Certifications could be part of Requirements or Qualifications. Travel Requirements maybe part of Schedule? Travel is not schedule. Could be under Requirements. Compensation & Benefits: we have Pay and Benefits sections. So we can split: Pay heading for salary range, Benefits heading for benefits description. Schedule: maybe not present; we have travel requirements but not schedule. So we may omit Schedule. Qualifications: maybe we can combine Education and Experience under Qualifications. But we already have Requirements heading. The instruction says we can use Requirements, Qualifications, Skills, etc. We need to decide. We need to preserve all substantive info. Let's map: - About the role: Position Summary paragraph. - Responsibilities: Essential Duties And Responsibilities list. - Requirements: Education and Experience (Bachelor's degree, previous operations experience, 1-3 years progressive team management experience). Also Licenses & Certifications (Valid driver's license). Travel Requirements (Willingness to travel more than 60%). Also maybe the note about reasonable accommodations? Could be included as a paragraph under Requirements. - Skills: Required Skills, Knowledge And Abilities list. - Pay: Compensation & Benefits salary range. - Benefits: Compensation & Benefits benefits description. We should not include Qualifications if we already have Requirements; but we could also have Qualifications separate for education/experience. However to avoid thin sections, we can combine education/experience under Requirements and maybe call it Requirements. That's fine. We need to output only HTML fragment, no /, no markdown. Let's craft. First, About the role:
Franklin Energy is redefining the clean energy future as the only integrated provider of comprehensive solutions, combining unmatched expertise in strategic consulting, program delivery, product solutions, and design/build services. Powered by our advanced AI-driven technology platforms, we deliver seamless, tech-driven support across the entire energy service ecosystem to accelerate impactful change and ensure an unmatched customer experience. Since 1994, Franklin Energy has been a trusted partner in protecting communities and our planet, paving the way for a sustainable future for all. Learn more at www.franklinenergy.com and join us in leading the clean energy revolution.
But that's company description, not exactly role summary. The Position Summary is: "The Operations Manager is primarily responsible for management of the day to day operation of components of the program portfolio/department under the direction of the program/department Manager. These tasks may include management and reporting of staff and program/department performance, forecasting, reporting tracking and reporting of program/department metrics. The position is also responsible for establishing, execution, and reporting of all proactive quality assurance processes." We should include that as About the role. The company description could be considered introductory but not required. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to keep company description as well. Where to put? Could be a preceding paragraph before About the role? But we cannot have extra headings not requested. We could include it as abefore the first heading. That's allowed: output only HTML fragment, can have paragraphs and headings. So we can start with a
containing the company description. Then
About the role
with Position Summary. Let's do that. Now Responsibilities: we need to extract list items from Essential Duties And Responsibilities. The list: - Manage and lead Operations team including Operations Analysts, Field Operations Auditors, Project Specialists, and Project Coordinators. - Support delivery of operations team goals towards program and portfolio Key Performance Indicators - Support and deliver payment reviews, application intake, customer service calls, and operations team scheduling - Program/Project forecasting, tracking, invoicing, and reporting - Oversight for weekly and monthly departmental/program reporting - Work with the program teams to identify opportunities for process improvement that would improve customer/client satisfaction - Work directly with internal functional teams and/or program teams on process and QA projects - Ensure all documentation on contracts, SOWs, Cost Allocation Agreements, KPIs, etc. are up to date and readily available on SharePoint - Support the organization of financial, legal, and budget tracking responsibilities in relation to portfolio programs compliance - Manage and track the compliance requirements for contracts, addendums, proposals, and subcontracts for the portfolio - Complete special ad-hoc projects and reporting for program, program manager, operations manager, and regional director - Act as a technical resource/consultant to develop systems, processes, and process improvements for the portfolio - Manage operations team staffing, budgets, goals, productivity, and provide analysis, solutions and recommendations on the operations team to Operations Manager and Regional Director - Coordinate the internal support team efforts across the portfolio including reporting, meetings, leadership team coordination, and portfolio wide training and events - Coordinate portfolio resource sharing inside and outside of the portfolio - Work with internal customers to support the reporting needs of the portfolio, program, and business We need to put each asunder Requirements. We could also include "The above information describes the general duties..." but that's boilerplate; remove. Now Skills: list from Required Skills, Knowledge And Abilities. Let's extract each bullet: - Ability to maintain confidentiality - Ability to analyze financial data and prepare financial reports and statements - Ability to analyze program performance data and reports - Proficient in data analysis and programmatic database management, ticketing, reporting, and dashboards - Data entry skills in entering, tracking, maintaining, and querying databases - Ability to communicate effectively both verbally and in writing. - Ability to communicate to customers, clients, employees, and supervisor effectively - Ability to analyze and interpret data and solve practical program problems - Ability to add, subtract, multiply and divide. Knowledge of mathematical concepts such as fractions, percentages, and ratios - Proficient in Microsoft Office, Word, PowerPoint, Excel, Visio - Ability to identify and resolve project, program, or application issues with customers, clients, trade allies, and internal stakeholders - Exhibits concern for personal goal attainment, team goal attainment, and programmatic goal attainment - Committed to diversity and inclusion - Reliable transportation We need to keep each as
under
Pay
. Benefits: "Franklin Energy offers a comprehensive benefits package, including medical, dental, and vision coverage; retirement benefits; paid time off; paid holidays; and other company-sponsored benefits and programs." Put underBenefits
. We should not include Schedule heading because no schedule info. We should not include Qualifications heading if we already have Requirements; but we could also have Qualifications separate for education/experience. However to avoid thin sections, we can keep Requirements as above and maybe rename to Requirements (includes education/experience, licenses, travel). That's fine. Now ensure we don't repeat job title as heading. We haven't. Now output HTML fragment. Let's construct:Franklin Energy is redefining the clean energy future as the only integrated provider of comprehensive solutions, combining unmatched expertise in strategic consulting, program delivery, product solutions, and design/build services. Powered by our advanced AI-driven technology platforms, we deliver seamless, tech-driven support across the entire energy service ecosystem to accelerate impactful change and ensure an unmatched customer experience. Since 1994, Franklin Energy has been a trusted partner in protecting communities and our planet, paving the way for a sustainable future