What Song

Web: https://what-song.com

Data API: https://what-song.com/data-api

WhatSong is a music discovery platform and database focused on songs featured in movies and TV shows. It combines a large catalog of soundtrack data with community contributions and integrations with services such as Spotify, Apple Music, and TMDB. I worked on WhatSong for more than 1.5 years as a developer at Embryonic Studio, which was responsible for the development and technical maintenance of the platform. During that time, I became one of the core developers maintaining the product, working across both the Next.js frontend and the NestJS API backed by PostgreSQL, Prisma, and GraphQL. Following the acquisition of WhatSong by its current owner, the platform went through a major redesign. As part of the Embryonic Studio team, I was responsible for much of the technical implementation of the redesign, rebuilding and adapting the frontend while continuing to maintain and extend the existing backend. Later, I also worked on the development of WhatSong's commercial Data API, which exposes its soundtrack dataset to external developers and businesses. I wasn't the technical lead for this project, but I implemented a significant part of the API and its underlying functionality using NestJS. All of this work was carried out as part of my role at Embryonic Studio.

During more than 1.5 years working on WhatSong through Embryonic Studio, I became one of the core developers responsible for the day-to-day evolution and maintenance of the platform. My work covered the technical implementation of its major redesign, continued development of the Next.js frontend and NestJS backend, new product and community features, third-party integrations, and maintenance of its large relational soundtrack dataset. I also contributed substantially to the implementation of the commercial WhatSong Data API, helping transform data originally built for the internal product into a service that could be consumed by external developers and businesses. What made the project particularly valuable from an engineering perspective was working on an established production system over an extended period. Changes had to account for existing users, data, URLs, integrations, and functionality rather than being designed in isolation. The project gave me extensive experience working as part of a professional development team with long-term responsibility for a production product, across frontend development, backend APIs, relational databases, external integrations, deployment, data maintenance, and production debugging.

Frontend

Next.js

React

TypeScript

Tailwind CSS

Responsive UI

Component Architecture Backend

NestJS

GraphQL

REST APIs

Prisma ORM

PostgreSQL

API Design Data

Relational Data Modeling

Data Migration

Data Cleanup & Deduplication

Large Dataset Maintenance Integrations

Spotify API

Apple Music API

TMDB API

Third-party Data Integration Product & Infrastructure

Production Application Maintenance

CI/CD

Docker

Nginx

Git

GitHub

Statsig

A/B Testing