The role

We’re looking for a Software Engineer with strong C++ expertise to join the team building and operating Nebius Data Platform — a distributed storage and a processing platform that acts as the company’s “source of truth” and the backbone of many internal (and some external) products.

Nebius Data Platform is a single multi-tenant ecosystem based on YTsaurus — instead of running separate HDFS/Kafka/HBase-style systems, we provide storage, compute, and analytics capabilities inside one platform.

Built on top of the open-source YTsaurus ecosystem, we run and extend our own Nebius distribution and develop significant in-house functionality (core and platform-level). We can design, implement, and roll out features end-to-end on our clusters without waiting for upstream approvals and contribute upstream when it makes sense.

At scale today, this includes~500 servers, ~20k CPU cores and ~10 PB of compressed data in our largest production cluster, supporting workloads ranging from business-critical pipelines and financial transactions to large-scale ML/LLM training datasets and compute.

What’s inside the platform

You’ll work on a system that includes (and ties together):

• Distributed Storage (Cypress): transactional semantics, tiered storage, erasure coding, replication, and strong reliability expectations.
• Compute & ETL: a cluster-wide job scheduler (tens of thousands of cores), MapReduce, YQL for SQL-like data processing, and SPYT (Spark over YTsaurus) for modern data engineering.
• Interactive analytics (CHYT): ClickHouse® instances spun up directly on compute nodes for fast SQL over data in-place.
• Dynamic Tables: low-latency NoSQL KV with distributed ACID transactions for OLTP-style workloads and feature stores.
• Orchestracto: workflow orchestration deeply integrated with the platform (Airflow-like, but platform-native).

What you’ll do

We’re looking for engineers who combine strong systems skills with product sense: understanding who uses the platform, why certain capabilities matter, and making pragmatic trade-offs to maximize impact. On our team, engineering work is expected to be connected to real users and outcomes — you’ll regularly align with internal stakeholders, clarify requirements, and help drive prioritization.

In this role, you will:

• Design and implement new functionality in YTsaurus core (C++) with production reliability in mind.
• Build and evolve platform-level capabilities: platform architecture and operating model—multi-cluster growth, shared primitives, and a consistent experience that scales with new teams and use cases.
• Improve end-to-end platform experience for internal (and external-facing) users: APIs, guardrails, debugging workflows, and automation.
• Own production quality: incident response / on-call rotation, root cause analysis, and turning learnings into durable fixes.

Example projects

• Roll out sharded YTsaurus masters (incl. Kubernetes operator support) and build automatic balancing of metadata across master cells (consensus groups) to remove control-plane bottlenecks and unlock 10–100x cluster growth.
• Make CHYT interactive SQL faster and more predictable at high load via performance work like data-skipping / min-max-style indexes and improved execution introspection.
• Turn Orchestracto into a platform product by defining the building blocks, developer experience, and governance for how teams create and share workflows.
• Scale and harden Parquet-on-S3 for native YTsaurus workloads by tackling replication/movement, consistent lifecycle semantics, and master-server metadata optimizations for performance and reliability.
• Design and ship complete, trustworthy audit trails for data changes (who/what/when) across heterogeneous storage and compute paths.

Tech stack

• Core: modern C++ (C++20, async + multithreaded primitives)
• Services & tooling: Go and Python (microservices, utilities, integration tests)

What we expect

• 5+ years of software engineering experience.
• Strong C++ skills (you’ll write core code).
• Working knowledge of Python and/or Go (you don’t have to be expert, but should be comfortable navigating them).
• Experience developing and/or operating high-load, distributed services.
• Production mindset: ability to use SSH, read logs/metrics/traces, and debug distributed systems behavior.
• Solid CS fundamentals: algorithms, data structures, concurrency basics.

Nice to have

• Experience with Big Data systems (YTsaurus/Hadoop/Spark/ClickHouse/Kafka-like ecosystems).
• Experience with multi-tenant platforms, schedulers, resource isolation, quotas, and reliability engineering.
• Strong performance engineering skills (profiling, lock contention, latency/throughput tradeoffs).

We conduct coding interviews as part of the process.

We're building an AI copilot for web testing automation. It enables manual and automation QA engineers to turn their manual testing flows into production-ready automated E2E testing scripts, saving hours of manual work and coding. We are a small team with zero bureaucracy, focusing on real users. We optimize for shipping value - not hype.

About the role:

You'll own the top of the funnel: outbound, qualification, and getting leads to sit down for a conversation. Demos, onboarding, and retention are staying with the founder for now.

Phase one: Get individual Automation QAs to try the product, aiming for fast adoption and no procurement. Once we hit 20+ weekly users, we’ll move on to phase two, where we’ll shift the focus to B2B – qualified meetings with QA Leads and Engineering Managers.

Your focus in the first three months:

• Build targeted lists: Automation QAs at companies with web products and Playwright, Cypress, or Selenium in their stack.
• Run outbound sequences (LinkedIn is the baseline, but you decide the channels). A/B test weekly.
• Design qualification gates (forms and scoring) to filter leads before the founder calls.
• Reach 20+ weekly active users after month one – ICP-qualified and giving direct feedback to engineering.
• Document what works into a repeatable playbook.

Growth path:

This role expands as your strategies deliver results. Once the user pipeline works, you can take over demos and run B2B sales end to end. From there, the natural next step is Growth Lead (funnel optimization and scaling the playbook) or Account Executive (owning deal execution).

Why to join:

• You'll be building a strategy that scales the product, not filling a quota. What you create from scratch becomes the foundation.
• Your outreach turns into users who talk directly to engineering, and their feedback ships as features within days.
• AI for developer tools is a market with real pull, and QA automation is one of its sharpest pain points.
• We’re backed by JetBrains – financially secure with no reliance on external VC funding.

Who we're looking for:

You should have a high level of agency and be quant-minded – you live in funnel metrics, run experiments, and are comfortable saying "no" to leads that are a bad fit. 

The ideal candidate will:

• Have done 0-to-1 outbound for an early-stage devtool, QA tool, infrastructure product, or similar.
• Have proven cold outbound results, instead of being dependent on warm inbound.
• Be able to talk credibly about flaky tests, CI pain, and Playwright vs. Cypress. You don't need to be an engineer, but you do need domain empathy.
• Possess strong written communication skills, with the ability to craft short, sharp messages that get replies.

Nice to have:

• A QA or SDET background – you've felt the pain yourself before moving to sales or BD.
• Exposure to security/compliance objections – enough to pre-empt and route.
• Content skills – your LinkedIn posts get engagement, not just your DMs.
• Experience as one of the first 10 employees at a startup.

#LI-REMOTE 
#LI-KT1