Civil Project Manager / Engineer
to differentiate. Could list essential qualifications as
- ... then Preferred Qualifications as another
- . That's okay under Qualifications.
- Skills: maybe we could extract skills from responsibilities? But we have no explicit skills list; we could omit Skills section if no specific content.
- Benefits: we have bullet list under "Why You’ll Love SEH": career development, work arrangements, flexible holidays, paid family leave. Also ESOP, flexible work arrangements (already), ability to build client portfolio, strong technical team, influence strategic direction, collaborative culture, meaningful projects. Also "Check out our full benefits package at SEH Hiring Journey." So we can create Benefits section with those items.
- Pay: we have base compensation range $100k-$140k.
- Schedule: we have flexible work arrangements, hybrid/remote options based on project and client needs. Also flexible holidays. Could be schedule.
We must not create sections with filler like "not specified". So we include only those with real content.
We must not repeat job title as heading. So no heading for "Civil Project Manager / Engineer". Good.
We must not include Job ID etc.
We must output only HTML fragment, no /, no markdown fences.
Thus produce something like:
About the role
Imagine being an employee-owner of a company guided by engaged and empowered team members...
... maybe combine multiple paragraphs. But we need to preserve all substantive info; we cannot omit details like quotes, etc. We need to include all substantive info from the posting, except boilerplate. That's a lot. We need to include quotes from employee-owners, the "Why You’ll Love SEH" bullet list, "Shape the Future of Infrastructure in Nebraska", "Why SEH?" bullet list, "What Success Looks Like", "This Opportunity" duties, Essential Qualifications, Preferred Qualifications, Who We Are, compensation, benefits, location restrictions, work authorization note. We must not include EEO, third party agency notice, etc. We need to decide how to structure. We could have:About the role
Imagine being an employee-owner of a company guided by engaged and empowered team members like yourself. Where a culture of respect, flexibility, and accountability aren't just ideals - they're our foundation, and diverse backgrounds and perspectives are valued as drivers of innovation and growth. Join us, as together, we are Building a Better World for All of Us®. You belong at SEH. SEH is currently searching for a Civil Project Manager / Engineer to join our talented Civil team!
“I was on vacation last week and had zero concerns that my colleagues would help out with anything that came into my inbox!” – GIS Analyst
“What company has a CEO who cares enough to seek out one-on-one conversations ranging from ‘How are you?’ to ‘What do you think would help the company?’ SEH, that's who.” – Civil Engineering Technician
“Having the feeling that my voice matters and believing that SEH truly cares about the employees is so satisfying!” – Sr Financial Analyst
“It feels good having colleagues and supervisors that provide support and resources for growth and learning!” – Civil Engineer
“This is the first company I've worked for with a true entrepreneurial spirit.” – Sr Mechanical Engineer
Then maybe aWhy You’ll Love SEH
but that's not in allowed headings. Could fold into About the role or Benefits. Since Benefits heading exists, we could put those bullet points under Benefits. But the "Why You’ll Love SEH" includes both benefits and culture items. We could split: culture items under About the role, benefits under Benefits. But we must not create headings not in list. So we cannot have a heading "Why You’ll Love SEH". So we need to incorporate that content under allowed headings. Thus: - About the role: include introductory paragraphs, employee-owner culture, quotes, mission, maybe also "Shape the Future of Infrastructure in Nebraska" and "Why SEH?" (since those describe role/opportunity). But we also have Responsibilities separate. Better: About the role: general description of role and company culture. Responsibilities: the "This Opportunity" bullet list. Qualifications: Essential and Preferred Qualifications. Benefits: the "Why You’ll Love SEH" bullet list (career development, work arrangements, flexible holidays, paid family leave, ESOP, ability to build client portfolio, strong technical team, influence strategic direction, collaborative culture, meaningful projects) plus maybe reference to full benefits package. Pay: compensation range. Schedule: flexible work arrangements, hybrid/remote, flexible holidays. We also need to include location restrictions and work authorization note. Where to put? Could be under Requirements (as eligibility). Or maybe under About the role? Probably Requirements. Thus Requirements heading: include "Bachelor's degree in Civil Engineering or related field." etc? Actually those are qualifications. But we have Qualifications heading for education/license/experience. Requirements could be things like "must be authorized to work for any employer in the U.S. without requiring visa sponsorship now or in the future." and location restrictions (states unable to hire). Also maybe "willing to relocate". So we can put those under Requirements. Thus we need to decide mapping: - About the role: intro, culture, mission, quotes, shape future, why SEH, what success looks like. - Responsibilities: This Opportunity bullet list. - Requirements: work authorization, location restrictions, willingness to relocate. - Qualifications: Essential Qualifications bullet list, Preferred Qualifications bullet list. - Benefits: Why You’ll Love SEH bullet list (career development, work arrangements, flexible holidays, paid family leave, ESOP, ability to build client portfolio, strong technical team, influence strategic direction, collaborative culture, meaningful projects) plus note to check full benefits. - Pay: base compensation range. - Schedule: flexible work arrangements, hybrid/remote options, flexible holidays. We must not create sections with filler. All have content. Now we need to ensure we don't repeat content unnecessarily. But we must preserve all substantive info. Some info may appear in multiple sections; we need to ensure we don't lose any. For example, "flexible work arrangements" appears both in Why You’ll Love SEH and also in Schedule. We could mention it in both places; that's okay as preserving info. But we might duplicate; but it's okay as long as we don't invent or summarize away detail. Duplication is allowed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited, but we should avoid unnecessary duplication? Not explicitly forbidden. However we might want to avoid duplication to keep clean. But we need to preserve all info; if we mention it only once, we still preserve it. So we can place flexible work arrangements under Schedule, and not repeat under Benefits unless we also want to mention other benefits. But the "Why You’ll Love SEH" includes flexible work arrangements as a benefit; we could keep it under Benefits as well. But to avoid duplication, we could mention it only under Schedule and note that it's also a benefit. However the instruction says preserve all substantive information; if we mention it only under Schedule, we still preserve it. So it's fine. Similarly, "flexible holidays" appears under Benefits and also Schedule; we can put under Schedule. "Paid Family Leave" is a benefit. "ESOP" is a benefit. "Ability to build and grow your own client portfolio and area of expertise" is a benefit. "Strong technical team and national resources supporting local project delivery" benefit. "Ability to influence strategic direction and growth of the Omaha office" benefit. "Collaborative culture focused on relationships, technical excellence, and long-term success" benefit. "Opportunity to work on meaningful projects that improve communities across Nebraska and the Midwest" benefit. Thus Benefits section can include those. Now we need to format. We'll produce:About the role
Imagine being an employee-owner of a company guided by engaged and empowered team members like yourself. Where a culture of respect, flexibility, and accountability aren't just ideals - they're our foundation, and diverse backgrounds and perspectives are valued as drivers of innovation and growth. Join us, as together, we are Building a Better World for All of Us®. You belong at SEH. SEH is currently searching for a Civil Project Manager / Engineer to join our talented Civil team!
“I was on vacation last week and had zero concerns that my colleagues would help out with anything that
- . That's okay under Qualifications.
- Skills: maybe we could extract skills from responsibilities? But we have no explicit skills list; we could omit Skills section if no specific content.
- Benefits: we have bullet list under "Why You’ll Love SEH": career development, work arrangements, flexible holidays, paid family leave. Also ESOP, flexible work arrangements (already), ability to build client portfolio, strong technical team, influence strategic direction, collaborative culture, meaningful projects. Also "Check out our full benefits package at SEH Hiring Journey." So we can create Benefits section with those items.
- Pay: we have base compensation range $100k-$140k.
- Schedule: we have flexible work arrangements, hybrid/remote options based on project and client needs. Also flexible holidays. Could be schedule.
We must not create sections with filler like "not specified". So we include only those with real content.
We must not repeat job title as heading. So no heading for "Civil Project Manager / Engineer". Good.
We must not include Job ID etc.
We must output only HTML fragment, no /, no markdown fences.
Thus produce something like: