🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
About Medical Guardian: Medical Guardian is a fast-growing digital health and safety company on a mission to help people live a life without limits. With 13 consecutive years on the Inc. 5000 list of Fastest Growing Companies, we are redefining what it means to age confidently and independently. We support over 625,000 members nationwide with life-saving emergency response systems and remote patient monitoring solutions. Trusted by families, healthcare providers, and care managers, our work is powered by a culture of innovation, compassion, and purpose. Mission: This role is focused on building and leading the data engineering foundation that powers real-time decisioning, operational applications, analytics, ML/AI model development, and data services across Medical Guardian. The Principal Data Engineer will own the design, delivery, and maturity of production-grade data pipelines and data platforms, with a primary emphasis on real-time streaming, IoT telemetry, Databricks, Azure, data services for APIs and microservices, and reliable data products for downstream consumption. Role Summary: We are looking for a Principal Data Engineer to serve as a hands-on technical and people leader for data engineering, data platform architecture, real-time streaming, and production data services. This role will focus on designing, building, operating, and improving data pipelines and data products while also bringing principal-level judgment to architecture, stakeholder shaping, delivery priorities, team management, and production readiness. This is a hands-on engineering leadership role first. The ideal candidate should be comfortable spending significant time working directly with Databricks, Spark, SQL, Python/PySpark, Azure services, streaming architectures, data quality frameworks, pipeline automation, CI/CD, and production troubleshooting. They should also be able to operate with the maturity of a principal-level leader: shaping unclear requirements, making pragmatic technical decisions, managing and mentoring engineers, and driving work forward without waiting for perfect specifications. This is a fast-moving, startup-like environment. Requirements may be incomplete, priorities may evolve, and the right candidate will help create clarity while building quickly. We need someone who can move from ambiguous business need to reliable data capability with urgency, discipline, and ownership. Stakeholder shaping is a critical part of this role. The Principal Data Engineer should be able to work directly with business, product, software engineering, analytics, ML/AI, operations, and leadership stakeholders to define what data needs to exist, how it should be consumed, what production guarantees are required, and how success should be measured. A background in commercial software, SaaS, digital products, healthtech, fintech, IoT, data platforms, or other product-driven environments is strongly preferred. We want someone who understands that data pipelines and data services are not just technical artifacts. They are product capabilities that support real users, real workflows, operational decisions, ML/AI systems, APIs, analytics, and measurable business outcomes. Key Responsibilities: Hands-On Data Engineering and Platform Development Design, build, optimize, and operate production-grade batch and streaming data pipelines on Azure and Databricks, with a primary focus on real-time IoT and telemetry use cases within a Medallion architecture. Develop ETL/ELT workflows to ingest, transform, validate, and serve large volumes of structured, semi-structured, unstructured, and streaming data. Build and maintain reliable data products, data services, APIs, and microservices that support operational applications, analytics, software engineering, and ML/AI teams. Use Python, PySpark, Spark SQL, SQL, Delta Lake, Databricks Workflows, CI/CD, and related tools to build maintainable, testable, and observable data systems. Troubleshoot complex production pipeline issues across Databricks, Azure, streaming systems, APIs, and source systems, including root cause analysis, corrective action, and prevention planning. Move quickly from rough business need to prototype, pilot, and production-ready data capability while maintaining appropriate engineering discipline. Real-Time Streaming, IoT Telemetry, and Operational Data Services Lead the design and delivery of real-time streaming ingestion and processing patterns for connected medical device telemetry, event data, and operational data feeds. Implement streaming solutions using Azure Event Hubs, Azure Stream Analytics, Databricks, Delta Lake, and related Azure integration patterns. Design cost-effective throughput, partitioning, delivery, retention, and replay strategies for high-volume event and telemetry workloads. Create consumption patterns that support APIs, microservices, operational applications, near-real-time decisioning, analytics, and ML/AI use cases. Define reliability, latency, quality, observability, and supportability expectations for production streaming systems. Databricks, Lakehouse, and Data Platform Architecture Set direction for Databricks-based data engineering patterns, including Medallion architecture, Delta Lake, Spark optimization, data modeling, data quality, and reusable pipeline design. Optimize production Databricks pipelines using PySpark, Spark SQL, Delta Lake, partitioning strategies, caching, shuffle optimization, cluster/job configuration, and cost-aware design. Establish practical standards for pipeline structure, code organization, testing, deployment, monitoring, documentation, and ownership. Partner with data platform, security, infrastructure, and engineering teams to ensure the data platform is scalable, secure, reliable, and aligned with enterprise architecture. Make pragmatic architecture tradeoffs between speed, durability, cost, governance, performance, and downstream business impact. Stakeholder Shaping and Cross-Functional Partnership Work directly with business, product, analytics, ML/AI, operations, software engineering, and leadership stakeholders to clarify what data is needed, why it matters, how it will be used, and what success looks like. Translate ambiguous business needs into concrete data requirements, data product definitions, architecture options, delivery priorities, and implementation plans. Ask practical questions early: who will use the data, what decision or workflow does it support, what latency and quality are required, what happens if the data is wrong or late, and how will we know the capability is creating value? Help the organization avoid becoming a data ticket factory by shaping solutions, not just executing requests. Communicate architecture decisions, tradeoffs, risks, dependencies, and delivery options clearly to technical and non-technical stakeholders. Team Management and Principal-Level Technical Leadership Manage, mentor, and develop data engineers, providing clear expectations, technical guidance, prioritization support, feedback, and accountability. Provide technical leadership through hands-on example, strong engineering judgment, clear recommendations, and pragmatic decision-making. Lead design reviews, code reviews, production readiness reviews, incident reviews, and architecture discussions across data engineering initiatives. Establish and improve engineering standards for data quality, testing, CI/CD, observability, documentation, runbooks, cost management, privacy, and security. Proactively identify platform risks, data gaps, unclear ownership, operational weaknesses, and opportunities to improve reliability, scalability, and delivery speed. Influence without relying only on formal authority by building trust, framing tradeoffs, and helping cross-functional teams get to decisions. ML/AI, Analytics, and GenAI Enablement Partner with ML engineers, data scien
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.