Director of Engineering - Platform & Integrations
for sections: 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 etc. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". So we need to parse the posting.
The posting includes:
- Who We Are (company description)
- The Role (description)
- Responsibilities (list)
- How You’ll Work (collaborators)
- What Success Looks Like (goals)
- Qualifications (list)
- Preferred Qualifications (list)
- Leadership Profile (list)
- Remote Culture (some description)
- Benefits (list)
- Diversity, Equity and Inclusion (some description)
- "applicable to in-office employees" (maybe ignore)
We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to map content.
"About the role": likely the description under "The Role". Could be a paragraph summarizing role.
"Responsibilities": we have a big list under "Responsibilities" heading with subheadings: Engineering and People Leadership, API and Platform Strategy, Partner Integrations, Delivery and Operational Excellence. We need to output a
- for any list of duties/requirements/benefits. So we can flatten each bullet point.
"Requirements": maybe combine Qualifications and Preferred Qualifications? Usually Requirements are mandatory qualifications. We'll treat Qualifications as Requirements. Preferred Qualifications could be Skills? Or we could have Skills section for preferred qualifications. The instruction: Use sections only when posting has real specific content. So we can have Requirements (Qualifications) and Skills (Preferred Qualifications). Also maybe "Leadership Profile" could be part of Skills or Requirements? It's more about leadership traits; could be part of Skills.
"Benefits": we have Benefits section with list.
"Pay": not mentioned; no pay info. So we should NOT include Pay section.
"Schedule": not mentioned; remote work but no schedule specifics. So we should NOT include Schedule.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to preserve all substantive info; not invent or summarize away detail. So we need to include all points from Responsibilities, Qualifications, Preferred Qualifications, Leadership Profile, Benefits, etc. Also include "Who We Are"? Not required as a section; but we could incorporate into About the role? The instruction: About the role section heading. Could include description of role and maybe company? But "About the role" likely refers to role description, not company. However we have "Who We Are" which is company description; not required as a section but we could include as a paragraph under About the role? Might be considered part of role context. Safer to include a short paragraph about the company under About the role? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role is a heading; we can put the role description there, maybe also include company mission? But we must preserve all substantive info; if we omit Who We Are, we lose that info. So we should incorporate Who We Are into About the role section (maybe as a paragraph). That seems acceptable.
Thus About the role: combine Who We Are and The Role description (maybe two paragraphs). Use
for prose.
Responsibilities: list each bullet under subheadings. We'll need to extract each bullet point.
Let's parse Responsibilities section:
"Engineering and People Leadership
Lead, coach, and develop the engineers supporting Platform APIs and partner integrations.
Create clear ownership, expectations, and development opportunities across the team.
Establish effective engineering practices for planning, design reviews, code reviews, testing, deployment, documentation, and production support.
Partner with Product and business leaders to build realistic roadmaps and make clear tradeoffs across partner commitments, platform investments, technical debt, and team capacity.
Support hiring, onboarding, performance management, and succession planning for the team.
Build a culture of accountability, collaboration, knowledge sharing, and continuous improvement."
"API and Platform Strategy
Define the technical vision and roadmap for ZenBusiness’s Enterprise APIs and integration capabilities.
Lead the design and evolution of APIs, schemas, webhooks, authentication, fulfillment packages, and supporting developer tools.
Ensure APIs are scalable, secure, observable, well documented, and easy for partners to adopt.
Establish standards for API versioning, backward compatibility, change management, deprecation, and release communication.
Reduce partner-specific customizations by developing reusable platform capabilities and consistent integration patterns.
Partner with internal platform teams to connect Enterprise APIs to formation, compliance, pricing, order management, schemas, and fulfillment workflows.
Lead through influence across engineering teams whose systems contribute to the end-to-end partner experience, establishing clear ownership and resolving cross-team dependencies.
Evolve core business capabilities so they can be safely discovered and invoked by AI agents through MCP and other emerging standards, with clear authorization, observability, guardrails, and human oversight."
"Partner Integrations
Represent ZenBusiness in senior-level technical conversations with strategic partners to understand their architecture, requirements, constraints, and implementation plans, while clearly communicating decisions, risks, dependencies, and delivery expectations.
Guide partners through solution design, testing, and launch. Establish clear launch-readiness criteria and lead technical go/no-go decisions, production stabilization, and ongoing integration health.
Translate partner needs into platform capabilities while protecting the long-term integrity of the architecture.
Identify integration risks early and create clear mitigation and escalation plans.
Coordinate across Product, Engineering, Sales, Partner Success, Operations, Legal, Security, and Finance when delivering new partner capabilities.
Ensure partner commitments, dependencies, ownership, and launch criteria are clearly documented and understood."
"Delivery and Operational Excellence
Own the reliable delivery of API and integration roadmap commitments.
Improve release processes for schemas, fulfillment packages, portal updates, changelogs, and production deployments.
Establish service-level objectives and operational metrics for API availability, latency, errors, webhook delivery, data accuracy, and partner adoption.
Strengthen monitoring, alerting, incident response, and root-cause analysis for partner-facing services.
Ensure production incidents and partner escalations receive clear ownership, communication, and follow-through.
Use operational data and partner feedback to identify platform improvements and prioritize investments."
We need to output each as
- . Could group under subheadings? Not required; just a list. But we could keep subheadings as
maybe? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can have a
containing all responsibility items as - . No need for subheadings inside list; but we could include them as part of the li text.
Now Requirements (Qualifications): list:
"Significant experience leading software engineering teams, including managing and developing engineering managers and/or senior engineers.
Experience designing, building, or operating external APIs and enterprise integration platforms.
Strong understanding of REST APIs, webhooks, event-driven architecture, authentication, API gateways, versioning, and integration security.
Experience delivering complex integrations involving multiple internal systems and external partners.
Demonstrated ability to translate business requirements into scalable technical solutions.
Strong understanding of software delivery, testing, observability, incident management, and production operations.
Experience managing technical roadmaps, dependencies, risks, and cross-functional delivery.
Strong written and verbal communication skills, including the ability to communicate technical decisions to nontechnical audiences.
Experience participating in customer- or partner-facing technical conversations.
Ability to balance urgent partner needs with long-term platform health."
We'll output each as
- under Requirements.
Skills (Preferred Qualifications + Leadership Profile maybe). Let's combine Preferred Qualifications and Leadership Profile as skills.
Preferred Qualifications list:
"Experience building developer portals, integration sandboxes, API documentation, SDKs, or partner certification programs.
Experience supporting high-volume, business-critical integrations.
Familiarity with schema-driven platforms, API lifecycle management, and automated contract testing.
Experience leading teams through platform modernization or the migration of legacy integrations.
Experience working in a product-led, SaaS, or platform organization.
Experience leading complex, partner-facing enterprise integrations, including direct communication with senior product and engineering leaders at external companies.
Strong prioritization and stakeholder-management skills, especially when contractual or launch commitments compete with internal platform investments, operational needs, and technical debt.
The ability to move between executive-level conversations and detailed technical or delivery decisions without becoming either a purely strategic leader or the team’s day-to-day solution architect."
Leadership Profile list:
"We Are Looking For a Leader Who
Develops people and creates clarity without becoming a delivery bottleneck.
Is technically credible but does not need to be the person writing every solution.
Can move comfortably between architecture, execution, operations, and partner conversations.
Makes pragmatic decisions while protecting long-term platform scalability.
Communicates risks and tradeoffs early and clearly.
Builds strong relationships across technical, product, operational, and commercial teams.
Treats documentation, reliability, and knowledge sharing as essential parts of engineering."
We could treat these as Skills items.
Thus Skills section:
with all those items.
Benefits section: list from Benefits paragraph:
"The company offers various benefits to employees and their dependents, including medical, vision, dental, disability, and life insurance, as well as parental and military leave. Other benefits include an employee assistance program, 401k + match, annual bonus, pet insurance, and RSUs. Paid parking* and 10 paid holidays are also provided."
We need to output each benefit as - . Could split: medical, vision, dental, disability, life insurance, parental leave, military leave, employee assistance program, 401k + match, annual bonus, pet insurance, RSUs, paid parking, 10 paid holidays.
We should preserve the asterisk note? Probably keep as part of text: "Paid parking*". We'll include as is.
Now we need to ensure we don't include boilerplate: Remote Culture paragraph, Diversity, Equity and Inclusion paragraph, "applicable to in-office employees". Those are not required sections; we could omit them as they are not under specified headings. However we must preserve ALL substantive information; but the instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not say we must keep Remote Culture or DEI sections; they are not boilerplate but they are substantive. However we only have to output sections for the given headings; we could include them as prose under About the role or maybe under a separate section not listed? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings; but we could also add other headings if needed? It says "Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the examples are those. Safer to stick to those headings and incorporate any extra info into those sections where appropriate.
Remote Culture paragraph: "Remote Culture. A great company culture leads to happy employees, and happy employees lead to happy customers. We provide our employees with good salaries, benefits, equity, and interesting challenges that have a positive impact. Let’s stay connected! We believe in staying connected, and we have a weekly “All Hands” meeting every week. We also have a social committee that hosts frequent events. We’ve held a virtual talent show, costume competitions, monthly lunch and learn series, Hackathons and more!"
We could incorporate this into About the role or Benefits? It's about culture, not benefits. Could add a paragraph
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Preserve all substantive info. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section only when posting has real specific content for it. Avoid filler like "commensurate with experience". So we need to parse the posting. The posting includes: - Who We Are (company description) - The Role (description) - Responsibilities (list) - How You’ll Work (collaborators) - What Success Looks Like (goals) - Qualifications (list) - Preferred Qualifications (list) - Leadership Profile (list) - Remote Culture (some description) - Benefits (list) - Diversity, Equity and Inclusion (some description) - "applicable to in-office employees" (maybe ignore) We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. "About the role": likely the description under "The Role". Could be a paragraph summarizing role. "Responsibilities": we have a big list under "Responsibilities" heading with subheadings: Engineering and People Leadership, API and Platform Strategy, Partner Integrations, Delivery and Operational Excellence. We need to output a
- for any list of duties/requirements/benefits. So we can flatten each bullet point.
"Requirements": maybe combine Qualifications and Preferred Qualifications? Usually Requirements are mandatory qualifications. We'll treat Qualifications as Requirements. Preferred Qualifications could be Skills? Or we could have Skills section for preferred qualifications. The instruction: Use sections only when posting has real specific content. So we can have Requirements (Qualifications) and Skills (Preferred Qualifications). Also maybe "Leadership Profile" could be part of Skills or Requirements? It's more about leadership traits; could be part of Skills.
"Benefits": we have Benefits section with list.
"Pay": not mentioned; no pay info. So we should NOT include Pay section.
"Schedule": not mentioned; remote work but no schedule specifics. So we should NOT include Schedule.
Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits.
We need to ensure we don't include filler like "commensurate with experience". Not present.
We need to preserve all substantive info; not invent or summarize away detail. So we need to include all points from Responsibilities, Qualifications, Preferred Qualifications, Leadership Profile, Benefits, etc. Also include "Who We Are"? Not required as a section; but we could incorporate into About the role? The instruction: About the role section heading. Could include description of role and maybe company? But "About the role" likely refers to role description, not company. However we have "Who We Are" which is company description; not required as a section but we could include as a paragraph under About the role? Might be considered part of role context. Safer to include a short paragraph about the company under About the role? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So About the role is a heading; we can put the role description there, maybe also include company mission? But we must preserve all substantive info; if we omit Who We Are, we lose that info. So we should incorporate Who We Are into About the role section (maybe as a paragraph). That seems acceptable. Thus About the role: combine Who We Are and The Role description (maybe two paragraphs). Use
for prose. Responsibilities: list each bullet under subheadings. We'll need to extract each bullet point. Let's parse Responsibilities section: "Engineering and People Leadership Lead, coach, and develop the engineers supporting Platform APIs and partner integrations. Create clear ownership, expectations, and development opportunities across the team. Establish effective engineering practices for planning, design reviews, code reviews, testing, deployment, documentation, and production support. Partner with Product and business leaders to build realistic roadmaps and make clear tradeoffs across partner commitments, platform investments, technical debt, and team capacity. Support hiring, onboarding, performance management, and succession planning for the team. Build a culture of accountability, collaboration, knowledge sharing, and continuous improvement." "API and Platform Strategy Define the technical vision and roadmap for ZenBusiness’s Enterprise APIs and integration capabilities. Lead the design and evolution of APIs, schemas, webhooks, authentication, fulfillment packages, and supporting developer tools. Ensure APIs are scalable, secure, observable, well documented, and easy for partners to adopt. Establish standards for API versioning, backward compatibility, change management, deprecation, and release communication. Reduce partner-specific customizations by developing reusable platform capabilities and consistent integration patterns. Partner with internal platform teams to connect Enterprise APIs to formation, compliance, pricing, order management, schemas, and fulfillment workflows. Lead through influence across engineering teams whose systems contribute to the end-to-end partner experience, establishing clear ownership and resolving cross-team dependencies. Evolve core business capabilities so they can be safely discovered and invoked by AI agents through MCP and other emerging standards, with clear authorization, observability, guardrails, and human oversight." "Partner Integrations Represent ZenBusiness in senior-level technical conversations with strategic partners to understand their architecture, requirements, constraints, and implementation plans, while clearly communicating decisions, risks, dependencies, and delivery expectations. Guide partners through solution design, testing, and launch. Establish clear launch-readiness criteria and lead technical go/no-go decisions, production stabilization, and ongoing integration health. Translate partner needs into platform capabilities while protecting the long-term integrity of the architecture. Identify integration risks early and create clear mitigation and escalation plans. Coordinate across Product, Engineering, Sales, Partner Success, Operations, Legal, Security, and Finance when delivering new partner capabilities. Ensure partner commitments, dependencies, ownership, and launch criteria are clearly documented and understood." "Delivery and Operational Excellence Own the reliable delivery of API and integration roadmap commitments. Improve release processes for schemas, fulfillment packages, portal updates, changelogs, and production deployments. Establish service-level objectives and operational metrics for API availability, latency, errors, webhook delivery, data accuracy, and partner adoption. Strengthen monitoring, alerting, incident response, and root-cause analysis for partner-facing services. Ensure production incidents and partner escalations receive clear ownership, communication, and follow-through. Use operational data and partner feedback to identify platform improvements and prioritize investments." We need to output each as
- . Could group under subheadings? Not required; just a list. But we could keep subheadings as
maybe? The instruction: Use
- for any list of duties/requirements/benefits, and
for prose. So we can have a
- containing all responsibility items as
- . No need for subheadings inside list; but we could include them as part of the li text. Now Requirements (Qualifications): list: "Significant experience leading software engineering teams, including managing and developing engineering managers and/or senior engineers. Experience designing, building, or operating external APIs and enterprise integration platforms. Strong understanding of REST APIs, webhooks, event-driven architecture, authentication, API gateways, versioning, and integration security. Experience delivering complex integrations involving multiple internal systems and external partners. Demonstrated ability to translate business requirements into scalable technical solutions. Strong understanding of software delivery, testing, observability, incident management, and production operations. Experience managing technical roadmaps, dependencies, risks, and cross-functional delivery. Strong written and verbal communication skills, including the ability to communicate technical decisions to nontechnical audiences. Experience participating in customer- or partner-facing technical conversations. Ability to balance urgent partner needs with long-term platform health." We'll output each as
- under Requirements.
Skills (Preferred Qualifications + Leadership Profile maybe). Let's combine Preferred Qualifications and Leadership Profile as skills.
Preferred Qualifications list:
"Experience building developer portals, integration sandboxes, API documentation, SDKs, or partner certification programs.
Experience supporting high-volume, business-critical integrations.
Familiarity with schema-driven platforms, API lifecycle management, and automated contract testing.
Experience leading teams through platform modernization or the migration of legacy integrations.
Experience working in a product-led, SaaS, or platform organization.
Experience leading complex, partner-facing enterprise integrations, including direct communication with senior product and engineering leaders at external companies.
Strong prioritization and stakeholder-management skills, especially when contractual or launch commitments compete with internal platform investments, operational needs, and technical debt.
The ability to move between executive-level conversations and detailed technical or delivery decisions without becoming either a purely strategic leader or the team’s day-to-day solution architect."
Leadership Profile list:
"We Are Looking For a Leader Who
Develops people and creates clarity without becoming a delivery bottleneck.
Is technically credible but does not need to be the person writing every solution.
Can move comfortably between architecture, execution, operations, and partner conversations.
Makes pragmatic decisions while protecting long-term platform scalability.
Communicates risks and tradeoffs early and clearly.
Builds strong relationships across technical, product, operational, and commercial teams.
Treats documentation, reliability, and knowledge sharing as essential parts of engineering."
We could treat these as Skills items.
Thus Skills section:
- with all those items.
Benefits section: list from Benefits paragraph:
"The company offers various benefits to employees and their dependents, including medical, vision, dental, disability, and life insurance, as well as parental and military leave. Other benefits include an employee assistance program, 401k + match, annual bonus, pet insurance, and RSUs. Paid parking* and 10 paid holidays are also provided."
We need to output each benefit as
- . Could split: medical, vision, dental, disability, life insurance, parental leave, military leave, employee assistance program, 401k + match, annual bonus, pet insurance, RSUs, paid parking, 10 paid holidays.
We should preserve the asterisk note? Probably keep as part of text: "Paid parking*". We'll include as is.
Now we need to ensure we don't include boilerplate: Remote Culture paragraph, Diversity, Equity and Inclusion paragraph, "applicable to in-office employees". Those are not required sections; we could omit them as they are not under specified headings. However we must preserve ALL substantive information; but the instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not say we must keep Remote Culture or DEI sections; they are not boilerplate but they are substantive. However we only have to output sections for the given headings; we could include them as prose under About the role or maybe under a separate section not listed? The instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings; but we could also add other headings if needed? It says "Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the examples are those. Safer to stick to those headings and incorporate any extra info into those sections where appropriate. Remote Culture paragraph: "Remote Culture. A great company culture leads to happy employees, and happy employees lead to happy customers. We provide our employees with good salaries, benefits, equity, and interesting challenges that have a positive impact. Let’s stay connected! We believe in staying connected, and we have a weekly “All Hands” meeting every week. We also have a social committee that hosts frequent events. We’ve held a virtual talent show, costume competitions, monthly lunch and learn series, Hackathons and more!" We could incorporate this into About the role or Benefits? It's about culture, not benefits. Could add a paragraph
- . Could split: medical, vision, dental, disability, life insurance, parental leave, military leave, employee assistance program, 401k + match, annual bonus, pet insurance, RSUs, paid parking, 10 paid holidays.
We should preserve the asterisk note? Probably keep as part of text: "Paid parking*". We'll include as is.
Now we need to ensure we don't include boilerplate: Remote Culture paragraph, Diversity, Equity and Inclusion paragraph, "applicable to in-office employees". Those are not required sections; we could omit them as they are not under specified headings. However we must preserve ALL substantive information; but the instruction says "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." It does not say we must keep Remote Culture or DEI sections; they are not boilerplate but they are substantive. However we only have to output sections for the given headings; we could include them as prose under About the role or maybe under a separate section not listed? The instruction says "use
- for any list of duties/requirements/benefits, and