Jobs · Management · Utah

Design Build Leader - Transportation

Jacobs · Holladay, UT · Yesterday
Management$200k–$285k/yrFull-time
We need to output HTML fragment with sections: headings

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/requisition numbers as headings. Preserve all substantive info; remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". Pay and Schedule sections only if posting actually states them. The posting includes base salary range $200,000 to $285,000. So Pay section should be included. Schedule? Not mentioned explicitly; there is hybrid working policy but not schedule. Probably not include Schedule unless explicit. Benefits: they list health and welfare benefits: medical, dental, vision, basic life insurance, 401(k), ability to purchase company stock at discount, deferred compensation plan, Executive Deferral Plan, unlimited U.S. Personalized Paid Time Off (PPTO) for full-time salaried/exempt employees, seven paid holidays, caregiver leave, possible additional rewards: merit increases, performance discretionary bonus, stock. So Benefits section should be included. We need sections: About the role (maybe a summary), Responsibilities (What You'll Do), Requirements/Qualifications (maybe combine?), Skills (maybe list skills), Benefits, Pay. We must not invent sections. Use headings only when content exists. We need to parse the posting. First paragraph: "At Jacobs, we're challenging today to reinvent tomorrow..." That's generic company description; could be part of About the role? Might be considered boilerplate? It's not exactly boilerplate but it's generic marketing. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This generic description may be considered part of the job description but not essential? It's about Jacobs mission. Could be included in About the role. We'll keep it as part of About the role. Then "Your impact At Jacobs, we're challenging today to reinvent tomorrow. As our West Central Design-Build Leader, you will play a critical role in growing and delivering major infrastructure programs across the region. Partnering with business, operations, sales, and project delivery leaders, you'll help shape pursuit strategies, strengthen contractor relationships, lead complex alternative delivery opportunities, and support successful project execution from opportunity identification through project award and delivery. This position is ideal for a collaborative leader who understands the full design-build lifecycle and is passionate about building high-performing teams, developing winning pursuit strategies, and delivering innovative solutions for our clients." That's about the role. Then "What You'll Do As the Design-Build Leader for the West Central geography, you will serve as the operational leader for alternative delivery projects and pursuits within the region. You will partner closely with transportation and infrastructure leaders to identify new opportunities, support business growth, and lead project teams through the pursuit and delivery process." Then sub-sections: Growth and Opportunity Development, Pursuit Leadership, Design-Build Project Delivery, Leadership and Team Development. Those are responsibilities. Then "Why Jacobs Join a team that is delivering some of the region's most complex and transformative infrastructure projects. You'll have the opportunity to influence strategy, build high-performing teams, develop client relationships, and help shape the future of design-build delivery across the West Central market." That could be part of About the role or separate but we can incorporate. Then "Here's what you'll need" list of qualifications. Then "Ideally, You'll Also Have" additional qualifications. Then benefits paragraph. Then "The base salary range for this position is $200,000.00 to $285,000.00." Then EEO statement etc (remove). Then job posted date etc (maybe minor metadata, can be short p). Then hybrid working policy etc (maybe part of Benefits? It's about work arrangement; could be included in Benefits or a separate section like Work Arrangement but not requested; we can include as part of Benefits or maybe as a short p under Benefits? The instruction: include a section only when posting has real specific content for it. We have hybrid working policy; could be part of Benefits or maybe a separate section like Work Arrangement but not in allowed headings list. Since not in list, we could incorporate into Benefits or maybe into About the role? Probably better to include under Benefits as a bullet? But Benefits heading expects list of benefits; we could add a bullet about hybrid working policy. However the instruction: Use

    • for any list of duties/requirements/benefits. So we can include hybrid working policy as a list item under Benefits. We must not include application instructions (like "If you require further support..."). We must not include duplicated lines. Now craft HTML. We'll have sections:

      About the role

      with paragraphs summarizing role impact.

      Responsibilities

      with
      • items covering the bullet points from What You'll Do and sub-sections. We need to preserve all substantive info; we should not lose details. Let's extract responsibilities: - Serve as the operational leader for alternative delivery projects and pursuits within the region. - Partner closely with transportation and infrastructure leaders to identify new opportunities, support business growth, and lead project teams through the pursuit and delivery process. - Growth and Opportunity Development: * Collaborate with sales, client account managers, operations leaders, and technical leadership to identify and evaluate strategic design-build opportunities. * Develop and maintain strong relationships with contractors, teaming partners, and key stakeholders across the marketplace. * Support go/no-go decision-making, opportunity assessments, and pursuit planning activities. * Help shape regional design-build growth strategies and support market expansion initiatives. - Pursuit Leadership: * Lead operational planning and coordination during qualifications- and proposal-based pursuits. * Provide leadership on teaming strategies and partner engagement. * Serve as a key Jacobs representative with contractors and design partners throughout the pursuit process. * Guide multidisciplinary teams through risk reviews, pricing discussions, proposal development, and commercial strategy. * Coordinate project controls, commercial management, scheduling, and resource planning activities during pursuit development. * Help develop winning strategies that position Jacobs for success on complex alternative delivery opportunities. - Design-Build Project Delivery: * Support the seamless transition from pursuit to project execution following award. * Coordinate project startup and mobilization activities, including resource planning, contract execution, project controls, and delivery alignment. * Work closely with Design Managers, Project Managers, and Delivery Project Executives to establish project success strategies. * Provide ongoing leadership and operational support throughout project delivery. * Serve in key project leadership roles including Major Opportunity Pursuit Lead, Delivery Project Executive, Design Manager, or Project Manager, depending on project scale and strategic importance. - Leadership and Team Development: * Maintain visibility into the regional portfolio of design-build pursuits and active projects. * Support recruitment, development, and mentorship of key design-build professionals, including Design Managers, Technical Leads, Commercial Managers, and project delivery staff. * Champion best practices, collaboration, and continuous improvement across the design-build lifecycle. * Partner with regional operations leadership to ensure effective governance, resource planning, and project performance. Also "Why Jacobs" maybe part of About the role. Now Requirements/Qualifications: Here's what you'll need: - Bachelor's degree in Engineering, Construction Management, Architecture, or a related field. - Extensive experience leading major transportation design-build or transportation alternative delivery projects and pursuits. - Demonstrated success managing large, multidisciplinary infrastructure teams. - Strong understanding of project delivery, commercial management, risk management, and project controls. - Experience collaborating with contractors, design partners, and public-sector clients. - Proven ability to influence stakeholders, build teams, and drive successful business outcomes. - Excellent communication, leadership, and relationship management skills. Ideally, You'll Also Have: - Professional Engineer (PE) registration or equivalent professional credential. - Experience serving in Design Manager, Project Manager, Delivery Executive, or Pursuit Leadership roles. - Experience delivering transportation, water, environmental, aviation, or other large infrastructure projects. - Established relationships with contractors and public-sector agencies throughout the West Central region. - Experience supporting pursuits and projects exceeding $100M in construction value. We could combine Requirements and Qualifications into one section maybe "Requirements" or "Qualifications". The instruction says use headings like Requirements, Qualifications, Skills. We could have a section "Requirements" containing the bullet list of required qualifications, and maybe another section "Preferred Qualifications" but not in allowed headings. Could put under "Qualifications". Or we could have "Requirements" for required, and "Qualifications" for preferred? But we must not create sections with filler. We have both required and preferred content; we could combine into one section "Requirements" and include both required and preferred as bullet list, maybe differentiate with wording? But we must preserve all info; we can include both. Alternatively we could have two sections: "Requirements" and "Qualifications". Both are allowed headings. We'll put required under Requirements, and ideally you'll also have under Qualifications. That seems fine. Skills: Could extract skills like communication, leadership, relationship management, stakeholder influence, etc. But those are already in requirements. Could create a Skills section listing: Communication, Leadership, Relationship management, Stakeholder influence, Team building, Business acumen, etc. But we risk inventing. Better to not create Skills section unless we have explicit list. The posting mentions "Excellent communication, leadership, and relationship management skills." That's a skill list. Could make a Skills section with those three. But we already have them in Requirements; we could still create a Skills section but might be redundant. The instruction: Prefer a few substantive sections over many thin ones. So maybe we skip Skills section and include communication etc under Requirements. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now Benefits: list items: - Medical, dental, vision, and basic life insurance - 401(k) plan - Ability to purchase company stock at a discount - Deferred compensation plan - Executive Deferral Plan - Unlimited U.S. Personalized Paid Time Off (PPTO) for full-time salaried/exempt employees - Seven paid holidays - Caregiver leave - Possible additional rewards: merit increases, performance discretionary bonus, stock Also hybrid working policy: "We empower employees with our hybrid working policy, allowing them to split their work week between Jacobs offices/projects and remote locations enabling them to deliver their best work." Could add as benefit. Now Pay: base salary range $200,000 to $285,000. Also note that individual pay determined by work location and additional factors including job-related skills, experience, relevant education/training. We'll include that as prose. Now we must remove boilerplate: EEO statement, job posted date, etc. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

        or drop it." So we could include a short p for job posted date maybe but it's minor metadata; we could drop it. Safer to drop it. Also remove duplicated lines: there is repeated "At Jacobs, we're challenging today to reinvent tomorrow." We'll keep only once. Now produce HTML. We'll need to wrap content in appropriate tags. Let's craft:

        About the role

        At Jacobs, we're challenging today to reinvent tomorrow by solving the world's most critical problems for thriving cities, resilient environments, mission‑critical outcomes, operational advancement, scientific discovery and cutting‑edge manufacturing. As the West Central Design‑Build Leader, you will play a critical role in growing and delivering major infrastructure programs across the region, partnering with business, operations, sales and project delivery leaders to shape pursuit strategies, strengthen contractor relationships, lead complex alternative delivery opportunities and support successful project execution from

Similar jobs