EU remote
Senior Fullstack Engineer (Elixir)
About this role
About the Role Tellent is a talent management suite: an ATS, an HRIS, and Performance Management, with AI capabilities woven through all of them. Our customers increasingly use more than one product, and expect them to work as one. The Platform team is where those products meet: shared foundations, cross-module sync, the pieces that make three apps feel like one suite. You'd join Platform and work closely with our Product Enablement team on cross-product work, including a growing set of AI-driven capabilities.
This is a genuinely cross-stack seat. The backend core is Elixir, and can show up too, for example in Manage. But the problems don't stay in one codebase: one week it's a Phoenix service, the next it's a React screen in one product and an Angular one in another. We're looking for someone who follows the problem wherever it lives, doesn't need a fully specified ticket, and enjoys working in more than one codebase without waiting for a pattern to exist first.
Your 12-Month Journey First 3 months: learn how our products talk to each other, ship your first cross-product improvement in, get comfortable in at least two of our codebases. Within 6 months: own an enablement or platform area end to end, from an ambiguous ask through design, build, and measured outcome. Be the person others ask about it. After 1 year: shape how cross-product capabilities get built at Tellent , and be one of the engineers who raises the bar for working across the suite.
What You'll Be Doing Building the shared foundations and integrations that connect our products, on an Elixir/Phoenix core. Working across the frontend stacks of the products you touch: React in some, Angular in others, whatever the problem needs on top of the backend work. Think 60/40 backend/frontend, not 100/0. Turning fuzzy enablement and AI ideas into buildable slices: you get problems, not tickets, and help decide what to build before deciding how.
Shipping to mature products with thousands of organizations on them, then checking whether it actually moved anything. Working in existing codebases with existing conventions. Bringing a new pattern into a mature codebase takes more effort, but we do it often, and your judgment on when it is worth it counts. Collaboration: daily with the Platform team and Product Enablement (PM, design), plus the engineers of the product teams you integrate with.