Data Engineer
NTT DATA (company site, opens in a new tab)7+ yrsBengaluruOn-siteDirect career pageEst. 18–30 LPA
Posted 6d ago
Reach people at NTT DATA
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at NTT DATA you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own and optimize Databricks pipelines for ingesting, classifying, extracting, validating, and serving information from insurance documents and communications.
- Improve LLM-based extraction accuracy and production performance, including handling complex Excel/SOV files and scaling pipeline concurrency.
- Map validated outputs into consistent JSON and an insurance ontology for downstream underwriting and brokerage workflows; support migration from Microsoft Fabric to Databricks.
Minimum Requirements
- Work Experience Required: Minimum 7+ years in data engineering, software development, or production data pipeline development; minimum 4+ years of hands-on Databricks and scalable pipeline experience.
- Strong hands-on Databricks, Python, PySpark, and SQL skills, including production ingestion and transformation pipelines.
- Experience processing unstructured and semi-structured business documents, integrating LLMs or AI models, and validating or reconciling AI-generated outputs.
- Experience with data modeling and ontology concepts, downstream APIs or JSON data products, cloud data architectures, and production performance, scalability, or concurrency troubleshooting.
Ideal Candidate Profile
- Has practical experience improving document-intelligence pipelines where extraction errors, source-specific rules, or validation gaps affect business use.
- Can connect document-derived fields to consistent business entities and relationships, rather than delivering raw extracted data alone.
- Fits a hands-on production environment involving Databricks migration, large or complex files, and close collaboration with insurance underwriting and brokerage workflows.