What would your job be like at Scilife?
At Scilife, we are on a mission to empower life sciences companies with robust, scalable, and compliant solutions. As a Senior Backend Engineer in our Oxygen team, you will primarily work on our fundamental Training module that is at the core of our QMS. You’ll dive deep into our existing systems, helping us tackle tech debt head-on while building clean, maintainable, and performant backend services.
This role is perfect for someone who enjoys balancing the act of refactoring legacy code with building modern, scalable backend systems. You'll be involved in decisions that shape the architecture and future of our Training module while ensuring it remains stable, secure, and efficient.
If you’re excited about improving systems from the ground up, crafting high-quality backend solutions, and collaborating with an ambitious remote team, this role is for you!
Your responsibilities
- Design, implement, and maintain core backend services in Go — including authentication, event bus, audit trails, and other shared infrastructure components.
- Integrate these foundational services with both the legacy QMS monolith and new microservices, helping to establish the foundation for Scilife’s next-generation QMS platform.
- Apply clean architecture and domain-driven design principles to ensure the system remains maintainable, scalable, and future-proof.
- Proactively identify and reduce technical debt across key components and shared services.
- Collaborate closely with Oxygen main stakeholder - other engineering teams to meet their needs and deliver secure, high-performing, and compliant solutions.
- Promote best practices in testing (including TDD), code quality, and automation.
- Contribute to architecture discussions and design reviews, both mentoring and learning from peers.
- Partner with your Engineering Manager to align technical initiatives with Scilife’s long-term platform vision.
What you will need
Technical skills:
- 5+ years of experience in backend engineering.
- Strong understanding of system design, microservices, REST APIs, and platform-level topics such as authentication, integrations, and observability.
- Solid foundation and hands-on experience with Go, or a strong willingness to quickly become proficient in it.
- Working knowledge of PHP — comfortable reading and modifying existing code, though not focused on developing new features in it.
- Familiarity with modern infrastructure and DevOps tools such as Docker, Kubernetes, Infrastructure-as-Code, and AWS.
- Experience with automated testing practices, including unit and integration testing, and CI/CD pipelines.
- Enthusiasm for improving and integrating with legacy systems through thoughtful refactoring.
Mindset & working style:
- Think in systems, not just code — see the bigger picture of platform architecture.
Balance pragmatism with long-term quality.
- Excited about working with legacy code as much as building new systems.
- Strong communicator and collaborator in a remote-first, international environment.
- Ownership mindset with eagerness to continuously learn.
Why Scilife?
- Work on platform services that power a regulated SaaS product used globally in Life Sciences.
- Help shape the future of a mission-critical QMS platform as we transition to modern architecture and Go-based services.
- Be part of a remote, ambitious team that values collaboration, knowledge sharing, and engineering excellence.
- Grow your career by working on cross-cutting platform challenges: scalability, security, APIs, service orchestration.
Application Instructions:
- Stage 1 — HR Screening Call (20–25 min)
Goal: to assess: motivation, remote-work maturity, expectations, compensation, basic experience verification.
- Stage 2 - Technical Screening (45 min, EM)
Goal: Validate they can reason about systems similar to Scilife, verify culture/architecture alignment. No testing coding here — only reasoning and engineering maturity
- Stage 3 — Deep Dive Session (90 min) (Senior Engineer(s), EM)
Goal: deep dive into coding, maybe a task or two, talk and verify system architecture and design experience and skills.
- Stage 4 - CTO / VPE Fit Call (30 min)
Goal: Brief alignment
- Stage 5 - Offer
