Senior Backend Developer (Rust&Node.JS)

We are looking for a Senior Backend Developer to join Group107 project.

You will join the platform team behind a high-scale, performance-marketing ad-tracking and attribution product that has been in production for 6+ years. The system processes clicks, installs and conversions at scale: a Rust tracker plus a fleet of ~30 services for ingest, attribution, conversion reporting and scheduled jobs, backed by ClickHouse, MySQL/Aurora and Kafka, all running on AWS EKS. The team is small and senior, decisions happen in conversation rather than by committee, and every engineer’s work carries real weight — accuracy and revenue correctness are non-negotiable. This is a broad, high-ownership role for an engineer who reaches for the right tool rather than a single-language specialist.

• 7+ years of backend engineering experience, including 1+ years of production Rust
• Working knowledge of TypeScript/Node — able to extend a NestJS API unsupervised
• Strong knowledge of SQL — able to reason about query plans and explain why a given write pattern deadlocks under concurrency (not just “can write a JOIN”)
• Production experience with Kafka — consumer semantics, ordering, and replay
• Real operational AWS experience (not a certificate): EKS, managed databases, managed Kafka, S3
• Advanced knowledge of Docker, Kubernetes and Helm — enough to author and debug your own chart
• CI/CD ownership — you have built pipelines, not just consumed them
• Testing discipline — you write tests for code that handles money, and you can explain what you deliberately chose not to test
• English at C1 or above
• Clear technical writing by default — design notes before significant work, a clean summary after a production incident, and context shared without being asked
• Proactiveness and ownership — works from thin briefs, forms a hypothesis, drives work to completion, and unsticks stalled work rather than routing around it
• Raises risk early — comfortable saying “I’m not confident about this edge case, I’d like a second opinion”
• Mentorship and code review — comments on colleagues’ work with reasons, helps teammates get unblocked
• Architectural thinking across a complex, high-scale system — confident anywhere in the platform, not only in the corner you built
• Judged, fluent use of AI coding assistants — knows where they help (test generation, boilerplate, migrations, orientation) and where they don’t (undocumented third-party APIs, production data reconciliation, concurrency)

• ClickHouse or another columnar/OLAP store — materialized views, aggregation tiers, sharding
• Background in ad tech, attribution or mobile measurement (click identifiers, server-to-server postbacks, deduplication, attribution windows, fraud/proxy filtering) — or, failing that, payments/fintech where data integrity was non-negotiable
• Terraform / Terragrunt / CDK
• Experience with Redis and React (operator dashboard)

• Build and run the backend services behind the platform — primarily Rust today (Axum, Tokio, sqlx, serde), but spanning the full stack: TypeScript in the NestJS API and the warehouse ETL, SQL against MySQL/Aurora and ClickHouse, and the Helm charts and CI that ship your work to production.
• Design and build server-to-server integrations with ad platforms, mobile measurement partners, advertisers and affiliate reporting endpoints — sources that are rarely well documented and often behave unlike their spec. Half the job is disciplined detective work.
• Own data correctness across MySQL and ClickHouse: write the attribution and revenue queries, and be the person who can answer “why don’t our numbers match theirs?” with evidence rather than theory.
• Take services from an empty directory through to production and operate them — you deploy your own work and own it, including the weeks immediately after it lands in production.
• Raise the engineering baseline: automated testing in CI, judged AI-assisted development, and smart monitoring.
• Set technical standards and support the wider team through design notes, code review with reasons, and clear written communication across a distributed team.

• 20 vacation days (workdays)
• 7 sick days
• Personalized career growth
• Internal English classes
• Education reimbursement
• Corporate events and team buildings
• Equipment provided