Principal Software Engineer

At Epignosis our mission is simple yet bold: To make learning technologies accessible to every business, regardless of geography, sector, or company size. And we've been doing just that for more than two decades, empowering millions of people to grow, learn, and thrive through technology that's both powerful and affordable. We're rapidly becoming one of Greece's largest SaaS companies, serving 12,000+ companies and 22+ million learners worldwide with solutions like TalentLMS (an award-winning cloud LMS built for simplicity), eFront (an enterprise LMS), TalentCards (a mobile app for deskless training), and TalentHR (a lightweight HRIS for people operations). Our success is built on a team that believes that work should matter: not only to you, but to the world around you. We're looking for people who light up when solving hard problems, who care deeply about their craft, and who want to build something that genuinely helps people grow. We are looking for a Principal Software Engineer to serve as a technical authority across our four products, helping bring their independent architectures together into a connected suite. As our most senior individual contributor, you'll drive critical architectural decisions and shape the shared platform foundations that enable our product teams to move faster and scale effectively. Your initial focus will be on building common identity, authentication, billing, and subscription capabilities, ensuring secure, scalable solutions with clean interfaces and smooth migration paths. This is a highly influential role that combines strategic technical leadership with hands-on engineering, where you'll identify the challenges that matter most, guide teams toward the right solutions, and build foundations that other engineers can rely on. Responsibilities As a Principal Software Engineer, you will: • Set cross-product technical direction and the architectural constraints Staff and teams operate within, written down so teams can move quickly without painting us into corners. Anchor that direction on our emerging platform layer: identity and billing. • Lead the design of our first shared platform services, starting with a common identity layer across products with different starting points, and set the patterns the services after it will follow. • Work hands-on where it counts: proving out an approach, building the first version of something hard, or unblocking a team that's stuck. • Raise the technical bar through code review, design review and mentorship, including Staff and less experienced engineers. • Help us get the most out of AI-assisted development while keeping what reaches production safe. This has shifted the constraint to review and validation, and we want a serious mind on it. • Make build-versus-buy recommendations on foundational services, and be clear-eyed about the long-term cost of each. • Identify organisation-level technical risks and drive clear mitigation priorities. • Partner with engineering managers and product leadership, translating between technical reality and business consequence in both directions. What success looks like in your first year: • Multi-year platform direction is written down and shows up in the roadmaps of the teams that depend on it. • First shared platform services are in motion, with interfaces, migration paths, and a security bar other teams can trust. • Staff and senior engineers around you own cross-domain work without needing you in every decision. Requirements To be successful as a Principal Software Engineer you should: • 6+ years building production software, with several years operating at staff or principal level. • Experience with multi-tenant SaaS architecture, including tenant isolation, shared services, and cross-product data at scale