Project Manager (Design Build)
for each heading. Use - for lists. Use
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info. Include sections only when posting has real specific content.
Let's parse the posting.
Content:
- "Want to learn more about this role and Jobot? Click our Jobot logo and follow our LinkedIn page!" (boilerplate, remove)
- "Job details: Top End Compensation Plan, Ownership Potential, Flexible Work Arrangements"
- "This Jobot Job is hosted by: Ross Theel"
- "Are you a fit? Easy Apply now by clicking the "Easy Apply" button and sending us your resume." (application instruction, remove)
- "Salary: $100,000 - $125,000 per year"
- "A bit about us: We are an established general contractor in the Minneapolis area that has been building for nearly 50 years. We pride ourselves on our commitment to valuing the relationships we mold with our clients and customers. We have built a wide range of projects throughout our history, but our main focus has been on commercial, education, healthcare, and industrial construction. We are looking to add a Project Manager to our growing team. If you are a project management professional with previous GC experience and would like to learn more, please apply!"
- "Why join us? We offer: Competitive Compensation Package Complete Benefits Package (medical, dental, vision) 401k Retirement Plan w/ Match Maternity/Paternity Leave 15 PTO Days + Company Paid Holidays Flexible Work Schedule Accelerated Career Growth Fun Company Activities and Events"
- "Job Details Responsibilities: As a Commercial Project Manager, your duties will include but are not limited to: 1. Overseeing and directing construction projects from conception to completion, ensuring that they are competed on time and within budget. 2. Reviewing the project in-depth to schedule deliverables and estimate costs. 3. Coordinating and directing construction workers and subcontractors, ensuring they understand expectations and work efficiently. 4. Selecting tools, materials and equipment and tracking inventory, while ensuring the procurement processes are efficient and cost-effective. 5. Reviewing the work progress on a daily basis and conducting regular site inspections. 6. Preparing internal and external reports pertaining to job status, and presenting them to stakeholders. 7. Negotiating terms of agreements, draft contracts and obtain permits and licenses. 8. Ensuring quality construction standards and the use of proper construction techniques. 9. Analyzing, managing, and mitigating risks, and implementing quality control programs. 10. Leading and managing the project team, fostering a positive work environment that encourages collaboration and optimizes team performance."
- "Qualifications: The successful candidate should possess: 1. A Bachelor's degree in Construction Management, Civil Engineering, or a related field. 2. A minimum of 3 years' experience in construction project management. 3. Proven ability to lead a team and manage projects with a strong understanding of the construction industry. 4. Extensive knowledge of construction procedures, material, and project management principles. 5. Exceptional knowledge of construction cost control and basic accounting principles. 6. Excellent knowledge of construction contract negotiations and procurement processes. 7. Strong leadership and team management skills, with an ability to motivate and direct a team to achieve project goals. 8. Excellent time management skills, with a proven ability to meet deadlines. 9. Exceptional communication and negotiation skills. 10. Proficiency in construction management software packages."
- "This role is a fantastic opportunity for a Project Manager to take their career to the next level. If you're a proactive, enthusiastic, and dedicated professional looking to make a significant impact on our company, we'd love to hear from you."
- "Interested in hearing more? Easy Apply now by clicking the "Easy Apply" button." (application instruction, remove)
- Then EEO boilerplate etc, remove.
We need sections: About the role (maybe "A bit about us" and role description?), Responsibilities, Qualifications (maybe combine qualifications and requirements?), Skills (maybe from qualifications?), Benefits, Pay, Schedule.
We must not create sections with placeholder/filler. Must include only if real content.
Let's identify content for each:
- About the role: Could be the "A bit about us" paragraph describing company and role. Also maybe the "Why join us?" but that's benefits. The "A bit about us" is substantive. Also maybe the "This role is a fantastic opportunity..." but that's fluff but still substantive? It's not placeholder. Could include in About the role.
- Responsibilities: The list enumerated 1-10.
- Qualifications: The list enumerated 1-10.
- Skills: Could be extracted from qualifications (leadership, communication, etc.) but we already have qualifications list; maybe we can treat qualifications as skills? The instruction says use sections for Skills if posting has real specific content. The qualifications list includes skills; but we could still have a Skills section summarizing? However we must not invent or summarize away detail. Better to keep qualifications as is; maybe we can have a Skills section that lists specific skills like "Proficiency in construction management software packages", "Strong leadership and team management skills", etc. But that would be duplicating qualifications. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can have both Qualifications and Skills sections if content exists. The posting has qualifications list; we could split into Requirements (maybe education/experience) and Skills (abilities). But we must not invent content; we can parse the qualifications list into two categories: education/experience (items 1-2) and skills (items 3-10). However that would be summarizing? It's still using the same content, just grouping. Might be acceptable as not inventing. But we need to be careful not to lose any detail. Could create Requirements section for items 1-2 (education, experience) and Skills section for items 3-10. That would preserve all info.
Alternatively, we could just have Qualifications section containing the whole list, and omit Skills. That's simpler and still meets instruction: we only include sections when posting has real specific content. We have qualifications content, so we can include Qualifications. Skills section would be empty if we don't have distinct skills beyond qualifications; but we could still include Skills if we want, but we must not create a heading followed by filler/placeholder text. If we put Skills heading but no content, that's not allowed. So we should omit Skills if we don't have distinct content.
Similarly, Requirements: we could treat education/experience as Requirements. But we already have Qualifications; maybe we can combine. The instruction says we can use Requirements heading if posting has real specific content for it. The posting does have requirements (education, experience). So we could have Requirements section with those two items. Then Qualifications could be the rest? But the posting lumps them together as "Qualifications". Safer to follow the posting: have a Qualifications section with the whole list. Not create Requirements unless we have distinct content separate from qualifications. Since the posting does not separate, we can just have Qualifications.
Benefits: The "Why join us? We offer:" list includes Competitive Compensation Package, Complete Benefits Package (medical, dental, vision), 401k Retirement Plan w/ Match, Maternity/Paternity Leave, 15 PTO Days + Company Paid Holidays, Flexible Work Schedule, Accelerated Career Growth, Fun Company Activities and Events. Also earlier "Job details: Top End Compensation Plan, Ownership Potential, Flexible Work Arrangements". So we have benefits content.
Pay: Salary: $100,000 - $125,000 per year. Also "Top End Compensation Plan" maybe part of benefits but we can put Pay section with salary range.
Schedule: "Flexible Work Arrangements" and "Flexible Work Schedule" mentioned. So we have schedule content: flexible work schedule/arrangements.
Thus we can include sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We must not include Skills if no distinct content.
Now we need to format.
Use for each heading.
For lists: use - .
For prose:
.
We need to preserve all substantive information. Let's extract.
About the role: Combine "A bit about us:" paragraph and maybe the "This role is a fantastic opportunity..." sentence. Also maybe the "We are looking to add a Project Manager to our growing team." That's part of the paragraph. Let's include:
Paragraph: "We are an established general contractor in the Minneapolis area that has been building for nearly 50 years. We pride ourselves on our commitment to valuing the relationships we mold with our clients and customers. We have built a wide range of projects throughout our history, but our main focus has been on commercial, education, healthcare, and industrial construction. We are looking to add a Project Manager to our growing team. If you are a project management professional with previous GC experience and would like to learn more, please apply!"
Then maybe add: "This role is a fantastic opportunity for a Project Manager to take their career to the next level. If you're a proactive, enthusiastic, and dedicated professional looking to make a significant impact on our company, we'd love to hear from you."
We should not include application instruction like "please apply" but that's part of the prose; it's okay.
Now Responsibilities: list the 10 items as
- .
Qualifications: list the 10 items as
- .
Benefits: list items from "Why join us? We offer:" plus maybe "Top End Compensation Plan, Ownership Potential, Flexible Work Arrangements". But Flexible Work Arrangements also goes to Schedule; we can mention in Benefits but also Schedule. To avoid duplication, we can keep Flexible Work Arrangements in Benefits? But schedule section will cover it. Might duplicate but okay as long as we preserve info. However we should avoid duplication? The instruction says preserve ALL substantive information; duplication is okay as long as we don't lose info. But we might want to avoid repeating same phrase in two sections; but it's not prohibited. However better to keep each piece in appropriate section: Benefits: Competitive Compensation Package, Complete Benefits Package (medical, dental, vision), 401k Retirement Plan w/ Match, Maternity/Paternity Leave, 15 PTO Days + Company Paid Holidays, Accelerated Career Growth, Fun Company Activities and Events. Also maybe Top End Compensation Plan and Ownership Potential could be part of Benefits (compensation). We'll include them.
Schedule: Flexible Work Arrangements, Flexible Work Schedule.
Pay: Salary range: $100,000 - $125,000 per year. Also Top End Compensation Plan maybe but we already used.
Now we need to ensure we don't include boilerplate like Easy Apply, Jobot logo, EEO, etc.
Let's craft HTML.
We'll start with
About the role
then ...
.
Then Responsibilities
- ...
...
.
Then Qualifications
...
.
Then Benefits
...
.
Then Pay
Salary: $100,000 - $125,000 per year.
Then Schedule
Flexible work arrangements/schedule.
Maybe we can phrase as Flexible work arrangements
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate, navigation, EEO, etc. Preserve all substantive info. Include sections only when posting has real specific content. Let's parse the posting. Content: - "Want to learn more about this role and Jobot? Click our Jobot logo and follow our LinkedIn page!" (boilerplate, remove) - "Job details: Top End Compensation Plan, Ownership Potential, Flexible Work Arrangements" - "This Jobot Job is hosted by: Ross Theel" - "Are you a fit? Easy Apply now by clicking the "Easy Apply" button and sending us your resume." (application instruction, remove) - "Salary: $100,000 - $125,000 per year" - "A bit about us: We are an established general contractor in the Minneapolis area that has been building for nearly 50 years. We pride ourselves on our commitment to valuing the relationships we mold with our clients and customers. We have built a wide range of projects throughout our history, but our main focus has been on commercial, education, healthcare, and industrial construction. We are looking to add a Project Manager to our growing team. If you are a project management professional with previous GC experience and would like to learn more, please apply!" - "Why join us? We offer: Competitive Compensation Package Complete Benefits Package (medical, dental, vision) 401k Retirement Plan w/ Match Maternity/Paternity Leave 15 PTO Days + Company Paid Holidays Flexible Work Schedule Accelerated Career Growth Fun Company Activities and Events" - "Job Details Responsibilities: As a Commercial Project Manager, your duties will include but are not limited to: 1. Overseeing and directing construction projects from conception to completion, ensuring that they are competed on time and within budget. 2. Reviewing the project in-depth to schedule deliverables and estimate costs. 3. Coordinating and directing construction workers and subcontractors, ensuring they understand expectations and work efficiently. 4. Selecting tools, materials and equipment and tracking inventory, while ensuring the procurement processes are efficient and cost-effective. 5. Reviewing the work progress on a daily basis and conducting regular site inspections. 6. Preparing internal and external reports pertaining to job status, and presenting them to stakeholders. 7. Negotiating terms of agreements, draft contracts and obtain permits and licenses. 8. Ensuring quality construction standards and the use of proper construction techniques. 9. Analyzing, managing, and mitigating risks, and implementing quality control programs. 10. Leading and managing the project team, fostering a positive work environment that encourages collaboration and optimizes team performance." - "Qualifications: The successful candidate should possess: 1. A Bachelor's degree in Construction Management, Civil Engineering, or a related field. 2. A minimum of 3 years' experience in construction project management. 3. Proven ability to lead a team and manage projects with a strong understanding of the construction industry. 4. Extensive knowledge of construction procedures, material, and project management principles. 5. Exceptional knowledge of construction cost control and basic accounting principles. 6. Excellent knowledge of construction contract negotiations and procurement processes. 7. Strong leadership and team management skills, with an ability to motivate and direct a team to achieve project goals. 8. Excellent time management skills, with a proven ability to meet deadlines. 9. Exceptional communication and negotiation skills. 10. Proficiency in construction management software packages." - "This role is a fantastic opportunity for a Project Manager to take their career to the next level. If you're a proactive, enthusiastic, and dedicated professional looking to make a significant impact on our company, we'd love to hear from you." - "Interested in hearing more? Easy Apply now by clicking the "Easy Apply" button." (application instruction, remove) - Then EEO boilerplate etc, remove. We need sections: About the role (maybe "A bit about us" and role description?), Responsibilities, Qualifications (maybe combine qualifications and requirements?), Skills (maybe from qualifications?), Benefits, Pay, Schedule. We must not create sections with placeholder/filler. Must include only if real content. Let's identify content for each: - About the role: Could be the "A bit about us" paragraph describing company and role. Also maybe the "Why join us?" but that's benefits. The "A bit about us" is substantive. Also maybe the "This role is a fantastic opportunity..." but that's fluff but still substantive? It's not placeholder. Could include in About the role. - Responsibilities: The list enumerated 1-10. - Qualifications: The list enumerated 1-10. - Skills: Could be extracted from qualifications (leadership, communication, etc.) but we already have qualifications list; maybe we can treat qualifications as skills? The instruction says use sections for Skills if posting has real specific content. The qualifications list includes skills; but we could still have a Skills section summarizing? However we must not invent or summarize away detail. Better to keep qualifications as is; maybe we can have a Skills section that lists specific skills like "Proficiency in construction management software packages", "Strong leadership and team management skills", etc. But that would be duplicating qualifications. The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we can have both Qualifications and Skills sections if content exists. The posting has qualifications list; we could split into Requirements (maybe education/experience) and Skills (abilities). But we must not invent content; we can parse the qualifications list into two categories: education/experience (items 1-2) and skills (items 3-10). However that would be summarizing? It's still using the same content, just grouping. Might be acceptable as not inventing. But we need to be careful not to lose any detail. Could create Requirements section for items 1-2 (education, experience) and Skills section for items 3-10. That would preserve all info.
Alternatively, we could just have Qualifications section containing the whole list, and omit Skills. That's simpler and still meets instruction: we only include sections when posting has real specific content. We have qualifications content, so we can include Qualifications. Skills section would be empty if we don't have distinct skills beyond qualifications; but we could still include Skills if we want, but we must not create a heading followed by filler/placeholder text. If we put Skills heading but no content, that's not allowed. So we should omit Skills if we don't have distinct content.
Similarly, Requirements: we could treat education/experience as Requirements. But we already have Qualifications; maybe we can combine. The instruction says we can use Requirements heading if posting has real specific content for it. The posting does have requirements (education, experience). So we could have Requirements section with those two items. Then Qualifications could be the rest? But the posting lumps them together as "Qualifications". Safer to follow the posting: have a Qualifications section with the whole list. Not create Requirements unless we have distinct content separate from qualifications. Since the posting does not separate, we can just have Qualifications.
Benefits: The "Why join us? We offer:" list includes Competitive Compensation Package, Complete Benefits Package (medical, dental, vision), 401k Retirement Plan w/ Match, Maternity/Paternity Leave, 15 PTO Days + Company Paid Holidays, Flexible Work Schedule, Accelerated Career Growth, Fun Company Activities and Events. Also earlier "Job details: Top End Compensation Plan, Ownership Potential, Flexible Work Arrangements". So we have benefits content.
Pay: Salary: $100,000 - $125,000 per year. Also "Top End Compensation Plan" maybe part of benefits but we can put Pay section with salary range.
Schedule: "Flexible Work Arrangements" and "Flexible Work Schedule" mentioned. So we have schedule content: flexible work schedule/arrangements.
Thus we can include sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule.
We must not include Skills if no distinct content.
Now we need to format.
Use for each heading.
For lists: use - .
For prose:
.
We need to preserve all substantive information. Let's extract.
About the role: Combine "A bit about us:" paragraph and maybe the "This role is a fantastic opportunity..." sentence. Also maybe the "We are looking to add a Project Manager to our growing team." That's part of the paragraph. Let's include:
Paragraph: "We are an established general contractor in the Minneapolis area that has been building for nearly 50 years. We pride ourselves on our commitment to valuing the relationships we mold with our clients and customers. We have built a wide range of projects throughout our history, but our main focus has been on commercial, education, healthcare, and industrial construction. We are looking to add a Project Manager to our growing team. If you are a project management professional with previous GC experience and would like to learn more, please apply!"
Then maybe add: "This role is a fantastic opportunity for a Project Manager to take their career to the next level. If you're a proactive, enthusiastic, and dedicated professional looking to make a significant impact on our company, we'd love to hear from you."
We should not include application instruction like "please apply" but that's part of the prose; it's okay.
Now Responsibilities: list the 10 items as
- .
Qualifications: list the 10 items as
- .
Benefits: list items from "Why join us? We offer:" plus maybe "Top End Compensation Plan, Ownership Potential, Flexible Work Arrangements". But Flexible Work Arrangements also goes to Schedule; we can mention in Benefits but also Schedule. To avoid duplication, we can keep Flexible Work Arrangements in Benefits? But schedule section will cover it. Might duplicate but okay as long as we preserve info. However we should avoid duplication? The instruction says preserve ALL substantive information; duplication is okay as long as we don't lose info. But we might want to avoid repeating same phrase in two sections; but it's not prohibited. However better to keep each piece in appropriate section: Benefits: Competitive Compensation Package, Complete Benefits Package (medical, dental, vision), 401k Retirement Plan w/ Match, Maternity/Paternity Leave, 15 PTO Days + Company Paid Holidays, Accelerated Career Growth, Fun Company Activities and Events. Also maybe Top End Compensation Plan and Ownership Potential could be part of Benefits (compensation). We'll include them.
Schedule: Flexible Work Arrangements, Flexible Work Schedule.
Pay: Salary range: $100,000 - $125,000 per year. Also Top End Compensation Plan maybe but we already used.
Now we need to ensure we don't include boilerplate like Easy Apply, Jobot logo, EEO, etc.
Let's craft HTML.
We'll start with
About the role
then ...
.
Then Responsibilities
- ...
...
.
Then Qualifications
...
.
Then Benefits
...
.
Then Pay
Salary: $100,000 - $125,000 per year.
Then Schedule
Flexible work arrangements/schedule.
Maybe we can phrase as Flexible work arrangements
- .
For prose:
. We need to preserve all substantive information. Let's extract. About the role: Combine "A bit about us:" paragraph and maybe the "This role is a fantastic opportunity..." sentence. Also maybe the "We are looking to add a Project Manager to our growing team." That's part of the paragraph. Let's include: Paragraph: "We are an established general contractor in the Minneapolis area that has been building for nearly 50 years. We pride ourselves on our commitment to valuing the relationships we mold with our clients and customers. We have built a wide range of projects throughout our history, but our main focus has been on commercial, education, healthcare, and industrial construction. We are looking to add a Project Manager to our growing team. If you are a project management professional with previous GC experience and would like to learn more, please apply!" Then maybe add: "This role is a fantastic opportunity for a Project Manager to take their career to the next level. If you're a proactive, enthusiastic, and dedicated professional looking to make a significant impact on our company, we'd love to hear from you." We should not include application instruction like "please apply" but that's part of the prose; it's okay. Now Responsibilities: list the 10 items as
- . Qualifications: list the 10 items as
- .
Benefits: list items from "Why join us? We offer:" plus maybe "Top End Compensation Plan, Ownership Potential, Flexible Work Arrangements". But Flexible Work Arrangements also goes to Schedule; we can mention in Benefits but also Schedule. To avoid duplication, we can keep Flexible Work Arrangements in Benefits? But schedule section will cover it. Might duplicate but okay as long as we preserve info. However we should avoid duplication? The instruction says preserve ALL substantive information; duplication is okay as long as we don't lose info. But we might want to avoid repeating same phrase in two sections; but it's not prohibited. However better to keep each piece in appropriate section: Benefits: Competitive Compensation Package, Complete Benefits Package (medical, dental, vision), 401k Retirement Plan w/ Match, Maternity/Paternity Leave, 15 PTO Days + Company Paid Holidays, Accelerated Career Growth, Fun Company Activities and Events. Also maybe Top End Compensation Plan and Ownership Potential could be part of Benefits (compensation). We'll include them.
Schedule: Flexible Work Arrangements, Flexible Work Schedule.
Pay: Salary range: $100,000 - $125,000 per year. Also Top End Compensation Plan maybe but we already used.
Now we need to ensure we don't include boilerplate like Easy Apply, Jobot logo, EEO, etc.
Let's craft HTML.
We'll start with
About the role
then...
. ThenResponsibilities
- ... ...
Qualifications
- ...
Benefits
- ...
Pay
Salary: $100,000 - $125,000 per year.
ThenSchedule
Flexible work arrangements/schedule.
Maybe we can phrase asFlexible work arrangements