Mainframe Technical Specialist
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We need to decide what constitutes a list. Many bullet-like sentences are separated by periods. We could treat each sentence as a list item? The instruction: "Use
- for any list of duties/requirements/benefits". So we need to identify lists. The posting has sections like "Key Responsibilities" with many sentences each starting with a verb. Those are duties. So we should make a
with each duty as - . Similarly for "Required Technical Skills" maybe list. Also "Preferred Skills". Also "Production Support Responsibilities". Also "Technical Leadership". Also "Required Qualifications". Also "Preferred Qualifications". Also "Soft Skills". Also "What You Will Do". Also "Mainframe Modernization Experience". Also "Experience With Modernization Initiatives Is Highly Desirable, Including ..." That's a list.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include each point as is.
We must not include boilerplate: Equal Opportunity, How to Apply, etc. Also remove duplicated lines.
We need to decide headings: About the role (from Job Overview). Responsibilities (maybe combine Key Responsibilities, Production Support Responsibilities, Technical Leadership? But we could have separate sections if they have distinct content. However instruction: "Prefer a few substantive sections over many thin ones." So we could combine similar content under Responsibilities. But we must preserve all detail; combining is okay as long as we don't lose detail. We could have a single Responsibilities section containing all duty-related bullet points from Key Responsibilities, Production Support Responsibilities, Technical Leadership, What You Will Do, Mainframe Modernization Experience, etc. That might be many items but still one section.
Similarly, Requirements could combine Required Technical Skills, Required Qualifications, maybe also Preferred Qualifications? But Preferred Qualifications is separate; we could put under Skills or Requirements? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate headings for Requirements, Qualifications, Skills. So we should follow that: Requirements (maybe mandatory technical skills), Qualifications (education/experience), Skills (preferred/soft skills). But we need to decide mapping.
Let's parse:
- Job Overview: prose.
- Key Responsibilities: list of duties.
- Required Technical Skills: list (Mainframe Technologies, Programming & Database, Production Support, Tools & Utilities). This could go under Requirements.
- Preferred Skills: list (Experience with CICS..., Strong knowledge..., etc). This could go under Skills.
- Mainframe Modernization Experience: list (Experience With Modernization Initiatives Is Highly Desirable, Including ...). Could go under Skills or maybe under Responsibilities? It's more like desired experience; could be Skills.
- Technical Leadership: list of expectations. Could be under Responsibilities or Skills? It's about role expectations; maybe Responsibilities.
- Production Support Responsibilities: list. Could be under Responsibilities.
- Required Qualifications: list (Bachelor's degree, 8+ years, etc). This is Qualifications.
- Preferred Qualifications: list (10+ years, experience in banking..., etc). Could be under Qualifications as preferred.
- Soft Skills: list. Could be under Skills.
- What You Will Do: prose (similar to responsibilities). Could be under Responsibilities.
- Mainframe Modernization Experience: already covered.
Thus we can structure:
About the role
Job Overview text.
Responsibilities
- each duty from Key Responsibilities, Production Support Responsibilities, Technical Leadership, What You Will Do, Mainframe Modernization Experience (the bullet list items). Need to ensure we capture each distinct sentence.
We must be careful not to lose any detail. Let's extract all duty-like sentences.
From Key Responsibilities (the block after "Key Responsibilities"):
- Design, develop, enhance, and maintain enterprise mainframe applications.
- Analyze business and technical requirements and translate them into scalable mainframe solutions.
- Develop and maintain COBOL programs, JCL, DB2 queries, CICS transactions, and VSAM files.
- Perform application troubleshooting, debugging, root-cause analysis, and production support.
- Analyze system and application failures and implement permanent corrective solutions.
- Develop and optimize batch processing jobs and production workflows.
- Monitor batch jobs, resolve job failures, and ensure successful completion of critical processing.
- Work with production support teams to resolve high-priority incidents and service-impacting issues.
- Participate in application modernization and mainframe transformation initiatives.
- Perform code reviews and ensure development standards and best practices are followed.
- Analyze application performance and identify opportunities for optimization.
- Develop technical specifications, design documents, and implementation plans.
- Perform unit testing, integration testing, regression testing, and production validation.
- Coordinate with QA teams to resolve defects and support testing activities.
- Work with DBAs on DB2 performance, SQL optimization, database design, and data-related issues.
- Work with system administrators and infrastructure teams on z/OS-related issues.
- Participate in production deployments, release management, and change-management activities.
- Provide technical guidance and mentoring to junior developers.
- Participate in on-call or after-hours production support when required.
- Maintain technical documentation, application diagrams, support procedures, and knowledge articles.
- Ensure compliance with enterprise security, audit, and change-control requirements.
From Production Support Responsibilities:
- Provide Level 2/Level 3 production support.
- Monitor critical batch and online applications.
- Investigate application abends and system failures.
- Analyze logs, dumps, job output, and system messages.
- Identify recurring production issues and implement permanent fixes.
- Participate in incident, problem, and change-management processes.
- Support critical production releases and emergency fixes.
- Participate in an on-call rotation when required.
- Communicate technical issues and resolution status to stakeholders.
From Technical Leadership:
- Provide technical direction to development and support teams.
- Review technical designs and proposed solutions.
- Identify technical risks and recommend mitigation strategies.
- Assist with estimation and technical planning.
- Mentor junior and mid-level developers.
- Establish coding, testing, and documentation standards.
- Participate in architecture and solution-design discussions.
- Coordinate technical activities across multiple teams.
From What You Will Do (prose): "In this role, you will be responsible for maintaining and enhancing critical enterprise mainframe applications while ensuring system reliability and performance. You will work across development, production support, database, infrastructure, QA, and business teams to deliver stable and scalable solutions. The ideal candidate is a hands-on technical professional who can independently troubleshoot complex mainframe issues, develop high-quality solutions, and provide technical leadership when required."
We could break that into list items? It's prose; maybe we keep as
under Responsibilities? But instruction: Use
- for any list of duties/requirements/benefits. This is not a list but prose. Could be
. However we already have a list for duties; we could add this as a
before or after list. But to preserve all info, we could include as a
inside Responsibilities section.
From Mainframe Modernization Experience: "Experience With Modernization Initiatives Is Highly Desirable, Including Mainframe application modernizationAPI enablementMainframe-to-cloud integrationMicroservices integrationLegacy application transformationData modernizationMainframe DevOpsAutomated testing and deploymentIntegration with Java, REST APIs, or distributed applications"
That seems like a list but missing punctuation. We can split by the capitalized words? Actually it's a sentence: "Experience With Modernization Initiatives Is Highly Desirable, Including Mainframe application modernizationAPI enablementMainframe-to-cloud integrationMicroservices integrationLegacy application transformationData modernizationMainframe DevOpsAutomated testing and deploymentIntegration with Java, REST APIs, or distributed applications". It's a bit messy. We could treat as a single sentence
. But better to split into items: Mainframe application modernization, API enablement, Mainframe-to-cloud integration, Microservices integration, Legacy application transformation, Data modernization, Mainframe DevOps, Automated testing and deployment, Integration with Java, REST APIs, or distributed applications.
We'll make list items.
Now Requirements section: Should contain Required Technical Skills (maybe broken into sublists). But we can just make a flat list of each bullet.
Required Technical Skills block includes:
Mainframe Technologies
- IBM z/OS
- COBOL
- JCL
- DB2
- CICS
- VSAM
- TSO/ISPF
- SDSF
Programming & Database
- Strong COBOL programming experience
- Strong JCL development and troubleshooting
- DB2 SQL
- Stored procedures and database utilities
- File handling and VSAM
- Batch and online transaction processing
Production Support
- Production incident management
- Job monitoring and troubleshooting
- Abend analysis
- Root-cause analysis
- Performance troubleshooting
- Batch scheduling
- Production deployment and release support
Tools & Utilities
- Experience with some or all of the following is preferred: Endevor
- ChangeMan
- CA7 / Control-M
- File-AID
- Abend-AID
- SPUFI
- QMF
- IDCAMS
- DFSORT / SORT
- TRA
- CFIBM utilities (maybe "TRA CFIBM utilities"? Actually original: "TRA CFIBM utilities"? It says "TRA CFIBM utilities"? Let's copy: "TRA CFIBM utilities". We'll keep as is.)
We need to preserve each item.
Now Preferred Skills block:
- Experience with CICS application development and troubleshooting.
- Strong knowledge of DB2 database architecture and SQL performance tuning.
- Experience with large-scale batch processing environments.
- Experience supporting high-volume transaction-processing applications.
- Knowledge of mainframe security and RACF.
- Experience with enterprise scheduling tools such as Control-M or CA7.
- Experience with source-code management and deployment tools such as Endevor or ChangeMan.
- Exposure to mainframe modernization initiatives.
- Knowledge of APIs, web services, or integration between mainframe and distributed platforms.
- Experience working with Agile/Scrum development teams.
- Familiarity with DevOps practices and automated deployment processes is a plus.
Now Soft Skills block:
- Strong problem-solving and analytical abilities.
- Excellent written and verbal communication.
- Strong troubleshooting skills.
- Ability to work effectively with technical and business teams.
- Strong ownership and accountability.
- Ability to work under pressure during production incidents.
- Attention to detail.
- Strong documentation skills.
- Ability to mentor and collaborate with team members.
Now Required Qualifications block:
- Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field, or equivalent professional experience.
- 8+ years of hands-on Mainframe development and support experience.
- Strong experience with COBOL, JCL, DB2, CICS, and VSAM.
- Strong understanding of IBM z/OS environments.
- Experience troubleshooting complex production issues.
- Strong analytical and problem-solving skills.
- Excellent communication and collaboration skills.
- Ability to work independently in a large enterprise environment.
- Ability to manage multiple
for prose. We need to decide what constitutes a list. Many bullet-like sentences are separated by periods. We could treat each sentence as a list item? The instruction: "Use
- for any list of duties/requirements/benefits". So we need to identify lists. The posting has sections like "Key Responsibilities" with many sentences each starting with a verb. Those are duties. So we should make a
- with each duty as
- . Similarly for "Required Technical Skills" maybe list. Also "Preferred Skills". Also "Production Support Responsibilities". Also "Technical Leadership". Also "Required Qualifications". Also "Preferred Qualifications". Also "Soft Skills". Also "What You Will Do". Also "Mainframe Modernization Experience". Also "Experience With Modernization Initiatives Is Highly Desirable, Including ..." That's a list.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include each point as is.
We must not include boilerplate: Equal Opportunity, How to Apply, etc. Also remove duplicated lines.
We need to decide headings: About the role (from Job Overview). Responsibilities (maybe combine Key Responsibilities, Production Support Responsibilities, Technical Leadership? But we could have separate sections if they have distinct content. However instruction: "Prefer a few substantive sections over many thin ones." So we could combine similar content under Responsibilities. But we must preserve all detail; combining is okay as long as we don't lose detail. We could have a single Responsibilities section containing all duty-related bullet points from Key Responsibilities, Production Support Responsibilities, Technical Leadership, What You Will Do, Mainframe Modernization Experience, etc. That might be many items but still one section.
Similarly, Requirements could combine Required Technical Skills, Required Qualifications, maybe also Preferred Qualifications? But Preferred Qualifications is separate; we could put under Skills or Requirements? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate headings for Requirements, Qualifications, Skills. So we should follow that: Requirements (maybe mandatory technical skills), Qualifications (education/experience), Skills (preferred/soft skills). But we need to decide mapping.
Let's parse:
- Job Overview: prose.
- Key Responsibilities: list of duties.
- Required Technical Skills: list (Mainframe Technologies, Programming & Database, Production Support, Tools & Utilities). This could go under Requirements.
- Preferred Skills: list (Experience with CICS..., Strong knowledge..., etc). This could go under Skills.
- Mainframe Modernization Experience: list (Experience With Modernization Initiatives Is Highly Desirable, Including ...). Could go under Skills or maybe under Responsibilities? It's more like desired experience; could be Skills.
- Technical Leadership: list of expectations. Could be under Responsibilities or Skills? It's about role expectations; maybe Responsibilities.
- Production Support Responsibilities: list. Could be under Responsibilities.
- Required Qualifications: list (Bachelor's degree, 8+ years, etc). This is Qualifications.
- Preferred Qualifications: list (10+ years, experience in banking..., etc). Could be under Qualifications as preferred.
- Soft Skills: list. Could be under Skills.
- What You Will Do: prose (similar to responsibilities). Could be under Responsibilities.
- Mainframe Modernization Experience: already covered.
Thus we can structure:
About the role
Job Overview text.
Responsibilities
- each duty from Key Responsibilities, Production Support Responsibilities, Technical Leadership, What You Will Do, Mainframe Modernization Experience (the bullet list items). Need to ensure we capture each distinct sentence.
We must be careful not to lose any detail. Let's extract all duty-like sentences.
From Key Responsibilities (the block after "Key Responsibilities"):
- Design, develop, enhance, and maintain enterprise mainframe applications.
- Analyze business and technical requirements and translate them into scalable mainframe solutions.
- Develop and maintain COBOL programs, JCL, DB2 queries, CICS transactions, and VSAM files.
- Perform application troubleshooting, debugging, root-cause analysis, and production support.
- Analyze system and application failures and implement permanent corrective solutions.
- Develop and optimize batch processing jobs and production workflows.
- Monitor batch jobs, resolve job failures, and ensure successful completion of critical processing.
- Work with production support teams to resolve high-priority incidents and service-impacting issues.
- Participate in application modernization and mainframe transformation initiatives.
- Perform code reviews and ensure development standards and best practices are followed.
- Analyze application performance and identify opportunities for optimization.
- Develop technical specifications, design documents, and implementation plans.
- Perform unit testing, integration testing, regression testing, and production validation.
- Coordinate with QA teams to resolve defects and support testing activities.
- Work with DBAs on DB2 performance, SQL optimization, database design, and data-related issues.
- Work with system administrators and infrastructure teams on z/OS-related issues.
- Participate in production deployments, release management, and change-management activities.
- Provide technical guidance and mentoring to junior developers.
- Participate in on-call or after-hours production support when required.
- Maintain technical documentation, application diagrams, support procedures, and knowledge articles.
- Ensure compliance with enterprise security, audit, and change-control requirements.
From Production Support Responsibilities:
- Provide Level 2/Level 3 production support.
- Monitor critical batch and online applications.
- Investigate application abends and system failures.
- Analyze logs, dumps, job output, and system messages.
- Identify recurring production issues and implement permanent fixes.
- Participate in incident, problem, and change-management processes.
- Support critical production releases and emergency fixes.
- Participate in an on-call rotation when required.
- Communicate technical issues and resolution status to stakeholders.
From Technical Leadership:
- Provide technical direction to development and support teams.
- Review technical designs and proposed solutions.
- Identify technical risks and recommend mitigation strategies.
- Assist with estimation and technical planning.
- Mentor junior and mid-level developers.
- Establish coding, testing, and documentation standards.
- Participate in architecture and solution-design discussions.
- Coordinate technical activities across multiple teams.
From What You Will Do (prose): "In this role, you will be responsible for maintaining and enhancing critical enterprise mainframe applications while ensuring system reliability and performance. You will work across development, production support, database, infrastructure, QA, and business teams to deliver stable and scalable solutions. The ideal candidate is a hands-on technical professional who can independently troubleshoot complex mainframe issues, develop high-quality solutions, and provide technical leadership when required."
We could break that into list items? It's prose; maybe we keep as
under Responsibilities? But instruction: Use
- for any list of duties/requirements/benefits. This is not a list but prose. Could be
. However we already have a list for duties; we could add this as a
before or after list. But to preserve all info, we could include as a
inside Responsibilities section. From Mainframe Modernization Experience: "Experience With Modernization Initiatives Is Highly Desirable, Including Mainframe application modernizationAPI enablementMainframe-to-cloud integrationMicroservices integrationLegacy application transformationData modernizationMainframe DevOpsAutomated testing and deploymentIntegration with Java, REST APIs, or distributed applications" That seems like a list but missing punctuation. We can split by the capitalized words? Actually it's a sentence: "Experience With Modernization Initiatives Is Highly Desirable, Including Mainframe application modernizationAPI enablementMainframe-to-cloud integrationMicroservices integrationLegacy application transformationData modernizationMainframe DevOpsAutomated testing and deploymentIntegration with Java, REST APIs, or distributed applications". It's a bit messy. We could treat as a single sentence
. But better to split into items: Mainframe application modernization, API enablement, Mainframe-to-cloud integration, Microservices integration, Legacy application transformation, Data modernization, Mainframe DevOps, Automated testing and deployment, Integration with Java, REST APIs, or distributed applications. We'll make list items. Now Requirements section: Should contain Required Technical Skills (maybe broken into sublists). But we can just make a flat list of each bullet. Required Technical Skills block includes: Mainframe Technologies - IBM z/OS - COBOL - JCL - DB2 - CICS - VSAM - TSO/ISPF - SDSF Programming & Database - Strong COBOL programming experience - Strong JCL development and troubleshooting - DB2 SQL - Stored procedures and database utilities - File handling and VSAM - Batch and online transaction processing Production Support - Production incident management - Job monitoring and troubleshooting - Abend analysis - Root-cause analysis - Performance troubleshooting - Batch scheduling - Production deployment and release support Tools & Utilities - Experience with some or all of the following is preferred: Endevor - ChangeMan - CA7 / Control-M - File-AID - Abend-AID - SPUFI - QMF - IDCAMS - DFSORT / SORT - TRA - CFIBM utilities (maybe "TRA CFIBM utilities"? Actually original: "TRA CFIBM utilities"? It says "TRA CFIBM utilities"? Let's copy: "TRA CFIBM utilities". We'll keep as is.) We need to preserve each item. Now Preferred Skills block: - Experience with CICS application development and troubleshooting. - Strong knowledge of DB2 database architecture and SQL performance tuning. - Experience with large-scale batch processing environments. - Experience supporting high-volume transaction-processing applications. - Knowledge of mainframe security and RACF. - Experience with enterprise scheduling tools such as Control-M or CA7. - Experience with source-code management and deployment tools such as Endevor or ChangeMan. - Exposure to mainframe modernization initiatives. - Knowledge of APIs, web services, or integration between mainframe and distributed platforms. - Experience working with Agile/Scrum development teams. - Familiarity with DevOps practices and automated deployment processes is a plus. Now Soft Skills block: - Strong problem-solving and analytical abilities. - Excellent written and verbal communication. - Strong troubleshooting skills. - Ability to work effectively with technical and business teams. - Strong ownership and accountability. - Ability to work under pressure during production incidents. - Attention to detail. - Strong documentation skills. - Ability to mentor and collaborate with team members. Now Required Qualifications block: - Bachelor's degree in Computer Science, Information Technology, Engineering, or a related field, or equivalent professional experience. - 8+ years of hands-on Mainframe development and support experience. - Strong experience with COBOL, JCL, DB2, CICS, and VSAM. - Strong understanding of IBM z/OS environments. - Experience troubleshooting complex production issues. - Strong analytical and problem-solving skills. - Excellent communication and collaboration skills. - Ability to work independently in a large enterprise environment. - Ability to manage multiple
- for any list of duties/requirements/benefits. This is not a list but prose. Could be
- each duty from Key Responsibilities, Production Support Responsibilities, Technical Leadership, What You Will Do, Mainframe Modernization Experience (the bullet list items). Need to ensure we capture each distinct sentence.
We must be careful not to lose any detail. Let's extract all duty-like sentences.
From Key Responsibilities (the block after "Key Responsibilities"):
- Design, develop, enhance, and maintain enterprise mainframe applications.
- Analyze business and technical requirements and translate them into scalable mainframe solutions.
- Develop and maintain COBOL programs, JCL, DB2 queries, CICS transactions, and VSAM files.
- Perform application troubleshooting, debugging, root-cause analysis, and production support.
- Analyze system and application failures and implement permanent corrective solutions.
- Develop and optimize batch processing jobs and production workflows.
- Monitor batch jobs, resolve job failures, and ensure successful completion of critical processing.
- Work with production support teams to resolve high-priority incidents and service-impacting issues.
- Participate in application modernization and mainframe transformation initiatives.
- Perform code reviews and ensure development standards and best practices are followed.
- Analyze application performance and identify opportunities for optimization.
- Develop technical specifications, design documents, and implementation plans.
- Perform unit testing, integration testing, regression testing, and production validation.
- Coordinate with QA teams to resolve defects and support testing activities.
- Work with DBAs on DB2 performance, SQL optimization, database design, and data-related issues.
- Work with system administrators and infrastructure teams on z/OS-related issues.
- Participate in production deployments, release management, and change-management activities.
- Provide technical guidance and mentoring to junior developers.
- Participate in on-call or after-hours production support when required.
- Maintain technical documentation, application diagrams, support procedures, and knowledge articles.
- Ensure compliance with enterprise security, audit, and change-control requirements.
From Production Support Responsibilities:
- Provide Level 2/Level 3 production support.
- Monitor critical batch and online applications.
- Investigate application abends and system failures.
- Analyze logs, dumps, job output, and system messages.
- Identify recurring production issues and implement permanent fixes.
- Participate in incident, problem, and change-management processes.
- Support critical production releases and emergency fixes.
- Participate in an on-call rotation when required.
- Communicate technical issues and resolution status to stakeholders.
From Technical Leadership:
- Provide technical direction to development and support teams.
- Review technical designs and proposed solutions.
- Identify technical risks and recommend mitigation strategies.
- Assist with estimation and technical planning.
- Mentor junior and mid-level developers.
- Establish coding, testing, and documentation standards.
- Participate in architecture and solution-design discussions.
- Coordinate technical activities across multiple teams.
From What You Will Do (prose): "In this role, you will be responsible for maintaining and enhancing critical enterprise mainframe applications while ensuring system reliability and performance. You will work across development, production support, database, infrastructure, QA, and business teams to deliver stable and scalable solutions. The ideal candidate is a hands-on technical professional who can independently troubleshoot complex mainframe issues, develop high-quality solutions, and provide technical leadership when required."
We could break that into list items? It's prose; maybe we keep as
- . Similarly for "Required Technical Skills" maybe list. Also "Preferred Skills". Also "Production Support Responsibilities". Also "Technical Leadership". Also "Required Qualifications". Also "Preferred Qualifications". Also "Soft Skills". Also "What You Will Do". Also "Mainframe Modernization Experience". Also "Experience With Modernization Initiatives Is Highly Desirable, Including ..." That's a list.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include each point as is.
We must not include boilerplate: Equal Opportunity, How to Apply, etc. Also remove duplicated lines.
We need to decide headings: About the role (from Job Overview). Responsibilities (maybe combine Key Responsibilities, Production Support Responsibilities, Technical Leadership? But we could have separate sections if they have distinct content. However instruction: "Prefer a few substantive sections over many thin ones." So we could combine similar content under Responsibilities. But we must preserve all detail; combining is okay as long as we don't lose detail. We could have a single Responsibilities section containing all duty-related bullet points from Key Responsibilities, Production Support Responsibilities, Technical Leadership, What You Will Do, Mainframe Modernization Experience, etc. That might be many items but still one section.
Similarly, Requirements could combine Required Technical Skills, Required Qualifications, maybe also Preferred Qualifications? But Preferred Qualifications is separate; we could put under Skills or Requirements? The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we have separate headings for Requirements, Qualifications, Skills. So we should follow that: Requirements (maybe mandatory technical skills), Qualifications (education/experience), Skills (preferred/soft skills). But we need to decide mapping.
Let's parse:
- Job Overview: prose.
- Key Responsibilities: list of duties.
- Required Technical Skills: list (Mainframe Technologies, Programming & Database, Production Support, Tools & Utilities). This could go under Requirements.
- Preferred Skills: list (Experience with CICS..., Strong knowledge..., etc). This could go under Skills.
- Mainframe Modernization Experience: list (Experience With Modernization Initiatives Is Highly Desirable, Including ...). Could go under Skills or maybe under Responsibilities? It's more like desired experience; could be Skills.
- Technical Leadership: list of expectations. Could be under Responsibilities or Skills? It's about role expectations; maybe Responsibilities.
- Production Support Responsibilities: list. Could be under Responsibilities.
- Required Qualifications: list (Bachelor's degree, 8+ years, etc). This is Qualifications.
- Preferred Qualifications: list (10+ years, experience in banking..., etc). Could be under Qualifications as preferred.
- Soft Skills: list. Could be under Skills.
- What You Will Do: prose (similar to responsibilities). Could be under Responsibilities.
- Mainframe Modernization Experience: already covered.
Thus we can structure: