Manager - Infrastructure & Operations
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes description of role (About the role), essential duties (Responsibilities), qualifications required (Qualifications), qualifications desired (maybe also Qualifications?), preferred certifications (maybe Skills?), physical demands, working conditions (maybe Schedule?), salary range (Pay), benefits (Benefits). Also note: we should not repeat job title as heading. No Job ID etc. Remove boilerplate like EEO, legal, etc. Also remove application instructions (like applications accepted through date, etc). Also remove unsolicited resumes note, etc. Also remove visa sponsorship note? Might be considered metadata; but we can fold minor metadata into short p or drop it. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include some metadata like location, remote, etc in a paragraph maybe under About the role or separate? But we should avoid creating sections with filler. We'll produce sections: About the role (summary), Responsibilities (essential duties), Qualifications (required and desired maybe combined?), Skills (maybe certifications?), Benefits, Pay. Schedule maybe from working conditions (some work outside normal business hours, periodic travel). That could be Schedule. We'll include Schedule if there is specific content: "Some work outside normal business hours may be required to support system releases, incidents, global operations, or other business needs. Periodic travel may also be required for meetings, events, or other business purposes." That's schedule info. So include Schedule section. We must not include sections like "Physical Demands" unless we map to something else; but we could incorporate into Working Conditions maybe not needed. We'll keep Schedule. We must not include boilerplate like EEO, equal opportunity, etc. Remove those paragraphs. We must preserve all substantive information; not invent or summarize away detail. So we need to keep details like responsibilities list, qualifications list, desired qualifications, preferred certifications, benefits description, salary range, working conditions (location, remote, travel, hours). Also note: "This is a full-time, salaried, exempt position." That's schedule/employment type; could be part of Schedule or maybe a short p. We must not include application instructions like "Applications will be accepted through October 11, 2026." That's application instruction; remove. Also "We will consider for employment all qualified applicants, including those with criminal histories..." that's EEO/legal; remove. Also "We may use artificial intelligence (AI) tools..." that's hiring process; remove. We must not include "Physical Demands" and "WORKING CONDITIONS" as headings unless we map to Schedule or maybe we can include a short p under About the role? But we need to preserve substantive info: location preference, remote possibility, work environment, travel, hours. That's schedule/working conditions. So we can put that in Schedule section. Benefits: "This position is eligible for company-sponsored benefits, including medical, dental, and vision insurance, paid time off, paid holidays, and participation in the company's 401(k) plan, subject to the terms and eligibility requirements of the applicable benefit plans." Keep that. Pay: "The anticipated salary range for this position is $127,000.00 to $180,391.00 annually. Actual compensation will be determined based on factors such as experience, qualifications, skills, and geographic location." Keep that. Now we need to decide sections: About the role (intro paragraph), Responsibilities (essential duties list), Qualifications (maybe combine required and desired and preferred certifications?), Skills (maybe we could separate certifications as Skills? But we have no explicit Skills section besides certifications; we could put certifications under Qualifications or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples; we can use Requirements as a heading maybe for qualifications? But they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can choose which to use. They said "include a section ONLY when the posting has real, specific content for it". So we need to decide which headings have content.
We have content for About the role (intro). Responsibilities (essential duties). Qualifications (required and desired). Skills (maybe certifications). Benefits. Pay. Schedule (working conditions). Requirements maybe not needed if we use Qualifications. But we could use Requirements for qualifications required, and Qualifications for desired? But better to follow typical: Requirements = qualifications required, Qualifications = desired? However they gave both as examples; we can use either. To avoid thin sections, we can combine required and desired into Qualifications section, and maybe Skills for certifications. Or we could have Requirements (required) and Qualifications (desired). But that would be two sections; both have content. That's okay. But we need to avoid filler. Both have substantive content. So we can do:
About the role
...
Responsibilities
- ...
Requirements
- ...
Qualifications
- ...
Benefits
...
Pay
...
Schedule
...
We should not include Skills if we already used Qualifications for certifications. But we could also put certifications under Skills. However we already have Qualifications for desired; we could put certifications under Skills. Let's decide: Use Requirements for required qualifications. Use Qualifications for desired qualifications. Use Skills for preferred certifications. That gives three sections with content. Check if we have content for Skills: "PREFERRED CERTIFICATIONS:• Shopify Partner, Shopify Developer, or Shopify Plus Certification." That's specific. So Skills section can list those. Now we need to ensure we don't repeat job title as heading. Not needed. We must not include any markdown code fences. Just raw HTML. Now we need to extract the substantive content. Let's parse the posting. Intro: "The Director of Application Integration is the lead owner for SeneGence's business applications, with primary responsibility for Shopify and its connected application ecosystem. Reporting to the SVP of IT, this role owns application strategy, configuration, integration, reliability, and delivery of business requirements across a complex commerce environment.Working directly with business stakeholders, the Director translates business rules, workflows, and requirements into scalable application solutions using native platform capabilities, configuration, and proven off-the-shelf applications wherever practical. When custom development is needed, this role defines the business and technical requirements and partners with the Software Development team through delivery.Marketing owns the day-to-day operation of Shopify content, merchandising, and campaigns, while IT, led by this role for the application layer, owns platform configuration, integrations, technical capabilities, and ongoing platform evolution." We can combine into a paragraph for About the role. Now Responsibilities: list of essential duties (bulleted). We'll preserve each bullet as