Back End Developer / Engineer II- #26-21402

**Duration: 9 months

Remote Opportunity**

Summary:

We are looking for a Backend Engineer to join our Data Infrastructure engineering organization. You will forge new ground in how we help teams at clients build analytics for internal and Music industry facing tools. Our platform enables capabilities that include showing artists how many streams their latest release has to informing internal teams about their cloud resource usage.

As a part of a platform team, you will help exemplify, measure and raise the reliability of data infrastructure of squads across different verticals. You’ll work closely with engineers to provide OLAP capabilities to build dynamic, reliable data visualizations and share responsibility with them in diagnosing, resolving, and preventing production issues. We are strong believers in engineering teams taking operational responsibility for their products and work hard to support them in this.

What you’ll do

• Build, operate, and evolve data analytics platform that includes backend services as well as OLAP data store (Druid) for teams building analytics across ***.
• Build internal tooling, libraries, and services that streamline integration patterns with our analytics platform.
• Advocate for best practices in service design, data modeling, schema evolution, and contract testing to ensure long-term maintainability.
• Work in an autonomous, multi-functional environment and collaborate with squads across *** to continuously iterate and deliver on new product objectives.

Who you are

• 3 years of relevant experience with distributed datastores, and backend services.
• Proficient in Java and excited to learn Kubernetes, Terraform.
• Understanding of data modeling, dimensional schemas, and analytical query patterns.
• Experience building internal developer tools, libraries, or shared services that support large engineering organizations.
• Strong sense of ownership of service quality, SLOs, and operational excellence.
• Familiar with OLAP databases or analytics warehouses (e.g., Druid, ClickHouse, Pinot, BigQuery, Snowflake). Experience with Druid is a strong plus.
• Comfort with metrics-driven development and observability stacks (Prometheus, Grafana, similar).
• You are a good communicator and an empathetic, attentive listener with the capability to anticipate the needs of partners
• You are deeply curious, and enjoy exploring both technical and organizational problems and domains.
• You are eager to learn new technologies and to expand your area of expertise

Will this position directly or indirectly manage others?

No

Top 3 hard and soft skills required for this role

• Hard Skills: Java, Backend Engineering, Distributed Databases
• Soft Skills: Collaboration, Communication, Active Listening & Empathy

Nice to have skills or experience

• OLAP Databases: Experience with OLAP/analytical data warehouses (preferably Apache Druid, or ClickHouse, Pinot, BigQuery, Snowflake).
• Infrastructure Tools: Hands-on exposure to Kubernetes and Terraform.
• Integrations Experience: Background in solutions/integrations engineering or building shared internal developer tools and libraries.
• Domain Knowledge: Experience in data analytics, marketing, or advertising industries.

Known obstacles

• Transition to a Platform Model: The candidate will navigate a dynamic environment as the team shifts from supporting specific backend features with their database to delivering a centralized, scalable platform model.
• Complex Stakeholder Environments: The position requires interfacing with diverse cross-functional squads and internal stakeholders across the organization to guide platform adoption.
• Ownership Ambiguities: The candidate must manage and resolve architectural boundaries and system ownership ambiguities that naturally arise during the transition to a platform-based ecosystem.

Necessary skills to navigate challenges

• Deep architectural and systems thinking, backed by background in backend services, distributed databases, and solutions or integrations engineering.
• Team’s top priorities for the next 6-12 months
• Over the next 6 to 12 months, main priorities are building a declarative infrastructure pipeline, refining developer tooling, and optimizing OLAP database performance, with success measured by reduced cloud resource costs, seamless cross-squad platform adoption, and operational reliability.
• Current team dynamic and core values
• Highly…