Time since we first saw it
Day 3
Early. Similar jobs usually come down between day 6 and day 56.
From 14,771 similar postings that came down. Coming down is not always a hire.
Remote - Portugal
Actively hiring, first seen by us 3 days agoTotal Compensation Range €52.500—€82.500 EUR Country-specific benefits may vary and will be detailed separately.Read the full posting
Listed location: Remote - PortugalRead the full posting
Design and evolve the streaming lakehouse that all data consumers depend on
Build and operate low-latency distributed streaming pipelines
Own durable workflows that coordinate complex data movement across systems
Shape the API surface producers and consumers use to self-serve
Evaluate and integrate vendor data platforms, weighing architectural trade-offs
Design and evolve Sword’s streaming lakehouse
Build and operate distributed streaming pipelines that move data at low latency and high reliability.
Own the durable workflows that coordinate complex data movement across systems.
Shape the platform’s API surface - the interface producers and consumers use so they never need to touch infrastructure.
Drive evaluations and integrations with vendor data platforms, sitting inside the architectural trade-offs rather than just consuming the output.
Proven experience designing and operating data platforms at scale - warehouse, data lake, or lakehouse architectures in production.
Experience in HIPAA, FedRAMP, or SOC 2 environments.
Hands-on experience with a modern lakehouse table format - Iceberg strongly preferred; Delta Lake or Hudi also welcome. You understand how the format works under the hood: metadata layout, snapshots, manifests, compaction, copy-on-write vs. merge-on-read.
Strong experience with a distributed processing engine - Flink strongly preferred; Spark also fine. You can reason about its internals, fine-tune a running job, and debug a pipeline that’s silently degrading.
Familiarity with durable execution - Temporal, Restate, or similar - or at minimum a solid mental model of what durable execution means and why it matters for data workflows.
Solid understanding of Kafka and event-driven architectures (producers/consumers, partitioning, delivery semantics).
Actively hiringFirst seen by us 3 days ago, still listed, and not a repost of an earlier posting.
These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.
Day 3
Early. Similar jobs usually come down between day 6 and day 56.
From 14,771 similar postings that came down. Coming down is not always a hire.
2 open jobs
Open jobs by the week we first saw them, last 12 weeks.
Hiring recordAdd 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.
- Clear mental model of catalogs (REST, Polaris, Glue, Unity, Hive) - their trade-offs, and how compute stays detached from storage. - Exposure to at least one vendor lakehouse or query platform - Snowflake, Starburst, or Databricks — at the level where you can reason about its architecture, not just use its UI. - Strong experience with a distributed processing engine - Flink strongly preferred; Spark also fine. You can reason about its internals, fine-tune a running job, and debug a pipeline that’s silently degrading.
- Experience in HIPAA, FedRAMP, or SOC 2 environments. - dbt, DataHub, or data contract tooling exposure. Mindset and Collaboration
- Proven experience designing and operating data platforms at scale - warehouse, data lake, or lakehouse architectures in production. - Hands-on experience with a modern lakehouse table format - Iceberg strongly preferred; Delta Lake or Hudi also welcome. You understand how the format works under the hood: metadata layout, snapshots, manifests, compaction, copy-on-write vs. merge-on-read. - Clear mental model of catalogs (REST, Polaris, Glue, Unity, Hive) - their trade-offs, and how compute stays detached from storage.
- Deeper familiarity with open/REST catalogs (Polaris, Nessie, Unity) beyond basic use. - Observability stack fluency (Prometheus, Grafana, OpenTelemetry). - Prior work on agentic or AI-facing API surfaces, or MCP-style interfaces.
- Production experience building and operating APIs (REST or gRPC) at scale - good instincts about contracts, versioning, retries, rate limiting, and observability. - Solid understanding of Kafka and event-driven architectures (producers/consumers, partitioning, delivery semantics). - Comfortable in regulated environments (healthcare, fintech, gov) where audit, compliance, and data governance are part of every design.
Complete your application on job-boards.greenhouse.io. The employer’s form will show what is required.
Already applied? Track this application
At Sword, we’re building AI to heal billions and unlock humanity’s full potential. In doing so, we’re pioneering AI Care, a fundamentally new approach to healthcare built for medical reasoning, safety, and real-time treatment, not generic technology applied after the fact. As both a clinical-centric frontier AI lab and an applied AI platform, Sword is reimagining how care is delivered at scale, removing traditional barriers like appointments, waiting rooms, and stigma so more people can access the care they need—and ultimately get back to lives lived in full.
Since 2020, Sword has expanded across physical therapy, women’s health, cardiometabolic, and mental health, and is now moving beyond the session to a fully AI-native, 24/7 care program that brings physical activity, therapeutic exercise, psychotherapy, nutrition, and behavior change into one connected experience. More than 700,000 members across three continents have completed over 10 million AI sessions, helping 1,000+ enterprise clients avoid more than $1 billion in unnecessary healthcare costs. Backed by 42 clinical studies, 44+ patents, and more than $500 million raised from leading investors including Khosla Ventures, General Catalyst, and Founders Fund, Sword is defining a new standard for healthcare.
AI fluency is a core expectation at Sword. Every candidate is assessed against our three-level framework — be ready to share real examples of how AI is already part of how you work.
Explorer (Level 1) — Uses AI daily to boost personal productivity
Builder (Level 2) — Creates workflows and tools that elevate the whole team
Integrator (Level 3) — Embeds AI into products and processes at scale
Every hire must demonstrate at least Level 1. The expected level will vary depending on the seniority of the role.
At Sword, data powers our mission to build a pain-free world. The Data Platform Team is building the foundation that makes data usable across clinical, operations, AI, and product teams: a modern streaming lakehouse, distributed processing for low-latency data movement, durable workflows coordinating complex operations, and an API-first surface that lets producers and consumers serve themselves - without tickets, without infra context, and increasingly through agentic interfaces.
This role is for an engineer who thinks about data platforms as products. You’ve built or operated data systems at scale, you reason fluently from storage format up to query engine, and you want to shape the self-service and agentic experiences layered on top of that foundation.
To get to know more about our Tech Stack, check here.
Design and evolve Sword’s streaming lakehouse - the foundation that every data consumer in the company depends on.
Build and operate distributed streaming pipelines that move data at low latency and high reliability.
Own the durable workflows that coordinate complex data movement across systems.
Shape the platform’s API surface - the interface producers and consumers use so they never need to touch infrastructure.
Drive evaluations and integrations with vendor data platforms, sitting inside the architectural trade-offs rather than just consuming the output.
Contribute to the self-service and agentic layer: interfaces designed to be consumed by humans, systems, and AI agents alike.
Partner with data engineers and analysts on contracts, governance, and lineage.
Build and maintain AI-ready data infrastructure that powers ML and AI-driven products across Sword.
Leverage AI coding assistants and LLMs to accelerate development, automate documentation, and raise code quality.
Work in a regulated environment where audit, compliance, and governance are part of every design.
Proven experience designing and operating data platforms at scale - warehouse, data lake, or lakehouse architectures in production.
Hands-on experience with a modern lakehouse table format - Iceberg strongly preferred; Delta Lake or Hudi also welcome. You understand how the format works under the hood: metadata layout, snapshots, manifests, compaction, copy-on-write vs. merge-on-read.
Clear mental model of catalogs (REST, Polaris, Glue, Unity, Hive) - their trade-offs, and how compute stays detached from storage.
Exposure to at least one vendor lakehouse or query platform - Snowflake, Starburst, or Databricks — at the level where you can reason about its architecture, not just use its UI.
Strong experience with a distributed processing engine - Flink strongly preferred; Spark also fine. You can reason about its internals, fine-tune a running job, and debug a pipeline that’s silently degrading.
Familiarity with durable execution - Temporal, Restate, or similar - or at minimum a solid mental model of what durable execution means and why it matters for data workflows.
Production experience building and operating APIs (REST or gRPC) at scale - good instincts about contracts, versioning, retries, rate limiting, and observability.
Solid understanding of Kafka and event-driven architectures (producers/consumers, partitioning, delivery semantics).
Comfortable in regulated environments (healthcare, fintech, gov) where audit, compliance, and data governance are part of every design.
Platform mindset: you design for self-service, API-first, and with systems and agents - not only humans - as legitimate consumers.
Bonus
Deeper familiarity with open/REST catalogs (Polaris, Nessie, Unity) beyond basic use.
Observability stack fluency (Prometheus, Grafana, OpenTelemetry).
Prior work on agentic or AI-facing API surfaces, or MCP-style interfaces.
Experience in HIPAA, FedRAMP, or SOC 2 environments.
dbt, DataHub, or data contract tooling exposure.
Mindset and Collaboration
Service orientation: you build APIs (and increasingly agent-facing tools) that others love to use.
Reliability-first: failure modes, retries, and observability are part of day-one design.
Cross-functional: you enjoy working with data engineers, analysts, and ML engineers and understanding their problems.
Documentation mindset: good APIs come with great docs — and good docs now means machine-readable too.
Iterative: you ship incrementally and improve based on feedback.
*The range below reflects base, variable, and equity for this role.
This is a starting point, not a ceiling — once someone joins and proves they're outlier talent, we adjust quickly to make sure their compensation matches their impact.
Job titles may span more than one career level, so actual pay depends on skills, qualifications, experience, location, and market demand, among other factors. The range reflects base salary plus any variable, bonus, or sales incentives, and our estimate of the value of private company stock options where applicable. It's subject to change, and future stock value isn't guaranteed. Sword also offers additional benefits beyond total compensation.
New Data Engineer postings at the employers we follow are up 13% over the last 6 weeks compared with the 6 before.
Each bar is one week of new postings. The darkest bars are the last 6 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.
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.
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.
Selected passages from the saved posting. Check the full description for conditions and exceptions.
Total Compensation Range €52.500—€82.500 EUR Country-specific benefits may vary and will be detailed separately.
Remote - Portugal
Working pattern and location restrictions need checking in the full posting.
Country-specific benefits may vary and will be detailed separately. Sword Health complies with applicable Federal and State civil rights laws and does not discriminate on the basis of Age, Ancestry, Color, Citizenship, Gender, Gender expression, Gender identity, Gender information, Marital status, Medical condition, National origin, Physical or mental disability, Pregnancy, Race, Religion, Caste, Sexual orientation, and Veteran status.