Principal Project Manager, Rail + Transit
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We must not repeat job title as heading. We must not put Job ID/requisition numbers as headings. We must include a section only when posting has real, specific content for it. We must preserve all substantive information; do not invent or summarize away detail. Remove boilerplate etc.
We need to decide which sections to include based on content.
We have:
- Job Summary: description of role, purpose. Could be "About the role" or "Job Summary". The allowed headings list includes "About the role". We'll use that.
- Responsibilities & Qualifications: includes responsibilities and qualifications. Could split into "Responsibilities" and "Qualifications" or "Requirements". The allowed headings include Responsibilities, Requirements, Qualifications, Skills. We'll need to extract responsibilities list and qualifications list.
- "What You'll Focus On" includes responsibilities broken into subpoints: Lead Delivery..., Support Client Development..., Mentor & Strengthen Technical Teams. Those are responsibilities.
- "What You Bring" includes qualifications: years experience, proven track record, deep expertise, strong understanding, established relationships, experience working with public-sector agencies, experience supporting pursuits, degree, PE etc, strong communication etc. Those are qualifications/requirements/skills.
- "Why This Role Stands Out": could be "Benefits"? Not exactly; it's about role highlights. Could be "About the role" but we already used. Maybe we can treat as "Why This Role Stands Out" as a section heading? Not in allowed list but we could still use with that text? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. But we can also use other headings if needed? Safer to stick to those. So we need to map content to those headings.
We have:
- About the role: could contain Job Summary and maybe Why This Role Stands Out? But we need to avoid filler. We'll put Job Summary in About the role.
- Responsibilities: list of duties.
- Requirements/Qualifications/Skills: we need to decide which to use. Could combine qualifications and skills into one section "Qualifications" or "Requirements". Since we have both qualifications and skills, we could have "Qualifications" for education/experience, and "Skills" for soft skills. But we need to avoid thin sections. Perhaps combine into "Qualifications" covering both experience and skills.
- Benefits: we have benefits info in Additional Information: "TYLin offers a comprehensive total rewards package. Our benefits may include extensive medical, disability and life insurance coverage, continuing education benefits, paid time off, employee assistance program and a retirement savings plan with company matching contributions." That's specific enough for Benefits section.
- Pay: we have base compensation range $200,000 - $290,000 annually. That's specific, so we need Pay section.
- Schedule: not mentioned; we should not create Schedule section.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
We must not include empty sections.
Now we need to format lists with - for any list of duties/requirements/benefits. For prose, use
.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details exactly as in posting, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Probably we should keep the wording close but can restructure into HTML. We'll try to keep the substance.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At the end there is EEO statement, military service, etc. Those are boilerplate; we should remove them. Also "Additional Information" includes some boilerplate like "TYLin is committed to pay equity." That's substantive? It mentions pay equity but we already have Pay range. Might keep? It's not boilerplate; it's about pay equity commitment. Could keep as part of Additional Information but we already have Pay and Benefits sections; we could incorporate that sentence into About the role or Pay? Might be considered filler? It's not boilerplate but it's a statement. We could include it in About the role or Pay as a note. However we need to preserve all substantive information; we can't omit it. So we need to include that statement somewhere. Perhaps we can add a
under About the role or Pay that says "TYLin is committed to pay equity." But we already have Pay section with range; we could add that sentence as a
inside Pay section.
Also "TYLin is proud to offer exciting career development opportunities." That's substantive; could be part of Benefits or About the role. We'll incorporate into Benefits maybe.
Also "We encourage all candidates to explore our total rewards offering." That's boilerplate? Might be considered generic; but it's about benefits. Could be omitted? It's not duplicated lines but it's generic encouragement. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not those; it's about exploring total rewards. Might keep.
But we need to avoid filler like "commensurate with experience", "not specified", etc. Not present.
We'll need to extract responsibilities list:
From "What You’ll Focus On":
- Lead Delivery of Complex Rail & Transit Projects — Primary Focus (~70%)
* Serve as Project Manager or Project Director on major rail and transit programs across the Pacific Northwest.
* Lead multidisciplinary teams across civil, structural, track, systems, facilities, and other transit disciplines.
* Drive project execution—including scope, schedule, budget, risk, quality, and client expectations—from planning through delivery.
* Act as a senior technical and project delivery authority, providing guidance on design decisions, constructability, coordination, and delivery strategy.
* Ensure projects are delivered to TYLin’s standards for technical excellence, safety, quality, and client satisfaction.
* Support coordination with transit agencies, municipalities, contractors, consultants, and project partners throughout all phases of delivery.
* Help establish strong project teams, accountability, communication, and delivery processes.
- Support Client Development & Pursuits — ~30%
* Leverage existing relationships, market knowledge, and technical credibility to support business development efforts.
* Act as a trusted advisor to clients and agencies across the Pacific Northwest transit market.
* Contribute to pursuits through positioning, capture planning, client engagement, and proposal development.
* Support interviews and technical presentations, bringing project delivery credibility to pursuit strategies.
* Help identify and shape new opportunities aligned with TYLin’s rail and transit capabilities.
* Build relationships across the regional transportation market while strengthening TYLin’s long-term client partnerships.
- Mentor & Strengthen Technical Teams
* Provide mentorship, technical guidance, and project leadership to project managers, engineers, designers, and other technical staff.
* Help develop the next generation of project delivery leaders within the Rail & Transit practice.
* Share best practices and help elevate consistency, technical quality, and delivery capability across the team.
* Contribute to a collaborative, delivery-focused culture grounded in accountability, technical excellence, and continuous improvement.
We need to preserve all these bullet points. We'll put them under Responsibilities as
- .
Now Qualifications/Requirements/Skills:
From "What You Bring":
- 15–25+ years of experience in Rail & Transit project delivery, with a strong emphasis on complex infrastructure programs.
- Proven track record as a Project Manager or Project Director on major rail, transit, or transportation infrastructure projects.
- Deep expertise in one or more areas such as civil, structural, track, stations, rail facilities, systems, or transit infrastructure.
- Strong understanding of project execution, including scope, schedule, budget, risk management, stakeholder coordination, and multidisciplinary integration.
- Established relationships within the Pacific Northwest transportation and transit market, or demonstrated ability to quickly establish credibility and relationships within the region.
- Experience working with public-sector transportation agencies, transit authorities, municipalities, contractors, and/or major program partners.
- Experience supporting pursuits and contributing to winning work, without primary responsibility for sales targets or P&L.
- Bachelor’s or Master’s degree in Civil or Structural Engineering, Architecture, or a related discipline.
- PE, RA, or other relevant professional registration strongly preferred, depending on discipline.
- Strong communication, leadership, and relationship-building skills.
Also from "Who This Role Will Suit": bullet points describing ideal candidate. Those are also qualifications/skills but could be considered additional. We should preserve them as well. They are:
- Is a proven project and delivery leader but prefers technical and project leadership over full business-unit management.
- Enjoys leading complex projects and being accountable for execution and outcomes.
- Has credibility with clients and technical teams and can build trusted relationships across the transportation industry.
- Has strong project delivery experience and understands what it takes to successfully coordinate complex, multidisciplinary infrastructure programs.
- Wants to contribute to growth and strategy while remaining grounded in project delivery.
- Enjoys mentoring others and helping develop stronger project managers and technical leaders.
- Is looking for a senior role with meaningful regional impact without stepping fully away from the technical side of the business.
These are more like traits; could be considered Skills or Qualifications. We'll include them under Qualifications or Skills. Since we have a Skills heading allowed, we could put these under Skills. But we already have many qualifications; we could split: Qualifications for experience/education, Skills for soft skills and traits. However we must avoid thin sections. If we split, we might have many sections but each will have content. That's okay. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid too many sections. Maybe combine all into Qualifications (or Requirements) and keep Skills omitted. But we have a Skills heading allowed; we could use Skills for the soft skill bullets from "Who This Role Will Suit" and the communication/leadership etc. But that might be thin? Let's see.
We have Qualifications content: experience, track record, expertise, understanding, relationships, experience with public sector, experience supporting pursuits, degree, professional registration. That's substantive.
Skills content: strong communication, leadership, relationship-building skills (already in What You Bring) plus the Who This Role Will Suit bullets (proven leader, enjoys leading complex projects, credibility, wants to contribute to growth, enjoys mentoring, looking for senior role). That's also substantive.
We could combine both into Qualifications section to avoid many sections. That would be one big list. That's acceptable.
Thus we will have Qualifications section with a
- list combining all those points.
Now Benefits section: we have benefits description: "TYLin offers a comprehensive total rewards package. Our benefits may include extensive medical, disability and life insurance coverage, continuing education benefits, paid time off, employee assistance program and a retirement savings plan with company matching contributions." Also "TYLin is proud to offer exciting career development opportunities." and "We encourage all candidates to explore our total rewards offering." Also maybe "TYLin is committed to pay equity." but that's more about pay.
We'll include benefits as list items: extensive medical, disability and life insurance coverage, continuing education benefits, paid time off, employee assistance program, retirement savings plan with company matching
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we can use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. But we can also use other headings if needed? Safer to stick to those. So we need to map content to those headings.
We have:
- About the role: could contain Job Summary and maybe Why This Role Stands Out? But we need to avoid filler. We'll put Job Summary in About the role.
- Responsibilities: list of duties.
- Requirements/Qualifications/Skills: we need to decide which to use. Could combine qualifications and skills into one section "Qualifications" or "Requirements". Since we have both qualifications and skills, we could have "Qualifications" for education/experience, and "Skills" for soft skills. But we need to avoid thin sections. Perhaps combine into "Qualifications" covering both experience and skills.
- Benefits: we have benefits info in Additional Information: "TYLin offers a comprehensive total rewards package. Our benefits may include extensive medical, disability and life insurance coverage, continuing education benefits, paid time off, employee assistance program and a retirement savings plan with company matching contributions." That's specific enough for Benefits section.
- Pay: we have base compensation range $200,000 - $290,000 annually. That's specific, so we need Pay section.
- Schedule: not mentioned; we should not create Schedule section.
Thus sections: About the role, Responsibilities, Qualifications, Benefits, Pay.
We must not include empty sections.
Now we need to format lists with - for any list of duties/requirements/benefits. For prose, use
.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details exactly as in posting, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Probably we should keep the wording close but can restructure into HTML. We'll try to keep the substance.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At the end there is EEO statement, military service, etc. Those are boilerplate; we should remove them. Also "Additional Information" includes some boilerplate like "TYLin is committed to pay equity." That's substantive? It mentions pay equity but we already have Pay range. Might keep? It's not boilerplate; it's about pay equity commitment. Could keep as part of Additional Information but we already have Pay and Benefits sections; we could incorporate that sentence into About the role or Pay? Might be considered filler? It's not boilerplate but it's a statement. We could include it in About the role or Pay as a note. However we need to preserve all substantive information; we can't omit it. So we need to include that statement somewhere. Perhaps we can add a
under About the role or Pay that says "TYLin is committed to pay equity." But we already have Pay section with range; we could add that sentence as a
inside Pay section.
Also "TYLin is proud to offer exciting career development opportunities." That's substantive; could be part of Benefits or About the role. We'll incorporate into Benefits maybe.
Also "We encourage all candidates to explore our total rewards offering." That's boilerplate? Might be considered generic; but it's about benefits. Could be omitted? It's not duplicated lines but it's generic encouragement. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not those; it's about exploring total rewards. Might keep.
But we need to avoid filler like "commensurate with experience", "not specified", etc. Not present.
We'll need to extract responsibilities list:
From "What You’ll Focus On":
- Lead Delivery of Complex Rail & Transit Projects — Primary Focus (~70%)
* Serve as Project Manager or Project Director on major rail and transit programs across the Pacific Northwest.
* Lead multidisciplinary teams across civil, structural, track, systems, facilities, and other transit disciplines.
* Drive project execution—including scope, schedule, budget, risk, quality, and client expectations—from planning through delivery.
* Act as a senior technical and project delivery authority, providing guidance on design decisions, constructability, coordination, and delivery strategy.
* Ensure projects are delivered to TYLin’s standards for technical excellence, safety, quality, and client satisfaction.
* Support coordination with transit agencies, municipalities, contractors, consultants, and project partners throughout all phases of delivery.
* Help establish strong project teams, accountability, communication, and delivery processes.
- Support Client Development & Pursuits — ~30%
* Leverage existing relationships, market knowledge, and technical credibility to support business development efforts.
* Act as a trusted advisor to clients and agencies across the Pacific Northwest transit market.
* Contribute to pursuits through positioning, capture planning, client engagement, and proposal development.
* Support interviews and technical presentations, bringing project delivery credibility to pursuit strategies.
* Help identify and shape new opportunities aligned with TYLin’s rail and transit capabilities.
* Build relationships across the regional transportation market while strengthening TYLin’s long-term client partnerships.
- Mentor & Strengthen Technical Teams
* Provide mentorship, technical guidance, and project leadership to project managers, engineers, designers, and other technical staff.
* Help develop the next generation of project delivery leaders within the Rail & Transit practice.
* Share best practices and help elevate consistency, technical quality, and delivery capability across the team.
* Contribute to a collaborative, delivery-focused culture grounded in accountability, technical excellence, and continuous improvement.
We need to preserve all these bullet points. We'll put them under Responsibilities as
- .
Now Qualifications/Requirements/Skills:
From "What You Bring":
- 15–25+ years of experience in Rail & Transit project delivery, with a strong emphasis on complex infrastructure programs.
- Proven track record as a Project Manager or Project Director on major rail, transit, or transportation infrastructure projects.
- Deep expertise in one or more areas such as civil, structural, track, stations, rail facilities, systems, or transit infrastructure.
- Strong understanding of project execution, including scope, schedule, budget, risk management, stakeholder coordination, and multidisciplinary integration.
- Established relationships within the Pacific Northwest transportation and transit market, or demonstrated ability to quickly establish credibility and relationships within the region.
- Experience working with public-sector transportation agencies, transit authorities, municipalities, contractors, and/or major program partners.
- Experience supporting pursuits and contributing to winning work, without primary responsibility for sales targets or P&L.
- Bachelor’s or Master’s degree in Civil or Structural Engineering, Architecture, or a related discipline.
- PE, RA, or other relevant professional registration strongly preferred, depending on discipline.
- Strong communication, leadership, and relationship-building skills.
Also from "Who This Role Will Suit": bullet points describing ideal candidate. Those are also qualifications/skills but could be considered additional. We should preserve them as well. They are:
- Is a proven project and delivery leader but prefers technical and project leadership over full business-unit management.
- Enjoys leading complex projects and being accountable for execution and outcomes.
- Has credibility with clients and technical teams and can build trusted relationships across the transportation industry.
- Has strong project delivery experience and understands what it takes to successfully coordinate complex, multidisciplinary infrastructure programs.
- Wants to contribute to growth and strategy while remaining grounded in project delivery.
- Enjoys mentoring others and helping develop stronger project managers and technical leaders.
- Is looking for a senior role with meaningful regional impact without stepping fully away from the technical side of the business.
These are more like traits; could be considered Skills or Qualifications. We'll include them under Qualifications or Skills. Since we have a Skills heading allowed, we could put these under Skills. But we already have many qualifications; we could split: Qualifications for experience/education, Skills for soft skills and traits. However we must avoid thin sections. If we split, we might have many sections but each will have content. That's okay. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid too many sections. Maybe combine all into Qualifications (or Requirements) and keep Skills omitted. But we have a Skills heading allowed; we could use Skills for the soft skill bullets from "Who This Role Will Suit" and the communication/leadership etc. But that might be thin? Let's see.
We have Qualifications content: experience, track record, expertise, understanding, relationships, experience with public sector, experience supporting pursuits, degree, professional registration. That's substantive.
Skills content: strong communication, leadership, relationship-building skills (already in What You Bring) plus the Who This Role Will Suit bullets (proven leader, enjoys leading complex projects, credibility, wants to contribute to growth, enjoys mentoring, looking for senior role). That's also substantive.
We could combine both into Qualifications section to avoid many sections. That would be one big list. That's acceptable.
Thus we will have Qualifications section with a
- list combining all those points.
Now Benefits section: we have benefits description: "TYLin offers a comprehensive total rewards package. Our benefits may include extensive medical, disability and life insurance coverage, continuing education benefits, paid time off, employee assistance program and a retirement savings plan with company matching contributions." Also "TYLin is proud to offer exciting career development opportunities." and "We encourage all candidates to explore our total rewards offering." Also maybe "TYLin is committed to pay equity." but that's more about pay.
We'll include benefits as list items: extensive medical, disability and life insurance coverage, continuing education benefits, paid time off, employee assistance program, retirement savings plan with company matching
- for any list of duties/requirements/benefits. For prose, use
. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details exactly as in posting, but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can rephrase? Probably we should keep the wording close but can restructure into HTML. We'll try to keep the substance. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. At the end there is EEO statement, military service, etc. Those are boilerplate; we should remove them. Also "Additional Information" includes some boilerplate like "TYLin is committed to pay equity." That's substantive? It mentions pay equity but we already have Pay range. Might keep? It's not boilerplate; it's about pay equity commitment. Could keep as part of Additional Information but we already have Pay and Benefits sections; we could incorporate that sentence into About the role or Pay? Might be considered filler? It's not boilerplate but it's a statement. We could include it in About the role or Pay as a note. However we need to preserve all substantive information; we can't omit it. So we need to include that statement somewhere. Perhaps we can add a
under About the role or Pay that says "TYLin is committed to pay equity." But we already have Pay section with range; we could add that sentence as a
inside Pay section. Also "TYLin is proud to offer exciting career development opportunities." That's substantive; could be part of Benefits or About the role. We'll incorporate into Benefits maybe. Also "We encourage all candidates to explore our total rewards offering." That's boilerplate? Might be considered generic; but it's about benefits. Could be omitted? It's not duplicated lines but it's generic encouragement. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This line is not those; it's about exploring total rewards. Might keep. But we need to avoid filler like "commensurate with experience", "not specified", etc. Not present. We'll need to extract responsibilities list: From "What You’ll Focus On": - Lead Delivery of Complex Rail & Transit Projects — Primary Focus (~70%) * Serve as Project Manager or Project Director on major rail and transit programs across the Pacific Northwest. * Lead multidisciplinary teams across civil, structural, track, systems, facilities, and other transit disciplines. * Drive project execution—including scope, schedule, budget, risk, quality, and client expectations—from planning through delivery. * Act as a senior technical and project delivery authority, providing guidance on design decisions, constructability, coordination, and delivery strategy. * Ensure projects are delivered to TYLin’s standards for technical excellence, safety, quality, and client satisfaction. * Support coordination with transit agencies, municipalities, contractors, consultants, and project partners throughout all phases of delivery. * Help establish strong project teams, accountability, communication, and delivery processes. - Support Client Development & Pursuits — ~30% * Leverage existing relationships, market knowledge, and technical credibility to support business development efforts. * Act as a trusted advisor to clients and agencies across the Pacific Northwest transit market. * Contribute to pursuits through positioning, capture planning, client engagement, and proposal development. * Support interviews and technical presentations, bringing project delivery credibility to pursuit strategies. * Help identify and shape new opportunities aligned with TYLin’s rail and transit capabilities. * Build relationships across the regional transportation market while strengthening TYLin’s long-term client partnerships. - Mentor & Strengthen Technical Teams * Provide mentorship, technical guidance, and project leadership to project managers, engineers, designers, and other technical staff. * Help develop the next generation of project delivery leaders within the Rail & Transit practice. * Share best practices and help elevate consistency, technical quality, and delivery capability across the team. * Contribute to a collaborative, delivery-focused culture grounded in accountability, technical excellence, and continuous improvement. We need to preserve all these bullet points. We'll put them under Responsibilities as
- .
Now Qualifications/Requirements/Skills:
From "What You Bring":
- 15–25+ years of experience in Rail & Transit project delivery, with a strong emphasis on complex infrastructure programs.
- Proven track record as a Project Manager or Project Director on major rail, transit, or transportation infrastructure projects.
- Deep expertise in one or more areas such as civil, structural, track, stations, rail facilities, systems, or transit infrastructure.
- Strong understanding of project execution, including scope, schedule, budget, risk management, stakeholder coordination, and multidisciplinary integration.
- Established relationships within the Pacific Northwest transportation and transit market, or demonstrated ability to quickly establish credibility and relationships within the region.
- Experience working with public-sector transportation agencies, transit authorities, municipalities, contractors, and/or major program partners.
- Experience supporting pursuits and contributing to winning work, without primary responsibility for sales targets or P&L.
- Bachelor’s or Master’s degree in Civil or Structural Engineering, Architecture, or a related discipline.
- PE, RA, or other relevant professional registration strongly preferred, depending on discipline.
- Strong communication, leadership, and relationship-building skills.
Also from "Who This Role Will Suit": bullet points describing ideal candidate. Those are also qualifications/skills but could be considered additional. We should preserve them as well. They are:
- Is a proven project and delivery leader but prefers technical and project leadership over full business-unit management.
- Enjoys leading complex projects and being accountable for execution and outcomes.
- Has credibility with clients and technical teams and can build trusted relationships across the transportation industry.
- Has strong project delivery experience and understands what it takes to successfully coordinate complex, multidisciplinary infrastructure programs.
- Wants to contribute to growth and strategy while remaining grounded in project delivery.
- Enjoys mentoring others and helping develop stronger project managers and technical leaders.
- Is looking for a senior role with meaningful regional impact without stepping fully away from the technical side of the business.
These are more like traits; could be considered Skills or Qualifications. We'll include them under Qualifications or Skills. Since we have a Skills heading allowed, we could put these under Skills. But we already have many qualifications; we could split: Qualifications for experience/education, Skills for soft skills and traits. However we must avoid thin sections. If we split, we might have many sections but each will have content. That's okay. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid too many sections. Maybe combine all into Qualifications (or Requirements) and keep Skills omitted. But we have a Skills heading allowed; we could use Skills for the soft skill bullets from "Who This Role Will Suit" and the communication/leadership etc. But that might be thin? Let's see.
We have Qualifications content: experience, track record, expertise, understanding, relationships, experience with public sector, experience supporting pursuits, degree, professional registration. That's substantive.
Skills content: strong communication, leadership, relationship-building skills (already in What You Bring) plus the Who This Role Will Suit bullets (proven leader, enjoys leading complex projects, credibility, wants to contribute to growth, enjoys mentoring, looking for senior role). That's also substantive.
We could combine both into Qualifications section to avoid many sections. That would be one big list. That's acceptable.
Thus we will have Qualifications section with a
- list combining all those points. Now Benefits section: we have benefits description: "TYLin offers a comprehensive total rewards package. Our benefits may include extensive medical, disability and life insurance coverage, continuing education benefits, paid time off, employee assistance program and a retirement savings plan with company matching contributions." Also "TYLin is proud to offer exciting career development opportunities." and "We encourage all candidates to explore our total rewards offering." Also maybe "TYLin is committed to pay equity." but that's more about pay. We'll include benefits as list items: extensive medical, disability and life insurance coverage, continuing education benefits, paid time off, employee assistance program, retirement savings plan with company matching
- .
Now Qualifications/Requirements/Skills:
From "What You Bring":
- 15–25+ years of experience in Rail & Transit project delivery, with a strong emphasis on complex infrastructure programs.
- Proven track record as a Project Manager or Project Director on major rail, transit, or transportation infrastructure projects.
- Deep expertise in one or more areas such as civil, structural, track, stations, rail facilities, systems, or transit infrastructure.
- Strong understanding of project execution, including scope, schedule, budget, risk management, stakeholder coordination, and multidisciplinary integration.
- Established relationships within the Pacific Northwest transportation and transit market, or demonstrated ability to quickly establish credibility and relationships within the region.
- Experience working with public-sector transportation agencies, transit authorities, municipalities, contractors, and/or major program partners.
- Experience supporting pursuits and contributing to winning work, without primary responsibility for sales targets or P&L.
- Bachelor’s or Master’s degree in Civil or Structural Engineering, Architecture, or a related discipline.
- PE, RA, or other relevant professional registration strongly preferred, depending on discipline.
- Strong communication, leadership, and relationship-building skills.
Also from "Who This Role Will Suit": bullet points describing ideal candidate. Those are also qualifications/skills but could be considered additional. We should preserve them as well. They are:
- Is a proven project and delivery leader but prefers technical and project leadership over full business-unit management.
- Enjoys leading complex projects and being accountable for execution and outcomes.
- Has credibility with clients and technical teams and can build trusted relationships across the transportation industry.
- Has strong project delivery experience and understands what it takes to successfully coordinate complex, multidisciplinary infrastructure programs.
- Wants to contribute to growth and strategy while remaining grounded in project delivery.
- Enjoys mentoring others and helping develop stronger project managers and technical leaders.
- Is looking for a senior role with meaningful regional impact without stepping fully away from the technical side of the business.
These are more like traits; could be considered Skills or Qualifications. We'll include them under Qualifications or Skills. Since we have a Skills heading allowed, we could put these under Skills. But we already have many qualifications; we could split: Qualifications for experience/education, Skills for soft skills and traits. However we must avoid thin sections. If we split, we might have many sections but each will have content. That's okay. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid too many sections. Maybe combine all into Qualifications (or Requirements) and keep Skills omitted. But we have a Skills heading allowed; we could use Skills for the soft skill bullets from "Who This Role Will Suit" and the communication/leadership etc. But that might be thin? Let's see.
We have Qualifications content: experience, track record, expertise, understanding, relationships, experience with public sector, experience supporting pursuits, degree, professional registration. That's substantive.
Skills content: strong communication, leadership, relationship-building skills (already in What You Bring) plus the Who This Role Will Suit bullets (proven leader, enjoys leading complex projects, credibility, wants to contribute to growth, enjoys mentoring, looking for senior role). That's also substantive.
We could combine both into Qualifications section to avoid many sections. That would be one big list. That's acceptable.
Thus we will have Qualifications section with a