Senior Backend(major) +Frontend(minor) Engineer (Contract, 3 months):
Summary
Three-month contract senior engineer (via emagine) building a dedicated release-tracking database and a release-gate dashboard for Spotify's Android/iOS apps, including migrating release tooling off Jira. Mostly backend work in Java and Python, with minor frontend work in React and TypeScript.
Location: [Remote / Stockholm / hybrid]
Duration: 3 months, starting ASAP
Team: Release Squad , Client Platform
About the role
As part of owning this process we also interact with a lot of teams and projects that develop features shipped as part of the main apps. To keep track of bugs and blockers for specific releases we use multi-team projects in Jira with a lot of automation in place. The Release Process progress is currently also tracked in Jira. We are migrating to a new tooling and want to have a separate proper database for tracking the Releases.
Along with this we are also updating the Release process to include more metrics, guardrails and alerting. Our goal is a release gate that adds stronger quality checks, using agreed performance and stability metrics with clear thresholds, without slowing releases down.
Today, the Release Manager has to piece together signals from several dashboards, and those dashboards use different definitions and data sources. You’ll help turn our Release Manager Dashboard into the single control center for release decisions. It should show the right metrics, compare them against thresholds, and make the consequence of each threshold clear, creating automatic tickets and alerts when the thresholds are breached.
This is a hands-on, high-ownership role. We’re looking for someone who can ramp up quickly, ship in the first weeks, and work comfortably across frontend and backend.
What you’ll do
Build the solution for a separate database for tracking the Release Process.
Understand the dependency of the multi-team projects in Jira and the related automation of the release tooling to help propose, design and implement solution
Build the release gate experience in the Release Manager Dashboard. This includes metric and threshold views, pass/warn/block states, and clear next steps for release managers.
Build the tooling so it supports the flagship Spotify Android and iOS apps first and can be extended to other clients later.
Work closely with the Release Manager, Data Scientists and Release Engineers, to turn agreed decisions into working software.
Write clean, tested, maintainable code, and leave good documentation behind so the team can own it after your contract ends.
What you’ll bring
5+ years of professional software engineering experience, with a track record of shipping full-stack features from start to finish.
Strong Backend skills in Java and Python. You should be experienced with REST or gRPC APIs and service design
Experience with frontend in React and TypeScript, including building data-rich internal tools and dashboards with good attention to usability.
Experience working in a large, existing codebase and getting productive quickly with little hand-holding.
Good product judgment. You can take a loosely defined process and turn it into a simple, usable tool.
Clear written and verbal communication, and comfort working with several partner teams at once.
Nice to have
Familiarity with mobile release processes and CI/CD tooling.
Experience with Backstage plugin development.
What success looks like after 3 months
The Release Process has a separate database for tracking the releases and are not on Jira
The Automated Release tooling dependent on Jira is successfully migrated.
Nice to have The Release Manager Dashboard is a translation of the new updated Release Process.
The team has a clean handover: documentation, tests, and a short list of recommended next steps.
Top 3 Hard Skills:
Backend Engineering: Java, Python, REST/gRPC API & database design.
Frontend Development: React & TypeScript for internal dashboards.
Full-Stack Execution: Navigating large codebases and shipping features end-to-end.
Top 3 Soft Skills:
High Ownership: Ramping up fast and delivering with minimal guidance.
Product Judgment: Turning loose requirements into intuitive tools.
Cross-Team Communication: Collaborating effectively with partner engineering teams.
Start: ASAP - 3 months.
