Senior Sales Engineer - Life Science - North America

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We need to extract content. From posting: - About The Role: description: "As a Sales Engineer it’s your mission to show the value of Camunda and guide organizations planning to automate their core business processes. You accompany prospective customers in their product evaluation of Camunda. You are responsible for achieving the product win, getting answers to all product related technical questions, and arranging all presales interactions driving the evaluation. In this role you will partner with our Account Executives and Solution Architects, supporting you by conducting proof of concepts or handling other deeply technical discussions. You will help qualify opportunities and then help set and execute a sales strategy to achieve a win. The effectiveness of Camunda's Sales Engineers is gauged by their ability to convert prospects into Camunda customers both efficiently and at a high rate. This position requires a strong interest in cutting-edge software technologies. You should take pleasure in crafting sample code or custom demonstrations and exploring new technology, even if you're not highly experienced in software development. By empathizing with prospects, you better grasp their requirements and have engaging technical conversations, and excel at clarifying how Camunda's technology can benefit their business." We can put that as

under About the role. - Responsibilities: list under "What You'll Be Doing": bullet points: Map customer requirements to our Camunda product portfolio Position potential quantitative and qualitative business value of Camunda Develop individual Camunda evaluation plans and demos for our prospects Conduct product demos and product related Q&A sessions Support the completion of RFI / RFP documents Team with Account Executives to develop accounts Organize and execute pre-sales engagements Implement code snippets Create and maintain pre-sales content and technical artifacts We need

• . - Requirements: maybe "What You Bring" includes ability/willingness to use product, strong technical foundation, proven sales engineering experience, communication excellence, language proficiency, travel flexibility. Those are requirements. Could separate into Requirements and Qualifications? The instruction says we can have sections: Requirements, Qualifications, Skills. We need to decide where to put content. We have "What You Bring" includes: Ability and/or willingness to use our product. Strong Technical Foundation: A degree in Computer Science, Information Systems, or a related field—or equivalent practical experience. Solid understanding of programming fundamentals, modern software engineering practices, and common IT/system architectures. Proven Sales Engineering Experience: Experience in Sales Engineering or Pre-Sales, with a deep understanding of sales cycles, value-based selling, and stakeholder engagement. Skilled in handling objections and driving deals to closure in a consultative selling environment. Communication Excellence: Exceptional presentation and interpersonal skills, with the ability to translate complex technical concepts into clear, compelling narratives tailored to technical and non-technical audiences alike. Language Proficiency: Fluent in English (C1/C2 level or native proficiency) Travel Flexibility: Willingness to travel occasionally for customer meetings, events, and team collaboration. We could treat these as Requirements (maybe technical foundation, sales engineering experience, communication, language, travel). Qualifications could be nice-to-haves? Actually "Nice-to-haves" list: Experience in enterprise automation, BPM, process orchestration, RPA, Agentic-AI or similar domains. Familiarity with value-based selling, including conducting value workshops and applying value engineering frameworks. Strong understanding of the process automation and orchestration product landscape and key industry players. Industry experience in BFSI, Telecommunications, or Logistics. We could put those under Qualifications or Skills. The instruction says we can have sections: Requirements, Qualifications, Skills. We need to avoid filler. We'll put: - Requirements: the "What You Bring" bullet list (maybe as
  ). - Qualifications: the "Nice-to-haves" bullet list. - Skills: maybe we could combine some overlapping but we can also leave out if not distinct. However we have "Communication Excellence" etc which are skills. Could put under Skills: communication, presentation, interpersonal, technical demo creation, etc. But we already have many under Requirements. To avoid duplication, we could put Skills as separate: maybe "Technical demo creation, proof of concept, code snippets" but those are in responsibilities. Might be better to have only Requirements and Qualifications, and omit Skills if not distinct. But instruction says we can include sections only when posting has real specific content. We have content for Skills? Could extract "Ability to craft sample code or custom demonstrations", "exploring new technology", "empathizing with prospects", "clarifying how Camunda's technology can benefit their business". Those are skills. Could make a Skills section. But we need to avoid filler. Let's decide: Sections: - About the role (paragraph) - Responsibilities (ul) - Requirements (ul) from What You Bring (core) - Qualifications (ul) from Nice-to-haves - Skills (ul) maybe from ability to craft sample code, exploring new tech, empathizing, clarifying benefit, presentation, interpersonal, etc. But many overlap with Requirements. Might be thin. Could combine Requirements and Skills into one? But we need to follow instruction: Prefer a few substantive sections over many thin ones. So maybe we just have About the role, Responsibilities, Requirements (combining What You Bring and Nice-to-haves as Requirements?), Benefits, Pay. But we need to separate Benefits and Pay as they have specific content. Benefits: list under "Benefits & Perks": Remote & Flexible, In Person Connection, Health & Wellbeing, Financial Security, Professional Growth, AI in hiring process (maybe not benefit), plus Live Well Lifestyle Spending Account details. We'll extract bullet points. Pay: compensation details: salary ranges for US, UK, Singapore, Canada, equity via VSOP. That's specific. Schedule: not mentioned besides remote/flexible, but not explicit schedule. Could infer flexible time off but not schedule. Probably no schedule section. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also Qualifications? But we could incorporate nice-to-haves into Requirements as "Preferred qualifications". However instruction says we can have Requirements and Qualifications separate. Might be better to have Requirements (mandatory) and Qualifications (preferred). Let's split: Requirements (mandatory): Ability/willingness to use product, Strong Technical Foundation (degree or equivalent, understanding programming fundamentals, modern software engineering practices, IT/system architectures), Proven Sales Engineering Experience (experience in sales engineering/pre-sales, understanding sales cycles, value-based selling, stakeholder engagement, handling objections, driving deals), Communication Excellence (exceptional presentation/interpersonal skills, translate complex tech), Language Proficiency (fluent English C1/C2/native), Travel Flexibility (willingness to travel occasionally). Qualifications (nice-to-haves): Experience in enterprise automation, BPM, process orchestration, RPA, Agentic-AI or similar domains; Familiarity with value-based selling (value workshops, value engineering frameworks); Strong understanding of process automation and orchestration product landscape and key industry players; Industry experience in BFSI, Telecommunications, or Logistics. Skills: maybe we could omit as overlapping. But we could include "Ability to craft sample code or custom demonstrations, exploring new technology, empathizing with prospects, clarifying how Camunda's technology benefits business". However these are somewhat covered in responsibilities and requirements. To keep sections few, we might omit Skills. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce:

  About the role

  ...

  Responsibilities

  • ...
  ...

  Requirements

  • ...
  ...

  Qualifications

  • ...
  ...

  Benefits

  • ...
  ...

  Pay

  ...

  maybe list. We must not include filler like "commensurate with experience". Ensure we preserve all substantive info. Let's craft content. About the role paragraph: combine the description. Responsibilities list: each bullet as given. Requirements list: each bullet summarizing each point. We need to keep details: Ability and/or willingness to use our product. Strong Technical Foundation: A degree in Computer Science, Information Systems, or a related field—or equivalent practical experience. Solid understanding of programming fundamentals, modern software engineering practices, and common IT/system architectures. Proven Sales Engineering Experience: Experience in Sales Engineering or Pre-Sales, with a deep understanding of sales cycles, value-based selling, and stakeholder engagement. Skilled in handling objections and driving deals to closure in a consultative selling environment. Communication Excellence: Exceptional presentation and interpersonal skills, with the ability to translate complex technical concepts into clear, compelling narratives tailored to technical and non-technical audiences alike. Language Proficiency: Fluent in English (C1/C2 level or native proficiency). Travel Flexibility: Willingness to travel occasionally for customer meetings, events, and team collaboration. We could break into separate
  • for each major bullet. Qualifications list: Experience in enterprise automation, business process management (BPM), process orchestration, robotic process automation (RPA), Agentic-AI or similar domains. Familiarity with value-based selling, including conducting value workshops and applying value engineering frameworks. Strong understanding of the process automation and orchestration product landscape and key industry players. Industry experience in BFSI, Telecommunications, or Logistics. Benefits list: Remote & Flexible: Work from anywhere with the setup that suits you, home office budget, co-working space support, and flexible time off to recharge when you need it. In Person Connection: We invest in meaningful face time through our Annual Kickoff (Vienna in 2025, Madrid in 2026!), team offsites, and Camundi Connection Budgets, including contributing to meetups while travelling, and local gatherings with fellow Camundi. Health & Wellbeing: Access locally tailored healthcare, Modern Health for global mental wellbeing, and our Live Well Lifestyle Spending Account (LSA), a flexible, global benefit that puts you in control of your whole life, not just work, from: staying active, to caring for family, exploring personal passions, meaningful experiences, and investing in your financial wellbeing. The Live Well program launches in 2026 and scales to €1,000 annually from 2027. Financial Security: Retirement and pension plans (often with company contributions), plus life and disability insurance where relevant. Professional Growth: Up to $/€/£1,000 per year for self-driven learning: courses, certifications, books, you decide! AI in our hiring process: Camunda may use AI tools to aid the screening of applications and during the interview process. You can learn more here ”Everyone is welcome at Camunda” — it’s a celebrated component of our culture. We strive to create an inclusive environment that empowers our people. At Camunda, we honour diverse cultures and backgrounds and are proud to be an equal opportunity employer. All qualified applicants will receive consideration without regard to gender, race, ethnicity, religion, belief, sexual orientation, age, disability or any other protected characteristics under applicable law. We are looking forward to your application! Come join us and be part of Camunda’s incredible journey: Make an impact at a pivotal moment in our story! Please be aware that scammers may impersonate Camunda by reaching out about job opportunities. Camunda will only contact candidates from an email address ending in @camunda.com or @talent.camunda.com. We will never ask candidates for bank account details, checks, payment, or other sensitive financial information as part of our hiring process. If you receive a suspicious message, please do not respond, click any links, or share personal information. Note for recruiting and placement agencies: Camunda does not accept unsolicited agency resumes. Please do not forward resumes to our careers site