Senior BIM Specialist
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate, navigation, legal, EEO, duplicated lines, application instructions. Must preserve all substantive info.
We need to parse the posting.
Let's extract content.
The posting begins with a generic intro about Jacobs repeated twice. That's likely boilerplate? It's about company mission. Might be considered "About the role"? Actually it's generic company description. Could be considered "About the role" or "About Jacobs". The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have an "About the role" section summarizing the role description. The generic Jacobs mission may be considered boilerplate but it's repeated; maybe we can keep a concise version? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep the substantive info, but we can remove duplicated lines. The repeated intro appears twice; we should keep one copy? It's duplicated lines. So we should keep one instance of the Jacobs mission description? It's generic but maybe considered substantive? It's about the company's mission; not specific to role. Might be considered boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The Jacobs mission is not exactly those categories, but it's generic fluff. However it's repeated; we could keep one instance as part of "About the role" maybe.
Then there is "Your impact Drive Excellence in Advanced Designs - Electronics At Jacobs, we don’t settle..." That's more role-specific.
Then "Why Join Us?" bullet list.
Then "Hybrid Flexibility" paragraph.
Then "What You’ll Do" list.
Then "What We’re Looking For" list.
Then "Ready to lead..." that's call to action.
Then "Bring your curiosity..." that's more fluff.
Then "Here's what you'll need" list of requirements.
Then "Ideally, you’ll also have" list.
Then benefits paragraph.
Then salary range paragraph.
Then EEO statement (remove).
Then job posted date etc (maybe minor metadata, can be folded into short p or drop). We can include a short p for metadata like "Posted September 15, 2026." but instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a short p for posting date. Then hybrid working policy paragraph (maybe part of Hybrid Flexibility). Already have hybrid flexibility earlier. Then application experience paragraph (maybe application instructions, remove). Then reasonable adjustments paragraph (maybe application instructions, remove). Thus we need to produce sections: - About the role (maybe combine Jacobs mission + impact statement). Could be one
About the role
with paragraphs. - Responsibilities (Responsibilities
) with- from "What You’ll Do".
- Requirements / Qualifications? The posting has "What We’re Looking For" and "Here's what you'll need" and "Ideally, you’ll also have". Could combine into Requirements and Qualifications. But we need to decide headings: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Requirements, Qualifications, Skills, Benefits, Pay. Possibly also Schedule if present (not really). Hybrid flexibility maybe not schedule but could be considered Schedule? Not exactly. The posting mentions hybrid flexibility but not specific schedule. So we may not include Schedule. We need to avoid thin sections. So we should combine similar content into fewer sections. We have: - About the role: company mission + impact statement. - Responsibilities: What You’ll Do list. - Requirements: maybe combine "What We’re Looking For" (proven experience, expertise, leadership) and "Here's what you'll need" (education, years experience, proficiency) and "Ideally, you’ll also have" (NEC, associate degree, semiconductor experience). Could be one Requirements section. - Skills: maybe we could extract skills like AutoCAD, Revit MEP, BIM workflows, leadership, mentoring, process improvements, NEC knowledge, etc. But we already have them in Requirements. Could create a Skills section separate. But we need to avoid thin sections; maybe combine into Requirements. - Benefits: paragraph about health and welfare benefits. - Pay: salary range paragraph. - Schedule: not present. Thus we will output:
About the role
At Jacobs, we're challenging today to reinvent tomorrow by solving the world's most critical problems for thriving cities, resilient environments, mission-critical outcomes, operational advancement, scientific discovery and cutting-edge manufacturing, turning abstract ideas into realities that transform the world for good. Your impact Drive Excellence in Advanced Designs - Electronics At Jacobs, we don’t settle -- we are always looking beyond raising the bar and delivering with excellence. We apply our expertise and knowledge as we look into the future with optimism and focus. We don’t settle until we give our best and know that we’re making a difference. Are you ready to lead the future of electrical design? We’re looking for a Senior BIM Specialist to join our team where you’ll set the standard for innovation and quality in advanced facilities. From semiconductor manufacturing to state-of-the-art industrial projects, you’ll play a pivotal role in shaping world-class designs for global clients.
But we need to avoid duplication: The first sentence appears twice; we should keep only one. Also the "Your impact Drive Excellence..." seems to be continuation. We'll combine. Better to write:At Jacobs, we're challenging today to reinvent tomorrow by solving the world's most critical problems for thriving cities, resilient environments, mission-critical outcomes, operational advancement, scientific discovery and cutting-edge manufacturing, turning abstract ideas into realities that transform the world for good. Your impact: Drive Excellence in Advanced Designs - Electronics. At Jacobs, we don’t settle -- we are always looking beyond raising the bar and delivering with excellence. We apply our expertise and knowledge as we look into the future with optimism and focus. We don’t settle until we give our best and know that we’re making a difference. Are you ready to lead the future of electrical design? We’re looking for a Senior BIM Specialist to join our team where you’ll set the standard for innovation and quality in advanced facilities. From semiconductor manufacturing to state-of-the-art industrial projects, you’ll play a pivotal role in shaping world-class designs for global clients.
That seems fine. Next Responsibilities:Responsibilities
- Establish and maintain BIM standards, configure project environments, and ensure seamless coordination.
- Oversee model integrity, conduct clash detection, and implement quality control processes for accurate, high-performing designs.
- Mentor and train designers, fostering a culture of technical excellence and innovation.
- Work autonomously to solve complex challenges, propose process enhancements, and guide your team in delivering world-class deliverables.
Requirements
with a- list.
We need to avoid duplication: "Proficiency in AutoCAD" appears also in Expertise in AutoCAD; but we can keep both but maybe combine? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep both statements even if similar. However we could combine them into one bullet that captures both? That would be summarizing away detail (maybe losing nuance). Safer to keep both as separate bullets, even if redundant.
But we need to avoid duplicated lines: The posting may have duplicated lines elsewhere; we already removed duplicate intro. The AutoCAD proficiency appears twice; that's not a duplicated line in the posting? It's mentioned in both "What We’re Looking For" and "Here's what you'll need". That's not a duplicate line exactly but similar content. The instruction says remove duplicated lines. It's not identical line; it's similar but not identical. I'd keep both.
We'll list bullets:
- Proven experience in BIM leadership and electrical design for advanced facilities.
- Expertise in AutoCAD, Revit MEP, and BIM workflows.
- Strong leadership skills with a passion for mentoring and driving process improvements.
- High school graduate or equivalent.
- At least 7 years of relevant experience in design utilizing 3D modeling / drafting.
- At least 3 years of design experience with Revit and Navisworks.
- Proficiency in AutoCAD.
- Visa Sponsorship is not available for this role.
- Knowledge and application of NEC and electrical design requirements.
- Two-year associate’s degree in relevant field.
- At least 2 years of semiconductor experience.
That seems comprehensive.
Next Benefits:
Benefits
Our health and welfare benefits are designed to invest in you, and in the things you care about. Your health. Your well-being. Your security. Your future. Employees have access to medical, dental, vision and basic life insurance, 401(k) plan, paid time off (allocated plans start date 17 days per calendar year), seven paid holidays, and caregiver leave and the ability to purchase company stock at a discount as well as legally mandated benefits.
Next Pay:Pay
The base salary range for this position is $71,000.00 to $97,600.00; though will be paid hourly based on hours worked. Within the range, individual pay is determined by work location and additional factors, including job-related skills, experience, and relevant education or training.
Schedule: Not present, so omit. We might also include a short p for metadata like posting date. Could add after Pay maybe. But instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a shortor drop it." So we can add a short p: "Posted September 15, 2026." Not a heading. We should not include application instructions etc. Thus final HTML fragment:
About the role
...
Responsibilities
- ...
Requirements
- ...
Benefits
...
Pay
...
Posted September 15, 2026.
Make sure no extra whitespace? It's fine. Check for any leftover boilerplate: We removed EEO, legal, application instructions, etc. Check for any duplicated lines: We kept only one intro. Check for any placeholder text like