Software Engineering Manager - Heritage Integrations
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
We need to parse the posting and extract sections.
The posting includes:
- Position Purpose (intro paragraph)
- Key Responsibilities (multiple bullet-like paragraphs)
- Minimum Qualifications (list)
- Preferred Qualifications (list)
- Core Competencies (list)
- Why This Role Matters (paragraph)
- Job Location (address)
- Benefits paragraph: "Competitive weekly/bi-weekly pay, discretionary bonuses, 401(k) with company match, Employee Stock Purchase Plan, paid time off (vacation, sick, volunteer, holidays, birthday, floating), medical/dental/vision, flexible spending accounts, company-paid life and short-term disability, plus optional long-term disability, and additional life insurance. All benefits subject to eligibility."
Also there is mention of "Competitive weekly/bi-weekly pay" which is pay info. So we can include a Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay: "Competitive weekly/bi-weekly pay". So we can include a Pay section. Benefits: they list benefits, so we can include Benefits section. Schedule: not mentioned, so no Schedule section.
We also have "Job Location" which could be considered metadata; we can fold into a short
maybe under an "About the role" or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Job location is minor metadata; we could include it in a
under About the role or separate paragraph. Probably best to include it as a
after the purpose.
We need to decide sections: About the role (maybe combine Position Purpose and location). Responsibilities (Key Responsibilities). Requirements (Minimum Qualifications). Qualifications (Preferred Qualifications). Skills (Core Competencies). Benefits (list). Pay (maybe short paragraph). Why This Role Matters could be part of About the role or separate? Could be its own section but we need to avoid thin sections. Could combine Why This Role Matters into About the role or Responsibilities? It's more about impact; maybe we can include as a separate section "Impact" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "Why This Role Matters" could go under About the role or maybe under Responsibilities? Probably About the role is appropriate to include purpose and impact.
Thus sections:
- About the role: include Position Purpose paragraph, Job Location paragraph, Why This Role Matters paragraph.
- Responsibilities: list of responsibilities (the bullet-like paragraphs under Key Responsibilities). We need to convert each bullet into
- . The responsibilities are multiple paragraphs each starting with a bold heading? Let's extract:
Key Responsibilities
Partner Integration Leadership
Lead the technical onboarding of new partners and customers across both API and EDI integration models, ensuring smooth and efficient integration into the Heritage ecosystem.
Act as the primary engineering leader supporting partner integrations, working closely with business development, product, and external partners.
Translate partner requirements into scalable integration solutions, balancing customization with platform reuse
Evaluate and recommend appropriate integration patterns:
REST APIs
Event-driven architecture
EDI batch/file-based models
Hybrid approaches
Own integration success from onboarding through production stabili (typo: stability)
API, EDI, and Integration Development
Design, build, and maintain custom APIs, services, and integration applications to support partner onboarding and growth initiatives.
Design, implement, and support EDI integrations using:
ANSI X12
EDIFACT
Support core transaction sets:
850 (Purchase Order)
855 (Acknowledgment)
856 (ASN)
810 (Invoice)
846 (Inventory)
Ensure APIs follow enterprise standards aligned with the Enterprise Integration Layer (EIL), including canonical data models, observability, and security.
Develop integration patterns that support both real-time APIs, event-driven architectures, and EDI workflows.
Fulfillment & Order-to-Cash Integration Leadership
Own EDI-based fulfillment integrations supporting order-to-cash workflows
Ensure accurate processing of:
Orders
Shipment notifications
Invoices
Inventory updates
Implement EDI acknowledgment handling (997/999) and reconciliation processes
Partner with operations, supply chain, finance, and customer service teams
Drive standardization to reduce partner-specific customization
Custom Solutions for Growth
Build targeted applications and services to enable strategic partner capabilities such as:
Order integration and automation
Pricing and catalog synchronization
Customer onboarding workflows
Data exchange and transformation services
EDI-driven fulfillment workflows
Make pragmatic decisions on when to build reusable services vs. purpose-built solutions to accelerate revenue opportunities.
Architecture and Scalability
Ensure all partner integrations are designed for scalability, reliability, and performance, avoiding point-to-point technical debt where possible.
Collaborate with Architecture and Platform teams to align integrations with enterprise standards and long-term platform strategy.
Drive adoption of API-first and reusable integration patterns.
Establish reusable:
EDI transformation libraries
Canonical mappings
Agile Delivery and Execution
Lead a high-performing Agile team delivering integration solutions in a fast-paced environment.
Ensure continuous integration and deployment of reliable solutions using DevOps best practices.
Own delivery timelines for partner integrations, often tied directly to revenue and customer commitments.
Observability and Operational Excellence
Implement strong monitoring, logging, and alerting practices for all integrations.
Ensure rapid detection and resolution of issues impacting partners, minimizing downtime and business disruption.
Collaborate with L1/L2 support teams to ensure smooth operational handoff and incident management.
AI-Enabled Engineering and Innovation
Drive adoption of AI-assisted software development across the team, leveraging tools such as GitHub Copilot and agent-based workflows to improve developer productivity and code quality.
Embed AI into the entire software development lifecycle (SDLC), including:
Requirements analysis and API design acceleration
Automated code generation and refactoring
Test case generation and intelligent QA automation
AI-assisted debugging using logs, traces, and telemetry
Utilize AI to enhance integration development, including mapping, transformation logic generation, and documentation of APIs and partner workflows.
Partner with architecture and platform teams to explore agentic integration patterns, where AI can orchestrate workflows, monitor integrations, and proactively resolve issues.
Continuously evaluate emerging AI capabilities and integrate them into engineering practices to maintain a competitive advantage.
Team Leadership and Development
Mentor and coach engineers on API design, EDI Standards, integration patterns, and partner-facing solutions.
Foster a culture of ownership, accountability, and speed, aligned with business outcomes.
Manage all HR responsibilities, including performance reviews, career development, and team planning.
Promote continuous learning, especially in modern integration patterns and AI-enabled engineering practices.
We need to turn each of these bullet points into
- . However many are sub-bullets (like under "Evaluate and recommend appropriate integration patterns:" we have list). We could treat each line as separate
- . But we need to preserve structure? The instruction: Use
- for any list of duties/requirements/benefits. So we can flatten all duty statements into a single
with each duty as - . That may lose some grouping but acceptable.
We must preserve ALL substantive information; do not invent or summarize away detail. Flattening is okay as long as we keep each statement.
We need to be careful not to lose any details like the transaction sets etc.
We'll produce a
with many - items.
Similarly for Minimum Qualifications: list of items each starting with bullet? The text:
Minimum Qualifications
Proven experience as a hands-on engineering leader in API development and system integrations
Minimum 5 years of experience building cloud-native applications and integrations using Microservices or SOA
Strong expertise in:
Azure (Functions, API Management, Service Bus/Event Grid)
.NET / C#
RESTful APIs and integration patterns
EDI standards (ANSI X12, EDIFACT)
Common EDI transactions (850, 855, 856, 810, 846)
Experience designing and implementing partner-facing APIs and external integrations
Experience with EDI platforms/tools (SPS Commerce, Cleo, Boomi, MuleSoft, Logic Apps, or similar)
Strong understanding of data transformation, mapping, and orchestration
Experience with CI/CD pipelines and DevOps practices
Knowledge of security standards (OAuth, API security, OWASP)
Experience with observability tools and logging frameworks
Practical experience applying AI-assisted development tools and building or integrating AI-driven solutions (e.g., leveraging LLMs, automation, or intelligent workflows to enhance engineering productivity or system capabilities)
Ability to balance speed of delivery with long-term architectural integrity
We need to treat each line as
- . For sub-items like under Strong expertise: we could flatten each as separate
- . That's okay.
Preferred Qualifications similarly.
Core Competencies list:
Core Competencies
Partner-Focused Engineering Ability to understand partner needs and translate them into practical, scalable technical solutions.
Integration Architecture Expertise Deep understanding of API design, system interoperability, and integration patterns.
AI-Driven Engineering Mindset Leverages AI tools and agentic workflows to enhance productivity, quality, and operational efficiency.
Speed with Discipline Delivers solutions quickly while maintaining architectural integrity and avoiding long-term technical debt.
Strategic Thinking Balances immediate partner needs with long-term platform evolution and reuse.
Communication and Influence Effectively communicates with internal teams and external partners, bridging business and technical discussions.
Ownership and Accountability Takes full ownership of partner integration success, from onboarding to production stability.
Each line is a competency with description. We'll make each as
- .
Benefits: we have a paragraph listing many benefits. We can turn each benefit into
- maybe. The instruction: Use
- for any list of duties/requirements/benefits. So we can split the benefits sentence into items.
Benefits list: Competitive weekly/bi-weekly pay, discretionary bonuses, 401(k) with company match, Employee Stock Purchase Plan, paid time off (vacation, sick, volunteer, holidays, birthday, floating), medical/dental/vision, flexible spending accounts, company-paid life and short-term disability, plus optional long-term disability, and additional life insurance. All benefits subject to eligibility.
We could make each benefit as
- . Also note "All benefits subject to eligibility." could be a separate
or included as note.
Pay: we have "Competitive weekly/bi-weekly pay" already in benefits; but we could also have a Pay section with that line. However we must not duplicate? The instruction: Prefer a few substantive sections over many thin ones. If we put pay in Benefits section, we might not need separate Pay section. But they said never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay, but we could include pay within Benefits section as a benefit
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to parse the posting and extract sections. The posting includes: - Position Purpose (intro paragraph) - Key Responsibilities (multiple bullet-like paragraphs) - Minimum Qualifications (list) - Preferred Qualifications (list) - Core Competencies (list) - Why This Role Matters (paragraph) - Job Location (address) - Benefits paragraph: "Competitive weekly/bi-weekly pay, discretionary bonuses, 401(k) with company match, Employee Stock Purchase Plan, paid time off (vacation, sick, volunteer, holidays, birthday, floating), medical/dental/vision, flexible spending accounts, company-paid life and short-term disability, plus optional long-term disability, and additional life insurance. All benefits subject to eligibility." Also there is mention of "Competitive weekly/bi-weekly pay" which is pay info. So we can include a Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay: "Competitive weekly/bi-weekly pay". So we can include a Pay section. Benefits: they list benefits, so we can include Benefits section. Schedule: not mentioned, so no Schedule section. We also have "Job Location" which could be considered metadata; we can fold into a short
maybe under an "About the role" or separate? The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Job location is minor metadata; we could include it in a
under About the role or separate paragraph. Probably best to include it as a
after the purpose. We need to decide sections: About the role (maybe combine Position Purpose and location). Responsibilities (Key Responsibilities). Requirements (Minimum Qualifications). Qualifications (Preferred Qualifications). Skills (Core Competencies). Benefits (list). Pay (maybe short paragraph). Why This Role Matters could be part of About the role or separate? Could be its own section but we need to avoid thin sections. Could combine Why This Role Matters into About the role or Responsibilities? It's more about impact; maybe we can include as a separate section "Impact" but not in allowed headings list. The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings. "Why This Role Matters" could go under About the role or maybe under Responsibilities? Probably About the role is appropriate to include purpose and impact. Thus sections: - About the role: include Position Purpose paragraph, Job Location paragraph, Why This Role Matters paragraph. - Responsibilities: list of responsibilities (the bullet-like paragraphs under Key Responsibilities). We need to convert each bullet into
- for any list of duties/requirements/benefits. So we can flatten all duty statements into a single
- with each duty as
- . That may lose some grouping but acceptable.
We must preserve ALL substantive information; do not invent or summarize away detail. Flattening is okay as long as we keep each statement.
We need to be careful not to lose any details like the transaction sets etc.
We'll produce a
- with many
- items. Similarly for Minimum Qualifications: list of items each starting with bullet? The text: Minimum Qualifications Proven experience as a hands-on engineering leader in API development and system integrations Minimum 5 years of experience building cloud-native applications and integrations using Microservices or SOA Strong expertise in: Azure (Functions, API Management, Service Bus/Event Grid) .NET / C# RESTful APIs and integration patterns EDI standards (ANSI X12, EDIFACT) Common EDI transactions (850, 855, 856, 810, 846) Experience designing and implementing partner-facing APIs and external integrations Experience with EDI platforms/tools (SPS Commerce, Cleo, Boomi, MuleSoft, Logic Apps, or similar) Strong understanding of data transformation, mapping, and orchestration Experience with CI/CD pipelines and DevOps practices Knowledge of security standards (OAuth, API security, OWASP) Experience with observability tools and logging frameworks Practical experience applying AI-assisted development tools and building or integrating AI-driven solutions (e.g., leveraging LLMs, automation, or intelligent workflows to enhance engineering productivity or system capabilities) Ability to balance speed of delivery with long-term architectural integrity We need to treat each line as
- . For sub-items like under Strong expertise: we could flatten each as separate
- . That's okay. Preferred Qualifications similarly. Core Competencies list: Core Competencies Partner-Focused Engineering Ability to understand partner needs and translate them into practical, scalable technical solutions. Integration Architecture Expertise Deep understanding of API design, system interoperability, and integration patterns. AI-Driven Engineering Mindset Leverages AI tools and agentic workflows to enhance productivity, quality, and operational efficiency. Speed with Discipline Delivers solutions quickly while maintaining architectural integrity and avoiding long-term technical debt. Strategic Thinking Balances immediate partner needs with long-term platform evolution and reuse. Communication and Influence Effectively communicates with internal teams and external partners, bridging business and technical discussions. Ownership and Accountability Takes full ownership of partner integration success, from onboarding to production stability. Each line is a competency with description. We'll make each as
- . Benefits: we have a paragraph listing many benefits. We can turn each benefit into
- maybe. The instruction: Use
- for any list of duties/requirements/benefits. So we can split the benefits sentence into items. Benefits list: Competitive weekly/bi-weekly pay, discretionary bonuses, 401(k) with company match, Employee Stock Purchase Plan, paid time off (vacation, sick, volunteer, holidays, birthday, floating), medical/dental/vision, flexible spending accounts, company-paid life and short-term disability, plus optional long-term disability, and additional life insurance. All benefits subject to eligibility. We could make each benefit as
- . Also note "All benefits subject to eligibility." could be a separate
or included as note. Pay: we have "Competitive weekly/bi-weekly pay" already in benefits; but we could also have a Pay section with that line. However we must not duplicate? The instruction: Prefer a few substantive sections over many thin ones. If we put pay in Benefits section, we might not need separate Pay section. But they said never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay, but we could include pay within Benefits section as a benefit
- . That may lose some grouping but acceptable.
We must preserve ALL substantive information; do not invent or summarize away detail. Flattening is okay as long as we keep each statement.
We need to be careful not to lose any details like the transaction sets etc.
We'll produce a