At Splice, Principal Engineers are responsible for developing the technical strategy that informs technical planning and allows their Product Group to achieve their objective. They have no management responsibilities. They actively contribute to the codebase, are stewards for technical excellence and represent the platform in technical decision making.
As part of our Growth team, you’ll play a critical role in helping us grow Splice effectively. We do this by building features, infrastructure, and experiments to maximize growth. You’ll join a multicultural, inclusive and distributed team of engineers that will drive double-digit growth month-over-month.
This position reports to the VP of Engineering.
We’re building a creative ecosystem for music producers. With this ecosystem, we’re cultivating a global community of creators that fosters inspiration, connection, focus, and growth.
Our work environment is no different. We champion collaboration, big ideas, helping where we can and asking for assistance when we need it. We aim for steady, measured expansion through experimentation and iteration. We encourage optimism, inclusion, and transparency in the workplace. We aren’t afraid to stumble, because every stumble can teach us something about our processes, strategies, and even ourselves.
What You’ll Do:
As the Principal Engineer [on/of] the Growth Engineering team, you might find yourself:
- Partnering with the Growth Engineering Manager and Software Engineers to develop a cohesive technical strategy that unlocks growth for our company
- Using your knowledge of the web and API design to support the team as they build features with quantifiably high impact through prototyping and experimentation
- Participating in architectural reviews, and identifying projects that would benefit from architectural reviews
- Co-authoring RFCs to determine the expansion of our experimentation framework or an innovative way to scale our messaging system.
- Working throughout our stack with Go, Angular/TypeScript, and 3rd-party analytics software to build scalable, efficient experiments across our user journey
- Building infrastructure that enables us to understand our user’s journey end to end. (It’s hard to optimize that which you do not understand.)
- Defining technical best practices to optimize Splice’s organic reach on search engines
- Providing technical mentorship to engineers across the organization
- Leading contributing to and developing the growth engineering practice at Splice
- Building tools that help teams outside of engineering scale
- Sharing with your teammates, whether it’s mentoring another engineer, posting something awesome you just learned or hosting a book club session.
- Collaborating with your peers in Engineering, Product Management, and Design to support product decisions and review future implementations
- Collaborating with other Principal Engineers to drive consistency across Splice
- Partnering with our SRE team to deploy highly reliable systems to production
- Researching and solving problems with code, without code, and sometimes by deleting code
- Offering office hours to engineers for discussing or pairing on tricky technical issues
- Participating in mindful code reviews to shape not just our code but also the way we think and talk about it
- Adjusting to the requirements of a rapidly growing team and doing your part to make sure every new hire has it easier than the last
- Contributing to our effective distributed team culture by communicating decisions and supporting all team members
- Increasing Splice’s profile in our industries — both music and engineering — through a combination of writing, public speaking, and other externally visible activities, and raising their teammates’ visibility in the process
Relevant experience and mindset:
- You share our vision
- You’re self-directed towards generating excellent work outcomes
You have a bias towards action and experimentation
- You care about quality. It drives you.
- You are comfortable, or even prefer working across technical stacks
- You get excited about data and using it to make technical decisions
- You communicate clearly and effectively with technical and non-technical audiences
- You thrive in a fast-paced environment
- You are comfortable both deploying and maintaining code
- You have 10+ years of relevant work experience in building and maintaining production quality software
- You have 2+ years of experience working in a Growth team
- Experience working in or with distributed teams
- You have leadership experience in a Growth team
How We’ll Handle Your Application:
We know that applying for a job can be stressful, and the amount of time it takes varies wildly from company to company. So, we’re sharing with you up front how a typical application proceeds through the interview process for this role.
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.
If your application is selected to proceed through our interview process, you may:
- Meet with a Technical Recruiter 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.
- Meet with our VP of Engineering to discuss your experience and the open role
- Complete a take-home exercise at your own pace within a 1-week window from when you receive the exercise. A working solution should be manageable with around 4 hours of dedicated effort or less.
- Have your anonymized exercise reviewed by Splice engineers and evaluated according to a rubric.
- Meet with one of Splice’s Principal Engineers and one of our Growth Engineers for an hour to chat with you about your submission, your work experience, and answer any questions you may have.
- Meet with the Growth Group PM and Growth Engineering Manager for 60 minutes
That’s it! After each step, the hiring manager will use the feedback from our panel to determine who progresses to the next step. The whole process can be completed in as little as two weeks, depending on your availability, the applicant pool size and when applications close.