Solutions Architect
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for any list of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading (the page already shows it)
4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it
5. Preserve ALL substantive information; do NOT invent or summarize away detail
6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
8. Never create Pay/Schedule/Benefits sections unless the posting actually states them
9. Prefer a few substantive sections over many thin ones
10. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
The posting has:
- Company intro (Celonis description)
- "The Role" section - describes the Solutions Architect role
- "What You'll Do" with subsections:
- Data integration and ingestion (with bullet points)
- Actions, AI, and platform connectivity (with bullet points)
- Identity, security, and governance (with bullet points)
- Customer and team impact (with bullet points)
- "What You'll Bring" - requirements (bullet points)
- "Nice to have" - preferred qualifications (bullet points)
- "Visa sponsorship is not offered for this role" - metadata
- "What Celonis can offer you:" - benefits (bullet points)
- "About Us:" - company description (duplicate of intro)
- "Celonis Inclusion Statement" - boilerplate
- "Your Privacy" - legal boilerplate
- "Use of Artificial Intelligence Tools" - legal boilerplate
- Scam warning - boilerplate
I need to structure this into semantic HTML with appropriate sections. Let me identify the sections:
1. About the role (from "The Role" section)
2. Responsibilities (from "What You'll Do" - all the bullet points)
3. Requirements (from "What You'll Bring")
4. Qualifications (from "Nice to have" - preferred qualifications)
5. Benefits (from "What Celonis can offer you")
6. Maybe a note about visa sponsorship
I should not include the boilerplate sections (Inclusion Statement, Privacy, AI Tools, Scam warning). The "About Us" is duplicate of the intro, so I can skip it or include a brief company description.
The "Visa sponsorship is not offered for this role" is metadata - I can include it as a short
note.
Let me structure the HTML:
-
About the role
with prose from "The Role"
- Responsibilities
with - for all the bullet points under "What You'll Do" (I'll combine all subsections into one list or maybe keep subsections? The rules say use
- for any list of duties. I think I should keep the structure but use nested lists or just flatten. Since the original has subsections with headings, I could use
for subsections? But the rules only mention for section headings. It says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid but says use for section headings. I think I should use for main sections only. For subsections within Responsibilities, I could use or just include as part of list items. But the content has clear subcategories. I'll include them as maybe? The rules don't explicitly forbid, but they say "use for section headings". I'll use for main sections and for subsections within Responsibilities, I'll use to preserve structure. However, the instruction says "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I cannot use other heading levels. But to be safe, I'll use for main sections and for subsections I'll use labels within list items or just incorporate into list items.
Actually, looking at the example headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". These are top-level sections. The "What You'll Do" has subsections: Data integration and ingestion, Actions, AI, and platform connectivity, Identity, security, and governance, Customer and team impact. These are subsections of Responsibilities. I could make them or just include as bold text before each list. I think using is fine for semantic structure. But the instruction says "use for section headings". It doesn't say "only use ". I'll use for main sections and for subsections within Responsibilities.
But the output should be a fragment, not a full document. I'll proceed.
Let me write the HTML.
First, About the role: prose from "The Role" paragraph.
Second, Responsibilities: with four subsections, each with a list.
Third, Requirements: list from "What You'll Bring".
Fourth, Qualifications: list from "Nice to have".
Fifth, Benefits: list from "What Celonis can offer you".
Sixth, a note about visa sponsorship.
I'll omit the duplicate About Us, Inclusion Statement, Privacy, AI Tools, Scam warning.
Now, I need to preserve ALL substantive information. So I must include all bullet points exactly as they appear (but formatted as
- ). I should not summarize.
Let me extract the bullet points:
Under "What You'll Do":
Data integration and ingestion:
- Implement standard extractors. Install, configure, and troubleshoot Celonis out-of-the-box extractors in customer landscapes, including SAP (ECC and S/4HANA), JDBC-based databases, and cloud applications such as Salesforce, ServiceNow, and others.
- Build custom API connectors. Design and build custom connectors with Celonis Extractor Builder for source systems that expose data through REST or SOAP APIs, handling authentication (OAuth 2.0, API keys, certificates), pagination, rate limits, and incremental (delta) loads.
- Enable push-based ingestion. Help customers design and develop scripts and pipelines (typically in Python) that push data to Celonis via the Data Ingestion API, and advise on file formats, scheduling, and error handling.
- Connect to the lakehouse. Set up zero-copy data sharing between Celonis and customer lakehouses such as Databricks and Microsoft Fabric, including Delta Sharing configuration, access controls, and data freshness.
Actions, AI, and platform connectivity:
- Close the loop with writebacks. Configure Action Flows and other integration patterns that write back to customer systems (for example, updating records in SAP, Salesforce, or ticketing tools) so Celonis insights turn into action.
- Connect Celonis to AI. Help customers connect Celonis to their LLMs and AI agents through MCP, covering authentication, permissions, and governance.
Identity, security, and governance:
- Own authentication and provisioning. Configure SSO (SAML, OIDC) with identity providers such as Microsoft Entra ID, Okta, and Ping, and set up SCIM-based user and group provisioning.
- Be the security translator. Support customer security, privacy, and compliance reviews, explain the Celonis architecture and data flows, and advise on topics like data minimization, pseudonymization, and least-privilege access.
Customer and team impact:
- Scope with confidence. Run technical discovery, document integration architectures and requirements, and estimate effort so projects start on solid footing.
- Be the voice of the field. Escalate product gaps and bugs with clear, reproducible detail, and share field feedback that shapes our integration roadmap.
- Build reusable assets. Contribute reusable connector templates, scripts, runbooks, and best-practice documentation that scale across customers and partners.
"What You'll Bring" (requirements):
- 2–5 years of experience in a technical, customer-facing role such as solutions engineering, integration or implementation consulting, data engineering, or technical consulting.
- Hands-on experience with REST APIs and common authentication patterns (OAuth 2.0, API keys, tokens); comfort using tools like Postman to explore and test APIs.
- Solid programming skills in Python (or a similar language) and strong SQL skills.
- Working knowledge of data pipelines and ETL/ELT concepts, including incremental loads, scheduling, and handling large data volumes.
- Familiarity with identity and access management concepts such as SSO (SAML/OIDC) and SCIM provisioning.
- A basic understanding of networking and security fundamentals (TLS and certificates, proxies, firewalls, VPNs).
- The ability to explain technical topics clearly to both engineers and business stakeholders, and to manage your own workstreams across multiple customer projects.
- Curiosity, ownership, and a bias toward solving problems hands-on.
- A Bachelor’s degree in Computer Science, Information Systems, Engineering, or a related field, or equivalent practical experience.
"Nice to have":
- Experience with SAP data structures, tables, or extraction (for example, RFC, ODP, or S/4HANA).
- Experience with at least one major cloud platform (AWS, Azure, GCP) and/or lakehouse platforms such as Databricks, Microsoft Fabric, or Snowflake.
- Exposure to iPaaS or low-code integration tools (for example, MuleSoft, Boomi, Workato, or Power Automate).
- Familiarity with LLMs, AI agents, or MCP.
- Experience with Docker or Linux server administration.
- Relevant certifications (for example, Celonis, cloud, or SAP certifications).
"What Celonis can offer you:" (benefits):
- Pioneer Innovation: Work with the global leader in Process Mining and the Process Intelligence Graph to shape the future of AI-driven business operations.
- Ownership from Day 1: Every full-time Celonaut is an owner, receiving Restricted Stock Units (RSUs) and merit-based refresh grants.
- Unrivaled Family Support: Benefit from our inclusive parental leave policy—24 weeks of fully paid leave for primary carers and 12 weeks for supporting carers, available from your first day of employment.
- Work-Life Integration: Enjoy Unlimited PTO (in applicable regions) and generous PTO globally, as well as a flexible hybrid work model that balances remote focus with vibrant office collaboration.
- Continuous Growth: Elevate your skills through our 70-20-10 learning framework, mentorship programs, and access to a dedicated learning platform.
- Holistic Well-being: Prioritize your health with subsidized Wellhub memberships, mental health counseling, and dedicated Wellness Weeks that prioritize work/life balance.
- Drive Sustainability: Participate in annual Impact Days, where you receive paid time off to volunteer for community and environmental causes with your local office, or virtually.
- Global Inclusion & Belonging: Find community through our Inclusion Think Tank and participate in our annual Inclusion Days, ensuring every voice is heard and valued.
- Value-Driven Impact: Join a mission-led organization where our core values—Live for Customer Value, The Best Team Wins, We Own It, and Earth Is Our Future—drive every decision.
Visa sponsorship note: "Visa sponsorship is not offered for this role."
Now, I'll create the HTML.
I'll start with
About the role
and a for the role description.
Then
Responsibilities
for prose 3. Do NOT repeat the job title as a heading (the page already shows it) 4. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it 5. Preserve ALL substantive information; do NOT invent or summarize away detail 6. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 7. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 8. Never create Pay/Schedule/Benefits sections unless the posting actually states them 9. Prefer a few substantive sections over many thin ones 10. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - Company intro (Celonis description) - "The Role" section - describes the Solutions Architect role - "What You'll Do" with subsections: - Data integration and ingestion (with bullet points) - Actions, AI, and platform connectivity (with bullet points) - Identity, security, and governance (with bullet points) - Customer and team impact (with bullet points) - "What You'll Bring" - requirements (bullet points) - "Nice to have" - preferred qualifications (bullet points) - "Visa sponsorship is not offered for this role" - metadata - "What Celonis can offer you:" - benefits (bullet points) - "About Us:" - company description (duplicate of intro) - "Celonis Inclusion Statement" - boilerplate - "Your Privacy" - legal boilerplate - "Use of Artificial Intelligence Tools" - legal boilerplate - Scam warning - boilerplate I need to structure this into semantic HTML with appropriate sections. Let me identify the sections: 1. About the role (from "The Role" section) 2. Responsibilities (from "What You'll Do" - all the bullet points) 3. Requirements (from "What You'll Bring") 4. Qualifications (from "Nice to have" - preferred qualifications) 5. Benefits (from "What Celonis can offer you") 6. Maybe a note about visa sponsorship I should not include the boilerplate sections (Inclusion Statement, Privacy, AI Tools, Scam warning). The "About Us" is duplicate of the intro, so I can skip it or include a brief company description. The "Visa sponsorship is not offered for this role" is metadata - I can include it as a short
note. Let me structure the HTML: -
About the role
with prose from "The Role" -Responsibilities
with- for all the bullet points under "What You'll Do" (I'll combine all subsections into one list or maybe keep subsections? The rules say use
- for any list of duties. I think I should keep the structure but use nested lists or just flatten. Since the original has subsections with headings, I could use
for subsections? But the rules only mention
for section headings. It says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't forbid
but says use
for section headings. I think I should use
for main sections only. For subsections within Responsibilities, I could use or just include as part of list items. But the content has clear subcategories. I'll include them as
maybe? The rules don't explicitly forbid, but they say "use
for section headings". I'll use
for main sections and for subsections within Responsibilities, I'll use
to preserve structure. However, the instruction says "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It doesn't say I cannot use other heading levels. But to be safe, I'll use
for main sections and for subsections I'll use labels within list items or just incorporate into list items. Actually, looking at the example headings: "About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule". These are top-level sections. The "What You'll Do" has subsections: Data integration and ingestion, Actions, AI, and platform connectivity, Identity, security, and governance, Customer and team impact. These are subsections of Responsibilities. I could make them
or just include as bold text before each list. I think using
is fine for semantic structure. But the instruction says "use
for section headings". It doesn't say "only use
". I'll use
for main sections and
for subsections within Responsibilities. But the output should be a fragment, not a full document. I'll proceed. Let me write the HTML. First, About the role: prose from "The Role" paragraph. Second, Responsibilities: with four subsections, each with a list. Third, Requirements: list from "What You'll Bring". Fourth, Qualifications: list from "Nice to have". Fifth, Benefits: list from "What Celonis can offer you". Sixth, a note about visa sponsorship. I'll omit the duplicate About Us, Inclusion Statement, Privacy, AI Tools, Scam warning. Now, I need to preserve ALL substantive information. So I must include all bullet points exactly as they appear (but formatted as
- ). I should not summarize. Let me extract the bullet points: Under "What You'll Do": Data integration and ingestion: - Implement standard extractors. Install, configure, and troubleshoot Celonis out-of-the-box extractors in customer landscapes, including SAP (ECC and S/4HANA), JDBC-based databases, and cloud applications such as Salesforce, ServiceNow, and others. - Build custom API connectors. Design and build custom connectors with Celonis Extractor Builder for source systems that expose data through REST or SOAP APIs, handling authentication (OAuth 2.0, API keys, certificates), pagination, rate limits, and incremental (delta) loads. - Enable push-based ingestion. Help customers design and develop scripts and pipelines (typically in Python) that push data to Celonis via the Data Ingestion API, and advise on file formats, scheduling, and error handling. - Connect to the lakehouse. Set up zero-copy data sharing between Celonis and customer lakehouses such as Databricks and Microsoft Fabric, including Delta Sharing configuration, access controls, and data freshness. Actions, AI, and platform connectivity: - Close the loop with writebacks. Configure Action Flows and other integration patterns that write back to customer systems (for example, updating records in SAP, Salesforce, or ticketing tools) so Celonis insights turn into action. - Connect Celonis to AI. Help customers connect Celonis to their LLMs and AI agents through MCP, covering authentication, permissions, and governance. Identity, security, and governance: - Own authentication and provisioning. Configure SSO (SAML, OIDC) with identity providers such as Microsoft Entra ID, Okta, and Ping, and set up SCIM-based user and group provisioning. - Be the security translator. Support customer security, privacy, and compliance reviews, explain the Celonis architecture and data flows, and advise on topics like data minimization, pseudonymization, and least-privilege access. Customer and team impact: - Scope with confidence. Run technical discovery, document integration architectures and requirements, and estimate effort so projects start on solid footing. - Be the voice of the field. Escalate product gaps and bugs with clear, reproducible detail, and share field feedback that shapes our integration roadmap. - Build reusable assets. Contribute reusable connector templates, scripts, runbooks, and best-practice documentation that scale across customers and partners. "What You'll Bring" (requirements): - 2–5 years of experience in a technical, customer-facing role such as solutions engineering, integration or implementation consulting, data engineering, or technical consulting. - Hands-on experience with REST APIs and common authentication patterns (OAuth 2.0, API keys, tokens); comfort using tools like Postman to explore and test APIs. - Solid programming skills in Python (or a similar language) and strong SQL skills. - Working knowledge of data pipelines and ETL/ELT concepts, including incremental loads, scheduling, and handling large data volumes. - Familiarity with identity and access management concepts such as SSO (SAML/OIDC) and SCIM provisioning. - A basic understanding of networking and security fundamentals (TLS and certificates, proxies, firewalls, VPNs). - The ability to explain technical topics clearly to both engineers and business stakeholders, and to manage your own workstreams across multiple customer projects. - Curiosity, ownership, and a bias toward solving problems hands-on. - A Bachelor’s degree in Computer Science, Information Systems, Engineering, or a related field, or equivalent practical experience. "Nice to have": - Experience with SAP data structures, tables, or extraction (for example, RFC, ODP, or S/4HANA). - Experience with at least one major cloud platform (AWS, Azure, GCP) and/or lakehouse platforms such as Databricks, Microsoft Fabric, or Snowflake. - Exposure to iPaaS or low-code integration tools (for example, MuleSoft, Boomi, Workato, or Power Automate). - Familiarity with LLMs, AI agents, or MCP. - Experience with Docker or Linux server administration. - Relevant certifications (for example, Celonis, cloud, or SAP certifications). "What Celonis can offer you:" (benefits): - Pioneer Innovation: Work with the global leader in Process Mining and the Process Intelligence Graph to shape the future of AI-driven business operations. - Ownership from Day 1: Every full-time Celonaut is an owner, receiving Restricted Stock Units (RSUs) and merit-based refresh grants. - Unrivaled Family Support: Benefit from our inclusive parental leave policy—24 weeks of fully paid leave for primary carers and 12 weeks for supporting carers, available from your first day of employment. - Work-Life Integration: Enjoy Unlimited PTO (in applicable regions) and generous PTO globally, as well as a flexible hybrid work model that balances remote focus with vibrant office collaboration. - Continuous Growth: Elevate your skills through our 70-20-10 learning framework, mentorship programs, and access to a dedicated learning platform. - Holistic Well-being: Prioritize your health with subsidized Wellhub memberships, mental health counseling, and dedicated Wellness Weeks that prioritize work/life balance. - Drive Sustainability: Participate in annual Impact Days, where you receive paid time off to volunteer for community and environmental causes with your local office, or virtually. - Global Inclusion & Belonging: Find community through our Inclusion Think Tank and participate in our annual Inclusion Days, ensuring every voice is heard and valued. - Value-Driven Impact: Join a mission-led organization where our core values—Live for Customer Value, The Best Team Wins, We Own It, and Earth Is Our Future—drive every decision. Visa sponsorship note: "Visa sponsorship is not offered for this role." Now, I'll create the HTML. I'll start with
About the role
and afor the role description. Then
Responsibilities
- ). I should not summarize. Let me extract the bullet points: Under "What You'll Do": Data integration and ingestion: - Implement standard extractors. Install, configure, and troubleshoot Celonis out-of-the-box extractors in customer landscapes, including SAP (ECC and S/4HANA), JDBC-based databases, and cloud applications such as Salesforce, ServiceNow, and others. - Build custom API connectors. Design and build custom connectors with Celonis Extractor Builder for source systems that expose data through REST or SOAP APIs, handling authentication (OAuth 2.0, API keys, certificates), pagination, rate limits, and incremental (delta) loads. - Enable push-based ingestion. Help customers design and develop scripts and pipelines (typically in Python) that push data to Celonis via the Data Ingestion API, and advise on file formats, scheduling, and error handling. - Connect to the lakehouse. Set up zero-copy data sharing between Celonis and customer lakehouses such as Databricks and Microsoft Fabric, including Delta Sharing configuration, access controls, and data freshness. Actions, AI, and platform connectivity: - Close the loop with writebacks. Configure Action Flows and other integration patterns that write back to customer systems (for example, updating records in SAP, Salesforce, or ticketing tools) so Celonis insights turn into action. - Connect Celonis to AI. Help customers connect Celonis to their LLMs and AI agents through MCP, covering authentication, permissions, and governance. Identity, security, and governance: - Own authentication and provisioning. Configure SSO (SAML, OIDC) with identity providers such as Microsoft Entra ID, Okta, and Ping, and set up SCIM-based user and group provisioning. - Be the security translator. Support customer security, privacy, and compliance reviews, explain the Celonis architecture and data flows, and advise on topics like data minimization, pseudonymization, and least-privilege access. Customer and team impact: - Scope with confidence. Run technical discovery, document integration architectures and requirements, and estimate effort so projects start on solid footing. - Be the voice of the field. Escalate product gaps and bugs with clear, reproducible detail, and share field feedback that shapes our integration roadmap. - Build reusable assets. Contribute reusable connector templates, scripts, runbooks, and best-practice documentation that scale across customers and partners. "What You'll Bring" (requirements): - 2–5 years of experience in a technical, customer-facing role such as solutions engineering, integration or implementation consulting, data engineering, or technical consulting. - Hands-on experience with REST APIs and common authentication patterns (OAuth 2.0, API keys, tokens); comfort using tools like Postman to explore and test APIs. - Solid programming skills in Python (or a similar language) and strong SQL skills. - Working knowledge of data pipelines and ETL/ELT concepts, including incremental loads, scheduling, and handling large data volumes. - Familiarity with identity and access management concepts such as SSO (SAML/OIDC) and SCIM provisioning. - A basic understanding of networking and security fundamentals (TLS and certificates, proxies, firewalls, VPNs). - The ability to explain technical topics clearly to both engineers and business stakeholders, and to manage your own workstreams across multiple customer projects. - Curiosity, ownership, and a bias toward solving problems hands-on. - A Bachelor’s degree in Computer Science, Information Systems, Engineering, or a related field, or equivalent practical experience. "Nice to have": - Experience with SAP data structures, tables, or extraction (for example, RFC, ODP, or S/4HANA). - Experience with at least one major cloud platform (AWS, Azure, GCP) and/or lakehouse platforms such as Databricks, Microsoft Fabric, or Snowflake. - Exposure to iPaaS or low-code integration tools (for example, MuleSoft, Boomi, Workato, or Power Automate). - Familiarity with LLMs, AI agents, or MCP. - Experience with Docker or Linux server administration. - Relevant certifications (for example, Celonis, cloud, or SAP certifications). "What Celonis can offer you:" (benefits): - Pioneer Innovation: Work with the global leader in Process Mining and the Process Intelligence Graph to shape the future of AI-driven business operations. - Ownership from Day 1: Every full-time Celonaut is an owner, receiving Restricted Stock Units (RSUs) and merit-based refresh grants. - Unrivaled Family Support: Benefit from our inclusive parental leave policy—24 weeks of fully paid leave for primary carers and 12 weeks for supporting carers, available from your first day of employment. - Work-Life Integration: Enjoy Unlimited PTO (in applicable regions) and generous PTO globally, as well as a flexible hybrid work model that balances remote focus with vibrant office collaboration. - Continuous Growth: Elevate your skills through our 70-20-10 learning framework, mentorship programs, and access to a dedicated learning platform. - Holistic Well-being: Prioritize your health with subsidized Wellhub memberships, mental health counseling, and dedicated Wellness Weeks that prioritize work/life balance. - Drive Sustainability: Participate in annual Impact Days, where you receive paid time off to volunteer for community and environmental causes with your local office, or virtually. - Global Inclusion & Belonging: Find community through our Inclusion Think Tank and participate in our annual Inclusion Days, ensuring every voice is heard and valued. - Value-Driven Impact: Join a mission-led organization where our core values—Live for Customer Value, The Best Team Wins, We Own It, and Earth Is Our Future—drive every decision. Visa sponsorship note: "Visa sponsorship is not offered for this role." Now, I'll create the HTML. I'll start with
- for any list of duties. I think I should keep the structure but use nested lists or just flatten. Since the original has subsections with headings, I could use