Jobs · Consulting · Texas

Senior Substation Project Engineer

Arup · Dallas, TX · 3 wk ago
HybridConsulting$135k–$175k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam warning, duplicated lines, application instructions. We need to parse the posting. First paragraph: "Joining Arup Arup’s purpose, shared values and collaborative approach has set us apart for over 75 years, guiding how we shape a better world. At Arup, you belong to an extraordinary collective – in which we encourage individuality to thrive. Our strength comes from how we respect, share and connect our diverse experiences, perspectives and ideas. You will have the opportunity do socially useful work that has meaning – to Arup, to your career, to our members and to the clients and communities we serve." That's about the company, could be "About the role"? Actually it's about Arup. Could be "About the role" maybe includes description of role? But we have a separate "The Opportunity" section describing responsibilities. So "About the role" could be the introductory paragraph about Arup and the role? However guidelines: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About the role: maybe the first paragraph describing Arup and the role? Could be considered "About the role". It includes purpose, values, etc. That's substantive. - Responsibilities: The "The Opportunity" bullet list (actually sentences) describing coordinate multidisciplinary engineering activities etc. That's responsibilities. - Requirements: The "Is this role right for you?" bullet list: Bachelor's degree, 10 years experience, PE license, etc. That's requirements. - Qualifications: maybe overlapping with requirements? Could separate: Qualifications could be education, licensure, experience. But we have both Requirements and Qualifications as possible headings. We need to decide what to put where. The posting includes "Is this role right for you?" which lists qualifications/requirements. Could treat that as Requirements. Qualifications could be things like "Project Management Professional designation or formal project management training is considered an asset." That's more of a qualification/asset. Also "Excellent communication skills — able to interact with clients, regulatory bodies, vendors, and internal stakeholders. Ability to represent the company credibly. Willingness to travel occasionally as needed (site visits, client/vendor meetings). The ability to prioritize work effectively, manage deadlines and organization skills required for our rapidly changing environment." Those are skills. Thus we can map: - About the role: introductory paragraph about Arup and purpose. - Responsibilities: The Opportunity paragraph (starting "Coordinate multidisciplinary engineering activities..."). - Requirements: Bachelor’s degree in engineering (preferably Electrical). At least 10 years’ experience in 15kV through 345kV physical utility substation design and IEEE/ANSI standards. Licensed Professional Engineer (PE). Experience delivering substation projects through feasibility, detailed design, procurement, construction and commissioning. Experience with utility, renewable energy, energy storage, industrial or data-center interconnection projects. Familiarity with EPC, design-build and engineer-of-record delivery models. Experience managing design changes and coordinating work within operating brownfield substations. - Qualifications: Project Management Professional designation or formal project management training is considered an asset. (maybe also "Experience delivering ..."? but that's already in requirements). Could also include "Experience with utility, renewable energy, energy storage, industrial or data-center interconnection projects." but that's also requirement. We'll keep qualifications as the PMP asset. - Skills: Excellent communication skills — able to interact with clients, regulatory bodies, vendors, and internal stakeholders. Ability to represent the company credibly. Willingness to travel occasionally as needed (site visits, client/vendor meetings). The ability to prioritize work effectively, manage deadlines and organization skills required for our rapidly changing environment. - Benefits: The "What We Offer You" section describing total reward package, health and wellbeing, learning opportunities, profit share, 401(k) match, flexible working. Also "Benefits at Work" details: comprehensive benefits program, health and welfare security, paid time off, global profit share scheme, 401(k) plan with up to 10% company match, flexible working options. So we have benefits content. - Pay: The "Houston Hiring Range – Hiring Range - The good faith base salary hiring range for this job if performed in Houston is $135,000 – $175,000 per year. This range is commensurate with experience, educational background, and skill level. Benefits are not included in the base salary. Please note hiring ranges for candidates performing work outside of Houston will differ." This is pay info. We should include Pay section with that range. Note we should not include filler like "commensurate with experience" etc? Actually that is part of the description; it's okay. The rule: do NOT emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") . But here the sentence includes "This range is commensurate with experience, educational background, and skill level." That's not filler; it's describing the range. It's okay. - Schedule: Not explicitly mentioned. There's flexible working but that's under benefits. No explicit schedule like full-time, part-time, shift. So we should NOT create a Schedule section because no specific content. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay. We need to output HTML fragment only, no /. Use

for each section heading. Use
  • for any list of duties/requirements/benefits, and

    for prose. We need to decide what to format as lists vs prose. Responsibilities: many sentences; could be a list of duties. Use

    • each duty. Requirements: list of bullet points; use
      • . Qualifications: maybe single item; could be

        or

        • . Since it's a list (maybe one item) we can still use
          • . Skills: list of abilities; use
            • . Benefits: multiple items: health and welfare security, paid time off, profit share, 401(k) match, flexible working, learning opportunities, etc. Use list. Pay: maybe a

              with the range. About the role: prose

              . We must not repeat job title as heading. No Job ID etc. We must remove boilerplate: The EEO statements, equal opportunity, scam warning, application instructions ("Please note that all applicants must apply directly via the job portal..."), "If this role is not quite what you are looking for..." etc. Also "Discover more about life at Arup at www.arup.com/careers/your-life-at-arup." That's maybe navigation? It's not boilerplate but could be considered a link; but it's not required. Might be considered extra but not prohibited. However it's not part of core sections; we could drop it as it's not a section heading. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop the EEO paragraphs, the scam warning, the application instructions, the Talent Community invitation, the "Discover more about life at Arup" link, the "Our Application Process" paragraph, the "Stay safe online." etc. Also drop "Different People, Shared Values" EEO paragraph. Also drop "Our members collaborate on ambitious projects..." maybe part of benefits? Actually that is more about Arup's culture; could be considered part of About the role? But we already have About the role paragraph; we could incorporate some of that but we must not invent or summarize away detail. However we can keep it as part of About the role if it's substantive. But the instruction says to remove boilerplate; that paragraph about members collaborating on ambitious projects is more generic but still about Arup. Might be considered boilerplate? It's not EEO or legal. It's describing the firm's work. Could keep as part of About the role. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that sentence if it's substantive. But we need to decide where to place it. It appears after "What We Offer You" section: "We are owned in trust on behalf of our members, giving us the freedom, with personal responsibility, to set our own direction and choose work that aligns with our purpose and adds to Arup’s legacy. Our members collaborate on ambitious projects to deliver remarkable outcomes for our clients and communities." That's descriptive of Arup; could be part of About the role. We'll incorporate into About the role paragraph. Also "Profit Share is a key part of our reward, enabling members to share in the results of our collective efforts." That's benefits. We'll need to extract benefits details: From "What We Offer You At Arup, we care about each member’s success, so we can grow together. Guided by our values, we provide an attractive total reward package that recognizes the contribution of each of our members to our shared success. As well as competitive, fair and equitable pay, we offer a career in which all of our members can belong, grow and thrive – through benefits that support health and wellbeing, a wide range of learning opportunities and many possibilities to have an impact through the work they do." Then "Benefits at Work - At Arup, we have a comprehensive and valuable benefits program that works for our employees and their families while keeping costs low. These benefits provide health and welfare security for you as well as paid time off for rest and renewal. As a member of Arup, everyone shares in our success through a global profit share scheme (payments are dependent on the firm’s financial performance). Our Global Profit Share Plan (paid bi-annually) provides an opportunity for you to share in the success of the Firm. As a valued employee of Arup, you can also choose to participate in our 401(k) plan with up to 10% company match to help you save for your future Flexible Working - We believe that flexible arrangements create a more inclusive way of working that supports our diversity and the wellbeing of our people. Options for alternative schedules and the ability to work outside of the office for a portion of your workweek are available" Thus benefits list: health and welfare security, paid time off, global profit share scheme (bi-annual), 401(k) plan with up to 10% company match, flexible working options (alternative schedules, remote work), learning opportunities, possibilities to have impact through work, total reward package, competitive fair equitable pay (but pay is separate). We'll include benefits as list items. Now we need to ensure we don't include filler like "competitive, fair and equitable pay" in benefits because pay is separate section; but it's still a benefit? Might be okay but we have Pay section separate; we could still mention it in benefits but it's redundant. Safer to exclude pay from benefits list. Now we need to format. Let's craft HTML:

              About the role

              Joining Arup, our purpose, shared values and collaborative approach have set us apart for over 75 years, guiding how we shape a better world. At Arup you belong to an extraordinary collective that encourages individuality to thrive. Our strength comes from respecting, sharing and connecting our diverse experiences, perspectives and ideas. You will have the opportunity to do socially useful work that has meaning—to Arup, to your career, to our members and to the clients and communities we serve. Arup is owned in trust on behalf of its members, giving us the freedom, with personal responsibility, to set our own direction and choose work that aligns with our purpose and adds to Arup’s legacy. Our members collaborate on ambitious projects to

Similar jobs