[Confluent] Senior Integrations Engineer
for section headings. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate.
We need to preserve all substantive info. No invented details. Only include sections when posting has real specific content. So we need to decide which sections have content.
- About the role: The introduction paragraphs describe role and company. Could be "About the role". We'll put that as
About the role
with paragraphs.
- Responsibilities: We have "Key Responsibilities" bullet list. Also "What Good Looks Like in This Role" maybe also responsibilities/qualities. Could be part of Responsibilities or Qualifications. But we can treat "What Good Looks Like" as part of Responsibilities or maybe as "Qualifications". However we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly.
We have:
- Introduction: about IBM Software, Confluent, role description. That's about the role.
- Responsibilities: bullet list under "Key Responsibilities". Also maybe "What Good Looks Like" could be considered "Qualifications" or "Skills". But we can include as part of Responsibilities as additional prose.
- Preferred Education: Bachelor's Degree. That's a qualification.
- Required Technical And Professional Expertise: list of requirements (experience, skills). That's Requirements.
- Preferred Technical And Professional Experience: additional preferred experience. Could be Skills or Qualifications.
We need to avoid filler sections like Benefits, Pay, Schedule if not present. The posting does not mention benefits, pay, schedule. So we omit those sections.
We need to ensure we don't create empty sections.
Thus we will output:
About the role
... (intro paragraphs)
Responsibilities
- ... each bullet from Key Responsibilities
What Good Looks Like in This Role: ... (maybe as prose)
Requirements
- ... each bullet from Required Technical And Professional Expertise
Qualifications
Preferred Education: Bachelor's Degree
Preferred Technical And Professional Experience: ... (list)
Alternatively we could combine Preferred Education and Preferred Technical under Qualifications.
We must not invent content. Ensure we preserve all substantive info.
Let's extract text.
Introduction:
"At IBM Software, we transform client challenges into solutions. Building the world’s leading AI-powered, cloud-native products that shape the future of business and society. Our legacy of innovation creates endless opportunities for IBMers to learn, grow, and make an impact on a global scale. Working in Software means joining a team fueled by curiosity and collaboration. You’ll work with diverse technologies, partners, and industries to design, develop, and deliver solutions that power digital transformation. With a culture that values innovation, growth, and continuous learning, IBM Software places you at the heart of IBM’s product and technology landscape. Here, you’ll have the tools and opportunities to advance your career while creating software that changes the world. With Confluent, data doesn’t sit still. We put information in motion, streaming in near real time so organizations can react faster, build smarter, and deliver experiences as dynamic as the world around them."
That's about the role.
Next: "Your Role And Responsibilities The Senior Integrations Engineer builds and supports business system integrations, with a strong focus on Workato-based automation and reliable data flow across core enterprise applications. This role owns complex integrations end-to-end, solves problems independently, and partners closely with business stakeholders on requirements, delivery, and support while demonstrating technical leadership and strong cross-functional influence."
That could be part of About the role or Responsibilities. But we already have About the role; we could include this as part of About the role as well. However we might want to keep About the role just the intro; but we can also incorporate this into About the role as it's still description. The instruction: "Do NOT repeat the job title as a heading". It's okay to include description.
We'll keep About the role as the intro paragraphs plus maybe the first paragraph after "Your Role And Responsibilities". But we need to avoid duplication. Let's include all descriptive paragraphs before the bullet list as About the role.
Thus About the role includes:
- At IBM Software... (first paragraph)
- Working in Software... (second)
- With Confluent... (third)
- Your Role And Responsibilities The Senior Integrations Engineer... (fourth)
Now Responsibilities: bullet list under "Key Responsibilities". Let's extract each bullet:
- Design, build, test, and support Workato recipes and related integrations across systems like Salesforce, NetSuite, and other business applications.
- Translate complex business needs into clear technical specifications and implementation plans.
- Troubleshoot integration issues, handle errors/debugging, and improve reliability, observability, and reusability.
- Partner with cross-functional teams to gather requirements, communicate trade-offs, and keep stakeholders informed.
- Document integration patterns, templates, and operational procedures to improve team efficiency.
Now "What Good Looks Like in This Role" bullet-ish sentences:
- Independently owns complex integration workstreams from design through delivery and support.
- Delivers reliable, supportable solutions and proactively identifies risks or recurring issues.
- Demonstrates leadership through proactive communication, clear technical decision-making, and effective collaboration with business and technical stakeholders.
- Improves existing recipes, processes, and documentation rather than only executing incoming tickets.
We could treat these as part of Responsibilities as well (maybe as additional prose). Could be separate section "Qualities". But we only have allowed headings; we could put them under Responsibilities as additional or
. Since they are not bullet list originally but sentences, we can put as with each sentence separated by
or as
. Better to keep as for prose.
Now location: "This job can be performed from anywhere in the US." That's schedule/location; not benefits/pay/schedule. Could be considered Schedule? It's about location, not schedule. The instruction says include Schedule section only if posting actually states them. It does not state schedule (like hours). It states location flexibility. Could be considered Schedule? Probably not; we can omit.
Now Preferred Education: "Preferred Education Bachelor's Degree". That's a qualification.
Now Required Technical And Professional Expertise: list:
- 5+ years of relevant experience in business systems, enterprise integrations, or automation engineering.
- Hands-on experience with Workato or similar iPaaS tools.
- Strong understanding of streaming patterns, asynchronous processing, and event-driven integration concepts.
- Experience working with Kafka and related ecosystem tools for event-based data movement and system integration.
- Familiarity with related integration technologies such as REST/SOAP APIs, webhooks, message queues, ETL/iPaaS tools, and middleware platforms.
- Experience with error handling, debugging, monitoring, and support of production integrations.
- Familiarity with business systems such as Salesforce, NetSuite, ERP, HRIS, finance, or billing platforms.
- Strong communication, collaboration, and project coordination skills.
- Enthusiastic self-learner who proactively picks up new tools, integration patterns, and business domains with minimal guidance.
Now Preferred Technical And Professional Experience:
- Experience supporting integrations in a SaaS or high-growth enterprise environment.
- Familiarity with Confluent Cloud or other streaming/data integration platforms.
- Working knowledge of integration security, authentication, and access patterns including OAuth, API keys, and SSO-related workflows.
- Experience documenting reusable integration patterns, standards, and operational runbooks.
We need to output HTML fragment only.
We'll structure:
About the role
At IBM Software, we transform client challenges into solutions. Building the world’s leading AI-powered, cloud-native products that shape the future of business and society. Our legacy of innovation creates endless opportunities for IBMers to learn, grow, and make an impact on a global scale. Working in Software means joining a team fueled by curiosity and collaboration. You’ll work with diverse technologies, partners, and industries to design, develop, and deliver solutions that power digital transformation. With a culture that values innovation, growth, and continuous learning, IBM Software places you at the heart of IBM’s product and technology landscape. Here, you’ll have the tools and opportunities to advance your career while creating software that changes the world. With Confluent, data doesn’t sit still. We put information in motion, streaming in near real time so organizations can react faster, build smarter, and deliver experiences as dynamic as the world around them. Your Role And Responsibilities The Senior Integrations Engineer builds and supports business system integrations, with a strong focus on Workato-based automation and reliable data flow across core enterprise applications. This role owns complex integrations end-to-end, solves problems independently, and partners closely with business stakeholders on requirements, delivery, and support while demonstrating technical leadership and strong cross-functional influence.
Responsibilities
- Design, build, test, and support Workato recipes and related integrations across systems like Salesforce, NetSuite, and other business applications.
- Translate complex business needs into clear technical specifications and implementation plans.
- Troubleshoot integration issues, handle errors/debugging, and improve reliability, observability, and reusability.
- Partner with cross-functional teams to gather requirements, communicate trade-offs, and keep stakeholders informed.
- Document integration patterns, templates, and operational procedures to improve team efficiency.
What Good Looks Like in This Role: Independently owns complex integration workstreams from design through delivery and support. Delivers reliable, supportable solutions and proactively identifies risks or recurring issues. Demonstrates leadership through proactive communication, clear technical decision-making, and effective collaboration with business and technical stakeholders. Improves existing recipes, processes, and documentation rather than only executing incoming tickets.
Requirements
- 5+ years of relevant experience in business systems, enterprise integrations, or automation engineering.
- Hands-on experience with Workato or similar iPaaS tools.
- Strong understanding of streaming patterns, asynchronous processing, and event-driven integration concepts.
- Experience working with Kafka and related ecosystem tools for event-based data movement and system integration.
- Familiarity with related integration technologies such as REST/SOAP APIs, webhooks, message queues, ETL/iPaaS tools, and middleware platforms.
- Experience with error handling, debugging, monitoring, and support of production integrations.
- Familiarity with business systems such as Salesforce, NetSuite, ERP, HRIS, finance, or billing platforms.
- Strong communication, collaboration, and project coordination skills.
- Enthusiastic self-learner who proactively picks up new tools, integration patterns, and business domains with minimal guidance.
Qualifications
Preferred Education: Bachelor's Degree
Preferred Technical And Professional Experience:
- Experience supporting integrations in a SaaS or high-growth enterprise environment.
- Familiarity with Confluent Cloud or other streaming/data integration platforms.
- Working knowledge of integration security, authentication, and access patterns including OAuth, API keys, and SSO-related workflows.
- Experience documenting reusable integration patterns, standards, and operational runbooks.
for prose. Do NOT repeat job title as heading. Do NOT put Job ID etc. Remove boilerplate. We need to preserve all substantive info. No invented details. Only include sections when posting has real specific content. So we need to decide which sections have content. - About the role: The introduction paragraphs describe role and company. Could be "About the role". We'll put that as
About the role
with paragraphs. - Responsibilities: We have "Key Responsibilities" bullet list. Also "What Good Looks Like in This Role" maybe also responsibilities/qualities. Could be part of Responsibilities or Qualifications. But we can treat "What Good Looks Like" as part of Responsibilities or maybe as "Qualifications". However we need to follow headings list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map content accordingly. We have: - Introduction: about IBM Software, Confluent, role description. That's about the role. - Responsibilities: bullet list under "Key Responsibilities". Also maybe "What Good Looks Like" could be considered "Qualifications" or "Skills". But we can include as part of Responsibilities as additional prose. - Preferred Education: Bachelor's Degree. That's a qualification. - Required Technical And Professional Expertise: list of requirements (experience, skills). That's Requirements. - Preferred Technical And Professional Experience: additional preferred experience. Could be Skills or Qualifications. We need to avoid filler sections like Benefits, Pay, Schedule if not present. The posting does not mention benefits, pay, schedule. So we omit those sections. We need to ensure we don't create empty sections. Thus we will output:About the role
... (intro paragraphs)
Responsibilities
- ... each bullet from Key Responsibilities
What Good Looks Like in This Role: ... (maybe as prose)
Requirements
- ... each bullet from Required Technical And Professional Expertise
Qualifications
Preferred Education: Bachelor's Degree
Preferred Technical And Professional Experience: ... (list)
Alternatively we could combine Preferred Education and Preferred Technical under Qualifications. We must not invent content. Ensure we preserve all substantive info. Let's extract text. Introduction: "At IBM Software, we transform client challenges into solutions. Building the world’s leading AI-powered, cloud-native products that shape the future of business and society. Our legacy of innovation creates endless opportunities for IBMers to learn, grow, and make an impact on a global scale. Working in Software means joining a team fueled by curiosity and collaboration. You’ll work with diverse technologies, partners, and industries to design, develop, and deliver solutions that power digital transformation. With a culture that values innovation, growth, and continuous learning, IBM Software places you at the heart of IBM’s product and technology landscape. Here, you’ll have the tools and opportunities to advance your career while creating software that changes the world. With Confluent, data doesn’t sit still. We put information in motion, streaming in near real time so organizations can react faster, build smarter, and deliver experiences as dynamic as the world around them." That's about the role. Next: "Your Role And Responsibilities The Senior Integrations Engineer builds and supports business system integrations, with a strong focus on Workato-based automation and reliable data flow across core enterprise applications. This role owns complex integrations end-to-end, solves problems independently, and partners closely with business stakeholders on requirements, delivery, and support while demonstrating technical leadership and strong cross-functional influence." That could be part of About the role or Responsibilities. But we already have About the role; we could include this as part of About the role as well. However we might want to keep About the role just the intro; but we can also incorporate this into About the role as it's still description. The instruction: "Do NOT repeat the job title as a heading". It's okay to include description. We'll keep About the role as the intro paragraphs plus maybe the first paragraph after "Your Role And Responsibilities". But we need to avoid duplication. Let's include all descriptive paragraphs before the bullet list as About the role. Thus About the role includes: - At IBM Software... (first paragraph) - Working in Software... (second) - With Confluent... (third) - Your Role And Responsibilities The Senior Integrations Engineer... (fourth) Now Responsibilities: bullet list under "Key Responsibilities". Let's extract each bullet: - Design, build, test, and support Workato recipes and related integrations across systems like Salesforce, NetSuite, and other business applications. - Translate complex business needs into clear technical specifications and implementation plans. - Troubleshoot integration issues, handle errors/debugging, and improve reliability, observability, and reusability. - Partner with cross-functional teams to gather requirements, communicate trade-offs, and keep stakeholders informed. - Document integration patterns, templates, and operational procedures to improve team efficiency. Now "What Good Looks Like in This Role" bullet-ish sentences: - Independently owns complex integration workstreams from design through delivery and support. - Delivers reliable, supportable solutions and proactively identifies risks or recurring issues. - Demonstrates leadership through proactive communication, clear technical decision-making, and effective collaboration with business and technical stakeholders. - Improves existing recipes, processes, and documentation rather than only executing incoming tickets. We could treat these as part of Responsibilities as well (maybe as additional prose). Could be separate section "Qualities". But we only have allowed headings; we could put them under Responsibilities as additionalor
- . Since they are not bullet list originally but sentences, we can put as
- Design, build, test, and support Workato recipes and related integrations across systems like Salesforce, NetSuite, and other business applications.
- Translate complex business needs into clear technical specifications and implementation plans.
- Troubleshoot integration issues, handle errors/debugging, and improve reliability, observability, and reusability.
- Partner with cross-functional teams to gather requirements, communicate trade-offs, and keep stakeholders informed.
- Document integration patterns, templates, and operational procedures to improve team efficiency.
- 5+ years of relevant experience in business systems, enterprise integrations, or automation engineering.
- Hands-on experience with Workato or similar iPaaS tools.
- Strong understanding of streaming patterns, asynchronous processing, and event-driven integration concepts.
- Experience working with Kafka and related ecosystem tools for event-based data movement and system integration.
- Familiarity with related integration technologies such as REST/SOAP APIs, webhooks, message queues, ETL/iPaaS tools, and middleware platforms.
- Experience with error handling, debugging, monitoring, and support of production integrations.
- Familiarity with business systems such as Salesforce, NetSuite, ERP, HRIS, finance, or billing platforms.
- Strong communication, collaboration, and project coordination skills.
- Enthusiastic self-learner who proactively picks up new tools, integration patterns, and business domains with minimal guidance.
- Experience supporting integrations in a SaaS or high-growth enterprise environment.
- Familiarity with Confluent Cloud or other streaming/data integration platforms.
- Working knowledge of integration security, authentication, and access patterns including OAuth, API keys, and SSO-related workflows.
- Experience documenting reusable integration patterns, standards, and operational runbooks.
with each sentence separated by
or as
- . Better to keep as
for prose. Now location: "This job can be performed from anywhere in the US." That's schedule/location; not benefits/pay/schedule. Could be considered Schedule? It's about location, not schedule. The instruction says include Schedule section only if posting actually states them. It does not state schedule (like hours). It states location flexibility. Could be considered Schedule? Probably not; we can omit. Now Preferred Education: "Preferred Education Bachelor's Degree". That's a qualification. Now Required Technical And Professional Expertise: list: - 5+ years of relevant experience in business systems, enterprise integrations, or automation engineering. - Hands-on experience with Workato or similar iPaaS tools. - Strong understanding of streaming patterns, asynchronous processing, and event-driven integration concepts. - Experience working with Kafka and related ecosystem tools for event-based data movement and system integration. - Familiarity with related integration technologies such as REST/SOAP APIs, webhooks, message queues, ETL/iPaaS tools, and middleware platforms. - Experience with error handling, debugging, monitoring, and support of production integrations. - Familiarity with business systems such as Salesforce, NetSuite, ERP, HRIS, finance, or billing platforms. - Strong communication, collaboration, and project coordination skills. - Enthusiastic self-learner who proactively picks up new tools, integration patterns, and business domains with minimal guidance. Now Preferred Technical And Professional Experience: - Experience supporting integrations in a SaaS or high-growth enterprise environment. - Familiarity with Confluent Cloud or other streaming/data integration platforms. - Working knowledge of integration security, authentication, and access patterns including OAuth, API keys, and SSO-related workflows. - Experience documenting reusable integration patterns, standards, and operational runbooks. We need to output HTML fragment only. We'll structure:
About the role
At IBM Software, we transform client challenges into solutions. Building the world’s leading AI-powered, cloud-native products that shape the future of business and society. Our legacy of innovation creates endless opportunities for IBMers to learn, grow, and make an impact on a global scale. Working in Software means joining a team fueled by curiosity and collaboration. You’ll work with diverse technologies, partners, and industries to design, develop, and deliver solutions that power digital transformation. With a culture that values innovation, growth, and continuous learning, IBM Software places you at the heart of IBM’s product and technology landscape. Here, you’ll have the tools and opportunities to advance your career while creating software that changes the world. With Confluent, data doesn’t sit still. We put information in motion, streaming in near real time so organizations can react faster, build smarter, and deliver experiences as dynamic as the world around them. Your Role And Responsibilities The Senior Integrations Engineer builds and supports business system integrations, with a strong focus on Workato-based automation and reliable data flow across core enterprise applications. This role owns complex integrations end-to-end, solves problems independently, and partners closely with business stakeholders on requirements, delivery, and support while demonstrating technical leadership and strong cross-functional influence.
Responsibilities
What Good Looks Like in This Role: Independently owns complex integration workstreams from design through delivery and support. Delivers reliable, supportable solutions and proactively identifies risks or recurring issues. Demonstrates leadership through proactive communication, clear technical decision-making, and effective collaboration with business and technical stakeholders. Improves existing recipes, processes, and documentation rather than only executing incoming tickets.
Requirements
Qualifications
Preferred Education: Bachelor's Degree
Preferred Technical And Professional Experience: