Director, Software Engineering
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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.
We need to include sections where there is real content.
Let's parse the posting:
- Intro paragraph about Cotality mission etc. Could be "About the role" or maybe "About Cotality". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings.
We have:
Job Description: Cotality is seeking a highly experienced and strategic Director of Software Engineering to lead our Digital Gateway initiatives. In this critical leadership role, you will hold ultimate responsibility for all file transfer operations across the organization. You will oversee the architecture, engineering, and 24/7 production support of our critical data exchange platforms, including our modern MFT Gateway and legacy EDE applications. The ideal candidate is a technical leader with deep expertise in managed file transfer (MFT) ecosystems, enterprise data exchange, and global team management. You will direct a blended workforce of onshore and offshore engineering professionals to ensure the seamless, secure, and highly available operation of the Cotality Digital Gateway (CDG).
That's like a summary; could be "About the role".
Then "Key Responsibilities" with subpoints: Enterprise MFT & Gateway Leadership (IBM Sterling File Gateway, Overall File Transfer Operations), Legacy System Management (CLEO Harmony EDE, Modernization Strategy), Global Team Leadership & Management (Onshore & Offshore Alignment, Resource Allocation), Production Support & Operational Excellence (CDG Production Support, Incident & SLA Management, Monitoring & Alerting). These are duties.
Then "Job Qualifications Required Experience & Technical Skills:" with bullet-like paragraphs: Experience: 10+ years..., IBM Sterling Expertise..., CLEO Harmony Experience..., Global Leadership..., Operational Management..., Protocols & Security:.
Then "Preferred Qualifications": Bachelor’s or Master’s degree..., Experience with Cloud environments..., Strong financial acumen...
Then "Attributes": Exceptional communication skills..., calm decisive leader..., strategic thinker...
Then "Annual Pay Range 185,400 - 210,000 USD"
Then "Application Window This opportunity is expected to remain posted through the date identified below, subject to business needs. 2026-09-26" (that's metadata; we can fold into short p or drop). Probably we can include as a short p.
Then "Thrive with Cotality At Cotality, we offer more than just a job, we provide a benefits experience designed to support your whole self. From a flexible working model to competitive time off and standout health coverage with meaningful perks and growth opportunities, our package is built to help you thrive at work and in life. Highlights, Depending On Role Classification, Include Time off: Generous PTO and 11 paid holidays, plus well-being and volunteer time off.Family Support: Up to 16 weeks of fully paid parental leave and a baby stipend.Health: Multiple medical plan options with mental health and wellness support offerings.Retirement: 401(k) with company match and vesting after one year.Financial Perks: $400 annual well-being stipend and tuition assistance up to $5,250.Extras: Recognition Rewards, Referral bonuses, exclusive discounts and more!"
That's benefits.
Then EEO boilerplate etc to remove.
Thus we need sections: About the role (intro), Responsibilities (key responsibilities), Qualifications (maybe combine Required Experience & Technical Skills and Preferred Qualifications and Attributes?), Benefits, Pay.
We should not create Schedule section because none.
We need to use
for each section heading.
Inside sections, we need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove duplicated lines.
Let's craft.
Section About the role: combine the introductory paragraphs (mission description and job description). Could be multiple paragraphs.
We'll put
for prose.
Section Responsibilities: we have bullet-like items but they are grouped under headings. We can create a
with each responsibility as - . Might need to preserve sub-bullets? The instruction says use
- for any list of duties/requirements/benefits. So we can flatten.
List items:
- Own the strategy, architecture, and optimization of the MFT Gateway utilizing IBM Sterling File Gateway; ensure the platform scales securely to meet business demands.
- Serve as the ultimate owner of all internal and external file transfer operations, ensuring secure, compliant, and efficient data routing, transformation, and delivery.
- Direct the ongoing engineering, maintenance, and support of the Legacy Electronic Data Exchange (EDE) application utilizing CLEO Harmony.
- Assess legacy systems to identify opportunities for optimization, consolidation, or strategic migration into the core Cotality Digital Gateway where appropriate.
- Build, mentor, and lead a high-performing, globally distributed team of software engineers, system administrators, and support personnel.
- Manage team capacity, vendor relationships, and onshore/offshore resource models to ensure efficient project delivery and continuous operational coverage.
- Oversee Level 1 through Level 3 production support across the entire Cotality Digital Gateway (CDG).
- Establish and enforce rigorous incident management, problem resolution, and escalation protocols; ensure all MFT operations meet or exceed strict Service Level Agreements (SLAs).
- Champion the implementation of proactive monitoring and alerting strategies to identify and resolve file transfer bottlenecks before they impact business operations.
That covers.
Section Qualifications: we have Required Experience & Technical Skills (list), Preferred Qualifications (list), Attributes (list). Could combine into one Qualifications section with subheadings? But we only allowed headings from list; we could still use
for Qualifications and then inside we can have for each bullet group maybe with headings? But we should not create extra headings beyond allowed? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside? It says use for section headings (e.g. ...). Likely they expect only those headings as top-level sections. Inside we can use
and
- . So we can put all qualification bullets in a single
list.
Thus combine:
- 10+ years of progressive experience in software engineering, B2B integration, and enterprise IT operations, with at least 5+ years in a leadership/management role.
- Deep technical understanding and proven experience managing, designing, or supporting IBM Sterling File Gateway (SFG), Sterling B2B Integrator, and related IBM MFT components.
- Strong working knowledge of CLEO Harmony or similar legacy MFT enterprise solutions.
- Demonstrated success in building, managing, and scaling hybrid engineering teams (onshore, offshore, and vendor resources) in a "follow-the-sun" support model.
- Extensive experience leading 24/7 production support operations, incident response, and root-cause analysis for mission-critical gateway environments.
- Deep knowledge of network protocols (SFTP, AS2, HTTPS, FTPS) and data security/compliance standards (encryption, PKI, certificates).
- Bachelor’s or Master’s degree in Computer Science, Information Technology, or a related field.
- Experience with Cloud environments (GCP preferred) and migrating legacy MFT workloads to the cloud.
- Strong financial acumen to manage department budgets, vendor contracts, and software licensing.
- Exceptional communication skills, with the ability to translate complex technical MFT concepts to non-technical business stakeholders.
- A calm, decisive leader during high-pressure critical incidents.
- A strategic thinker who balances long-term architectural vision with immediate operational stability.
That covers.
Section Benefits: we have bullet list.
List:
- Generous PTO and 11 paid holidays, plus well-being and volunteer time off.
- Up to 16 weeks of fully paid parental leave and a baby stipend.
- Multiple medical plan options with mental health and wellness support offerings.
- 401(k) with company match and vesting after one year.
- $400 annual well-being stipend and tuition assistance up to $5,250.
- Recognition Rewards, Referral bonuses, exclusive discounts and more.
- Flexible working model (mentioned earlier) maybe include as bullet? The paragraph says "From a flexible working model to competitive time off and standout health coverage...". Could add "Flexible working model". We'll include.
We'll also include "competitive time off" but we already have PTO.
We'll keep as list.
Section Pay: we have Annual Pay Range 185,400 - 210,000 USD. That's specific; we can create a Pay section with .
We should not include Schedule.
We also have Application Window date; we could fold into a short p maybe under About the role or separate? The instruction says fold minor metadata into a short
or drop it. So we can add a
after the sections maybe "Application window: open until 2026-09-26." But we need to avoid creating a section for it. We'll just add a
after Benefits maybe.
Now produce HTML fragment.
We must not include or tags, no markdown fences.
Let's craft:
About the role
At Cotality, we are driven by a single mission—to make the property industry faster, smarter, and more people-centric. Cotality is the trusted source for property intelligence, with unmatched precision, depth, breadth, and insights across the entire ecosystem. Our talented team of 5,000 employees globally uses our network, scale, connectivity and technology to drive the largest asset class in the world. Join us as we work toward our vision of fueling a thriving global property ecosystem and a more resilient society. Cotality is committed to cultivating a diverse and inclusive work culture that inspires innovation and bold thinking; it's a place where you can collaborate, feel valued, develop skills and directly impact the real estate economy. We know our people are our greatest asset. At Cotality, you can be yourself, lift people up and make an impact. By putting clients first and continuously innovating, we're working together to set the pace for unlocking new possibilities that better serve the property industry. Cotality is seeking a highly experienced and strategic Director of Software Engineering to lead our Digital Gateway initiatives. In this critical leadership role, you will hold ultimate responsibility for all file transfer operations across the organization. You will oversee the architecture, engineering, and 24/7 production support of our critical data exchange platforms, including our modern MFT Gateway and legacy EDE applications. The ideal candidate is a technical leader with deep expertise in managed file transfer (MFT) ecosystems, enterprise data exchange, and global
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a 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. We need to include sections where there is real content. Let's parse the posting: - Intro paragraph about Cotality mission etc. Could be "About the role" or maybe "About Cotality". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate headings. We have: Job Description: Cotality is seeking a highly experienced and strategic Director of Software Engineering to lead our Digital Gateway initiatives. In this critical leadership role, you will hold ultimate responsibility for all file transfer operations across the organization. You will oversee the architecture, engineering, and 24/7 production support of our critical data exchange platforms, including our modern MFT Gateway and legacy EDE applications. The ideal candidate is a technical leader with deep expertise in managed file transfer (MFT) ecosystems, enterprise data exchange, and global team management. You will direct a blended workforce of onshore and offshore engineering professionals to ensure the seamless, secure, and highly available operation of the Cotality Digital Gateway (CDG). That's like a summary; could be "About the role". Then "Key Responsibilities" with subpoints: Enterprise MFT & Gateway Leadership (IBM Sterling File Gateway, Overall File Transfer Operations), Legacy System Management (CLEO Harmony EDE, Modernization Strategy), Global Team Leadership & Management (Onshore & Offshore Alignment, Resource Allocation), Production Support & Operational Excellence (CDG Production Support, Incident & SLA Management, Monitoring & Alerting). These are duties. Then "Job Qualifications Required Experience & Technical Skills:" with bullet-like paragraphs: Experience: 10+ years..., IBM Sterling Expertise..., CLEO Harmony Experience..., Global Leadership..., Operational Management..., Protocols & Security:. Then "Preferred Qualifications": Bachelor’s or Master’s degree..., Experience with Cloud environments..., Strong financial acumen... Then "Attributes": Exceptional communication skills..., calm decisive leader..., strategic thinker... Then "Annual Pay Range 185,400 - 210,000 USD" Then "Application Window This opportunity is expected to remain posted through the date identified below, subject to business needs. 2026-09-26" (that's metadata; we can fold into short p or drop). Probably we can include as a short p. Then "Thrive with Cotality At Cotality, we offer more than just a job, we provide a benefits experience designed to support your whole self. From a flexible working model to competitive time off and standout health coverage with meaningful perks and growth opportunities, our package is built to help you thrive at work and in life. Highlights, Depending On Role Classification, Include Time off: Generous PTO and 11 paid holidays, plus well-being and volunteer time off.Family Support: Up to 16 weeks of fully paid parental leave and a baby stipend.Health: Multiple medical plan options with mental health and wellness support offerings.Retirement: 401(k) with company match and vesting after one year.Financial Perks: $400 annual well-being stipend and tuition assistance up to $5,250.Extras: Recognition Rewards, Referral bonuses, exclusive discounts and more!" That's benefits. Then EEO boilerplate etc to remove. Thus we need sections: About the role (intro), Responsibilities (key responsibilities), Qualifications (maybe combine Required Experience & Technical Skills and Preferred Qualifications and Attributes?), Benefits, Pay. We should not create Schedule section because none. We need to use
for each section heading.
Inside sections, we need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information; do not invent or summarize away detail.
We need to avoid filler like "commensurate with experience". Not present.
We need to remove duplicated lines.
Let's craft.
Section About the role: combine the introductory paragraphs (mission description and job description). Could be multiple paragraphs.
We'll put
for prose.
Section Responsibilities: we have bullet-like items but they are grouped under headings. We can create a
with each responsibility as - . Might need to preserve sub-bullets? The instruction says use
- for any list of duties/requirements/benefits. So we can flatten.
List items:
- Own the strategy, architecture, and optimization of the MFT Gateway utilizing IBM Sterling File Gateway; ensure the platform scales securely to meet business demands.
- Serve as the ultimate owner of all internal and external file transfer operations, ensuring secure, compliant, and efficient data routing, transformation, and delivery.
- Direct the ongoing engineering, maintenance, and support of the Legacy Electronic Data Exchange (EDE) application utilizing CLEO Harmony.
- Assess legacy systems to identify opportunities for optimization, consolidation, or strategic migration into the core Cotality Digital Gateway where appropriate.
- Build, mentor, and lead a high-performing, globally distributed team of software engineers, system administrators, and support personnel.
- Manage team capacity, vendor relationships, and onshore/offshore resource models to ensure efficient project delivery and continuous operational coverage.
- Oversee Level 1 through Level 3 production support across the entire Cotality Digital Gateway (CDG).
- Establish and enforce rigorous incident management, problem resolution, and escalation protocols; ensure all MFT operations meet or exceed strict Service Level Agreements (SLAs).
- Champion the implementation of proactive monitoring and alerting strategies to identify and resolve file transfer bottlenecks before they impact business operations.
That covers.
Section Qualifications: we have Required Experience & Technical Skills (list), Preferred Qualifications (list), Attributes (list). Could combine into one Qualifications section with subheadings? But we only allowed headings from list; we could still use
for Qualifications and then inside we can have for each bullet group maybe with headings? But we should not create extra headings beyond allowed? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside? It says use for section headings (e.g. ...). Likely they expect only those headings as top-level sections. Inside we can use
and
- . So we can put all qualification bullets in a single
list.
Thus combine:
- 10+ years of progressive experience in software engineering, B2B integration, and enterprise IT operations, with at least 5+ years in a leadership/management role.
- Deep technical understanding and proven experience managing, designing, or supporting IBM Sterling File Gateway (SFG), Sterling B2B Integrator, and related IBM MFT components.
- Strong working knowledge of CLEO Harmony or similar legacy MFT enterprise solutions.
- Demonstrated success in building, managing, and scaling hybrid engineering teams (onshore, offshore, and vendor resources) in a "follow-the-sun" support model.
- Extensive experience leading 24/7 production support operations, incident response, and root-cause analysis for mission-critical gateway environments.
- Deep knowledge of network protocols (SFTP, AS2, HTTPS, FTPS) and data security/compliance standards (encryption, PKI, certificates).
- Bachelor’s or Master’s degree in Computer Science, Information Technology, or a related field.
- Experience with Cloud environments (GCP preferred) and migrating legacy MFT workloads to the cloud.
- Strong financial acumen to manage department budgets, vendor contracts, and software licensing.
- Exceptional communication skills, with the ability to translate complex technical MFT concepts to non-technical business stakeholders.
- A calm, decisive leader during high-pressure critical incidents.
- A strategic thinker who balances long-term architectural vision with immediate operational stability.
That covers.
Section Benefits: we have bullet list.
List:
- Generous PTO and 11 paid holidays, plus well-being and volunteer time off.
- Up to 16 weeks of fully paid parental leave and a baby stipend.
- Multiple medical plan options with mental health and wellness support offerings.
- 401(k) with company match and vesting after one year.
- $400 annual well-being stipend and tuition assistance up to $5,250.
- Recognition Rewards, Referral bonuses, exclusive discounts and more.
- Flexible working model (mentioned earlier) maybe include as bullet? The paragraph says "From a flexible working model to competitive time off and standout health coverage...". Could add "Flexible working model". We'll include.
We'll also include "competitive time off" but we already have PTO.
We'll keep as list.
Section Pay: we have Annual Pay Range 185,400 - 210,000 USD. That's specific; we can create a Pay section with .
We should not include Schedule.
We also have Application Window date; we could fold into a short p maybe under About the role or separate? The instruction says fold minor metadata into a short
or drop it. So we can add a
after the sections maybe "Application window: open until 2026-09-26." But we need to avoid creating a section for it. We'll just add a
after Benefits maybe.
Now produce HTML fragment.
We must not include or tags, no markdown fences.
Let's craft:
About the role
At Cotality, we are driven by a single mission—to make the property industry faster, smarter, and more people-centric. Cotality is the trusted source for property intelligence, with unmatched precision, depth, breadth, and insights across the entire ecosystem. Our talented team of 5,000 employees globally uses our network, scale, connectivity and technology to drive the largest asset class in the world. Join us as we work toward our vision of fueling a thriving global property ecosystem and a more resilient society. Cotality is committed to cultivating a diverse and inclusive work culture that inspires innovation and bold thinking; it's a place where you can collaborate, feel valued, develop skills and directly impact the real estate economy. We know our people are our greatest asset. At Cotality, you can be yourself, lift people up and make an impact. By putting clients first and continuously innovating, we're working together to set the pace for unlocking new possibilities that better serve the property industry. Cotality is seeking a highly experienced and strategic Director of Software Engineering to lead our Digital Gateway initiatives. In this critical leadership role, you will hold ultimate responsibility for all file transfer operations across the organization. You will oversee the architecture, engineering, and 24/7 production support of our critical data exchange platforms, including our modern MFT Gateway and legacy EDE applications. The ideal candidate is a technical leader with deep expertise in managed file transfer (MFT) ecosystems, enterprise data exchange, and global
for prose. We need to preserve all substantive information; do not invent or summarize away detail. We need to avoid filler like "commensurate with experience". Not present. We need to remove duplicated lines. Let's craft. Section About the role: combine the introductory paragraphs (mission description and job description). Could be multiple paragraphs. We'll put
for prose. Section Responsibilities: we have bullet-like items but they are grouped under headings. We can create a
- with each responsibility as
- . Might need to preserve sub-bullets? The instruction says use
- for any list of duties/requirements/benefits. So we can flatten.
List items:
- Own the strategy, architecture, and optimization of the MFT Gateway utilizing IBM Sterling File Gateway; ensure the platform scales securely to meet business demands.
- Serve as the ultimate owner of all internal and external file transfer operations, ensuring secure, compliant, and efficient data routing, transformation, and delivery.
- Direct the ongoing engineering, maintenance, and support of the Legacy Electronic Data Exchange (EDE) application utilizing CLEO Harmony.
- Assess legacy systems to identify opportunities for optimization, consolidation, or strategic migration into the core Cotality Digital Gateway where appropriate.
- Build, mentor, and lead a high-performing, globally distributed team of software engineers, system administrators, and support personnel.
- Manage team capacity, vendor relationships, and onshore/offshore resource models to ensure efficient project delivery and continuous operational coverage.
- Oversee Level 1 through Level 3 production support across the entire Cotality Digital Gateway (CDG).
- Establish and enforce rigorous incident management, problem resolution, and escalation protocols; ensure all MFT operations meet or exceed strict Service Level Agreements (SLAs).
- Champion the implementation of proactive monitoring and alerting strategies to identify and resolve file transfer bottlenecks before they impact business operations.
That covers.
Section Qualifications: we have Required Experience & Technical Skills (list), Preferred Qualifications (list), Attributes (list). Could combine into one Qualifications section with subheadings? But we only allowed headings from list; we could still use
for Qualifications and then inside we can have
- for each bullet group maybe with
- . So we can put all qualification bullets in a single
- list.
Thus combine:
- 10+ years of progressive experience in software engineering, B2B integration, and enterprise IT operations, with at least 5+ years in a leadership/management role.
- Deep technical understanding and proven experience managing, designing, or supporting IBM Sterling File Gateway (SFG), Sterling B2B Integrator, and related IBM MFT components.
- Strong working knowledge of CLEO Harmony or similar legacy MFT enterprise solutions.
- Demonstrated success in building, managing, and scaling hybrid engineering teams (onshore, offshore, and vendor resources) in a "follow-the-sun" support model.
- Extensive experience leading 24/7 production support operations, incident response, and root-cause analysis for mission-critical gateway environments.
- Deep knowledge of network protocols (SFTP, AS2, HTTPS, FTPS) and data security/compliance standards (encryption, PKI, certificates).
- Bachelor’s or Master’s degree in Computer Science, Information Technology, or a related field.
- Experience with Cloud environments (GCP preferred) and migrating legacy MFT workloads to the cloud.
- Strong financial acumen to manage department budgets, vendor contracts, and software licensing.
- Exceptional communication skills, with the ability to translate complex technical MFT concepts to non-technical business stakeholders.
- A calm, decisive leader during high-pressure critical incidents.
- A strategic thinker who balances long-term architectural vision with immediate operational stability.
That covers.
Section Benefits: we have bullet list.
List:
- Generous PTO and 11 paid holidays, plus well-being and volunteer time off.
- Up to 16 weeks of fully paid parental leave and a baby stipend.
- Multiple medical plan options with mental health and wellness support offerings.
- 401(k) with company match and vesting after one year.
- $400 annual well-being stipend and tuition assistance up to $5,250.
- Recognition Rewards, Referral bonuses, exclusive discounts and more.
- Flexible working model (mentioned earlier) maybe include as bullet? The paragraph says "From a flexible working model to competitive time off and standout health coverage...". Could add "Flexible working model". We'll include.
We'll also include "competitive time off" but we already have PTO.
We'll keep as list.
Section Pay: we have Annual Pay Range 185,400 - 210,000 USD. That's specific; we can create a Pay section with
. We should not include Schedule. We also have Application Window date; we could fold into a short p maybe under About the role or separate? The instruction says fold minor metadata into a short
or drop it. So we can add a
after the sections maybe "Application window: open until 2026-09-26." But we need to avoid creating a section for it. We'll just add a
after Benefits maybe. Now produce HTML fragment. We must not include or tags, no markdown fences. Let's craft:
About the role
At Cotality, we are driven by a single mission—to make the property industry faster, smarter, and more people-centric. Cotality is the trusted source for property intelligence, with unmatched precision, depth, breadth, and insights across the entire ecosystem. Our talented team of 5,000 employees globally uses our network, scale, connectivity and technology to drive the largest asset class in the world. Join us as we work toward our vision of fueling a thriving global property ecosystem and a more resilient society. Cotality is committed to cultivating a diverse and inclusive work culture that inspires innovation and bold thinking; it's a place where you can collaborate, feel valued, develop skills and directly impact the real estate economy. We know our people are our greatest asset. At Cotality, you can be yourself, lift people up and make an impact. By putting clients first and continuously innovating, we're working together to set the pace for unlocking new possibilities that better serve the property industry. Cotality is seeking a highly experienced and strategic Director of Software Engineering to lead our Digital Gateway initiatives. In this critical leadership role, you will hold ultimate responsibility for all file transfer operations across the organization. You will oversee the architecture, engineering, and 24/7 production support of our critical data exchange platforms, including our modern MFT Gateway and legacy EDE applications. The ideal candidate is a technical leader with deep expertise in managed file transfer (MFT) ecosystems, enterprise data exchange, and global
headings? But we should not create extra headings beyond allowed? The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings inside? It says use
for section headings (e.g. ...). Likely they expect only those headings as top-level sections. Inside we can use
and
- . So we can put all qualification bullets in a single
- for any list of duties/requirements/benefits. So we can flatten.
List items:
- Own the strategy, architecture, and optimization of the MFT Gateway utilizing IBM Sterling File Gateway; ensure the platform scales securely to meet business demands.
- Serve as the ultimate owner of all internal and external file transfer operations, ensuring secure, compliant, and efficient data routing, transformation, and delivery.
- Direct the ongoing engineering, maintenance, and support of the Legacy Electronic Data Exchange (EDE) application utilizing CLEO Harmony.
- Assess legacy systems to identify opportunities for optimization, consolidation, or strategic migration into the core Cotality Digital Gateway where appropriate.
- Build, mentor, and lead a high-performing, globally distributed team of software engineers, system administrators, and support personnel.
- Manage team capacity, vendor relationships, and onshore/offshore resource models to ensure efficient project delivery and continuous operational coverage.
- Oversee Level 1 through Level 3 production support across the entire Cotality Digital Gateway (CDG).
- Establish and enforce rigorous incident management, problem resolution, and escalation protocols; ensure all MFT operations meet or exceed strict Service Level Agreements (SLAs).
- Champion the implementation of proactive monitoring and alerting strategies to identify and resolve file transfer bottlenecks before they impact business operations.
That covers.
Section Qualifications: we have Required Experience & Technical Skills (list), Preferred Qualifications (list), Attributes (list). Could combine into one Qualifications section with subheadings? But we only allowed headings from list; we could still use