Project Manager (Omaha)
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. We have:
- About the role: Could be the introductory paragraph about Turner and the role? The posting includes "If you picture yourself doing great things..." etc. That's more about company. Could be considered About the role. We'll include that as About the role
with
containing that paragraph(s). Need to preserve all substantive info. - Responsibilities: The duties list after "Position Description:" includes many bullet-like sentences. We'll put them in
- .
- Qualifications: The "Qualifications:" section includes bullet-like sentences: Bachelor's Degree plus..., Thorough knowledge..., Proven..., Must have..., Ability..., Demonstrated..., etc. We'll put in
- .
- Skills: Not explicitly separate; maybe we could treat some as Skills but we have Qualifications covering skills. The instruction says prefer few substantive sections over many thin ones. So we could combine Qualifications and Skills? But we have a Qualifications section already. Could also include Skills if there are distinct skill statements not covered. The Qualifications includes "Proven written and verbal communication abilities, proficiency with computer applications, including Microsoft Office Suite of programs. Must have advanced presentation skills." Those are skills. Could still be under Qualifications. We'll not create separate Skills unless there is explicit "Skills:" heading. There's none. So we skip Skills.
- Benefits, Pay, Schedule: Not present. So we omit those sections.
- Requirements: Could be same as Qualifications? The instruction says use headings like Requirements, Qualifications, Skills. We have Qualifications. Could also include Requirements if there are separate requirement statements like Minimum Years Experience etc. The posting includes metadata: Division, Location, Minimum Years Experience, Travel Involved, Job Type, etc. Those are minor metadata; we should fold into a short
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short
with that metadata maybe under About the role or separate? Probably better to include a short
after the heading About the role containing the metadata. But we must not repeat job title as heading. The job title is not given explicitly; maybe it's implied "Project Manager"? Not in text. We'll ignore. We need to preserve all substantive information: The company description, the position description duties, qualifications, physical demands, work environment. Also note the statement "This is not a remote/hybrid position and will be based in a Turner office or project location." That's substantive about location; we should include that maybe in About the role or a separate note. Could be part of About the role. Also "Turner is an Equal Opportunity Employer..." is boilerplate EEO; we should remove that per instruction: remove EEO/equal-opportunity boilerplate. So drop that. Also remove cookie/navigation/legal etc. Not present. We need to output only HTML fragment, no /, no markdown fences. Thus structure:
About the role
If you picture yourself doing great things that make a difference in the lives of others, Turner is the place to be. Turner Construction is an industry leading commercial construction general contractor with a 120-year history spanning iconic projects around the globe, including 10 of the world's 100 tallest buildings. Turner's Omaha office values relationships with trade partners, local businesses, and non-profit organizations, reflecting and reinforcing our commitment to Nebraska and local communities. Omaha's current working portfolio includes everything from data centers and elaborate pharmaceutical renovations to commercial spaces. Turner is committed to sustaining a diverse, equitable, and inclusive environment where everyone feels connected, sees themselves represented at all levels of the company, and feels supported to reach their ultimate potential. Turner builds some of the most ambitious projects in the world. The technical expertise of our people makes us a recognized leader in many markets. Our projects are well known. Our people set us apart. We inspire greatness. Can you picture yourself at Turner? If so, apply and let’s do great things together! This is not a remote/hybrid position and will be based in a Turner office or project location.
Responsibilities
- Lead in the development of high-performance teams through supervision, training, coaching, and mentoring.
- Ensure regular feedback is shared with staff including timely completion of employee performance appraisals.
- Manage and develop assigned staff toward maximum job performance and career potential.
- Develop and improve upon assigned client relationships fostering a “trusted advisor” status.
- Understand and administer Turner's contract and subcontract agreements.
- Provide leadership to positively influence change.
- Promote Turner's involvement in the community to help build strategic relationships and to embrace the community in which we live and work.
- Foster and enhance architect, subcontractor and vendor relations.
- Establish, update, and communicate the Master Project Schedule and manage its implementation.
- May work with preconstruction team in development of project.
- Manage budget and financial reporting, interpret and analyze reports to ensure adherence to project budget.
- Manage the Quality Assurance/Quality Control (QA/QC) program.
- Provide leadership in risk evaluation, contract negotiations, fee and pricing decisions.
- Understand, comply and advise others on Turner's business ethics and compliance programs.
- Demonstrate high standard of personal accountability and integrity. Mentor staff to the same high standards.
- Manage and oversee field operation and engineering processes and procedures.
- Drive competencies to team on requirements for insurance, labor relations, and employee relations.
- Drive enforcement of safety protocols by the project staff.
- Work with Finance to initiate the Pay Application process and follow up to ensure payment is received in a timely manner.
- Keep management informed on progress for project and budget through regularly scheduled Operations Review Meetings.
- Support and drive utilization of various Turner initiatives. Promote and utilize emerging technologies and innovations to support Turner sustainable competitive advantages.
- Provide leadership to foster an environment of diversity and inclusion.
Qualifications
- Bachelor's Degree plus a minimum of ten years related experience or an equivalent combination of education, training, and/or experience.
- Thorough knowledge of construction cost, scheduling, estimating, purchasing, and engineering principles and techniques, as well as accounting principles.
- Proven written and verbal communication abilities, proficiency with computer applications, including Microsoft Office Suite of programs.
- Must have advanced presentation skills.
- Ability to read, understand and interpret contract documents, drawings, specifications, scopes of work, and project schedule.
- Demonstrated leadership and interpersonal skills.
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use
for section headings (e.g. those). Likely we should stick to those headings only. But we have substantive info in Physical Demands and Work Environment; we need to preserve ALL substantive information. If we cannot create a heading for them, we could fold them into existing sections like Responsibilities or Qualifications? But they are not responsibilities or qualifications; they are about physical demands and work environment. Could we include them under a heading like "Requirements"? Possibly, but that might be misleading. However the instruction says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't restrict to only those headings; those are examples. So we can add other headings like Physical Demands and Work Environment as
as well, as long as they have real content. The instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not an exhaustive list. So we can add Physical Demands and Work Environment headings. Thus we will add:
Physical Demands
The physical demands described here are representative of those that must be met by an employee to successfully perform the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. Performance of the required duties will require physical ability to climb permanent and temporary stairs, passenger use of construction personnel hoists, ability to climb ladders, and negotiate work areas under construction. Specific vision abilities required by this job include close vision, peripheral vision, depth perception, and the ability to adjust focus. Performing this job requires the use of hands to finger, handle, or feel objects, tools or controls, sit, talk and hear, stand, climb, balance, stoop, kneel, crouch, or crawl. Employee may occasionally lift and/or move up to 50 pounds.
Work Environment
The work environment characteristics described here are representative of those employee encounters while performing the essential functions of this job. Reasonable accommodations may be made to enable individuals with disabilities to perform the essential functions. While performing the duties of this job, the employee regularly works on-site at the construction worksite where the employee is exposed to moving mechanical parts; high precarious places; fumes or airborne particles; outside weather conditions, and risk of electrical shock. The noise in these work environments is usually moderate to very loud. May perform other duties as assigned.
We should also include the metadata like Division, Location, Minimum Years Experience, Travel Involved, Job Type, Job Classification, Education, Job Family, Construction, Compensation: Salaried Exempt. This is minor metadata; we can fold into a shortmaybe after About the role or before Responsibilities. Let's add a short
after About the role: "Division: Omaha Main Project; Location: Omaha, NE 68154 USA; Minimum Years Experience: [not given? Actually it's blank]; Travel Involved: [blank]; Job Type: Regular; Job Classification: Experienced; Education: [blank]; Job Family: Construction; Compensation: Salaried Exempt." But we should not include placeholder like "not given" or blank. The posting shows those fields but no values after colon? Actually the text: "Division: Omaha Main Project Location(s): Omaha, NE 68154 USA Minimum Years Experience: Travel Involved: Job Type: Regular Job Classification: Experienced Education: Job Family: Construction Compensation: Salaried Exempt". So some fields have values, some are empty after colon. We should include only those with values. So we can include: Division: Omaha Main Project; Location(s): Omaha, NE 68154 USA; Job Type: Regular; Job Classification: Experienced; Job Family: Construction; Compensation: Salaried Exempt. Minimum Years Experience, Travel Involved, Education are empty; we drop them. Thus a short
after About the role: "
Division: Omaha Main Project; Location(s): Omaha, NE 68154 USA; Job Type: Regular;
- .
- Skills: Not explicitly separate; maybe we could treat some as Skills but we have Qualifications covering skills. The instruction says prefer few substantive sections over many thin ones. So we could combine Qualifications and Skills? But we have a Qualifications section already. Could also include Skills if there are distinct skill statements not covered. The Qualifications includes "Proven written and verbal communication abilities, proficiency with computer applications, including Microsoft Office Suite of programs. Must have advanced presentation skills." Those are skills. Could still be under Qualifications. We'll not create separate Skills unless there is explicit "Skills:" heading. There's none. So we skip Skills.
- Benefits, Pay, Schedule: Not present. So we omit those sections.
- Requirements: Could be same as Qualifications? The instruction says use headings like Requirements, Qualifications, Skills. We have Qualifications. Could also include Requirements if there are separate requirement statements like Minimum Years Experience etc. The posting includes metadata: Division, Location, Minimum Years Experience, Travel Involved, Job Type, etc. Those are minor metadata; we should fold into a short