Infrastructure Engineer

Engineering – Engineering

This position is open to all remote candidates who live in the US or in timezones within UTC-8 and UTC-5.

Why Splice?

In the past decade, the music industry has changed profoundly. Some might say catastrophically. Streaming services have shaken up the way music gets distributed (and the way labels and artists make money), shrinking revenues and leading to a winner-takes-all industry that revolves around— and survives on—mega hits from mega stars.

At Splice, we believe in a world where all musicians have access to world-class tools and content that help them achieve their creative potential. We are advocates for the modern musician, and everything we do confirms that we are in touch with their experiences, challenges, and ambitions. The result? More and better musicians, more and better music, and an industry that works for everyone.

That’s our vision, and we’re looking to connect with people who want to share the responsibility of making it a reality.

We’re a multicultural, inclusive and distributed team of engineers who consider empathy a core job skill. If this sounds like you, you might be the Infrastructure Engineer we’re looking for.

As part of Infrastructure Engineering, you’ll play a critical role in the team ensuring that Splice is available and performant for all of the artists who rely on it every day, and that we’re able to continuously deliver the tools and services that help them achieve their goals. You’ll be entrusted with safeguarding the product of artists’ hard work, ensuring they can focus on their creative process.

It’s a very meaningful role, and we hope you’ll consider applying.

As an Infrastructure Engineer at Splice, you'll find yourself:

    • Receiving help and mentorship from your peers and manager
    • Using your knowledge of cloud service providers and related tooling to pair with other engineers to deliver upon an approved RFC
    • Supporting and increasing our ability to learn and grow from complex systems failure
    • Collaborating with your peers in Frontend, Application, Data, and QA Engineering, as well as Product Management and Design, to support product decisions and review future implementations
    • Participating in respectful code reviews to shape not just our code, but the way we think and talk about it, as well
    • Adjusting to the requirements of a rapidly growing team, while doing your part to make sure every group of new hires has it easier than the last

You also may find yourself co-authoring RFCs that propose:

    • A reduction in complexity and overall cognitive load in our tooling
    • An improvement in the ability to understand the health of our service, and everyone’s ability to respond when things are unhealthy
    • A simplification of our approach to delivering stateless applications
    • An increase in the resilience of our primary and secondary datastores (MySQL, ElasticSearch, Redis)

How We’ll Handle Your Application

We know that applying for a job can be stressful, and the amount of time it can take varies wildly from company to company. So, we’re sharing a typical application process with you up front.

First, we try our best to get a response to all applicants within a week of receiving their application, whether they are selected for interviews or not.

We keep engineering job postings open for a limited window, and group applicants into a single cohort during that window. If your application is selected to proceed through our interview process, here’s what happens next:

1. You’ll meet with the hiring manager for the position for a brief, 30 minute video chat. They’ll get a sense of what you’re looking for and answer any questions you might have about the role.

2. You’ll be given a take-home exercise to complete at your own pace. A working solution should be manageable with around 4 hours of dedicated effort, or less.

3. You’ll submit this exercise to the hiring manager, who will anonymize it.

4. Two engineers will review the exercise and evaluate it according to a rubric, then we’ll schedule an hour for those engineers to chat with you about your submission, your work experience, and answer any questions you may have.

5. You’ll have a 30 minute chat with our VP of Engineering.

6. The hiring manager will schedule a time to get your feedback on the interview process and let you know about our decision.

That’s it! The whole process can be completed in as little as two weeks, depending on your availability, the size of the cohort, and when applications close.