🎁 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 →
Principal Data Engineer, User Success (Agentic Experiences) Experience: Not Available to Not Available years Location: Toronto, ON, CAN Skills: Python, Spark, PySpark, SQL, LLM ecosystems, embeddings, vector databases, Retrieval-augmented generation (RAG), Agent frameworks, Kafka, Flink, Spark Streaming, dbt, metrics stores, data governance, data lineage, data cataloging, ETL, ELT, Iceberg, Hive, Snowflake, Redshift, Athena, AWS, EMR, Glue, S3, IAM, Lambda, Step Functions Company Overview Job Requisition ID # 26WD98052 Position Overview At Autodesk, we do what no other company can: we help our customers design and make anything. The Experience Foundations team at Autodesk plays a critical role in designing the experiences that make that mission a reality, especially in this transformative moment where seamless digital experiences and AI-powered innovation will empower customers and teams to achieve meaningful outcomes faster. The Principal Data Engineer will report to Director of Growth and Data Science in the Experience Foundations organization. This is a critical data science role for our agentic insights platformwe are evolving our data tools and platform to support AI-native experiences, enabling both humans and intelligent systems to better understand user behavior and business impact. As a Principal Data Engineer, you will be driving the design of AI-ready data products that power analytics, machine learning, and emerging agentic experiences and insights and intelligence products. This role requires a balance of deep technical expertise, architectural vision, and cross-functional leadership, influencing how data is structured, governed, and consumed across Autodesk. Responsibilities Architect and implement scale batch and streaming pipelines for large-scale product telemetry with low-latency, high-throughput data access that support LLMs and agentic workflows optimized for: Retrieval (e.g., embeddings, vector search) Contextual data access Real-time and iterative feedback loops Partner with AI/ML teams to operationalize: Feature engineering and feature stores RAG-based systems and evaluation pipelines Ensure data quality and observability meet the needs of AI-driven decision systems Guide build vs. buy decisions for data tooling and platforms Enable analysts and product teams with trusted, well-modeled datasets Partner with stakeholders to translate product questions into measurable data signals Improve instrumentation strategy to ensure high-quality behavioral data Support self-service analytics and AI-assisted exploration Collaborate across Product, Engineering, Data Science, Research and Design Influence technical direction without direct authority Drive alignment on data standards, governance, and best practices Communicate complex technical concepts to both technical and non-technical audiences Minimum Qualifications 10+ years of experience in data engineering, data platform engineering, distributed systems, or related technical roles, including ownership of large-scale production data systems Strong hands-on experience with Python, Spark, PySpark, advanced SQL, and scripting Experience with: LLM ecosystems, embeddings, vector databases Retrieval-augmented generation (RAG) Agent frameworks or orchestration systems Experience with streaming technologies (Kafka, Flink, Spark Streaming) Knowledge of analytics engineering and semantic layer tools (dbt, metrics stores) Experience with data governance, lineage, and cataloging systems Exposure to product analytics and experimentation frameworks Experience designing and operating reliable ETL/ELT pipelines across batch and streaming workloads, including orchestration, validation, backfills, incremental processing, and data quality checks Experience with up-to-date data platforms, including Iceberg, Hive, Snowflake, Redshift, Athena, or equivalent technologies Hands-on experience with AWS services, including EMR, Glue, S3, IAM, Lambda, Step Functions, and related cloud-native infrastructure Demonstrated ability to lead cross-functional technical initiatives, influence architecture, define engineering standards, and mentor engineers Strong communication skills with technical and non-technical stakeholders. Preferred Qualifications Experience with product telemetry, clickstream data, behavioral analytics, or experimentation platforms Experience with ingestion, orchestration, and transformation tools such as Airflow, dbt, Fivetran, or similar Experience partnering with product, design, research, analytics, and ML teams to create data products that directly inform user experiences or power intelligent product capabilities Experience supporting LLM, RAG, agentic AI, or internal intelligence workflows in production or enterprise environments Track record of modernizing data infrastructure in .
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.