Duales Studium - Bachelor of Arts in BWL - Rosenheim; m​/w​/d

The ORCA Group is a PE-backed buy-and-build group: eight software companies for construction and planning (CAD, cost planning, BIM collaboration, project controlling), moving from on-premise licences to a subscription business. Mehr anzeigen

Expertise in modern cloud/cloud-native architectures and a proven track record delivering production-grade AI/ML solutions (deep learning, generative AI) that solve real business problems. Hands-on… Mehr anzeigen

As a Business Analyst at SYNTIVIS, you’ll be part of an interdisciplinary project environment. You make sure that business and functional requirements are clearly understood, well-documented, and…

The ORCA Group is a PE-backed buy-and-build group: eight software companies for construction and planning (CAD, cost planning, BIM collaboration, project controlling), moving from on-premise licences to a subscription business. In 2026 we are replacing the commercial core systems;
Salesforce, Zendesk and Zuora are going live across the first companies this year. That gives you a rare starting position: a current stack with no legacy automation debt, and a long list of manual GTM work waiting to be automated. You join as the first engineering hire in the new Revenue Operations team. Your job: reduce manual work across Sales, Customer Success and Support, improve data quality, and give the commercial teams more time with customers.

• You own automation across the commercial process from lead to churn. You find the spots where people copy, paste, type and chase, and you replace them with workflows that run, get monitored, and get used.
• AI agents and automations across the customer lifecycle: lead enrichment and routing, CRM hygiene, call and ticket summaries, support triage, onboarding and renewal workflows, forecasting support.
• Your own API integrations between Salesforce, Zendesk, Zuora and the rest of the stack; webhook- and event-driven where polling won’t do.
• Evals, monitoring and cost tracking for every LLM-based workflow, so we know an automation works before Sales depends on it, and notice when it stops working.
• Monitoring and cost tracking for what you run: tracing, error handling, alerting, a clear owner per workflow.

• You report to the Revenue Operations & AI lead, who sets architecture and priorities. Inside that frame, you own your solutions.
• Stack:
  Salesforce, Zendesk, Zuora, Clay, n8n, BI tooling, Claude (API and Claude Code). You work against the LLM APIs directly.
• Rollouts are phased: pilot, buy-in, then scale. We don’t push big-bang launches over the heads of the teams.

• Ship two to three production automations that remove manual work for Sales, Customer Success or Support.
• Map the lead-to-churn process and identify where automation pays off most.
• Establish how automations run in production here: monitoring, error handling, data privacy, ownership.

• Hours of manual work automated per quarter, and whether the teams actually use what you ship
• Reliability of the workflows you run in production
• Faster lead response, cleaner CRM data, more customer-facing time for the commercial teams

• You write production code, e.g. Python and/or Type Script.
• You have built and operated your own API integrations: auth, pagination, rate limits, retries. Clearly beyond pure no-/low-code tools.
• You work with LLM APIs directly (e.g. Anthropic, OpenAI): prompt and context engineering, structured outputs, tool calling.
• You test what you build. For LLM workflows that means evals, not gut feeling.
• End-to-end mindset: you think in whole processes and take ownership from problem to running workflow.

• Experience with agent frameworks and standards:
  …