🎁 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 →
We're Nagarro. We are a Digital Product Engineering company that is scaling in a big way! We build products, services, and experiences that inspire, excite, and delight. We work at scale across all devices and digital mediums, and our people exist everywhere in the world (17500 experts across 39 countries, to be exact). Our work culture is energetic and non-hierarchical. We are looking for great recent colleagues. That is where you come in! REQUIREMENTS: - Total experience: 4+ years. - Excellent knowledge and experience in Data Engineer with AWS role. - Strong working experience with architecture and development in Databricks, Python/Scala, AWS (EMR, Glue, Lambda etc.), Databricks, DLT (Delta Live Tables) pipelines, SQL. - Hands-on experience with Delta Live Tables (DLT). - Experience with data ingestion and transformation frameworks/platforms such as: Databricks, AWS, ETL pipelines. - Strong SQL skills for data manipulation and optimization. - Good understanding of data modeling concepts and ETL/ELT methodologies. - Experience working with cloud platforms such as AWS - Familiarity with Python or Scala for data engineering tasks. - Knowledge of data lake and lakehouse architectures. - Understanding of CI/CD practices and version control systems such as Git. - Build and manage Delta Live Tables (DLT) pipelines for reliable and scalable data processing. - Implement data ingestion workflows from various structured and unstructured data sources. - Develop data transformation logic using ETL/ELT frameworks and best practices. RESPONSIBILITIES: - Writing and reviewing great quality code. - Understanding the clients business use cases and technical requirements and be able to convert them into technical design which elegantly meets the requirements. - Mapping decisions with requirements and be able to translate the same to developers. - Identifying different solutions and being able to narrow down the best option that meets the clients requirements. - Defining guidelines and benchmarks for NFR considerations during project implementation. - Writing and reviewing design document explaining overall architecture, framework, and high-level design of the application for the developers. - Reviewing architecture and design on various aspects like extensibility, scalability, security, design patterns, user experience, NFRs, etc., and ensure that all relevant best practices are followed. - Developing and designing the overall solution for defined functional and non-functional requirements; and defining technologies, patterns, and frameworks to materialize it. - Understanding and relating technology integration scenarios and applying these learnings in projects. .
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.