Senior Integration Engineer - M&A
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should include only sections that have real content. The posting includes description about BKF and role: we can put that under "About the role". Then responsibilities list. Then requirements list. There's also "Physical Demands" and "Work Conditions" but those are not in allowed headings; we can maybe incorporate into a short paragraph under Requirements or maybe ignore? The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Also "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should drop the EEO paragraph and the unsolicited resumes note. Also drop "Physical Demands:" and "Work Conditions:"? Those are not boilerplate but they are details about the job; they could be included perhaps under a generic section? Not in allowed headings. Could we incorporate them into a short
under Requirements or About the role? Probably we can include them as a paragraph after Requirements, but we must not create a heading not listed. So we can just include them as a
after Requirements without a heading. Or we could fold them into Requirements as a paragraph. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we keep About the role, Responsibilities, Requirements, Benefits, Pay (since salary range given). Schedule? Not mentioned explicitly; there is "Flexible schedules" under Benefits. So we could include Schedule section if there is content: "Flexible schedules". That's a schedule detail. So we can create a Schedule section with that. Benefits section: we have list of benefits. Pay section: we have salary range. So we will include Pay and Benefits and Schedule. We must not include sections with filler like "commensurate with experience". We have actual content. We need to use
- for any list of duties/requirements/benefits. So responsibilities list, requirements list, benefits list.
We need to preserve all substantive information, not invent or summarize away detail.
Let's extract content.
About the role: The first paragraph(s) before "Responsibilities": "BKF is a multi-service infrastructure consulting firm providing civil engineering, construction management, environmental, planning, and surveying services across California, the Pacific Northwest, and beyond. With offices throughout California and the Portland area, BKF has served transportation, water resources, land development, government, and federal clients for over 110 years. At BKF, you'll find a unique opportunity to grow your career with intention. Our culture values professional autonomy, innovation, and meaningful collaboration across offices. We are proud to be recognized with the Great Place to Work certification for the second year in a row. The Senior M&A Technology Integration Engineer is the technical lead for integrating acquired companies into BKF's technology environment. Working with the Lead, M&A Technology Integration, this position owns the technical architecture, migration strategy, technical risk, and execution standards for each acquisition. This is a senior, hands-on individual-contributor role. The position provides technical direction to internal engineers, consultants, and vendors; coordinates with BKF technology teams; and participates directly in complex implementation and troubleshooting. The successful candidate will combine deep Microsoft cloud expertise with broad infrastructure knowledge, sound technical judgment, and the ability to lead multiple overlapping integrations. Travel to BKF and acquired-company locations may be required based on integration activities."
That's substantive.
Responsibilities: bullet list after "Responsibilities". Let's capture each bullet:
- Participate in technical discovery and due diligence, working with external partners as appropriate; interpret findings for BKF and continually refine due diligence requirements, questionnaires, and evaluation criteria
- Assess acquired-company technology licenses, subscriptions, and contracts; identify technical requirements, dependencies, and gaps; and partner with the M&A Integration Lead and BKF service owners to support contract harmonization and additional license purchases
- Develop integration architecture, migration plans, technical schedules, cutover plans, rollback procedures, and hypercare requirements
- Serve as the technical authority for Microsoft 365 tenant integrations, including Entra ID, Exchange Online, Teams, SharePoint Online, OneDrive, domains, licensing, identity, and coexistence
- Provide technical direction to internal and consulting Systems Engineers performing Microsoft tenant migrations and related integration work
- Coordinate SharePoint migrations and OneDrive-to-Box migrations
- Work with Box Consulting on file-system and Box migration design, sequencing, validation, and execution
- Partner with the Endpoint Deployment & Logistics team to align identity, applications, security, and data readiness with laptop deployment
- Coordinate technical dependencies with Cloud Operations, Service Operations, Security, Business Applications, Accounting, HR, GIS, CAD, vendors, and consultants
- Provide hands-on engineering, scripting, automation, troubleshooting, and cutover support when required
- Identify technical risks, resource constraints, and unrealistic timelines, and communicate them clearly to leadership
- Create and maintain integration standards, technical playbooks, scripts, checklists, documentation, and operational handoff procedures
- Ensure steady-state ownership is successfully transitioned to the appropriate BKF operational teams after integration and hyper care
That's all.
Requirements: after "Requirements". Bullets:
- Eight or more years of experience in systems engineering, cloud infrastructure, Microsoft 365, identity, or enterprise technology integration
- Significant hands-on experience with Microsoft 365 and Entra ID
- Experience designing or executing Microsoft 365 tenant-to-tenant migrations
- Strong knowledge of Exchange Online, Teams, SharePoint Online, OneDrive, identity, domains, licensing, and collaboration services
- Strong PowerShell, automation, troubleshooting, and technical documentation skills
- Experience providing technical direction to internal engineers, consultants, vendors, or technical project teams
- Ability to translate business objectives into realistic technical plans and communicate technical risk to nontechnical stakeholders
- Ability to support planned after-hours or weekend migrations
- Ability to travel to BKF and acquired-company locations when needed
- Ability to work effectively in a hybrid environment; San Francisco Bay Area location preferred
- Experience with mergers, acquisitions, or divestitures
- Experience with Intune, Windows Autopilot, Box, Box Shuttle, Azure, DNS, networking, and enterprise security controls
- Experience supporting multiple concurrent integration projects
- Relevant Microsoft, Azure, or security certifications
Also there is "Physical Demands: Must be able to regularly talk, hear and operate a computer, keyboard and mouse and occasionally lift, pull/push and carry up to 20 pounds with accommodations. Work Conditions: Exposure to constant or intermittent sounds at a low or moderate level consistent with an office setting. Exposure to high-stress, fast-paced, deadline-oriented environment. Travel to other BKF locations and client sites may be required."
We could incorporate these as a paragraph after Requirements, maybe under a short
without heading. Or we could add a section "Working Conditions" but not allowed headings. So we will just add a
after Requirements. Benefits: after "Benefits". The text: "The typical base salary range for this position is $100,000 - $145,000 annualized depending upon skills, experience, education, and geographical location. This is a salary position paid biweeklyCompetitive salaries, profit sharing, and 401kGenerous paid time off packages9 Paid HolidaysFlexible schedulesEducation reimbursement, Paid annual dues for professional and societal organizationsBKF offers competitive and award-winning benefits and perks. To learn more click here." We need to parse into list items. The text seems jammed: "Competitive salaries, profit sharing, and 401kGenerous paid time off packages9 Paid HolidaysFlexible schedulesEducation reimbursement, Paid annual dues for professional and societal organizations". We need to split into sensible items: - Competitive salaries, profit sharing, and 401k - Generous paid time off packages - 9 Paid Holidays - Flexible schedules - Education reimbursement - Paid annual dues for professional and societal organizations Also note "BKF offers competitive and award-winning benefits and perks. To learn more click here." That's boilerplate/link; we can drop the "To learn more click here." as it's application instruction? It's a link; we can drop. Pay: The salary range is also in Benefits paragraph; but we have a separate Pay section. The instruction says include Pay section only if posting actually states them. It does state salary range. So we will create a Pay section with that sentence: "The typical base salary range for this position is $100,000 - $145,000 annualized depending upon skills, experience, education, and geographical location. This is a salary position paid biweekly." Schedule: we have "Flexible schedules" mentioned under Benefits. Could also be a Schedule section: "Flexible schedules". We'll create a Schedule section with that. We must not repeat content; but Flexible schedules appears also in Benefits list. If we put it in both Benefits and Schedule, that's duplication. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's present in both places? But we should avoid unnecessary duplication. However the posting mentions Flexible schedules under Benefits; we could keep it only in Benefits and not create a separate Schedule section. But 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 does have content for schedule: "Flexible schedules". So we could make a Schedule section with that content. But then we would be duplicating the same sentence in Benefits list. Might be okay but could be considered duplication. Perhaps better to keep Flexible schedules only under Benefits and not create a Schedule section, because the schedule info is already captured there. However the instruction says "Prefer a few substantive sections over many thin ones." Having a Schedule section with just one item might be thin. So better to omit Schedule section and keep flexible schedules under Benefits. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. We need to ensure we don't include EEO boilerplate etc. Now produce HTML fragment:
About the role
... (the paragraph)
Responsibilities
- ... ...
Requirements
- ... ...
Physical Demands: Must be able to regularly talk, hear and operate a computer, keyboard and mouse and occasionally lift, pull/push and carry up to 20 pounds with accommodations. Work Conditions: Exposure to constant or intermittent sounds at a low or moderate level consistent with an office setting. Exposure to high-stress, fast-paced, deadline-oriented environment. Travel to other BKF locations and client sites may be required.
Benefits
- Competitive salaries, profit sharing, and 401k
- Generous paid time off packages
- 9 Paid Holidays
- Flexible schedules
- Education reimbursement
- Paid annual dues for professional and societal organizations
Pay
The typical base salary range for this position is $100,000 - $145,000 annualized depending upon skills, experience, education, and geographical location. This is a salary position paid biweekly.
We should also maybe include the sentence "BKF offers competitive and award-winning benefits and perks." but that's fluff; could be omitted as it's not specific detail. Might be considered boilerplate. Safer to omit