Senior Software Engineer

Start free →

Or apply yourself on the official page →

About the role

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 Senior Software Engineer to take ownership of the most complex and ambiguous engineering challenges within their team. You’ll take substantial projects from an unclear problem through to production and beyond, identify architectural and delivery risks before they become issues, and raise the bar for code quality, testing, and reliability across the systems your team owns. You’ll also play an important role in helping the engineers around you grow through code reviews, pairing, knowledge sharing, and technical direction. The role is scoped to a single team. You’ll collaborate across team boundaries when the work calls for it, while driving multi-team architecture or engineering standards sits at the level above. Responsibilities As a Senior Software Engineer, you will: • Lead complex work end to end. Take substantial features and services from design through delivery and production follow-up. You're accountable for how they behave in production, not just for merged pull requests. • Turn ambiguity into a plan. Turn unclear problem statements into a technical approach, a delivery plan, and explicit trade-offs. Work with Product Managers on PRD analysis, story breakdown, acceptance criteria, and success metrics. • Make and record design decisions. Own design decisions within your team's domain: data model, API surface, background processing, failure modes, caching, and concurrency. Write down significant decisions before building, including the alternatives you rejected and the consequences you accepted. • Spot risk early. Surface architectural, security, reliability, and delivery risks, such as unclear requirements, cross-team dependencies, and scale cliffs. Bring viable alternatives, and escalate decisions that sit beyond your authority. • Build security in. Design and implement security controls that fit the system and its trust boundaries. Be deliberate about who and what can reach each surface, how data is protected, and how dependencies and secrets are managed. Think about threats during design, not after. • Raise engineering health. Strengthen tests, observability, design boundaries, and reliability controls for team-owned systems. Propose refactoring, performance, and simplification work with a clear payoff, even when nobody asked for it. • Take on the hardest problems. Troubleshoot the team's toughest technical and production issues. Lead incident response for team-owned systems, and drive postmortem actions to closure so the same root cause doesn't come back. • Review in a way that teaches. Give technical direction through code and design review. Explain your reasoning, link references, flag missing tests, and separate fact from preference. • Grow the people around you. Mentor less experienced engineers through pairing and guidance so they can take on harder work

View the official posting →