Back to jobs

Staff Software Engineer - Data Platform Team

Tel Aviv-Yafo, Tel Aviv District, Israel

Actively hiring, first seen by us today
Pay
Pay not listed
Work setting
Not stated
Employment
Not stated

What you’ll work on

Full posting

The Serving Layer team owns the data infrastructure behind Orca's platform UI and API.

We're looking for a deeply hands-on engineer to own performance, data modeling, and operational reliability across that stack - someone who can move between a query execution plan, a Flink job's parallelism, and a Kubernetes operator upgrade in the same week.

  • Own end-to-end query performance: plan analysis, shard-key and index design, statistics, join strategy, and driving down p99 latency under real concurrency

  • Build the observability that catches performance regressions before customers do - query-level metrics, slow-query workflows, load-test harnesses

  • Partner with product and platform teams on schema and query contracts, and push back on designs that won't hold at scale

From the employer’s posting
The Serving Layer team owns the data infrastructure behind Orca's platform UI and API. Every asset, alert, and query a customer sees is served from it, at high concurrency and with latency budgets measured in milliseconds. On the write side, the team ingests continuously from across the platform; on the read side, it serves the product.
We're looking for a deeply hands-on engineer to own performance, data modeling, and operational reliability across that stack - someone who can move between a query execution plan, a Flink job's parallelism, and a Kubernetes operator upgrade in the same week.
What You'll Do: Own end-to-end query performance: plan analysis, shard-key and index design, statistics, join strategy, and driving down p99 latency under real concurrency Design and evolve the physical data models - sharding, partitioning, sort keys, retention - that serve product queries at scale, and the table layouts that make lakehouse reads fast
Tune the ingestion path end to end: Kafka topic design and consumer performance, Flink and Spark job parallelism, checkpointing, backpressure, and data freshness Build the observability that catches performance regressions before customers do - query-level metrics, slow-query workflows, load-test harnesses Partner with product and platform teams on schema and query contracts, and push back on designs that won't hold at scale
Build the observability that catches performance regressions before customers do - query-level metrics, slow-query workflows, load-test harnesses Partner with product and platform teams on schema and query contracts, and push back on designs that won't hold at scale What You Bring:

What you’ll bring

All qualifications

Core experience

  • 7+ years in backend, data, or infrastructure engineering, including 3+ years focused on distributed database or analytical query performance
  • Experience introducing performance engineering practice to a team - benchmarks, regression gates, load testing as part of CI
  • Hands-on experience with a distributed OLAP/HTAP or MPP engine - SingleStore, ClickHouse, Druid, Pinot, Trino/Presto, Snowflake, Redshift, Vertica, or similar
  • Strong data modeling judgment for read-heavy, latency-sensitive serving workloads, not only batch or warehouse modeling
  • Proven ownership of production systems: on-call, incident investigation, capacity planning
Qualification wording
7+ years in backend, data, or infrastructure engineering, including 3+ years focused on distributed database or analytical query performance
Experience introducing performance engineering practice to a team - benchmarks, regression gates, load testing as part of CI
Hands-on experience with a distributed OLAP/HTAP or MPP engine - SingleStore, ClickHouse, Druid, Pinot, Trino/Presto, Snowflake, Redshift, Vertica, or similar
Strong data modeling judgment for read-heavy, latency-sensitive serving workloads, not only batch or warehouse modeling
Proven ownership of production systems: on-call, incident investigation, capacity planning
Apply at Orca Security

Posting record

Report an error

Actively hiringFirst seen by us today, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 7, 2026today
Recorded sightings
1
Employer says posted
Nov 4, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Time since we first saw it

Day 0

Early. Similar jobs usually come down between day 6 and day 54.

From 11,508 similar postings that came down. Coming down is not always a hire.

Orca Security is hiring

1 open job

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
  • SQL
  • AWS
  • ClickHouse
  • Iceberg
  • Kafka
  • Kubernetes
  • Redshift
  • S3
  • Snowflake
  • Spark
  • Terraform
  • Trino
  • Go
Where the posting names them
- Infrastructure: AWS, EKS, Terraform, Helm, multi-region - Languages: Python, Go, and a lot of SQL What You'll Do:
- Kubernetes fluency in production: operators and StatefulSets, resource management, persistent storage, safely upgrading stateful workloads - Expert SQL, plus Python or Go - Infrastructure-as-code and cloud operations (Terraform, Helm, AWS)
- Lakehouse: Apache Iceberg on S3, Parquet, custom compaction - Infrastructure: AWS, EKS, Terraform, Helm, multi-region - Languages: Python, Go, and a lot of SQL
- Expert SQL, plus Python or Go - Infrastructure-as-code and cloud operations (Terraform, Helm, AWS) - Proven ownership of production systems: on-call, incident investigation, capacity planning
- Real depth in database internals: reading and reshaping execution plans, understanding how sharding, partitioning, indexing, and join distribution drive latency, and diagnosing skew, spills, lock contention, and memory pressure in production - Hands-on experience with a distributed OLAP/HTAP or MPP engine - SingleStore, ClickHouse, Druid, Pinot, Trino/Presto, Snowflake, Redshift, Vertica, or similar - Strong data modeling judgment for read-heavy, latency-sensitive serving workloads, not only batch or warehouse modeling
- Streaming and ingestion: Kafka / Amazon MSK, Apache Flink, Spark Structured Streaming, CDC pipelines - Lakehouse: Apache Iceberg on S3, Parquet, custom compaction - Infrastructure: AWS, EKS, Terraform, Helm, multi-region
- Production experience with distributed streaming- Kafka and at least one of Flink or Spark Structured Streaming - including performance and throughput tuning, not just wiring jobs together - Working knowledge of a table format (Iceberg, Delta, Hudi) and what partitioning, file sizing, and compaction do to query performance - Kubernetes fluency in production: operators and StatefulSets, resource management, persistent storage, safely upgrading stateful workloads
- Serving: SingleStore, self-managed on Kubernetes (operator-driven), plus Trino for analytical access - Streaming and ingestion: Kafka / Amazon MSK, Apache Flink, Spark Structured Streaming, CDC pipelines - Lakehouse: Apache Iceberg on S3, Parquet, custom compaction
- Run SingleStore in production on Kubernetes: capacity and node topology, operator-driven upgrades and node refreshes, backup and restore, blast-radius and failure design - Tune the ingestion path end to end: Kafka topic design and consumer performance, Flink and Spark job parallelism, checkpointing, backpressure, and data freshness - Build the observability that catches performance regressions before customers do - query-level metrics, slow-query workflows, load-test harnesses
- Strong data modeling judgment for read-heavy, latency-sensitive serving workloads, not only batch or warehouse modeling - Production experience with distributed streaming- Kafka and at least one of Flink or Spark Structured Streaming - including performance and throughput tuning, not just wiring jobs together - Working knowledge of a table format (Iceberg, Delta, Hudi) and what partitioning, file sizing, and compaction do to query performance
- The Serving Layer team owns the data infrastructure behind Orca's platform UI and API. Every asset, alert, and query a customer sees is served from it, at high concurrency and with latency budgets measured in milliseconds. On the write side, the team ingests continuously from across the platform; on the read side, it serves the product. - We're looking for a deeply hands-on engineer to own performance, data modeling, and operational reliability across that stack - someone who can move between a query execution plan, a Flink job's parallelism, and a Kubernetes operator upgrade in the same week. - This is a senior individual-contributor role. You'll set technical direction for how our data is modeled, stored, and served, and you'll be the person others come to when something is slow and nobody knows why.
Our stack: - Serving: SingleStore, self-managed on Kubernetes (operator-driven), plus Trino for analytical access - Streaming and ingestion: Kafka / Amazon MSK, Apache Flink, Spark Structured Streaming, CDC pipelines
- Design and evolve the physical data models - sharding, partitioning, sort keys, retention - that serve product queries at scale, and the table layouts that make lakehouse reads fast - Run SingleStore in production on Kubernetes: capacity and node topology, operator-driven upgrades and node refreshes, backup and restore, blast-radius and failure design - Tune the ingestion path end to end: Kafka topic design and consumer performance, Flink and Spark job parallelism, checkpointing, backpressure, and data freshness
- Working knowledge of a table format (Iceberg, Delta, Hudi) and what partitioning, file sizing, and compaction do to query performance - Kubernetes fluency in production: operators and StatefulSets, resource management, persistent storage, safely upgrading stateful workloads - Expert SQL, plus Python or Go
Bonus Points if You Have: - Direct SingleStore experience, especially self-managed on Kubernetes - Iceberg at scale: compaction strategy, metadata growth, maintenance jobs

Your next step

Complete your application on orca.security. The employer’s form will show what is required.

Applying through Greenhouse

  • No account needed: the form is one page, with an “Autofill my application” option that reads your resume.
  • Greenhouse doesn’t read resumes over 2.5 MB, or details placed in a header, footer, text box, table or second column. The file still attaches, but a recruiter has to type you in by hand.

Already applied? Track this application

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 8% over the last 5 weeks compared with the 5 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of October 26. The fewest in a week was 839, the most 1,314, and the latest week had 1,079.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 5 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Job description

View original posting ↗

Big Ideas. Real People.

At Orca, in the right environment and with the right team, talent has no boundaries. This team spirit, together with our drive to always aim high, has quickly earned us unicorn status and turned us into a global cloud security innovation leader. So if you’re ready to join an amazing team of people who inspire each other every day, now is the time to find your place in our pod. We’re looking for driven and talented people like you to join our R&D team and our mission to change the future of cloud security.

Ready to dive in and swim with our pod? 

Highlights:

  • High-growth: Over the past seven years, we’ve consistently achieved milestones that take other companies a decade or more. During this time, we’ve significantly grown our employee base, expanded our customer reach, and rapidly advanced our product capabilities.
  • Disruptive innovation: Our founders saw that traditional security didn’t work for the cloud, so they set out to carve a new path. We’re relentless pioneers who invented agentless technology and continue to be the most comprehensive and innovative cloud security company.
  • Well-capitalized: With a valuation of $1.8 billion, Orca is a cybersecurity unicorn dominating the cloud security space. We’re backed by an impressive team of investors such as Capital G, ICONIQ, GGV, and SVCI, a syndicate of CISOs who invest their own money after conducting their due diligence.
  • Respectful and transparent culture: Our executives pride themselves on being accessible to everyone and believe in sharing knowledge with the employees. Each employee has a place in shaping the future of our industry.

About the Role: 

  • The Serving Layer team owns the data infrastructure behind Orca's platform UI and API. Every asset, alert, and query a customer sees is served from it, at high concurrency and with latency budgets measured in milliseconds. On the write side, the team ingests continuously from across the platform; on the read side, it serves the product.
  • We're looking for a deeply hands-on engineer to own performance, data modeling, and operational reliability across that stack - someone who can move between a query execution plan, a Flink job's parallelism, and a Kubernetes operator upgrade in the same week.
  • This is a senior individual-contributor role. You'll set technical direction for how our data is modeled, stored, and served, and you'll be the person others come to when something is slow and nobody knows why.

Our stack:

  • Serving: SingleStore, self-managed on Kubernetes (operator-driven), plus Trino for analytical access
  • Streaming and ingestion: Kafka / Amazon MSK, Apache Flink, Spark Structured Streaming, CDC pipelines
  • Lakehouse: Apache Iceberg on S3, Parquet, custom compaction
  • Infrastructure: AWS, EKS, Terraform, Helm, multi-region
  • Languages: Python, Go, and a lot of SQL

What You'll Do:

  • Own end-to-end query performance: plan analysis, shard-key and index design, statistics, join strategy, and driving down p99 latency under real concurrency
  • Design and evolve the physical data models - sharding, partitioning, sort keys, retention - that serve product queries at scale, and the table layouts that make lakehouse reads fast
  • Run SingleStore in production on Kubernetes: capacity and node topology, operator-driven upgrades and node refreshes, backup and restore, blast-radius and failure design
  • Tune the ingestion path end to end: Kafka topic design and consumer performance, Flink and Spark job parallelism, checkpointing, backpressure, and data freshness
  • Build the observability that catches performance regressions before customers do - query-level metrics, slow-query workflows, load-test harnesses
  • Partner with product and platform teams on schema and query contracts, and push back on designs that won't hold at scale

What You Bring:

  • 7+ years in backend, data, or infrastructure engineering, including 3+ years focused on distributed database or analytical query performance
  • Real depth in database internals: reading and reshaping execution plans, understanding how sharding, partitioning, indexing, and join distribution drive latency, and diagnosing skew, spills, lock contention, and memory pressure in production
  • Hands-on experience with a distributed OLAP/HTAP or MPP engine - SingleStore, ClickHouse, Druid, Pinot, Trino/Presto, Snowflake, Redshift, Vertica, or similar
  • Strong data modeling judgment for read-heavy, latency-sensitive serving workloads, not only batch or warehouse modeling
  • Production experience with distributed streaming- Kafka and at least one of Flink or Spark Structured Streaming - including performance and throughput tuning, not just wiring jobs together
  • Working knowledge of a table format (Iceberg, Delta, Hudi) and what partitioning, file sizing, and compaction do to query performance
  • Kubernetes fluency in production: operators and StatefulSets, resource management, persistent storage, safely upgrading stateful workloads
  • Expert SQL, plus Python or Go
  • Infrastructure-as-code and cloud operations (Terraform, Helm, AWS)
  • Proven ownership of production systems: on-call, incident investigation, capacity planning

Bonus Points if You Have:

  • Direct SingleStore experience, especially self-managed on Kubernetes
  • Iceberg at scale: compaction strategy, metadata growth, maintenance jobs
  • Multi-region, multi-tenant SaaS
  • Experience introducing performance engineering practice to a team - benchmarks, regression gates, load testing as part of CI
  • Cloud security or CNAPP domain background
#LI-ORCA
Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay

No pay amount identified in the saved description.

Location & working pattern

Tel Aviv-Yafo, Tel Aviv District, Israel

Working pattern and location restrictions need checking in the full posting.

Work authorization

No clear work-authorization passage found. Eligibility is unconfirmed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.