Transportation Design Project Manager - Salt Lake City, UT
Civil Science · Salt Lake City, UT · Yesterday
Information TechnologyFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Candidates must have a valid driver’s license and be able to pass both a criminal background check and driving record review." That's maybe part of requirements? It's a requirement but not boilerplate? It's a requirement, but it's not EEO. It's a requirement. Keep it. Also remove "Civil Science evaluates and determines on a case-by-case basis whether it is willing to sponsor an individual to receive a temporary or permanent work visa (e.g., E-3, H-1B, H-1B1, or TN visa status)." That's maybe not boilerplate but could be considered immigration sponsorship note; it's not EEO. Might keep? It's not a standard EEO but it's about visa sponsorship. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Visa sponsorship is not exactly EEO, but could be considered legal. Might keep? Safer to keep if it's substantive. However it's not a requirement but a note. Might keep as part of Requirements? It's not a requirement but a statement. Could be considered boilerplate? I'd keep it as part of Requirements maybe.
We need to preserve all substantive information. Let's parse the posting.
Paragraphs:
- Intro: "Civil Science is seeking an experienced Transportation Design Project Manager to support and grow our Utah transportation practice. This opportunity is ideal for a licensed Professional Engineer with deep transportation design experience, a strong background delivering DOT and municipal projects, and a genuine interest in mentoring emerging engineers and project leaders. As a key member of our transportation group, you'll lead transportation design projects from pursuit through delivery, overseeing scope, schedule, budget, quality, and overall project performance while serving as a primary point of contact for UDOT and municipal clients. You'll coordinate multidisciplinary teams, provide technical oversight across roadway and related transportation design efforts, ensure adherence to agency standards and project requirements, and help stabilize and lead active project opportunities in northern Utah. This role also includes building client relationships, supporting business development and proposals, collaborating with leadership on strategic growth initiatives, and coaching team members in a collaborative, high-performing employee-owned environment."
That's description of role/responsibilities.
Then "Qualifications" heading appears in text: "Qualifications Bachelor's degree in Civil Engineering.Professional Engineer (PE) license required; Utah licensure required or ability to obtain within three months of hire.Minimum 12 years of relevant transportation design experience.Experience delivering DOT and/or municipal transportation projects.Proven ability to manage multiple projects, priorities, scope, schedule, and budget.Strong understanding of roadway, drainage, utility, or traffic design.Excellent communication, client management, organization, and leadership skills."
Then "Preferred Experience" list: "UDOT project experience or strong familiarity with Utah agencies.Experience with ProjectWise, Bluebeam, or similar tools.Experience supporting proposal development or business development efforts.Previous experience mentoring or supervising staff."
Then "Physical Requirements" list: "Prolonged periods sitting at a desk and working on a computer.Must be able to lift up to 30 pounds at times.Must be able to work on active project or construction sites, which may include uneven terrain, exposure to varying weather conditions, and moderate to high noise levels.Frequently required to stand, walk, sit, climb, balance, stoop, kneel, crouch, or crawl."
Then "Why Join Civil Science?" with bullet points: Ownership in Your Future..., Room to Grow..., Work-Life Harmony..., Comprehensive Benefits (Fulltime Employees): Enjoy three weeks of PTO, eight holidays, medical, dental, vision, life insurance, short/long-term disability, tuition reimbursement, and a 401K plan.
Then "About Civil Science" paragraph.
Then "Candidates must have a valid driver’s license and be able to pass both a criminal background check and driving record review."
Then "Civil Science evaluates and determines on a case-by-case basis whether it is willing to sponsor an individual to receive a temporary or permanent work visa (e.g., E-3, H-1B, H-1B1, or TN visa status)."
Then EEO statement.
Then more about Civil Science history.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Thus we should remove the EEO statement (the long paragraph about equal employment opportunities). Also remove any duplicated lines (none visible). Remove application instructions (none explicit). Also remove cookie/navigation/legal (none). Also remove the visa sponsorship note? It's not EEO but could be considered legal. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Visa sponsorship is legal but not necessarily boilerplate? Might be considered legal. Safer to remove it as it's not substantive to the role? It's about visa sponsorship; could be considered relevant for international candidates. But the instruction says remove legal boilerplate. I'd remove that sentence.
Also remove the "Candidates must have a valid driver’s license and be able to pass both a criminal background check and driving record review." That's a requirement; not boilerplate. Keep it.
Now we need to structure sections.
We have:
- About the role (maybe intro paragraph). Could be "About the role" heading.
- Responsibilities: could be derived from the intro describing duties: lead projects, oversee scope schedule budget quality, point of contact, coordinate teams, technical oversight, ensure adherence, stabilize/lead active projects, build client relationships, support business development/proposals, collaborate with leadership on strategic growth, coach team members.
We could combine About the role and Responsibilities? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include a section only when posting has real specific content. So we can have About the role (intro), Responsibilities (list of duties), Requirements (maybe includes qualifications?), Qualifications (maybe separate?), Skills (maybe communication etc), Benefits (from Why Join Civil Science), Pay (none), Schedule (none). Since Pay and Schedule not mentioned, we should not include those sections.
We need to avoid thin sections. Let's decide:
- About the role: short paragraph summarizing the role.
- Responsibilities: bullet list of duties.
- Requirements: maybe includes education, licensure, experience, physical requirements, driver's license, background check.
- Qualifications: maybe the same as Requirements? Could combine. But we have both "Qualifications" and "Preferred Experience". Could treat Qualifications as required qualifications, and Skills as preferred/experience? Or we could have Requirements (required) and Skills (preferred). The instruction says we can use Skills section for skills. Let's map:
Required: Bachelor's degree in Civil Engineering, PE license (Utah licensure required or ability to obtain within 3 months), Minimum 12 years relevant transportation design experience, Experience delivering DOT and/or municipal projects, Proven ability to manage multiple projects, priorities, scope, schedule, budget, Strong understanding of roadway, drainage, utility, or traffic design, Excellent communication, client management, organization, leadership skills, Valid driver's license, Ability to pass criminal background check and driving record review, Physical requirements (prolonged sitting, lift 30 lbs, work on sites, etc).
Preferred: UDOT project experience or familiarity with Utah agencies, Experience with ProjectWise, Bluebeam or similar tools, Experience supporting proposal development or business development, Previous experience mentoring or supervising staff.
We could put Required under "Requirements" and Preferred under "Skills" or maybe "Preferred Experience". But we have a heading "Skills". Could put preferred experience there.
Also we have Benefits section from "Why Join Civil Science?" includes ownership (ESOP), room to grow, work-life harmony, comprehensive benefits list.
We need to output only HTML fragment, no extra text.
Let's craft:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Candidates must have a valid driver’s license and be able to pass both a criminal background check and driving record review." That's maybe part of requirements? It's a requirement but not boilerplate? It's a requirement, but it's not EEO. It's a requirement. Keep it. Also remove "Civil Science evaluates and determines on a case-by-case basis whether it is willing to sponsor an individual to receive a temporary or permanent work visa (e.g., E-3, H-1B, H-1B1, or TN visa status)." That's maybe not boilerplate but could be considered immigration sponsorship note; it's not EEO. Might keep? It's not a standard EEO but it's about visa sponsorship. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Visa sponsorship is not exactly EEO, but could be considered legal. Might keep? Safer to keep if it's substantive. However it's not a requirement but a note. Might keep as part of Requirements? It's not a requirement but a statement. Could be considered boilerplate? I'd keep it as part of Requirements maybe.
We need to preserve all substantive information. Let's parse the posting.
Paragraphs:
- Intro: "Civil Science is seeking an experienced Transportation Design Project Manager to support and grow our Utah transportation practice. This opportunity is ideal for a licensed Professional Engineer with deep transportation design experience, a strong background delivering DOT and municipal projects, and a genuine interest in mentoring emerging engineers and project leaders. As a key member of our transportation group, you'll lead transportation design projects from pursuit through delivery, overseeing scope, schedule, budget, quality, and overall project performance while serving as a primary point of contact for UDOT and municipal clients. You'll coordinate multidisciplinary teams, provide technical oversight across roadway and related transportation design efforts, ensure adherence to agency standards and project requirements, and help stabilize and lead active project opportunities in northern Utah. This role also includes building client relationships, supporting business development and proposals, collaborating with leadership on strategic growth initiatives, and coaching team members in a collaborative, high-performing employee-owned environment."
That's description of role/responsibilities.
Then "Qualifications" heading appears in text: "Qualifications Bachelor's degree in Civil Engineering.Professional Engineer (PE) license required; Utah licensure required or ability to obtain within three months of hire.Minimum 12 years of relevant transportation design experience.Experience delivering DOT and/or municipal transportation projects.Proven ability to manage multiple projects, priorities, scope, schedule, and budget.Strong understanding of roadway, drainage, utility, or traffic design.Excellent communication, client management, organization, and leadership skills."
Then "Preferred Experience" list: "UDOT project experience or strong familiarity with Utah agencies.Experience with ProjectWise, Bluebeam, or similar tools.Experience supporting proposal development or business development efforts.Previous experience mentoring or supervising staff."
Then "Physical Requirements" list: "Prolonged periods sitting at a desk and working on a computer.Must be able to lift up to 30 pounds at times.Must be able to work on active project or construction sites, which may include uneven terrain, exposure to varying weather conditions, and moderate to high noise levels.Frequently required to stand, walk, sit, climb, balance, stoop, kneel, crouch, or crawl."
Then "Why Join Civil Science?" with bullet points: Ownership in Your Future..., Room to Grow..., Work-Life Harmony..., Comprehensive Benefits (Fulltime Employees): Enjoy three weeks of PTO, eight holidays, medical, dental, vision, life insurance, short/long-term disability, tuition reimbursement, and a 401K plan.
Then "About Civil Science" paragraph.
Then "Candidates must have a valid driver’s license and be able to pass both a criminal background check and driving record review."
Then "Civil Science evaluates and determines on a case-by-case basis whether it is willing to sponsor an individual to receive a temporary or permanent work visa (e.g., E-3, H-1B, H-1B1, or TN visa status)."
Then EEO statement.
Then more about Civil Science history.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
Thus we should remove the EEO statement (the long paragraph about equal employment opportunities). Also remove any duplicated lines (none visible). Remove application instructions (none explicit). Also remove cookie/navigation/legal (none). Also remove the visa sponsorship note? It's not EEO but could be considered legal. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Visa sponsorship is legal but not necessarily boilerplate? Might be considered legal. Safer to remove it as it's not substantive to the role? It's about visa sponsorship; could be considered relevant for international candidates. But the instruction says remove legal boilerplate. I'd remove that sentence.
Also remove the "Candidates must have a valid driver’s license and be able to pass both a criminal background check and driving record review." That's a requirement; not boilerplate. Keep it.
Now we need to structure sections.
We have:
- About the role (maybe intro paragraph). Could be "About the role" heading.
- Responsibilities: could be derived from the intro describing duties: lead projects, oversee scope schedule budget quality, point of contact, coordinate teams, technical oversight, ensure adherence, stabilize/lead active projects, build client relationships, support business development/proposals, collaborate with leadership on strategic growth, coach team members.
We could combine About the role and Responsibilities? The instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include a section only when posting has real specific content. So we can have About the role (intro), Responsibilities (list of duties), Requirements (maybe includes qualifications?), Qualifications (maybe separate?), Skills (maybe communication etc), Benefits (from Why Join Civil Science), Pay (none), Schedule (none). Since Pay and Schedule not mentioned, we should not include those sections.
We need to avoid thin sections. Let's decide:
- About the role: short paragraph summarizing the role.
- Responsibilities: bullet list of duties.
- Requirements: maybe includes education, licensure, experience, physical requirements, driver's license, background check.
- Qualifications: maybe the same as Requirements? Could combine. But we have both "Qualifications" and "Preferred Experience". Could treat Qualifications as required qualifications, and Skills as preferred/experience? Or we could have Requirements (required) and Skills (preferred). The instruction says we can use Skills section for skills. Let's map:
Required: Bachelor's degree in Civil Engineering, PE license (Utah licensure required or ability to obtain within 3 months), Minimum 12 years relevant transportation design experience, Experience delivering DOT and/or municipal projects, Proven ability to manage multiple projects, priorities, scope, schedule, budget, Strong understanding of roadway, drainage, utility, or traffic design, Excellent communication, client management, organization, leadership skills, Valid driver's license, Ability to pass criminal background check and driving record review, Physical requirements (prolonged sitting, lift 30 lbs, work on sites, etc).
Preferred: UDOT project experience or familiarity with Utah agencies, Experience with ProjectWise, Bluebeam or similar tools, Experience supporting proposal development or business development, Previous experience mentoring or supervising staff.
We could put Required under "Requirements" and Preferred under "Skills" or maybe "Preferred Experience". But we have a heading "Skills". Could put preferred experience there.
Also we have Benefits section from "Why Join Civil Science?" includes ownership (ESOP), room to grow, work-life harmony, comprehensive benefits list.
We need to output only HTML fragment, no extra text.
Let's craft:
About the role
Civil Science is seeking an experienced Transportation Design Project Manager to support and grow its Utah transportation practice. The role is ideal for a licensed Professional Engineer with deep transportation design experience, a strong background delivering DOT and municipal projects, and an interest in mentoring emerging engineers and project leaders. As a key member of the transportation group, you will lead transportation design projects from pursuit through delivery, overseeing scope, schedule, budget, quality, and overall project performance while serving as the primary point of contact for UDOT and municipal clients.
Responsibilities
- Lead transportation design projects from pursuit through delivery, overseeing scope, schedule, budget, quality, and overall project performance.
- Serve as primary point of contact for UDOT and municipal clients.
- Coordinate multidisciplinary teams and provide technical oversight across roadway and related transportation design efforts.
- Ensure adherence to agency standards and project requirements.
- Help stabilize and lead active project opportunities in northern Utah.
- Build client relationships and support business development and proposal efforts.
- Collaborate with leadership on strategic growth initiatives.
- Coach and mentor team members in a collaborative, high‑performing employee‑owned environment.
Requirements
- Bachelor’s degree in Civil Engineering.
- Professional Engineer (PE) license required; Utah licensure required or ability to obtain within three months of hire.
- Minimum 12 years of relevant transportation design experience.
- Experience delivering DOT and/or municipal transportation projects.
- Proven ability to manage multiple projects, priorities, scope, schedule, and budget.
- Strong understanding of roadway, drainage, utility, or traffic design.
- Excellent communication, client management, organization, and leadership skills.
- Valid driver’s license and ability to pass a criminal background check and driving record review.
- Physical requirements: prolonged periods sitting at a desk and working on a computer; ability to lift up to 30 pounds; ability to work on active project or construction sites (uneven terrain, varying weather, moderate to high noise); frequently required to stand, walk, sit, climb, balance, stoop, kneel, crouch, or crawl.
Skills
- UDOT project experience or strong familiarity with Utah agencies.
- Experience with ProjectWise, Bluebeam, or similar tools.
- Experience supporting proposal development or business development efforts.
- Previous experience mentoring or supervising staff.
Benefits
- Ownership in your future through a 100% employee‑owned ESOP.
- Room to grow: agile structure that empowers ownership of projects, exploration of new roles, and accelerated career.
- Work‑life harmony: flexibility to ensure career complements personal life.
- Comprehensive benefits for full‑time employees: three weeks of PTO, eight holidays, medical, dental, vision, life insurance, short/long‑term disability, tuition reimbursement, and a 401(k) plan.