Job Opportunities API

📍 Oslo 💰 Salary: 1,400,000 – 1,600,000 NOK Four years ago, Aidn was just an idea. Today, we offer the best EHR in Norway and are the market leader in the municipal healthcare sector. It would be hard to overstate how rewarding that journey has been—but it is just the beginning. As Aidn matures from startup to industry leader, we will do more than offer a great product. We will become the healthcare platform that elevates the entire ecosystem. This process will force us to level up continuously. The next few years will be hard, even by the standards of some of the most capable people around. But that’s what will make them special. During these transition years, a particular area of focus will be how we leverage our platform and its underlying services to give ourselves the speed and flexibility needed to improve our existing products while expanding into new markets. Whoever is leading this product area will be in the driver’s seat for one of the most critical initiatives in one of the most influential companies in Norway. They will learn and do more in the next two years than most people will in ten years at other companies. If that sounds like your cup of tea, read on. The team Aidn’s product, design, and engineering departments work cross-functionally from top to bottom. The CTO and CPO work in tight collaboration every day. Directors and product teams are expected to work in the same manner. You will work in a cross-functional leadership team alongside a product director and a design director. Together, you will own the product area that sits between our market-oriented areas, including PLO, helsestasjon, and patients/next-of-kin, and our platform area, which covers low-level concerns such as infrastructure, IAM, data analytics, integrations, and archive. This middle space builds upon our platforms, providing reusable domain services and common orchestration patterns to our user-facing products. Today, the area includes agentic services, chat, notifications, navigation, training, and personalization, but it will soon also include core concepts like the journal, forms, labs, e-prescription and tasks. Problems we're working on right now include: How do we build agentic services that can be used everywhere in our products while maintaining enough governance and control to satisfy medical device regulation (MDR)? How do we provide up-to-date training for thousands of health care workers across multiple roles without requiring classroom instruction? How do we offer personalized views for different roles and products without polluting our code with conditionals? Where are the boundaries between core domain services and role-based workflow services? How should our logical architecture be structured to support a multi-product, multi-surface, platform-enabled Aidn? The role As an engineering director, you will have the freedom to make real decisions and will have accountability for the technical outcomes and engineers in your product area. Your core responsibilities will include: Defining the delivery strategy for your area with your peers—ensuring area goals align with company goals, workload is sustainable, and capacity needs are within budget—and owning the technical outcomes from your product teams Managing risks and dependencies in your area with your peers, helping teams make mitigation plans and following up when those plans cross team boundaries. Setting the standard for how non-functional work is surfaced, discussed, and prioritized in your area and across Aidn. Owning the architectural direction for your area, defining goals and success metrics in collaboration with principal and staff engineers and supporting their concrete plans. Defining and maintaining the engineering standards in your area, ensuring quality and performance levels are aligned with the company’s objectives and risk appetite. Setting the bar for AI-native engineering across y