Sign in to see your fit: the skills, experience and location this job asks for, checked against your profile.
Job description
We're looking for a Staff Software Engineer, Data to lead the design and evolution of the data infrastructure that powers Albert OS. This is a high-impact role for someone who thinks deeply about data architecture across analytical and transactional systems, cares about correctness and reliability at scale, and can influence engineering direction across teams.
Responsibilities
Own the architecture and evolution of our core data platforms, spanning Lakehouse infrastructure, analytical pipelines, and transactional systems.
Design and build scalable data ingestion and transformation pipelines (batch and streaming) with a strong emphasis on data quality, reliability, and downstream usability.
Define data modeling standards across our stack, including dimensional, medallion, and schema-first patterns.
Drive performance optimization across SQL and NoSQL systems, with a focus on query efficiency, partitioning strategies, and throughput at scale.
Collaborate closely with API and Data Science teams to build robust pipelines and shared data contracts.
Establish and enforce data security practices, including encryption boundaries, access controls, and tenant isolation.
Set standards for observability across data systems using tools like Grafana, CloudWatch, and OpenTelemetry.
Mentor engineers across the org and lead architectural decisions through review and documentation.
Requirements
8+ years of experience in data engineering or a closely related discipline, with a focus on large-scale distributed systems.
Hands-on experience with Databricks and lakehouse architecture patterns.
Strong understanding of OLAP systems and experience designing star schema and galaxy schema data models.
Strong understanding of transactional systems design, including consistency models, write patterns, and operational reliability.
Expertise in data modeling across both SQL and NoSQL ecosystems.
Strong programming skills in Python and Spark with an emphasis on clean, maintainable code.
Hands-on experience with AWS services including S3, Lambda, and IAM.
Familiarity with observability stacks (Grafana, CloudWatch) and experience debugging production bottlenecks.
Knowledge of DynamoDB and PostgreSQL is a plus.
Excellent communication skills and a track record of influencing cross-functional technical decisions.
Key Competencies
Builder Mindset: Wants to create foundational systems that others build on.
Curiosity: Genuine interest in how your work enables scientific discovery.
Rigor: Commitment to quality. AI makes mistakes confidently, and our customers won't accept hand-waving.
Collaboration: Partners effectively with engineers across Product Engineering, AI/ML, and Enterprise Engineering.
Adaptability: Comfortable in a dynamic, fast-moving environment where priorities shift.
Why Albert
Revenue from day one. The product is loved and used by thousands of users.
Small team. Flexible hours. Collaboration over process.
Most IT Jobs posts in Bangalore ask for 3–6 years of experience (41% of 5484 that say).
Hiring most for IT Jobs in Bangalore
Bosch Group207 open jobs
Eurofins123 open jobs
Brillio118 open jobs
Jobs asking for AWS in Bangalore also ask for
Microsoft Azure58%
Python54%
Google Cloud Platform (GCP)47%
CI/CD41%
Kubernetes38%
From live job posts on CoreHRx, updated 21 Nov 2026. Skill figures count posts that list their skills; salary figures only posts that show a salary.
Questions about this job
What is the salary for this Staff Engineer, Data Platform job?
The post does not state the pay. As an estimate, comparable posts on CoreHRx advertise ₹13L – ₹25L a year (typical for IT Jobs in Bangalore, 293 posts).
This page is for Indian job seekers preparing for cloud engineer, DevOps, backend and solutions architect roles that list AWS as a skill, whether you are a fresher with a first certification or an experienced engineer moving into a senior role. It covers 60 questions in three levels: core services and concepts, then design and configuration choices for one to three years of experience, and finally scenario, security, cost and troubleshooting questions asked in senior rounds. Read each answer, explain it aloud in your own words, and try the CLI commands in a practice account with a billing alert set.
Questions you may be asked
What is the difference between an AWS Region and an Availability Zone?
Explain the AWS shared responsibility model.
What is Amazon EC2, and how do you read an instance type name like m7g.large?
What is Amazon S3, and what are its main storage classes?