Senior Full-Stack Engineer - Artist Success
SoundCloud · New York, United States · 3 wk ago
Engineering$160k–$190k/yrFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (or Qualifications, Skills), Benefits, Pay, Schedule if present. The posting includes salary range, benefits, schedule? No explicit schedule. So we include Pay and Benefits sections. Also maybe "About Us" but not required heading; we can include as prose maybe under About the role? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content. So we need sections: About the role (intro paragraph), Responsibilities (list), Requirements (list maybe combine Experience And Background), Benefits (list), Pay (salary). No Schedule.
We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove Diversity, Equity and Inclusion section? It's boilerplate? It's specific content about DEI; but it's not listed as required heading; we could include as prose maybe under About Us? But instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. DEI might be considered EEO? It's about diversity; but it's not exactly EEO warning. Might be okay to keep? Safer to remove? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The DEI section is more about company values, not a legal disclaimer. Could keep as prose under About Us? But we don't have a heading for About Us; we could incorporate into About the role? Might be better to keep as a separate section? Not in allowed headings list. Could just omit it to be safe.
We need to preserve all substantive information; not invent or summarize away detail. So we need to include the details about responsibilities, experience, benefits, salary, etc.
Let's extract:
About the role: first paragraph: "SoundCloud empowers artists... SoundCloud is looking for a Senior Full-Stack Engineer to join our Artist Success team. You will take technical ownership of the tools that help artists understand their audiences, grow their careers, and help the music industry discover its next stars. You will work within a high-performing, multi-disciplinary squad across our frontend (React, iOS, and Android) and backend (GraphQL, TypeScript) services, focused on strategic Artist Success products including the A&R Dashboard, Fan Insights, and artist-facing growth and insights experiences. This is an IC-heavy role for a technical expert who wants to drive architecture and execution while maintaining a hands-on presence in the code. The ideal candidate has a track record of building and evolving complex, high-quality products across frontend, API, backend, and data systems. You are a generalist who can navigate user-facing application logic, service architecture, data-intensive systems, or infrastructure bottlenecks with equal ease."
That's the About the role.
Responsibilities: bullet list under "Key Responsibilities". Items:
- Work closely with engineers, Product Managers, Designers, and other partners to shape the technical direction and roadmap across Artist Success products, including the A&R Dashboard, Fan Insights, and related artist-facing experiences. You'll help the team make thoughtful architectural decisions and build scalable, secure systems that support large datasets and high-performance user experiences
- Act as a senior technical contributor for a small, expert squad. You will contribute through architectural clarity, rigorous peer reviews, and a focus on maintaining high execution momentum
- Work as a peer to Product Managers and Designers to define requirements across Artist Success. You'll turn vague business "wants" into concrete technical "hows," ensuring the team builds the right things in the most efficient way
- Ensure high technical standards across frontend and backend disciplines. While the team is highly capable, you are responsible for contributing to the overall technical health, consistency, and long-term sustainability of the codebase
- Own the infrastructure and health of your domain. You'll manage deployment patterns, infrastructure as code using Terraform, and ensure we adhere to modern security standards
- Leverage agentic workflows and AI-assisted engineering as a force multiplier while keeping the needs, judgment, and experience of the people using and building our products at the center of the work
That's responsibilities.
Experience And Background (requirements): list:
- 4-6+ years of experience with React and modern frontend development, with the ability to influence architectural decisions and drive best practices; experience with native iOS or Android applications is a plus
- Strong proficiency in GraphQL and TypeScript for building reliable APIs and services, with familiarity in Golang or Scala, and a strong understanding of storage, querying, and data-intensive systems such as BigQuery and SQL
- Strong capability in Infrastructure as Code, particularly Terraform, and container orchestration
- Ability to explain complex technical trade-offs to non-technical stakeholders and collaborate effectively across engineering, product, design, and data
- Demonstrated ability to leverage modern AI and agentic tools to improve quality and velocity, while applying sound judgment around when human expertise is essential and maintaining code quality, product standards, maintainability, and user experience
That's requirements.
Benefits: list under "Benefits":
- Comprehensive health benefits including medical, dental, and vision plans, as well as mental health resources
- Robust 401k program
- Employee Equity Plan
- Generous professional development allowance
- Interested in a gym membership, photography course or book? We have a Creativity and Wellness benefit!
- Flexible vacation and public holiday policy where you can take up to 35 days of PTO annually
- 16 paid weeks for all parents (birthing and non-birthing), regardless of gender, to welcome newborns, adopted and foster children
- Various snacks, goodies, and 2 free lunches weekly when at the office
Pay: salary range: $160,000 - $190,000 annually. Also note final salary determined based on experience etc. We can include that as prose.
Schedule: not present, so omit.
We also have "About Us" paragraph: "We are a multinational company with offices in the US (New York and Los Angeles), Germany (Berlin), and the UK (London)We provide a flexible work culture that offers the opportunity to collaborate and connect in person at our offices as well as accommodating work from homeWe are deeply committed to ensuring diversity, equity and inclusion at all levels of our organization and fostering a community where everyone’s voice, perspective and experience is respected and heardWe believe a strong team is made by investing in employees through mentorship, workshops and enrichment opportunities". This is substantive; we could include as a paragraph under About the role or separate section? Not in allowed headings; maybe we can incorporate into About the role as additional prose. But we must not invent headings. Could add a paragraph after About the role before Responsibilities? Might be okay to include as part of About the role. However the instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Include a section ONLY when posting has real, specific content. So we need sections: About the role (intro paragraph), Responsibilities (list), Requirements (list maybe combine Experience And Background), Benefits (list), Pay (salary). No Schedule.
We must not repeat job title as heading. No Job ID. Remove boilerplate: cookie/navigation/legal/EEO etc. Also remove Diversity, Equity and Inclusion section? It's boilerplate? It's specific content about DEI; but it's not listed as required heading; we could include as prose maybe under About Us? But instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. DEI might be considered EEO? It's about diversity; but it's not exactly EEO warning. Might be okay to keep? Safer to remove? The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. The DEI section is more about company values, not a legal disclaimer. Could keep as prose under About Us? But we don't have a heading for About Us; we could incorporate into About the role? Might be better to keep as a separate section? Not in allowed headings list. Could just omit it to be safe.
We need to preserve all substantive information; not invent or summarize away detail. So we need to include the details about responsibilities, experience, benefits, salary, etc.
Let's extract:
About the role: first paragraph: "SoundCloud empowers artists... SoundCloud is looking for a Senior Full-Stack Engineer to join our Artist Success team. You will take technical ownership of the tools that help artists understand their audiences, grow their careers, and help the music industry discover its next stars. You will work within a high-performing, multi-disciplinary squad across our frontend (React, iOS, and Android) and backend (GraphQL, TypeScript) services, focused on strategic Artist Success products including the A&R Dashboard, Fan Insights, and artist-facing growth and insights experiences. This is an IC-heavy role for a technical expert who wants to drive architecture and execution while maintaining a hands-on presence in the code. The ideal candidate has a track record of building and evolving complex, high-quality products across frontend, API, backend, and data systems. You are a generalist who can navigate user-facing application logic, service architecture, data-intensive systems, or infrastructure bottlenecks with equal ease."
That's the About the role.
Responsibilities: bullet list under "Key Responsibilities". Items:
- Work closely with engineers, Product Managers, Designers, and other partners to shape the technical direction and roadmap across Artist Success products, including the A&R Dashboard, Fan Insights, and related artist-facing experiences. You'll help the team make thoughtful architectural decisions and build scalable, secure systems that support large datasets and high-performance user experiences
- Act as a senior technical contributor for a small, expert squad. You will contribute through architectural clarity, rigorous peer reviews, and a focus on maintaining high execution momentum
- Work as a peer to Product Managers and Designers to define requirements across Artist Success. You'll turn vague business "wants" into concrete technical "hows," ensuring the team builds the right things in the most efficient way
- Ensure high technical standards across frontend and backend disciplines. While the team is highly capable, you are responsible for contributing to the overall technical health, consistency, and long-term sustainability of the codebase
- Own the infrastructure and health of your domain. You'll manage deployment patterns, infrastructure as code using Terraform, and ensure we adhere to modern security standards
- Leverage agentic workflows and AI-assisted engineering as a force multiplier while keeping the needs, judgment, and experience of the people using and building our products at the center of the work
That's responsibilities.
Experience And Background (requirements): list:
- 4-6+ years of experience with React and modern frontend development, with the ability to influence architectural decisions and drive best practices; experience with native iOS or Android applications is a plus
- Strong proficiency in GraphQL and TypeScript for building reliable APIs and services, with familiarity in Golang or Scala, and a strong understanding of storage, querying, and data-intensive systems such as BigQuery and SQL
- Strong capability in Infrastructure as Code, particularly Terraform, and container orchestration
- Ability to explain complex technical trade-offs to non-technical stakeholders and collaborate effectively across engineering, product, design, and data
- Demonstrated ability to leverage modern AI and agentic tools to improve quality and velocity, while applying sound judgment around when human expertise is essential and maintaining code quality, product standards, maintainability, and user experience
That's requirements.
Benefits: list under "Benefits":
- Comprehensive health benefits including medical, dental, and vision plans, as well as mental health resources
- Robust 401k program
- Employee Equity Plan
- Generous professional development allowance
- Interested in a gym membership, photography course or book? We have a Creativity and Wellness benefit!
- Flexible vacation and public holiday policy where you can take up to 35 days of PTO annually
- 16 paid weeks for all parents (birthing and non-birthing), regardless of gender, to welcome newborns, adopted and foster children
- Various snacks, goodies, and 2 free lunches weekly when at the office
Pay: salary range: $160,000 - $190,000 annually. Also note final salary determined based on experience etc. We can include that as prose.
Schedule: not present, so omit.
We also have "About Us" paragraph: "We are a multinational company with offices in the US (New York and Los Angeles), Germany (Berlin), and the UK (London)We provide a flexible work culture that offers the opportunity to collaborate and connect in person at our offices as well as accommodating work from homeWe are deeply committed to ensuring diversity, equity and inclusion at all levels of our organization and fostering a community where everyone’s voice, perspective and experience is respected and heardWe believe a strong team is made by investing in employees through mentorship, workshops and enrichment opportunities". This is substantive; we could include as a paragraph under About the role or separate section? Not in allowed headings; maybe we can incorporate into About the role as additional prose. But we must not invent headings. Could add a paragraph after About the role before Responsibilities? Might be okay to include as part of About the role. However the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have About the role heading and then include all prose under it, including the About Us paragraph. That seems fine.
We must not repeat job title as heading. Good.
We must not include Job ID/requisition numbers.
We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The DEI section maybe considered EEO? It's about diversity; but it's not a warning. Might be safe to keep as part of About Us paragraph? Actually the DEI section is separate after Benefits. It's a longer description. Might be considered EEO boilerplate. Safer to remove it. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. So we should remove the Diversity, Equity and Inclusion at SoundCloud section.
Thus final HTML:
About the role
About the role
SoundCloud empowers artists, tastemakers and fans to connect and share through music. Founded in 2007, SoundCloud is a creator-first platform helping artists build and grow their careers by providing them with the most advanced tools, services, and resources. With over 4x the music catalog of every other major streaming platform, spanning 40+ million artists across 190+ countries, SoundCloud is where emerging artists find their sound, hidden gems are discovered, and music culture is shaped in real time. SoundCloud is looking for a Senior Full-Stack Engineer to join our Artist Success team. You will take technical ownership of the tools that help artists understand their audiences, grow their careers, and help the music industry discover its next stars. You will work within a high-performing, multi-disciplinary squad across our frontend (React, iOS, and Android) and backend (GraphQL, TypeScript) services, focused on strategic Artist Success products including the A&R Dashboard, Fan Insights, and artist-facing growth and insights experiences. This is an IC-heavy role for a technical expert who wants to drive architecture and execution while maintaining a hands-on presence in the code. The ideal candidate has a track record of building and evolving complex, high-quality products across frontend, API, backend, and data systems. You are a generalist who can navigate user-facing application logic, service architecture, data-intensive systems, or infrastructure bottlenecks with equal ease. We are a multinational company with offices in the US (New York and Los Angeles), Germany (Berlin), and the UK (London). We provide a flexible work culture that offers the opportunity to collaborate and connect in person at our offices as well as accommodating work from home. We are deeply committed to ensuring diversity, equity and inclusion at all levels of our organization and fostering a community where everyone’s voice, perspective and experience is respected and heard. We believe a strong team is made by investing in employees through mentorship, workshops and enrichment opportunities.
Responsibilities
- Work closely with engineers, Product Managers, Designers, and other partners to shape the technical direction and roadmap across Artist Success products, including the A&R Dashboard, Fan Insights, and related artist-facing experiences. You'll help the team make thoughtful architectural decisions and build scalable, secure systems that support large datasets and high-performance user experiences
- Act as a senior technical contributor for a small, expert squad. You will contribute through architectural clarity, rigorous peer reviews, and a focus on maintaining high execution momentum
- Work as a peer to Product Managers and Designers to define requirements across Artist Success. You'll turn vague business "wants" into concrete technical "hows," ensuring the team builds the right things in the most efficient way
- Ensure high technical standards across frontend and backend disciplines. While the team is highly capable, you are responsible for contributing to the overall technical health, consistency, and long-term sustainability of the codebase
- Own the infrastructure and health of your domain. You'll manage deployment patterns, infrastructure as code using Terraform, and ensure we adhere to modern security standards
- Leverage agentic workflows and AI-assisted engineering as a force multiplier while keeping the needs, judgment, and experience of the people using and building our products at the center of the work
Requirements
- 4-6+ years of experience with React and modern frontend development, with the ability to influence architectural decisions and drive best practices; experience with native iOS or Android applications is a plus
- Strong proficiency in GraphQL and TypeScript for building reliable APIs and services, with familiarity in Golang or Scala, and a strong understanding of storage, querying, and data-intensive systems such as BigQuery and SQL
- Strong capability in Infrastructure as Code, particularly Terraform, and container orchestration
- Ability to explain complex technical trade-offs to non-technical stakeholders and collaborate effectively across engineering, product, design, and data
- Demonstrated ability to leverage modern AI and agentic tools to improve quality and velocity, while applying sound judgment around when human expertise is essential and maintaining code quality, product standards, maintainability, and