Principal Software Engineer at Ayunis | Munich

Ayunis is recruiting a Principal Software Engineer, Product, Platform, and Infrastructure in Munich for work at the intersection of public-sector software, integration design, and production systems. The role centres on Ayunis Core, an open-source AI platform intended to automate repetitive administrative work. It asks for an engineer who can give technical direction while remaining engaged with implementation, operational questions, and the consequences of architectural choices in production.

The position spans product architecture, an integration platform, and infrastructure rather than a narrowly bounded component. It will suit a senior technical practitioner who can examine a difficult system-level problem, decide what should remain simple, and help engineers move forward without centralising every decision. The work also connects recurring needs from product and customer-facing colleagues to reusable capabilities that can serve public administration workflows.

Opportunity Details

Technical Direction Across Core Product and Production Systems

A hands-on engineering remit for architecture, integrations, and reliable operation

This Munich-based role covers the technical direction of Ayunis Core across frontend and backend concerns, an agent runtime, identity and permissions, extension interfaces, external integrations, and the production environment. The remit is deliberately broad because these areas affect one another: an extension boundary shapes integration work, identity choices influence access control, and architecture has practical implications for deployment, observability, security, and incident readiness.

Ayunis describes the post as hands-on technical leadership. The engineer will work closely with the CTO and the engineering team, set direction for important decisions, and support other engineers in delivering independently. The expectation is not to become a gatekeeper for every complex issue, but to create clarity where shared technical choices are needed and to stay close enough to code and production to understand the trade-offs.

The role also links technical design to the way public-sector customers use software. Product and customer-facing teams bring recurring needs into view; the engineer helps assess when those needs should become durable, reusable product capabilities. Stable APIs, software development kits, and integration patterns matter in this setting because external document-management and identity systems need dependable connections rather than one-off solutions.

About the Employer: Ayunis

Software Designed for Public Administration Workflows

Automation, controlled AI use, and structured digital processes

Ayunis develops specialised software for the public sector. Its software is used by cities, municipalities, and districts in Germany, Austria, and Switzerland. The company describes its purpose as helping public administration retain capacity for its core responsibilities by automating repeated processes, reducing manual effort in specialist departments, and making more room for work involving citizens and complex cases.

The employer's products are designed around concrete requirements from public institutions. Ayunis says its cloud-operable solutions are intended to create transparent workflows and enable a controlled use of AI while preserving data sovereignty. Its approach takes account of regulatory requirements, procurement processes, and organisational characteristics that are relevant when technology is introduced into public administration.

Ayunis connects consulting, implementation, and ongoing development. The company describes analysing existing processes, identifying appropriate use cases, and defining responsibilities for implementation. It also describes designing, developing, and integrating solutions into existing information-technology structures with attention to compatibility, security, and maintainability. This context gives the principal engineer a practical reason to care about integration quality as well as core-product design.

From Municipal Resource Software to Broader Administration Support

Product, engineering, and public-sector understanding in one setting

Ayunis Core is presented as an open-source AI platform for reducing repetitive administrative work. The employer says data protection, information security, and regulatory requirements are integral to its operation and use, and describes Germany-based hosting for its systems. It also states that its engineering and product work is informed by an understanding of public structures, with the aim of producing systems that are technically robust and can be integrated into organisational practice.

The company traces its development from software for managing municipal resources such as civic centres, sports facilities, and event spaces. Ayunis says that experience revealed a need for structural relief beyond resource management, leading to a broader focus on automated processes, modern infrastructure, and digital sovereignty for public administration. That background helps explain why the vacancy combines application architecture, integration patterns, operating concerns, and product judgement.

Open Positions

Application Guidance

Present Evidence of Architecture and Operational Judgement

Focus preparation on the decisions that connect product, platform, and infrastructure

A focused application for this position can make the connection between architecture and delivery visible. Rather than listing tools without context, candidates can select examples in which they designed a boundary, improved an integration, made a production system more observable, or resolved an issue that required both diagnosis and implementation. Explain the situation, the technical alternatives considered, the decision made, and the effect on reliability, maintainability, or delivery. That format is particularly relevant to a role that must make pragmatic choices rather than pursue complexity for its own sake.

It is also useful to prepare examples of influence without formal authority. Consider describing how a technical direction was communicated, how colleagues were enabled to make decisions independently, and how a disagreement was handled constructively. For the integration aspect, be ready to discuss API design, authentication or identity boundaries, event flows, synchronisation, and operational ownership. Because the vacancy calls for confident German and English communication, candidates should ensure that their technical explanations are clear and precise in both languages.

• Choose a production example that shows a concrete architecture decision and its operational consequences.
• Prepare an integration case covering an API, identity boundary, webhook, synchronisation flow, or event-driven design.
• Describe how observability, security, reliability, or incident readiness shaped a system you worked on.
• Identify an example of helping engineers progress through technical direction rather than title-based authority.
• Review the listed TypeScript, Node.js, application-stack, infrastructure, and AI-assisted development context before a technical discussion.
• Write concise German and English explanations of the systems and decisions most relevant to the role.

How to Apply

Submit Your Application Through the Verified Route

Use the employer's verified role-specific application portal

Ayunis receives applications for this specific position through its official portal, opened from the button below. The captured route opens with an email step; continue through the on-screen instructions and provide only the information and material requested there. The application component below reveals the verified route after its short countdown.

Before opening the portal, prepare a concise account of relevant production software work, architecture decisions, integrations, infrastructure ownership, and technical leadership. The vacancy requires confident communication in German and English, so present technical experience with clear and accurate language. The captured application route does not display a separate document checklist before the initial email step.