Integration Lead: Microsoft Azure Fabric
About the role
with. - Responsibilities: list of duties: lead technical discovery workshops, assess existing integration architectures, recommend future-state solutions, develop integration designs, oversee development, troubleshoot complex integration issues, provide technical leadership throughout implementation. Also many bullet points under "Required Skills" etc. But we need to separate responsibilities vs requirements vs qualifications vs skills. The posting lumps many items under "Required Skills" and "Desired Skills". We need to extract responsibilities: The role responsibilities described earlier: lead design, development, delivery; work with stakeholders; define integration requirements; develop scalable patterns; lead technical discovery workshops; assess existing integration architectures; recommend future-state solutions; develop integration designs; oversee development; troubleshoot complex integration issues; provide technical leadership throughout implementation. Also: lead integration architecture and delivery using Microsoft Fabric and Azure integration technologies; facilitate client workshops; translate functional and business requirements into detailed technical integration designs; design integration patterns for batch, near-real-time, event-driven, API-based, and file-based integrations; design and develop solutions using technologies list; lead integrations between Advancement platforms and enterprise systems; define canonical data structures, transformation rules, mappings, interface specifications, and data contracts; develop reusable integration frameworks, templates, logging standards, error-handling patterns, monitoring approaches, and deployment processes; troubleshoot complex data and integration issues across multiple source and target platforms; lead technical design reviews and provide guidance to integration developers and data engineers; establish appropriate Dev/Test/QA/Production deployment and release-management practices; support data reconciliation, validation, exception management, and operational monitoring; partner with Data Migration, Data Governance, CRM, Analytics, and functional teams; identify technical risks, integration dependencies, performance concerns, and opportunities to simplify the institution's integration landscape; develop future-state integration roadmaps and recommend modernization opportunities; provide technical estimates and support project planning, solutioning, and pre-sales activities when required; mentor technical consultants and developers and establish delivery standards and leading practices. That's a lot; we can list as
- items.
- Requirements: likely "Years of Experience" and "Certifications" and "Additional Requirements". Also "Higher Education / Advancement Experience" maybe part of qualifications. We'll need to decide sections: Requirements, Qualifications, Skills. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what goes where.
We have:
- About the role: description.
- Responsibilities: duties.
- Requirements: maybe years of experience, certifications, additional requirements (flexibility to travel, ability to build trusted advisor relationships, support sales and business development). Also "Higher Education / Advancement Experience" could be qualifications.
- Qualifications: maybe education? Not explicitly given. Could be "Higher Education / Advancement Experience" as qualification.
- Skills: required skills list (technical) and desired skills.
- Benefits: The posting mentions "industry-leading benefits packages", "flexible work environment", "culture of inclusion". Also "Attain Partners is committed to fair and equitable compensation practices." Also "Attain Partners is an Equal Opportunity/Affirmative Action employer." But we must not include EEO boilerplate. Benefits: "industry-leading benefits packages", "flexible work environment", "culture of inclusion". Also maybe "empower career growth". Those are substantive. So we can include Benefits section.
- Pay: The posting includes "Hourly Rate: $100 USD - $120 USD". Also "The individual hourly rate for this position is unique to each candidate and will be commensurate with experience, education, and skills." Also "Interested in this position but the compensation isn’t quite right? Let us know your expectations, and we’ll see if we can make it happen based on your qualifications." The phrase "commensurate with experience" is placeholder? It says "will be commensurate with experience, education, and skills." That's not a specific number but they gave a range. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we cannot include a Pay section if the content is just "commensurate with experience". However they also gave a specific range: $100 - $120 USD. That is substantive. So we can include Pay section with that range. Also we might include note about flexibility to negotiate? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we can include the range and maybe the statement that it's unique to each candidate and will be commensurate with experience, education, and skills. That's not filler; it's additional info. So we can include both.
- Schedule: Not mentioned explicitly. There's "flexible work environment". That could be schedule? But schedule usually refers to full-time/part-time, remote/hybrid. Not given. Could be omitted. The instruction: never create Schedule section unless posting actually states them. It doesn't state schedule explicitly. So we omit Schedule.
Now we need to ensure we don't repeat job title as heading. We'll not.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we must cut out the EEO paragraph, the accommodation request, etc.
Also we need to cut out duplicated lines: maybe some repeated sentences.
Now produce HTML fragment.
Structure:
About the role
... description ...
Responsibilities
- ... ...
Requirements
- 7+ years of professional experience in data integration, application integration, data engineering, or enterprise technology consulting.
- 4+ years of experience working with Microsoft Azure data and integration technologies.
- 2+ years of hands-on experience with Microsoft Fabric strongly preferred.
- 3+ years of experience leading technical teams, integration workstreams, or enterprise integration projects.
- Prior experience delivering projects within Higher Education is strongly preferred.
- Microsoft Certified: Fabric Data Engineer Associate
- Microsoft Certified: Azure Data Engineer Associate
- Microsoft Certified: Azure Solutions Architect Expert
- Microsoft Certified: Azure Developer Associate
- Microsoft Certified: Power BI Data Analyst Associate
- Microsoft Applied Skills credentials related to Microsoft Fabric, Azure integration, or data engineering
- Demonstrated ability to build trusted advisor relationships with clients
- Experience supporting sales and business development
- Position requires flexibility to travel periodically based on business and client needs
Requirements
- (years of experience, certifications, additional requirements)
Qualifications
- (Higher Education / Advancement Experience, understanding of Advancement concepts, understanding of how Advancement systems interact with institutional platforms)
maybe also "Experience working within Higher Education, preferably supporting Advancement, fundraising, alumni relations, or constituent engagement." etc.
- . We could separate required and desired as separate
- with a preceding
indicating "Required Skills:" and "Desired Skills:" but that might be considered adding extra text not from original? It's okay to include prose. We'll include a
before each list. Now Benefits: include industry-leading benefits packages, flexible work environment, culture of inclusion, empower career growth. Also maybe "Attain Partners is committed to fair and equitable compensation practices." That's more about compensation; but we already have Pay. Could include as part of Benefits? Might be okay. Pay: include hourly rate range and note about commensurate. Now we must ensure we don't include any boilerplate like EEO, legal, accommodation request, etc. Let's extract the exact substantive paragraphs. Original text: "Attain Partners is an innovative consulting firm dedicated to disrupting the status quo to change the world and improve the lives of those we touch. From strategy to technology and everywhere in between, our experts use their unique skills to advance the important missions of education, nonprofit, healthcare, and state and local government clients. People are at the center of all we do, and that’s why we empower career growth, provide industry-leading benefits packages, encourage a flexible work environment, and foster a culture of inclusion to support the needs of our team. We share a collective passion for our mission and our people. Guided by our seven core values, The Attain Way, our vision is the foundation of our culture—to be and attain the best." That's about company; we can put under About the role? Actually About the role should focus on role, but we can include company overview as part of About the role. It's substantive. Then role description: "The Integration Lead – Microsoft Fabric / Azure is responsible for leading the design, development, and delivery of enterprise data integration solutions for Higher Education institutions, with a particular focus on Advancement, fundraising, alumni relations, constituent engagement, and institutional data ecosystems. This role combines solution architecture, technical leadership, hands-on development, and client-facing consulting. The Integration Lead will work directly with institutional stakeholders, functional teams, architects, data engineers, and application teams to define integration requirements and develop scalable, secure, and maintainable integration patterns leveraging Microsoft Fabric and the broader Microsoft Azure data platform. The ideal candidate understands that Advancement technology environments frequently span CRM, ERP, SIS, finance, HR, data warehouse, marketing, fundraising, and third-party platforms. This individual will help institutions modernize those ecosystems while establishing reusable integration patterns and reducing reliance on point-to-point interfaces and legacy batch processes. The Integration Lead will be expected to lead technical discovery workshops, assess existing integration architectures, recommend future-state solutions, develop integration designs, oversee development, troubleshoot complex integration issues, and provide technical leadership throughout implementation." We can combine that into About the role paragraph(s). Might be two paragraphs: company overview and role description. Now Responsibilities: we can extract the bullet list of duties from after "The Integration Lead will be expected to..." plus the earlier list of tasks like "lead integration architecture and delivery using Microsoft Fabric and Azure integration technologies." etc. Actually many of those are under "Required Skills". But we can treat responsibilities as the actions the role will perform.
Skills
- (Required Skills list and Desired Skills list)