Senior Backend/Frontend Engineer (Contract)

Quick Facts

• Role: Senior Backend/Frontend Engineer (Contract)

• Duration: 3 months (starting ASAP)

• Focus: Release process tooling and Release Manager Dashboard

Description

Build and migrate release tracking to a separate database and modernize the Release Process with metrics, guardrails, and alerting. Turn the Release Manager Dashboard into a single control center with unified definitions, threshold comparisons, and automatic tickets/alerts when thresholds are breached. Work with Release Manager, Data Scientists, and Release Engineers to implement working software for Android and iOS apps first.

Responsibilities

• Build a separate database for tracking the Release Process (replacing Jira-based tracking).

• Understand Jira multi-team project dependencies and release tooling automation to propose and implement solutions.

• Build release-gate experience in the Release Manager Dashboard: metric and threshold views, pass/warn/block states, and clear next steps.

• Develop tooling that supports Spotify Android and iOS apps first and can extend to other clients.

• Collaborate with Release Manager, Data Scientists, and Release Engineers to translate decisions into working software.

• Write clean, tested, maintainable code and provide documentation and handover for team ownership after the contract ends.

Requirements

• 5+ years of professional software engineering experience with full-stack delivery end-to-end.

• Strong backend skills in Java and Python; experience with REST or gRPC APIs and service design.

• Frontend experience with React and TypeScript for data-rich internal tools and dashboards.

• Experience ramping up quickly in a large, existing codebase with limited hand-holding.

• Product judgment to turn loosely defined processes into simple, usable tools.

• Clear written and verbal communication and comfort working with multiple partner teams.

Benefits

• Hands-on, high-ownership role with the expectation to ship early.

• Opportunity to strengthen release quality checks using agreed performance and stability metrics without slowing releases.

Success Criteria (after 3 months)

• The Release Process uses a separate database for release tracking (not Jira).

• Automated Release tooling dependent on Jira is successfully migrated.

• (Nice to have) The Release Manager Dashboard reflects the updated Release Process.

• Clean handover with documentation, tests, and recommended next steps.