Data Engineer

NXP Semiconductors — Bengaluru, Karnataka

₹4–8 LPA (HireSetu estimate) · 0–2 yrs exp · Freshers eligible · Full-time · onsite

HireSetu listing reference c4ee37 · employer requisition R-10066333 — confirm requirements below, then apply on the employer site.

Quick answer: An entry-level Databricks and PySpark role at a semiconductor company, with CI/CD, change requests and monitoring written into the day job. Pipelines you built in an internship or a college project are the evidence that counts here.

From NXP Semiconductors' job posting

Position Summary

We are looking for an enthusiastic entry-level Data Engineer with a growing DevOps mindset to help build and maintain reliable, scalable data pipelines that power business functions across the enterprise. This is a great opportunity for an early-career engineer to learn, grow, and build hands-on expertise — you'll support the team in developing data pipelines, learn CI/CD and operational practices, and take on increasing responsibility under the guidance of senior engineers.

Core Skills

Databricks · Python (PySpark) · SQL · Data Pipelines · CI/CD

Engineering & Delivery

Help build and maintain data pipelines on Databricks under guidance.

Develop ETL/ELT processes with attention to data quality, consistency, and scalability.

  • Contribute to reusable frameworks for ingestion, transformation, and reconciliation across source systems.
  • Follow established engineering standards — coding standards, pipeline patterns, and ETL/ELT best practices.

Operations & DevOps

  • Assist with deploying changes through CI/CD and the Change Request (CR) lifecycle, including validation and ticket closure.
  • Participate in problem-solving and root-cause analysis, learning to drive permanent fixes over recurring firefighting.
  • Help monitor data workloads and support incident response with guidance from senior engineers.

Collaboration

  • Work with Reporting, Platform, and Business teams to help deliver curated datasets for downstream consumers.
  • Communicate progress and issues clearly to engineering peers and mentors.
  • Document workflows and runbooks to support reproducibility and knowledge sharing.

What Success Looks Like (First 6–12 Months)

  • In your first 6–12 months, you'll build a solid understanding of the data platform, confidently deliver assigned pipeline tasks, and become comfortable with CI/CD and operational practices — with support from senior engineers.

Required Qualifications

  • Bachelor's or Master's degree in Computer Science, Information Technology, or a related field.
  • 1+ years of experience (including internships) in data engineering or a related area — fresh graduates with relevant internships are encouraged to apply.
  • Foundational hands-on knowledge of Databricks, Python (PySpark), and SQL for data processing.
  • Exposure to building data pipelines (ETL/ELT), through projects, internships, or coursework.
  • Basic understanding of CI/CD pipelines and Git-based version control.
  • Familiarity with cloud platforms (AWS preferred) or willingness to learn.
  • Awareness of monitoring and observability concepts.
  • Good communication skills and eagerness to learn.

Preferred Qualifications

  • Exposure to orchestration frameworks or streaming technologies.
  • Basic familiarity with Infrastructure-as-Code and deployment tooling.
  • Awareness of observability tooling for data platforms.
  • Background or interest in semiconductor manufacturing or large-scale industrial data processing.
  • Any Databricks or cloud certification is a plus.

Competencies

  • Eagerness to learn and grow data engineering skills.
  • Ownership mindset — takes pride in the quality of assigned work.
  • Problem-solving orientation — curiosity and attention to detail.
  • Collaboration — works well with peers and mentors across teams.
  • Clear communication — able to explain technical details to peers.

More information about NXP in India...

#LI-29f4

Text from NXP Semiconductors' official job posting, formatted by HireSetu. The employer's own page is the final word on details.

Freshers with a data internship fit best

The listing asks for 1+ years including internships, and names Databricks, PySpark and SQL as hands-on skills. The person this fits has built at least one pipeline end to end: pulled data in, transformed it, wrote it out somewhere. An internship, a final-year project or a first job all count, as long as you can explain what the data was and why you structured the pipeline that way.

Databricks is a specific environment. If your pipeline experience is pandas scripts over a CSV, that is a real gap, and the free Databricks community edition is the cheapest way to shrink it. A dashboards and reporting background won't map here, because this work is building and running the pipelines other people read from.

The ops side is half the job

NXP lists CI/CD, change requests, validation, ticket closure, monitoring and incident response. So part of your week goes on deploying a change someone else wrote, checking it in a lower environment, and closing the ticket out. The preferred list mentions orchestration, streaming and infrastructure-as-code, which points to a platform that keeps growing.

Ask how the team splits pipeline development from support duty, and whether incident response runs on a rotation. Ask what a change request looks like in practice and who signs it off. Those answers decide how much of your week is heads-down building and how much is keeping existing jobs alive.

Pipeline terms in practice

A data pipeline pulls rows from a source system, reshapes them, and writes the result to a target table. Some teams load the raw records first and do the reshaping inside the warehouse or lakehouse. Databricks is the environment where PySpark code and SQL queries run against that stored data.

Transformation is where cleaning, joins and type changes happen; ingestion is the source connection that brings records in. Reconciliation compares source and target on keys, row counts or totals before a dataset is released. A runbook records the steps for starting, checking and recovering a pipeline, so support work follows a written sequence.

Steps behind a deployment

A code change starts in Git, moves through the CI/CD pipeline for build and test checks, then deploys to a lower environment for validation. The change request records the job, the validation evidence and the approval before the ticket closes.

After release, monitoring checks that a scheduled job completed and the target table received the records the next step needs. An incident triggers root-cause analysis, a fix committed through the same Git and CI/CD path, and closure of the linked ticket.

Prepared from NXP Semiconductors' job posting and checked against it before publishing. See our Editorial Policy.

How to apply

  1. The Apply button opens this job on NXP Semiconductors' careers site (nxp.wd3.myworkdayjobs.com).
  2. Its requisition number is R-10066333; search for it on the careers site if the link ever stops working.
  3. Workday logins are separate for every company, so you need an account made for NXP Semiconductors.

Apply on NXP Semiconductors' site

No fees, ever. HireSetu never charges candidates, and no genuine employer asks for money to apply, interview or join. If anyone asks you to pay, stop and report the job.

Similar openings on HireSetu

View Data Engineer on HireSetu · Software / IT jobs · Jobs in Bengaluru · Career Insights · FAQ · Companies

HireSetu
Career Intelligence Platform