Director, Platform Management
for each section heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate. No Pay/Schedule/Benefits unless present (none). So we will have sections: About the role (intro paragraph(s)), Responsibilities, Requirements (or Qualifications). Possibly Skills separate? The posting includes "Technical Skills & Competencies" with mandatory and preferable. Could combine into Requirements or Skills. The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate ones. We have responsibilities list, requirements list (education, experience, leadership, cloud, etc). Also technical skills list. Could make sections: About the role (intro), Responsibilities, Requirements (education/experience/leadership), Skills (technical skills). Ensure we only include sections with real content.
We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from posting.
Let's extract prose for About the role: first paragraph(s) before "Responsibilities:":
"We are seeking a strategic and experienced leader to drive our API Management Platform strategy and operations. In addition, lead the strategic development, deployment, and maintenance of our core software platforms and technology infrastructure. In this role, you will oversee a team of engineers and administrators, work with product engineering teams across JLL, negotiate with vendors, and ensure the reliability, security, and scalability of our API management core platform ecosystem. The ideal candidate will work closely with technical leaders and product development teams across JLL to prioritize enhancement requests while operating and maturing JLL’s Azure-based API management platform. Has deep experience on Microsoft Azure and AWS. Come up with a strategic plan to mature the platform while also driving portfolio initiatives, ensuring alignment with organizational goals and industry best practices. This role requires a visionary and organized approach to platform management, roadmap execution, and stakeholder management."
We need to keep that as prose in
. Possibly split into multiple paragraphs but one is fine.
Now Responsibilities: list after "Responsibilities:" includes bullet points each starting with a bold label? Actually they are sentences with colon. We'll extract each as list item.
Responsibilities items:
- API Management: Direct the governance, integration, and security of enterprise endpoints using Azure API Management (APIM). Work with product technical leads to prioritize and approve new platform features or enhancements. Take part in system development including analysis, coding, and testing.
- Application Lifecycles: Lead the roll-out, maintenance, integration, and upgrading of all enterprise software solutions.
- Security & Compliance: Enforce data protection protocols, identity access rules, backup schedules, and disaster recovery plans.
- Performance Monitoring: Maintain system uptime goals by establishing real-time monitoring workflows for bugs and latency. Help management to formulate group’s technology vision and set/enforce technical standards for the team. Consults with enterprise architecture group to develop documentation and communication materials to ensure accurate design standards and patterns are followed
- Team Management: Direct, mentor, and evaluate the performance of DevOps engineers, system administrators, and IT support leads. Mentors less experienced analysts on proper standards/techniques to improve their accuracy and efficiency. Articulates business requirements in sufficient detail such that a technical solution can be design and engineered. Provide on-going support to application used within the organization.
We need to keep each as
- with the full text.
Now Requirements/Education/Experience: after "Sound like you? To apply you need to be / have:" then "Education Experience & Education 12+ years IT experience Education: Bachelor’s degree in computer science, Information Technology, MIS, or equivalent experience in corporate IT, including deep hands-on familiarity with cloud environments. Leadership Experience: Minimum 4 years directly managing engineering teams, IT budgets, and technology vendors. Cloud & API Architecture: Deep expertise managing infrastructure platforms like Microsoft Azure, including practical knowledge of Azure APIM gateway deployment and policy configurations. Enterprise Software: Proven track record supporting ERP, CRM, or IAM tools like Salesforce, SAP, Okta, and Jira Communication: Exceptional ability to explain complex technical vulnerabilities and project roadmaps to executive leadership. Reliable, self-motivated, and self-disciplined individual capable of planning and executing multiple projects simultaneously within a fast-paced environment. Demonstrated ability to lead and develop teams and manage stakeholders globally across multiple project initiatives. Effective written and verbal communication skills, including technical writing. Excellent technical, analytical, project management and organizational skills."
We can treat these as list items under Requirements.
Now Technical Skills & Competencies: Mandatory list and Preferable list. We'll combine into Skills section with two sublists? Could just list all as items, maybe separate mandatory and preferable headings inside
? But we must use - for any list. Could have nested? Probably just a flat list. But we need to preserve distinction? Might be okay to list all items. However we should not lose the "Mandatory:" and "Preferable:" labels. Could include them as part of list item text.
Let's extract mandatory items:
- Expertise in API Management Platform (Apigee or Azure APIM or AWS APIM)
- Understanding of API management best practices, policy creation, authentication and authorization patterns
- Hands-on experience with Microsoft Azure infrastructure and services
- Proficiency in system monitoring, performance optimization, and troubleshooting
- Knowledge of security protocols, identity and access management (IAM), and data protection standards
- Experience with DevOps practices and CI/CD pipeline implementation
- Understanding of disaster recovery planning and business continuity protocols
- Ability to enforce technical standards and design patterns across engineering teams
- Experience managing enterprise software integrations (ERP, CRM, IAM tools)
- Strong stakeholder management and cross-functional collaboration skills
Preferable items:
- Familiarity with development of reusable frameworks and libraries to be used by multiple development teams
- Familiarity with Azure & AWS cloud native application architecture patterns
- API design concepts and development of various API types such as REST, GraphQL, and so on
- Experience with tools and best practices for secure application development
- AWS cloud platform experience and multi-cloud architecture knowledge
- Experience with enterprise tools like Salesforce, Okta, and Jira
- Knowledge of microservices architecture and containerization (Docker, Kubernetes)
- Familiarity with infrastructure as code (Terraform, ARM templates, Bicep)
- Experience with API gateway policy configuration and traffic management
- Understanding of OAuth 2.0, OpenID Connect, and modern authentication protocols
- Background in Agile/Scrum methodologies and sprint planning
- Experience mentoring technical teams and developing talent pipelines
- Certifications in Azure, AWS, or API management platforms
We'll include these as list items under Skills section.
Now produce HTML fragment:
About the role
...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- ...
...
Make sure no extra whitespace issues. Output only HTML.
Let's craft the prose exactly as given, preserving punctuation.
About the role paragraph: combine sentences.
"We are seeking a strategic and experienced leader to drive our API Management Platform strategy and operations. In addition, lead the strategic development, deployment, and maintenance of our core software platforms and technology infrastructure. In this role, you will oversee a team of engineers and administrators, work with product engineering teams across JLL, negotiate with vendors, and ensure the reliability, security, and scalability of our API management core platform ecosystem. The ideal candidate will work closely with technical leaders and product development teams across JLL to prioritize enhancement requests while operating and maturing JLL’s Azure-based API management platform. Has deep experience on Microsoft Azure and AWS. Come up with a strategic plan to mature the platform while also driving portfolio initiatives, ensuring alignment with organizational goals and industry best practices. This role requires a visionary and organized approach to platform management, roadmap execution, and stakeholder management."
Note: "Has deep experience..." seems fragment but we keep.
Now Responsibilities items: need to keep the colon and following text.
Let's list each:
1. "API Management: Direct the governance, integration, and security of enterprise endpoints using Azure API Management (APIM). Work with product technical leads to prioritize and approve new platform features or enhancements. Take part in system development including analysis, coding, and testing."
2. "Application Lifecycles: Lead the roll-out, maintenance, integration, and upgrading of all enterprise software solutions."
3. "Security & Compliance: Enforce data protection protocols, identity access rules, backup schedules, and disaster recovery plans."
4. "Performance Monitoring: Maintain system uptime goals by establishing real-time monitoring workflows for bugs and latency. Help management to formulate group’s technology vision and set/enforce technical standards for the team. Consults with enterprise architecture group to develop documentation and communication materials to ensure accurate design standards and patterns are followed"
5. "Team Management: Direct, mentor, and evaluate the performance of DevOps engineers, system administrators, and IT support leads. Mentors less experienced analysts on proper standards/techniques to improve their accuracy and efficiency. Articulates business requirements in sufficient detail such that a technical solution can be design and engineered. Provide on-going support to application used within the organization."
Now Requirements items: we need to parse each bullet after headings.
We have:
- "Education Experience & Education 12+ years IT experience Education: Bachelor’s degree in computer science, Information Technology, MIS, or equivalent experience in corporate IT, including deep hands-on familiarity with cloud environments."
Actually the text: "Education Experience & Education 12+ years IT experience Education: Bachelor’s degree in computer science, Information Technology, MIS, or equivalent experience in corporate IT, including deep hands-on familiarity with cloud environments."
Seems duplicated "Education Experience & Education". We'll keep as is.
- "Leadership Experience: Minimum 4 years directly managing engineering teams, IT budgets, and technology vendors."
- "Cloud & API Architecture: Deep expertise managing infrastructure platforms like Microsoft Azure, including practical knowledge of Azure APIM gateway deployment and policy configurations."
- "Enterprise Software: Proven track record supporting ERP, CRM, or IAM tools like Salesforce, SAP, Okta, and Jira"
- "Communication: Exceptional ability to explain complex technical vulnerabilities and project roadmaps to executive leadership."
- "Reliable, self-motivated, and self-disciplined individual capable of planning and executing multiple projects simultaneously within a fast-paced environment."
- "Demonstrated ability to lead and develop teams and manage stakeholders globally across multiple project initiatives."
- "Effective written and verbal communication skills, including technical writing."
- "Excellent technical, analytical, project management and organizational skills."
Now Skills items: mandatory and preferable.
We'll list them as separate items.
Mandatory:
- "Expertise in API Management Platform (Apigee or Azure APIM or AWS APIM)"
- "Understanding of API management best practices, policy creation, authentication and authorization patterns"
- "Hands-on experience with Microsoft Azure infrastructure and services"
- "Proficiency in system monitoring, performance optimization, and troubleshooting"
- "Knowledge of security protocols, identity and access management (IAM), and data protection standards"
- "Experience with DevOps practices and CI/CD pipeline implementation"
- "Understanding of disaster recovery planning and business continuity protocols"
- "Ability to enforce technical standards and design patterns across engineering teams"
- "Experience managing enterprise software integrations (ERP, CRM, IAM tools)"
- "Strong stakeholder management and cross-functional collaboration skills"
Preferable:
- "Familiarity with development of reusable frameworks and libraries to be used by multiple development teams"
- "Familiarity with Azure & AWS cloud native application architecture patterns"
- "API design
for prose. Do NOT repeat job title as heading. Do NOT include Job ID etc. Remove boilerplate. No Pay/Schedule/Benefits unless present (none). So we will have sections: About the role (intro paragraph(s)), Responsibilities, Requirements (or Qualifications). Possibly Skills separate? The posting includes "Technical Skills & Competencies" with mandatory and preferable. Could combine into Requirements or Skills. The instruction: Use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose appropriate ones. We have responsibilities list, requirements list (education, experience, leadership, cloud, etc). Also technical skills list. Could make sections: About the role (intro), Responsibilities, Requirements (education/experience/leadership), Skills (technical skills). Ensure we only include sections with real content. We must preserve all substantive information, not invent or summarize away detail. So we need to include all details from posting. Let's extract prose for About the role: first paragraph(s) before "Responsibilities:": "We are seeking a strategic and experienced leader to drive our API Management Platform strategy and operations. In addition, lead the strategic development, deployment, and maintenance of our core software platforms and technology infrastructure. In this role, you will oversee a team of engineers and administrators, work with product engineering teams across JLL, negotiate with vendors, and ensure the reliability, security, and scalability of our API management core platform ecosystem. The ideal candidate will work closely with technical leaders and product development teams across JLL to prioritize enhancement requests while operating and maturing JLL’s Azure-based API management platform. Has deep experience on Microsoft Azure and AWS. Come up with a strategic plan to mature the platform while also driving portfolio initiatives, ensuring alignment with organizational goals and industry best practices. This role requires a visionary and organized approach to platform management, roadmap execution, and stakeholder management." We need to keep that as prose in
. Possibly split into multiple paragraphs but one is fine. Now Responsibilities: list after "Responsibilities:" includes bullet points each starting with a bold label? Actually they are sentences with colon. We'll extract each as list item. Responsibilities items: - API Management: Direct the governance, integration, and security of enterprise endpoints using Azure API Management (APIM). Work with product technical leads to prioritize and approve new platform features or enhancements. Take part in system development including analysis, coding, and testing. - Application Lifecycles: Lead the roll-out, maintenance, integration, and upgrading of all enterprise software solutions. - Security & Compliance: Enforce data protection protocols, identity access rules, backup schedules, and disaster recovery plans. - Performance Monitoring: Maintain system uptime goals by establishing real-time monitoring workflows for bugs and latency. Help management to formulate group’s technology vision and set/enforce technical standards for the team. Consults with enterprise architecture group to develop documentation and communication materials to ensure accurate design standards and patterns are followed - Team Management: Direct, mentor, and evaluate the performance of DevOps engineers, system administrators, and IT support leads. Mentors less experienced analysts on proper standards/techniques to improve their accuracy and efficiency. Articulates business requirements in sufficient detail such that a technical solution can be design and engineered. Provide on-going support to application used within the organization. We need to keep each as
- ? But we must use
- for any list. Could have nested? Probably just a flat list. But we need to preserve distinction? Might be okay to list all items. However we should not lose the "Mandatory:" and "Preferable:" labels. Could include them as part of list item text.
Let's extract mandatory items:
- Expertise in API Management Platform (Apigee or Azure APIM or AWS APIM)
- Understanding of API management best practices, policy creation, authentication and authorization patterns
- Hands-on experience with Microsoft Azure infrastructure and services
- Proficiency in system monitoring, performance optimization, and troubleshooting
- Knowledge of security protocols, identity and access management (IAM), and data protection standards
- Experience with DevOps practices and CI/CD pipeline implementation
- Understanding of disaster recovery planning and business continuity protocols
- Ability to enforce technical standards and design patterns across engineering teams
- Experience managing enterprise software integrations (ERP, CRM, IAM tools)
- Strong stakeholder management and cross-functional collaboration skills
Preferable items:
- Familiarity with development of reusable frameworks and libraries to be used by multiple development teams
- Familiarity with Azure & AWS cloud native application architecture patterns
- API design concepts and development of various API types such as REST, GraphQL, and so on
- Experience with tools and best practices for secure application development
- AWS cloud platform experience and multi-cloud architecture knowledge
- Experience with enterprise tools like Salesforce, Okta, and Jira
- Knowledge of microservices architecture and containerization (Docker, Kubernetes)
- Familiarity with infrastructure as code (Terraform, ARM templates, Bicep)
- Experience with API gateway policy configuration and traffic management
- Understanding of OAuth 2.0, OpenID Connect, and modern authentication protocols
- Background in Agile/Scrum methodologies and sprint planning
- Experience mentoring technical teams and developing talent pipelines
- Certifications in Azure, AWS, or API management platforms
We'll include these as list items under Skills section.
Now produce HTML fragment:
About the role
...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- ... ...