Software Architect 80

For 26 years, Medgate has been bringing doctors directly to patients 24/7 thanks to telemedicine. At Medgate Switzerland, more than 300 motivated employees - including over 130 permanently employed doctors - are actively shaping the medicine of tomorrow with the help of future-oriented digital health solutions.

Those who treat patients remotely at Medgate receive intensive training in telemedicine at the beginning. The medical guidelines developed for the needs of telemedicine and continuously refined over the years are practice-oriented and designed for remote treatment. The patient management system supports doctors in their treatment by using artificial intelligence, among other things. This means that doctors have less administrative work and can focus more specifically on their patients. The medicine of the future is already a reality at Medgate.

With flexible working models and reliable duty scheduling, Medgate makes it easy to combine work, leisure and family life.

About the role

Medgate's technical ecosystem spans multiple platforms and components: Sofia (our core patient management system), partner-facing intake channels, mobile applications, data and analytics, internal tools, and prototypes still proving whether they belong in production. Each of them has its own history, constraints and reasons for existing. As Software Architect you work across all of it: two architects for five engineering teams, sharing the full scope between you.

You own the consistency of that ecosystem, the trade-offs between its parts, and the hard calls that span more than one team.

You hold a technical veto on architecture decisions, exercised in a room where commercial, medical and regulatory constraints carry their own weight. A large part of the role is spent upstream, while requirements are still being shaped, negotiating those trade-offs with the people who carry them: product owners, business stakeholders, medical and compliance. Getting a technically sound answer accepted by all of them is the job itself.

• Work upstream in the requirements process (PRD), establishing what each option costs to build and to run, what it commits us to later, and which one holds up once the commercial, medical and regulatory constraints are applied.
• Align architecture, security and data residency decisions with our internal Compliance team.
• Advise on which stack, pattern or vendor fits a given component or platform across Medgate's ecosystem, weighing each case on its own merits, with the incumbent stack as one option among several.
• Run cross-team design and architecture reviews that catch coupling, duplicated logic and inconsistencies between modules or projects before they harden into technical debt, independently of any single product owner's roadmap.
• Establish which build-or-buy options genuinely remain once vendor delivery model, data residency and existing licences have narrowed the field - and what each one costs to live with.
• Challenge existing architecture choices when a new problem's context calls for a fresh answer - and confirm them where they still hold, once actually tested against the new case.
• Maintain a lightweight, living set of shared technical standards and decision records, so settled trade-offs stay settled from one project to the next.
• Act as the technical counterpart for integration partners, from first feasibility discussion through to a working integration.
• Advise engineering leadership and product owners on scalability, integration risk and platform-level consequences ahead of major initiatives, in terms a business stakeholder can weigh in on.
• Take a system-level view of where and how Medgate's AI-assisted engineering workflow (Claude Code and its multi-agent pipeline) should evolve across teams and repositories, distinct from any one team's day-to-day use of it.

Your profile

Must have

• 8+ years of software engineering experience, including a genuine track record in architecture or cross-team technical leadership roles.
• Hands-on-enough background in modern backend and web stacks (.NET/EF Core, React-based SPAs) to credibly challenge concrete implementation choices, while implementation itself stays with the teams.
• Solid experience with server-side GraphQL, including schema composition.
• Working command of data and analytics, data flows, cloud infrastructure (Azure), infrastructure-as-code (Terraform) and security. Enough to hold a defensible position in each, across five teams with distinct technology profiles.
• Experience identifying and resolving architectural drift and duplicated patterns across teams (e.g. two teams solving the same problem in two different ways) and turning that into a remediation call that was actually carried out.
• Fluent English, spoken and written. German or French is a strong advantag