Field Strategy & Performance Specialist

We need to output HTML fragment with sections: About the role? The posting includes intro paragraphs about Rosendin, then "Your Next Opportunity" heading? Actually they have "Your Next Opportunity" then description of role. Then "What You’ll Do", "What You’ll Need To Be Successful", "What You Bring To Us", then "Working Conditions", then "YOU Matter – Our Benefits". Also they have "Why Rosendin?" earlier. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We need to map content to these headings. We have no explicit Pay or Schedule info. There's no mention of salary or schedule specifics. So we should NOT include Pay or Schedule sections. We have Benefits: they list many benefits. So include Benefits section. We have About the role: maybe the introductory paragraph describing role? Could be "Your Next Opportunity" description. We'll put that under About the role. Responsibilities: "What You’ll Do" list. Requirements: maybe "What You’ll Need To Be Successful" (skills/abilities). Could be Requirements. Qualifications: "What You Bring To Us" (education, experience). Could be Qualifications. Skills: maybe combine some? But we have separate sections; we could put skills under Skills if there is distinct skill list. The "What You’ll Need To Be Successful" includes abilities like communication, prioritize, etc. That could be Skills. But we already used that for Requirements. Let's think: The instructions: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which content maps to which. We have: - Intro about role: "Your Next Opportunity The Specialist, Field Strategy and Performance serves as..." That's about the role. - Responsibilities: "What You’ll Do" bullet list. - Requirements: maybe "What You’ll Need To Be Successful" (abilities, traits). Could be Requirements. - Qualifications: "What You Bring To Us" (education, experience, travel). Could be Qualifications. - Skills: maybe we could extract specific skills like "Proficient in using a computer and Microsoft Office (Outlook, Word, Excel, etc.)", "Oral and written communication skills", etc. But those are already in Requirements. Could split but risk duplication. Better to keep Requirements as abilities and Qualifications as education/experience, and maybe Skills not needed if content overlaps. But we need to include a section only when posting has real specific content. If we don't have distinct skills beyond those already covered, we could omit Skills section. - Benefits: list. Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We must not repeat job title as heading. Not include Job ID etc. We must use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from each section. Let's extract content. About the role: The paragraph(s) before "What You’ll Do". Let's capture: "Whether you’re a recent grad or a seasoned professional, you can experience meaningful career growth at Rosendin. Enjoy a true sense of ownership as you work with a proven industry leader on some of the most exciting and high-profile projects in the nation. We offer a wide range of job opportunities, competitive compensation, full benefits, an Employee Stock Ownership Plan and more. Why Rosendin? Committed. Innovative. Engaged. If you’re looking to take your career to the next level and work with some of the best and brightest in the industry, we want to hear from you. Since our founding over 100+ years ago, Rosendin has been driven to positively impact the communities where we live and work. We are an organization built on integrity and we have a culture that empowers people, embraces diversity, and inspires everyone to do their best. As one of the largest EMPLOYEE-OWNED electrical contractors in the United States, you will have the unique benefit of being a shareholder at a company that is experiencing tremendous growth and success. When our people succeed and fuel our success, we reward them. We'd love to have you as a shareholder! Your Next Opportunity The Specialist, Field Strategy and Performance serves as the foundational data, reporting, and coordination engine for the Field Strategy and Performance team. Reporting directly to the Senior Manager, this role is responsible for gathering raw field metrics, maintaining performance dashboards, and executing the administrative and analytical tasks required to drive the Field Operations business plan. The Specialist helps the Senior manager provide the Regional VPs and field leadership with the visibility, data clarity, and tracking necessary to align operations and execute strategic corporate initiatives." We need to keep all that. However we should remove boilerplate like EEO etc later. But this intro includes some EEO? Not yet. It's fine. We should not repeat the job title as a heading, but we can mention it in prose. Now Responsibilities: "What You’ll Do" list items. Let's capture each bullet: - KPI Management and Reporting: Maintain and execute the Field Operations KPI framework across the strategic pillars. Support data collection, data cleansing, and performance storytelling by transforming regional data into structured metrics. - Dashboard Maintenance: Partner with IT, HR, Finance, Safety, L&D, Purchasing, and project management teams to update, validate, and deliver accurate, real-time dashboards and monthly performance materials. - Field Data Support and Context: Analyze regional data trends to support the Senior Manager and Regional VPs ahead of performance discussions and calibration meetings. Track regional best practices, common challenges, and operational data contexts. - Cross functional Coordination: Act as a data coordination point between different departments like Field Quality, Field Innovation, HR, IT and regional teams to help define and track initiatives - Improvement Project Tracking: Coordinate and optimize workflows between Field Operations, HR, IT, Field Payroll and regional teams to eliminate operational bottlenecks and align cross-functional projects - Innovation Pipeline Administration: Support the intake process for the field-driven innovation pipeline. Track ideas, coordinate documentation for regional pilot sites, and organize case studies of successful solutions. - Initiative Tracking and Feedback Loops: Track the deployment of enterprise-level initiatives such as process changes, new application rollouts, policy updates, and compiling field feedback for corporate review. - Intake and Prioritization Management: Serve as the initial gatekeeper and tracking point for incoming field data requests, reporting adjustments, and process-change requests to maintain organizational alignment. We need to keep each as list items. Now Requirements: "What You’ll Need To Be Successful" list: - Ability to perform duties in a professional manner and appearance - Visit regional offices or job sites to better understand data context and build relationships. - Proficient in using a computer and Microsoft Office (Outlook, Word, Excel, etc.) - Prioritize and manage multiple tasks, changing priorities as necessary - Work under pressure and adapt to changing requirements with a positive attitude - Oral and written communication skills as required for the position - Self-motivated, proactive, and an effective team player - Interact effectively and professionally with all levels of employees, both management and staff alike, vendors, clients, and others Now Qualifications: "What You Bring To Us" list: - Bachelor’s degree in project management, process improvement, Construction Management, Civil Engineering, Structural Engineering, or other related discipline preferred - 2-4 years of experience in data analysis, business operations and project coordination - Can be a combination of training, education, and relevant work experience - Travel Up to 50% - Working Conditions General work environment – This position is performed primarily in an office. Activity includes sitting for extended periods, standing, walking, typing, carrying, pushing, bending. Work is conducted primarily indoors with varying environmental conditions, such as fluorescent lighting and air conditioning. - Noise level is typically low to medium. - We fully comply with the ADA and applicable state law, including considering reasonable accommodation measures that may enable qualified disabled applicants and employees to perform essential functions. But note: The "Working Conditions" part might be better as its own section? However we only have headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Working Conditions could be part of Qualifications or maybe we could treat as part of Qualifications (since it's about job conditions). But we have a separate "Working Conditions" paragraph after Qualifications. The instructions say we should only include sections when posting has real specific content for it. We don't have a heading for Working Conditions in allowed list, so we must incorporate that content somewhere else, maybe under Qualifications or About the role. Since it's about work environment, could fit under Qualifications (maybe as part of job details). We'll include it in Qualifications section as additional bullet points. But we must preserve ALL substantive information. So we need to include that working conditions text somewhere. We'll add as a bullet under Qualifications (or maybe as a separate paragraph after the list). Since we must use

  • for any list of duties/requirements/benefits. Working conditions is not a list but prose; we can put in

    . Now Benefits: list from "YOU Matter – Our Benefits". Let's capture: - ESOP – Employee Stock Ownership - 401 K - Annual bonus program based upon performance, profitability, and achievement - 17 PTO days per year plus 10 paid holidays - 3 days of paid sick leave each year - 3 days of paid Bereavement leave each year - 3 days of paid Jury Duty - Medical, Dental, Vision Insurance - Bonding Leave - Term Life, AD&D Insurance, and Voluntary Life Insurance - Disability Income Protection Insurance - Pre-tax Flexible Spending Plans (Health and Dependent Care) - Charitable Giving Match with our Rosendin Foundation We need to keep all. Now we must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At the end there is repeated EEO statement: "Rosendin is committed to creating a diverse environment and is proud to be an Equal Opportunity Employer. Employment decisions are considered regardless of race, color, religion, sex, sexual orientation, gender identity, national origin, disability, veteran status, pregnancy, age (over 40), or any other categories protected by applicable federal, state, or local law." This appears twice. We should remove that boilerplate. Also earlier there is "We fully comply with the ADA and applicable state law..." that's part of Working Conditions; we keep that as it's substantive about accommodation. The EEO repeated at end is boilerplate; remove. Also there may be duplicated lines like "Our success is rooted in our people..." etc. Let's see: after Benefits there is a paragraph: "Our success is rooted in our people. We all come together around long-term vision and a sense of shared ownership. As a group, we do whatever it takes to ensure the success of our business…and your career. Rosendin is committed to creating a diverse environment and is proud to be an Equal Opportunity Employer. Employment decisions are considered regardless of race, color, religion, sex, sexual orientation, gender identity, national origin, disability, veteran status, pregnancy, age (over 40), or any other categories protected by applicable federal, state, or local law." That's also boilerplate; remove. Thus we keep only substantive content. Now we need to output HTML fragment only. Structure:

    About the role

    ... (the intro paragraph(s) up to "Your Next Opportunity ...")

    But we need to ensure we don't include the heading "Your Next Opportunity" as a heading; we just include it in prose. Thus About the role paragraph will include the introductory fluff and the role description. Let's craft the About the role paragraph: "Whether you’re a recent grad or a seasoned professional