Senior Backend Engineer (Data Core Team) at Modash

About Us

Modash helps brands find, understand, and work with creators across Instagram, TikTok, and YouTube. Over 2,700 companies—including Stanley 1913, Sennheiser, and NordVPN—rely on Modash to manage and scale their creator partnerships.

Data Core is responsible for the systems that collect and maintain profiles for 400M+ creators across social platforms, process billions of data points, and supply the rest of Modash with the raw data it needs.

The Role

Data Core isn’t an internal support team; it owns the collection infrastructure that the entire Modash product—and every downstream data team—depends on. You’ll design resilient services, balance tradeoffs between coverage, freshness, reliability, and cost, and take production-critical systems from concept to dependable operation.

You’ll work closely with Data Search, Data Insights, product teams, and company leadership, with real ownership but not in isolation.

Key Responsibilities

1. Keep creator data flowing at massive scale.

You’ll build and evolve systems that maintain 400M+ creator profiles across Instagram, TikTok, and YouTube, ensuring billions of data points remain fresh for search, analytics, APIs, and customer-facing products.

2. Make collection resilient when the outside world isn’t.

Design services that handle third-party API instability, rate limits, provider outages, platform changes, and partial failures without causing customer incidents.

3. Improve the economics of collection.

At this scale, every request, proxy call, retry, storage decision, and compute cycle matters. You’ll optimize coverage and freshness while maintaining financial sustainability.

4. Own production, not just the code.

Shape the problem, design the architecture, write and review code, ship it, observe it, and continuously improve it. Build monitoring and operational safeguards to catch gaps and regressions before they affect customers.

Day-to-Day

Here’s what a typical week might look like:

• Monday. Address a social platform’s overnight behavior change causing partial traffic failures. Trace the issue, protect downstream freshness, and design a resilient fix instead of a brittle patch.
• Tuesday. Redesign the subscription system for creator collection, balancing customer value against request and compute costs.
• Wednesday. Collaborate with a Data Search engineer to refine indexing dependencies, improving freshness without coupling systems.
• Thursday. Review a new request-routing approach across proxy providers, modeling throughput, failure modes, and unit economics before running a production experiment.
• Friday. Improve data-quality checks to catch coverage regressions before they reach customers.

Meetings are purposeful, and deep work is protected. Expect a short standup, close collaboration when needed, and ample time for design, build, harden, and operate systems.

Requirements

What You’ve Done Before

• Built large-scale backend or data systems with experience in high-volume services where reliability, throughput, latency, and cost are critical.
• Shipped systems from concept to production, owning scoping, architecture, implementation, release, operation, and iteration—not just one layer.
• Designed distributed systems, reasoning about partial failure, retries, idempotency, backpressure, scaling, and operational tradeoffs.
• Built resilient integrations with third-party APIs or external dependencies that are rate-limited, unstable, or prone to change.
• Worked with proxy management or request routing, understanding the challenges of routing high-volume traffic and navigating anti-bot systems responsibly.
• Taken operational ownership, focusing on observability, alerting, runbooks, and post-deployment impact—not just code merging.
• Worked autonomously on ambiguous problems, gathering requirements, asking useful questions, and making progress without waiting for perfect specifications.
• Communicated clearly across teams, explaining tradeoffs, giving direct feedback, and collaborating without unnecessary process.

Bonus points for experience with social-media APIs, data-quality frameworks, large-scale collection systems, or freshness and coverage monitoring. Curiosity about the creator economy is a plus.

Our Stack

• AWS, with Pulumi for infrastructure as code
• TypeScript and Node.js as primary languages
• Aurora Limitless/Postgres for subscription and collection state
• S3 for raw data-lake storage
• CloudWatch for observability and alerting
• Proxy networks and custom routing layers
• ECS, SQS, Athena, and other AWS services
• Slack, GitHub, Linear, Notion, and Cursor

Benefits

• Fully remote in Europe with overlap in GMT+3
• Compensation: Annual salary range of 80,000€ - 110,000€, including stock options
• Flexible hours focused on outcomes
• Unlimited paid vacation
• Personal development support (courses, books, conferences)
• Real ownership over production-critical infrastructure
• Regular offsites for in-person collaboration