Solutions Architect
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones.
We need to parse the posting.
Content:
- Who We Are (description)
- What You’ll Do (list of duties)
- What We’re Looking For (list of requirements/qualifications)
- Bonus Points (list)
- Why You’ll Love Working at Orkes (list of benefits? Actually it's about culture)
- More Details (Pay, Start Date, Status, Type, Location, Department, Reports to, Travel)
- Benefits (list)
- Diversity statement (maybe part of culture)
- Your Journey with us (maybe not needed)
We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide which sections to include based on content.
- About the role: Could be "Who We Are" and maybe "What You’ll Do"? Actually "About the role" is typical heading for overview. We can put "Who We Are" as About the role? Or we could have separate sections: About the role (company overview), Responsibilities (What You’ll Do), Requirements (What We’re Looking For), Qualifications (maybe same as Requirements?), Skills (Bonus Points?), Benefits (Benefits list), Pay (More Details includes salary range), Schedule (More Details includes Start Date, Status, Type, Location, Travel). But we must not create sections with filler.
We need to include only sections where there is real specific content.
Let's extract:
About the role: Could be a brief description of the company and role. The "Who We Are" is company overview. Could be used as About the role. We'll include that.
Responsibilities: "What You’ll Do" bullet list.
Requirements: "What We’re Looking For" bullet list (5+ years experience etc.)
Qualifications: Might be overlapping with Requirements; but we could treat "Bonus Points" as Qualifications? Actually Qualifications often are required qualifications; Bonus Points are preferred. We could have Requirements (required) and Qualifications (preferred). But we need to avoid thin sections. Maybe combine Requirements and Qualifications into one section? But the instruction says use headings for those categories if content exists. We have both required and bonus points. Could make Requirements (required) and Qualifications (bonus). That seems okay.
Skills: Could be language proficiency in Java, experience with REST/Kafka, etc. Those are in Requirements. Might not need separate Skills.
Benefits: There's a Benefits section: "Comprehensive health coverage including medical, dental, and vision Flexible PTO Support for personal development". Also "Remote-friendly, flexible working hours, a global team and a strong culture of trust and ownership" from Why You’ll Love Working at Orkes. Also maybe "You’ll be working on real and difficult problems..." etc. That's more culture. But we have explicit Benefits bullet list. So we include Benefits.
Pay: More Details includes base salary range $80,000-180,000 USD. Also note compensation based on local market rates etc. That's specific. So we include Pay.
Schedule: More Details includes Start Date: ASAP, Status: Full time (via EOR vendor), Type: Remote daily w/expected travel to clients, Location: Europe, GMT +1 or within 1-2hrs of that timezone., Department: Engineering, Reports to: Head of Engineering, Travel: 15-20%. That's schedule/employment details. So we include Schedule.
We must not include filler like "commensurate with experience" etc. Not present.
We must remove boilerplate: diversity statement, EEO, etc. The diversity statement is present but maybe we should remove as it's EEO/equal-opportunity boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the diversity paragraph. Also remove "Your Journey with us is an opportunity..." maybe also boilerplate? It's somewhat generic but could be considered fluff. Might be okay to keep? It's not EEO but it's generic. Safer to remove? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The diversity statement is EEO-related, so remove. The "Your Journey with us..." is not EEO but could be considered fluff; but we can keep if it's substantive? It's vague. Might be better to drop.
Also remove "Not 100% sure you fit the description? That’s okay..." that's encouraging but maybe not boilerplate; it's part of the posting. Could keep? It's not EEO. It's a call to apply. Might be considered application instruction? It's not exactly instruction to apply but encouraging. The instruction says remove application instructions. That line is not an instruction to apply but motivational. Might keep? Safer to remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The line "Not 100% sure you fit the description? That’s okay. We care more about your potential and passion than checking every box. If this role excites you, we want to hear from you." is somewhat encouraging to apply, but not a direct instruction. Could be considered application instruction? I'd keep it as part of the role description maybe under About the role? But we might not need a separate section for it. Could incorporate into About the role paragraph.
We need to output only HTML fragment, no /, no markdown.
We need to use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve ALL substantive information; do not invent or summarize away detail.
Thus we need to include all details from the sections we keep.
Let's extract content for each section.
About the role: Could combine "Who We Are" and maybe the motivational paragraph. Let's parse "Who We Are":
"Building the Backbone of Distributed Applications. Orkes is building the platform that powers the next generation of enterprise applications and AI systems. Founded by the creators of the open-source Netflix Conductor orchestration platform, Orkes helps organizations build, deploy, and operate mission-critical workflows and AI agents at massive scale. Our platform combines workflow and agent orchestration, integrations, observability, and resilience into a unified developer experience, enabling teams to build and operate complex deterministic and agentic workflows with confidence. From global enterprises to fast-growing startups, customers rely on Orkes to automate business-critical processes and execute billions of workflow and agent executions with the reliability, visibility, and fault tolerance required for production systems. We’re solving some of the hardest infrastructure problems: how do you make distributed systems reliable, observable, and scalable – without every team having to reinvent the wheel? We absorb the complexity of distributed systems, letting teams build with confidence. We’re hiring a Solutions Architect to help us evolve and scale our platform. If you’re passionate about clean, efficient architecture, love solving tough distributed systems challenges, and thrive in an environment where your ideas actually shape the product then we’d love to talk. And the best part is we’re just getting started."
That's substantive. We'll put that in a
under
About the role
.
Responsibilities: "What You’ll Do" list:
- Become an expert on the Orkes platform to lead customers through training, adopting and implementing best practices for their orchestration journey
- Partner with the sales team to act as a technical advisor during the sales process
- Collaborate with the product team as an advocate of your customers in the field
- Help our customers to achieve tangible data-driven outcomes through the use of the Orkes platform, establishing a clear architectural vision and identifying compelling use cases so as to realize value
- Find solutions to our customers' biggest challenges in orchestration and application development in various business domains including logistics, fintech, cyber security, healthcare and cross vertical use cases like application modernization, performance scaling, and resilience
- Engage with the technical community by leading workshops, seminars and meet-ups
We'll put each as - under
.
Requirements: "What We’re Looking For" list:
- 5+ years of experience in software engineering, cloud architecture and customer-facing roles
- Understanding of business processes across multiple industries, geographies and technical domains
- Understanding of system design patterns, distributed systems, microservices, and cloud-native architecture
- Experience with integrations using REST and messaging systems (Kafka, MQ, etc.)
- Language proficiency in Java
- Strong problem-solving skills and a passion for learning new technologies
- A collaborative mindset—we win as a team
We'll put as - .
Qualifications (Bonus Points): "Bonus Points":
- Experience with orchestration engines or workflow systems (e.g., Conductor, Camunda, Temporal)
- Contributions to open-source projects
We'll put as
- under
Qualifications
.
Benefits: There's a Benefits section: "Comprehensive health coverage including medical, dental, and vision Flexible PTO Support for personal development". Also from Why You’ll Love Working at Orkes: "Remote-friendly, flexible working hours, a global team and a strong culture of trust and ownership". Also maybe "You’ll be working on real and difficult problems that developers face every day", "You’ll join a team that thinks deeply about the systems we build and the people who rely on them", "We’re a fast-growing team backed by top-tier investors and used by some of the world’s biggest companies", "You’ll have a huge impact on the direction of our technology and our company". Those are more culture/benefits. We could include them as benefits list. But we need to avoid thin sections. We'll combine all benefit-like statements into a Benefits .
Let's list:
- Comprehensive health coverage including medical, dental, and vision
- Flexible PTO
- Support for personal development
- Remote-friendly, flexible working hours
- Global team
- Strong culture of trust and ownership
- Working on real and difficult problems that developers face every day
- Team that thinks deeply about the systems we build and the people who rely on them
- Fast-growing team backed by top-tier investors and used by some of the world’s biggest companies
- Huge impact on the direction of our technology and our company
We'll put each as - .
Pay: More Details includes:
- The base salary for this role is $80,000-180,000 USD.
- However, compensation is based on local market rates for your country/region, along with your years of experience and qualifications.
We'll put as
under
Pay
.
Schedule: More Details includes:
- Start Date: ASAP
- Status: Full time (via EOR vendor)
- Type: Remote daily w/expected travel to clients
- Location: Europe, GMT +1 or within 1-2hrs of that timezone.
- Department: Engineering
- Reports to: Head of Engineering
- Travel: 15-20%
We'll put as - each.
We must not include duplicated lines.
for prose. Do NOT repeat job title as heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — 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. Prefer a few substantive sections over many thin ones. We need to parse the posting. Content: - Who We Are (description) - What You’ll Do (list of duties) - What We’re Looking For (list of requirements/qualifications) - Bonus Points (list) - Why You’ll Love Working at Orkes (list of benefits? Actually it's about culture) - More Details (Pay, Start Date, Status, Type, Location, Department, Reports to, Travel) - Benefits (list) - Diversity statement (maybe part of culture) - Your Journey with us (maybe not needed) We need to map to sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. - About the role: Could be "Who We Are" and maybe "What You’ll Do"? Actually "About the role" is typical heading for overview. We can put "Who We Are" as About the role? Or we could have separate sections: About the role (company overview), Responsibilities (What You’ll Do), Requirements (What We’re Looking For), Qualifications (maybe same as Requirements?), Skills (Bonus Points?), Benefits (Benefits list), Pay (More Details includes salary range), Schedule (More Details includes Start Date, Status, Type, Location, Travel). But we must not create sections with filler. We need to include only sections where there is real specific content. Let's extract: About the role: Could be a brief description of the company and role. The "Who We Are" is company overview. Could be used as About the role. We'll include that. Responsibilities: "What You’ll Do" bullet list. Requirements: "What We’re Looking For" bullet list (5+ years experience etc.) Qualifications: Might be overlapping with Requirements; but we could treat "Bonus Points" as Qualifications? Actually Qualifications often are required qualifications; Bonus Points are preferred. We could have Requirements (required) and Qualifications (preferred). But we need to avoid thin sections. Maybe combine Requirements and Qualifications into one section? But the instruction says use headings for those categories if content exists. We have both required and bonus points. Could make Requirements (required) and Qualifications (bonus). That seems okay. Skills: Could be language proficiency in Java, experience with REST/Kafka, etc. Those are in Requirements. Might not need separate Skills. Benefits: There's a Benefits section: "Comprehensive health coverage including medical, dental, and vision Flexible PTO Support for personal development". Also "Remote-friendly, flexible working hours, a global team and a strong culture of trust and ownership" from Why You’ll Love Working at Orkes. Also maybe "You’ll be working on real and difficult problems..." etc. That's more culture. But we have explicit Benefits bullet list. So we include Benefits. Pay: More Details includes base salary range $80,000-180,000 USD. Also note compensation based on local market rates etc. That's specific. So we include Pay. Schedule: More Details includes Start Date: ASAP, Status: Full time (via EOR vendor), Type: Remote daily w/expected travel to clients, Location: Europe, GMT +1 or within 1-2hrs of that timezone., Department: Engineering, Reports to: Head of Engineering, Travel: 15-20%. That's schedule/employment details. So we include Schedule. We must not include filler like "commensurate with experience" etc. Not present. We must remove boilerplate: diversity statement, EEO, etc. The diversity statement is present but maybe we should remove as it's EEO/equal-opportunity boilerplate. The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should remove the diversity paragraph. Also remove "Your Journey with us is an opportunity..." maybe also boilerplate? It's somewhat generic but could be considered fluff. Might be okay to keep? It's not EEO but it's generic. Safer to remove? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The diversity statement is EEO-related, so remove. The "Your Journey with us..." is not EEO but could be considered fluff; but we can keep if it's substantive? It's vague. Might be better to drop. Also remove "Not 100% sure you fit the description? That’s okay..." that's encouraging but maybe not boilerplate; it's part of the posting. Could keep? It's not EEO. It's a call to apply. Might be considered application instruction? It's not exactly instruction to apply but encouraging. The instruction says remove application instructions. That line is not an instruction to apply but motivational. Might keep? Safer to remove? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The line "Not 100% sure you fit the description? That’s okay. We care more about your potential and passion than checking every box. If this role excites you, we want to hear from you." is somewhat encouraging to apply, but not a direct instruction. Could be considered application instruction? I'd keep it as part of the role description maybe under About the role? But we might not need a separate section for it. Could incorporate into About the role paragraph. We need to output only HTML fragment, no /, no markdown. We need to use
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve ALL substantive information; do not invent or summarize away detail.
Thus we need to include all details from the sections we keep.
Let's extract content for each section.
About the role: Could combine "Who We Are" and maybe the motivational paragraph. Let's parse "Who We Are":
"Building the Backbone of Distributed Applications. Orkes is building the platform that powers the next generation of enterprise applications and AI systems. Founded by the creators of the open-source Netflix Conductor orchestration platform, Orkes helps organizations build, deploy, and operate mission-critical workflows and AI agents at massive scale. Our platform combines workflow and agent orchestration, integrations, observability, and resilience into a unified developer experience, enabling teams to build and operate complex deterministic and agentic workflows with confidence. From global enterprises to fast-growing startups, customers rely on Orkes to automate business-critical processes and execute billions of workflow and agent executions with the reliability, visibility, and fault tolerance required for production systems. We’re solving some of the hardest infrastructure problems: how do you make distributed systems reliable, observable, and scalable – without every team having to reinvent the wheel? We absorb the complexity of distributed systems, letting teams build with confidence. We’re hiring a Solutions Architect to help us evolve and scale our platform. If you’re passionate about clean, efficient architecture, love solving tough distributed systems challenges, and thrive in an environment where your ideas actually shape the product then we’d love to talk. And the best part is we’re just getting started."
That's substantive. We'll put that in a
under
About the role
.
Responsibilities: "What You’ll Do" list:
- Become an expert on the Orkes platform to lead customers through training, adopting and implementing best practices for their orchestration journey
- Partner with the sales team to act as a technical advisor during the sales process
- Collaborate with the product team as an advocate of your customers in the field
- Help our customers to achieve tangible data-driven outcomes through the use of the Orkes platform, establishing a clear architectural vision and identifying compelling use cases so as to realize value
- Find solutions to our customers' biggest challenges in orchestration and application development in various business domains including logistics, fintech, cyber security, healthcare and cross vertical use cases like application modernization, performance scaling, and resilience
- Engage with the technical community by leading workshops, seminars and meet-ups
We'll put each as - under
.
Requirements: "What We’re Looking For" list:
- 5+ years of experience in software engineering, cloud architecture and customer-facing roles
- Understanding of business processes across multiple industries, geographies and technical domains
- Understanding of system design patterns, distributed systems, microservices, and cloud-native architecture
- Experience with integrations using REST and messaging systems (Kafka, MQ, etc.)
- Language proficiency in Java
- Strong problem-solving skills and a passion for learning new technologies
- A collaborative mindset—we win as a team
We'll put as - .
Qualifications (Bonus Points): "Bonus Points":
- Experience with orchestration engines or workflow systems (e.g., Conductor, Camunda, Temporal)
- Contributions to open-source projects
We'll put as
- under
Qualifications
.
Benefits: There's a Benefits section: "Comprehensive health coverage including medical, dental, and vision Flexible PTO Support for personal development". Also from Why You’ll Love Working at Orkes: "Remote-friendly, flexible working hours, a global team and a strong culture of trust and ownership". Also maybe "You’ll be working on real and difficult problems that developers face every day", "You’ll join a team that thinks deeply about the systems we build and the people who rely on them", "We’re a fast-growing team backed by top-tier investors and used by some of the world’s biggest companies", "You’ll have a huge impact on the direction of our technology and our company". Those are more culture/benefits. We could include them as benefits list. But we need to avoid thin sections. We'll combine all benefit-like statements into a Benefits .
Let's list:
- Comprehensive health coverage including medical, dental, and vision
- Flexible PTO
- Support for personal development
- Remote-friendly, flexible working hours
- Global team
- Strong culture of trust and ownership
- Working on real and difficult problems that developers face every day
- Team that thinks deeply about the systems we build and the people who rely on them
- Fast-growing team backed by top-tier investors and used by some of the world’s biggest companies
- Huge impact on the direction of our technology and our company
We'll put each as - .
Pay: More Details includes:
- The base salary for this role is $80,000-180,000 USD.
- However, compensation is based on local market rates for your country/region, along with your years of experience and qualifications.
We'll put as
under
Pay
.
Schedule: More Details includes:
- Start Date: ASAP
- Status: Full time (via EOR vendor)
- Type: Remote daily w/expected travel to clients
- Location: Europe, GMT +1 or within 1-2hrs of that timezone.
- Department: Engineering
- Reports to: Head of Engineering
- Travel: 15-20%
We'll put as - each.
We must not include duplicated lines.
for prose. We need to preserve ALL substantive information; do not invent or summarize away detail. Thus we need to include all details from the sections we keep. Let's extract content for each section. About the role: Could combine "Who We Are" and maybe the motivational paragraph. Let's parse "Who We Are": "Building the Backbone of Distributed Applications. Orkes is building the platform that powers the next generation of enterprise applications and AI systems. Founded by the creators of the open-source Netflix Conductor orchestration platform, Orkes helps organizations build, deploy, and operate mission-critical workflows and AI agents at massive scale. Our platform combines workflow and agent orchestration, integrations, observability, and resilience into a unified developer experience, enabling teams to build and operate complex deterministic and agentic workflows with confidence. From global enterprises to fast-growing startups, customers rely on Orkes to automate business-critical processes and execute billions of workflow and agent executions with the reliability, visibility, and fault tolerance required for production systems. We’re solving some of the hardest infrastructure problems: how do you make distributed systems reliable, observable, and scalable – without every team having to reinvent the wheel? We absorb the complexity of distributed systems, letting teams build with confidence. We’re hiring a Solutions Architect to help us evolve and scale our platform. If you’re passionate about clean, efficient architecture, love solving tough distributed systems challenges, and thrive in an environment where your ideas actually shape the product then we’d love to talk. And the best part is we’re just getting started." That's substantive. We'll put that in a
under
About the role
. Responsibilities: "What You’ll Do" list: - Become an expert on the Orkes platform to lead customers through training, adopting and implementing best practices for their orchestration journey - Partner with the sales team to act as a technical advisor during the sales process - Collaborate with the product team as an advocate of your customers in the field - Help our customers to achieve tangible data-driven outcomes through the use of the Orkes platform, establishing a clear architectural vision and identifying compelling use cases so as to realize value - Find solutions to our customers' biggest challenges in orchestration and application development in various business domains including logistics, fintech, cyber security, healthcare and cross vertical use cases like application modernization, performance scaling, and resilience - Engage with the technical community by leading workshops, seminars and meet-ups We'll put each as- .
Requirements: "What We’re Looking For" list:
- 5+ years of experience in software engineering, cloud architecture and customer-facing roles
- Understanding of business processes across multiple industries, geographies and technical domains
- Understanding of system design patterns, distributed systems, microservices, and cloud-native architecture
- Experience with integrations using REST and messaging systems (Kafka, MQ, etc.)
- Language proficiency in Java
- Strong problem-solving skills and a passion for learning new technologies
- A collaborative mindset—we win as a team
We'll put as
- .
Qualifications (Bonus Points): "Bonus Points":
- Experience with orchestration engines or workflow systems (e.g., Conductor, Camunda, Temporal)
- Contributions to open-source projects
We'll put as
- under
Qualifications
. Benefits: There's a Benefits section: "Comprehensive health coverage including medical, dental, and vision Flexible PTO Support for personal development". Also from Why You’ll Love Working at Orkes: "Remote-friendly, flexible working hours, a global team and a strong culture of trust and ownership". Also maybe "You’ll be working on real and difficult problems that developers face every day", "You’ll join a team that thinks deeply about the systems we build and the people who rely on them", "We’re a fast-growing team backed by top-tier investors and used by some of the world’s biggest companies", "You’ll have a huge impact on the direction of our technology and our company". Those are more culture/benefits. We could include them as benefits list. But we need to avoid thin sections. We'll combine all benefit-like statements into a Benefits- .
Let's list:
- Comprehensive health coverage including medical, dental, and vision
- Flexible PTO
- Support for personal development
- Remote-friendly, flexible working hours
- Global team
- Strong culture of trust and ownership
- Working on real and difficult problems that developers face every day
- Team that thinks deeply about the systems we build and the people who rely on them
- Fast-growing team backed by top-tier investors and used by some of the world’s biggest companies
- Huge impact on the direction of our technology and our company
We'll put each as
- .
Pay: More Details includes:
- The base salary for this role is $80,000-180,000 USD.
- However, compensation is based on local market rates for your country/region, along with your years of experience and qualifications.
We'll put as
under
Pay
. Schedule: More Details includes: - Start Date: ASAP - Status: Full time (via EOR vendor) - Type: Remote daily w/expected travel to clients - Location: Europe, GMT +1 or within 1-2hrs of that timezone. - Department: Engineering - Reports to: Head of Engineering - Travel: 15-20% We'll put as- each. We must not include duplicated lines.
- .
Pay: More Details includes:
- The base salary for this role is $80,000-180,000 USD.
- However, compensation is based on local market rates for your country/region, along with your years of experience and qualifications.
We'll put as
- under