MQ Integration Engineer/Architect

We need to output HTML fragment with sections only if content present. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to extract relevant content. The posting includes: - Intro: Stefanini Group is hiring! ... MQ Integration Engineer/Architect for various locations (Hybrid). Contact info etc. Should we include contact? Probably not as it's application instruction; we should remove application instructions. The contact info is application instruction; we should drop it. - Description: "This is an exciting opportunity to work with and broadly apply your MQ engineering skills across various technology solution efforts, as well as build your skills in other areas by being exposed to various aspects from inception through design, build, and deployment. You will be a 'jack-of-all-trades' - working cross-functionally with Architects, Engineers, Business Analysts, and Service Managers across multiple teams in a rapidly evolving environment - completing design documentation, consulting with other engineers and architects, completing network and server build requests, installing and configuring software, etc. To be successful in this role, you must be an organized self-starter with stellar leadership and communication skills who can work independently, building relationships and driving technical solutions from inception to completion. This position requires the candidate to have strong MQ architect/integration experience and the candidate must be technically savvy, with a proven ability to work well in a highly dynamic environment and maintain a strong relationship with our customers and partners. This is an Integration Engineer/MQ Architect role requiring deep, advanced knowledge of IBM MQ and IBM MFTPractical experience with Infrastructure as Code (IaC - Terraform, packer etc.) is requiredExperience in Cloud infrastructure and DevOps is required" Then "Responsibilities:" then list of required skills? Actually after "Responsibilities:" they list "Required Skills Ability to coordinate and work with diverse groups of subject matter experts..." etc. That seems like responsibilities/skills. Then "Preferred Skills Working knowledge of other technology solutions/products such as MQ Salesforce Bridge, GrafanaExperience with Agile and DevOps in a cloud environmentPractical experience and knowledge of Service-Oriented Architecture, Microservices, and APIExpertise in Application Server and Web Server architecture in a large enterprise environmentExperience with both internally-facing integrations as well as externally-facing solutions" Then "Details: Education Bachelor's degree in Computer Science, Information Systems, or other related field; or equivalent work experience Technical Qualifications Candidates need 5-10 years of recent and related experience as an MQ Architect/Integration Engineer from Design through the Implementation of technical solutionsStrongly prefer recent, demonstrable experience with automated build and system configuration tools such as Terraform, Packer, Chef, Puppet, Ansible, Kubernetes, etc. Experience with Terraform is strongly preferredExperience with common AWS services such as S3, EC2, ASG, ELB, SFTP, CloudFormation, CloudTrail, CloudWatch, Lambda, etc.AWS Certification and/or experience utilizing AWS services in a production environment is preferredStrong knowledge of high-availability, load-balancing, and failover configurations across application, infrastructure, and platform componentsUnderstanding of security design for enterprise software systemsProven ability to write clear and concise technical documents, including design documents, specifications, and technology roadmapsPreference for proven ability to design, implement, and manage secure, scalable, and reliable cloud infrastructure environmentsExperience with source code management tools such as GIT, SVN, etc.Proven depth of knowledge and experience with Python scripting languageExperience with a variety of other programming languages such as JSON, YAML, Boto3, etc.Familiarity with the implementation of CI/CD pipelines and test automation within CI/CD is a plus" Then "Listed salary ranges may vary based on experience, qualifications, and local market. Also, some positions may include bonuses or other incentives." This is pay info but not specific numbers; we should not create Pay section unless posting actually states them. It says "Listed salary ranges may vary..." which is vague, not a specific range. According to rule: 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. This is vague, so we should not create Pay section. Benefits: none mentioned. Schedule: none mentioned. Thus we may have sections: About the role (intro description), Responsibilities (list of duties/skills), Requirements (education + technical qualifications), Skills (maybe separate required vs preferred? but we can combine). However we need to avoid thin sections. Could combine Responsibilities and Skills? But spec says use headings for those categories if content present. We have content for Responsibilities (list of duties). We have content for Requirements (education, experience). We have content for Skills (required and preferred). Could we put required skills under Responsibilities? Might be better to separate. We need to use

• for any list of duties/requirements/benefits. So for each section that has list, we output
  • items. We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the details as given, but we can format as list items. We must not repeat job title as heading. We must not include Job ID etc. We must remove boilerplate like EEO etc. Not present. We must not include application instructions (contact info). So drop "For quick Apply, please reach out to Prakhar Goel: 248 263 5255/ [email protected] W2 candidates Preferred!" Also drop "Details:" repeated. We need to ensure we keep all substantive info: the description about role, responsibilities list, required skills list, preferred skills list, education, technical qualifications list. Let's parse. Intro paragraph after hiring line: "This is an exciting opportunity to work with and broadly apply your MQ engineering skills across various technology solution efforts, as well as build your skills in other areas by being exposed to various aspects from inception through design, build, and deployment. You will be a 'jack-of-all-trades' - working cross-functionally with Architects, Engineers, Business Analysts, and Service Managers across multiple teams in a rapidly evolving environment - completing design documentation, consulting with other engineers and architects, completing network and server build requests, installing and configuring software, etc. To be successful in this role, you must be an organized self-starter with stellar leadership and communication skills who can work independently, building relationships and driving technical solutions from inception to completion. This position requires the candidate to have strong MQ architect/integration experience and the candidate must be technically savvy, with a proven ability to work well in a highly dynamic environment and maintain a strong relationship with our customers and partners. This is an Integration Engineer/MQ Architect role requiring deep, advanced knowledge of IBM MQ and IBM MFTPractical experience with Infrastructure as Code (IaC - Terraform, packer etc.) is requiredExperience in Cloud infrastructure and DevOps is required" Note there is a missing space after IBM MQ and IBM MFTPractical... but we keep as is. We can treat this as About the role. Then "Responsibilities:" then list: "Ability to coordinate and work with diverse groups of subject matter expertsDemonstrated initiative and self-motivationAbility to work effectively independently or in a team environmentStrong analytical, collaboration, leadership, critical thinking, multitasking, and time management skillsCustomer/people-focused orientation that drives and informs engagement with partners, leadership, and peersAbility to influence successfully in a highly matrix or virtual organizationDemonstrates independent thinking and decision-making abilitiesAbility to quickly receive and process informationJudgment to escalate risk-based decisions appropriately" These are run together without punctuation; we need to split into list items. We can separate by capital letters? Better to keep as given but we can insert line breaks. However we must not invent or summarize away detail; we can keep the text as is but we need to format as list items. We could split by the pattern where a new ability starts with a capital letter after a lowercase? Might be risky. Perhaps we can keep as a single paragraph under Responsibilities? But rule says use
    • for any list of duties/requirements/benefits. This is a list of abilities; we should make each ability a
    • . We need to parse. Let's manually split based on the phrases: - Ability to coordinate and work with diverse groups of subject matter experts - Demonstrated initiative and self-motivation - Ability to work effectively independently or in a team environment - Strong analytical, collaboration, leadership, critical thinking, multitasking, and time management skills - Customer/people-focused orientation that drives and informs engagement with partners, leadership, and peers - Ability to influence successfully in a highly matrix or virtual organization - Demonstrates independent thinking and decision-making abilities - Ability to quickly receive and process information - Judgment to escalate risk-based decisions appropriately That seems correct. Now "Preferred Skills" list: "Working knowledge of other technology solutions/products such as MQ Salesforce Bridge, GrafanaExperience with Agile and DevOps in a cloud environmentPractical experience and knowledge of Service-Oriented Architecture, Microservices, and APIExpertise in Application Server and Web Server architecture in a large enterprise environmentExperience with both internally-facing integrations as well as externally-facing solutions" We need to split: - Working knowledge of other technology solutions/products such as MQ Salesforce Bridge, Grafana - Experience with Agile and DevOps in a cloud environment - Practical experience and knowledge of Service-Oriented Architecture, Microservices, and API - Expertise in Application Server and Web Server architecture in a large enterprise environment - Experience with both internally-facing integrations as well as externally-facing solutions Now "Details: Education Bachelor's degree in Computer Science, Information Systems, or other related field; or equivalent work experience Technical Qualifications Candidates need 5-10 years of recent and related experience as an MQ Architect/Integration Engineer from Design through the Implementation of technical solutionsStrongly prefer recent, demonstrable experience with automated build and system configuration tools such as Terraform, Packer, Chef, Puppet, Ansible, Kubernetes, etc. Experience with Terraform is strongly preferredExperience with common AWS services such as S3, EC2, ASG, ELB, SFTP, CloudFormation, CloudTrail, CloudWatch, Lambda, etc.AWS Certification and/or experience utilizing AWS services in a production environment is preferredStrong knowledge of high-availability, load-balancing, and failover configurations across application, infrastructure, and platform componentsUnderstanding of security design for enterprise software systemsProven ability to write clear and concise technical documents, including design documents, specifications, and technology roadmapsPreference for proven ability to design, implement, and manage secure, scalable, and reliable cloud infrastructure environmentsExperience with source code management tools such as GIT, SVN, etc.Proven depth of knowledge and experience with Python scripting languageExperience with a variety of other programming languages such as JSON, YAML, Boto3, etc.Familiarity with the implementation of CI/CD pipelines and test automation within CI/CD is a plus" We need to separate Education and Technical Qualifications. Education: "Bachelor's degree in Computer Science, Information Systems, or other related field; or equivalent work experience" Technical Qualifications: many items. Let's split technical qualifications into list items: - Candidates need 5-10 years of recent and related experience as an MQ Architect/Integration Engineer from Design through the Implementation of technical solutions - Strongly prefer recent, demonstrable experience with automated build and system configuration tools such as Terraform, Packer, Chef, Puppet, Ansible, Kubernetes, etc. - Experience with Terraform is strongly preferred - Experience with common AWS services such as S3, EC2, ASG, ELB, SFTP, CloudFormation, CloudTrail, CloudWatch, Lambda, etc. - AWS Certification and/or experience utilizing AWS services in a production environment is preferred - Strong knowledge of high-availability, load-balancing, and failover configurations across application, infrastructure, and platform components - Understanding of security design for enterprise software systems - Proven ability to write clear and concise technical documents, including design documents, specifications, and technology roadmaps - Preference for proven ability to