> Markdown version of [/jobs/ext/1944106-senior-software-engineer-ai-native-development](https://www.wearedevelopers.com/jobs/ext/1944106-senior-software-engineer-ai-native-development). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Senior Software Engineer : AI-Native Development - **Company:** myra group GmbH - **Location:** München, Germany - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** PHP (Programming Language), Application Programming Interfaces (APIs), Artificial Intelligence, Mobile Application Development, Software Quality, Continuous Delivery, Continuous Integration, Data Validation, Linux, Python (Programming Language), Service Design, Symfony, ReactJS, Backend, Containerization, Graphql, Front End Software Development, Multiaccess Edge Computing, Software Coding, Docker - **Published:** August 6, 2026 - **Apply:** https://www.adzuna.de/details/5829298807 ## About the Role * You think in systems. You start from the problem and the constraints, not from a favorite language. To you the difference between languages is largely syntax; what actually matters is the environment code runs in: performance, portability, compatibility, operational cost, and long-term maintenance * You can explain your choices. You can walk us through a time you chose one language or runtime over another, and the trade-offs that drove the decision, and you can do the same for the frontend when a feature calls for it * You've gone deep, not just broad. At least 5 years of intensive, hands-on coding and engineering experience - this is a senior role and not a fit for juniors - with genuine depth in at least one or two ecosystems. Our stack today is mostly PHP / Symfony, React and GraphQL; Edge systems use C, Rust and Python mostly. * We care a lot about experience with Python, Go, C and/or Rust. These are parts that are being introduced to our dev department and where a significant part of our edge logic is based in, and someone who already reasons and builds fluently in them will make an outsized difference; this is a real signal for us, not a nice-to-have footnote * Security and code quality are instincts, not afterthoughts. You write code that holds up under hostile, high-volume traffic; you treat every input as untrusted, validate rigorously, and understand how a weak boundary or a hot-path regression becomes an attack surface. Reliability under load is a first-class concern for you * You're fluent with AI-assisted development. You treat AI coding agents as core tooling; you know their strengths and limits, and you own the outcome (including reviewing AI-written code for exactly the security and validation gaps above) * You reason comfortably about the whole picture: APIs, services, data, and the frontend the feature owns; you don't stop at a language boundary * You're at home on Linux systems, and CI/CD pipelines, containerization (Docker), and deployment considerations are a natural part of how you think about shipping software, not foreign territory * Curious by default; you like to validate ideas hands-on with POCs and RFCs * At home in an agile team with structured requirements, and quick to learn * You speak and write English fluently ## Description We protect our customers' digital infrastructure, keeping it secure, fast, and online, even under active attack. As a cybersecurity provider, we run high-performance systems in a genuinely hostile environment, where code quality, security, and rigorous input validation are not hygiene: they are the product. Our customers trust us with business-critical traffic, and we build and operate to the highest standards of certification for critical infrastructure., * Own features end-to-end, from backend service design through to the frontend slice the feature needs, in an international, cross-functional team of software engineers, QA and OPS professionals * Design, validate and advocate architecture decisions for your team's verticals, with a bias toward well-structured, service-oriented backends * Work AI-natively: use AI coding agents as core tooling to move faster and raise quality, while staying fully accountable for the code you ship * Drive technical discussions and decisions with your team * Push toward continuous delivery, improving both the software and how we build it * Write code that performs, and holds up in production under hostile, high-volume traffic, with security and input validation built in from the start ## Related Videos - [Docker network without Docker](https://www.wearedevelopers.com/videos/1418-docker-network-without-docker) - [Hiring AI Native Talents](https://www.wearedevelopers.com/videos/100268-hiring-ai-native-talents) - [Docker Compose: Rediscovered](https://www.wearedevelopers.com/videos/1978-docker-compose-rediscovered) - [Putting the Graph In GraphQL With The Neo4j GraphQL Library](https://www.wearedevelopers.com/videos/257-putting-the-graph-in-graphql-with-the-neo4j-graphql-library) - [Docker exec without Docker](https://www.wearedevelopers.com/videos/1094-docker-exec-without-docker) - [Docker build without Docker](https://www.wearedevelopers.com/videos/100114-docker-build-without-docker) ## Related Articles - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [The Most Popular IT Jobs on the Market](https://www.wearedevelopers.com/magazine/376-the-most-popular-it-jobs-on-the-market) - [Where To Find Software Engineering Jobs](https://www.wearedevelopers.com/magazine/396-where-to-find-software-engineering-jobs) - [The 12 Best Jobs for Software Engineers](https://www.wearedevelopers.com/magazine/401-the-12-best-jobs-for-software-engineers) - [Is Software Engineering Over-Saturated?](https://www.wearedevelopers.com/magazine/418-is-software-engineering-over-saturated) - [Find a Developer Job: 12 Best Job Sites For Developers](https://www.wearedevelopers.com/magazine/165-find-a-developer-job-12-best-job-sites-for-developers)