Senior Data Platform Engineer

Rudram Consultancy; Bengaluru; On-site; INR 4,200,000 - 6,500,000; Full time

Job summary

Rudram Consultancy is hiring a Senior Data Platform Engineer to design and build a pluggable connector framework that unifies diverse data sources and exposes them via REST/GraphQL APIs. You will own the architecture for multi-tenant isolation, schema discovery, and secure credential handling, shaping a scalable, developer-friendly platform.

The role emphasizes deep systems design, end-to-end ownership, and collaboration with frontend and platform teams to enable low-code use cases and internal

Qualifications

• 7+ years of backend/platform engineering experience including end-to-end design.

Responsibilities

• Design and build a pluggable connector framework for multiple data sources.
• Build unified REST / GraphQL APIs for interacting with different databases and storage systems.

Skills

PostgreSQL

MySQL

NoSQL

Python

REST/GraphQL API

Multi-tenant

AWS

Docker

System design

Tools

Docker

AWS

Kubernetes

Job description

Senior Data Platform Engineer

Connectors Unified APIs Multi-Tenant Platform

About the Role

We are building a generic data platform that connects to many different databases and storage systems and exposes them through a single, unified API layer similar in spirit to Supabase, but designed to work across heterogeneous data sources.

We are looking for a Senior Data Platform Engineer to design and build the connector based architecture at the heart of it.

You will own the pluggable connector framework that brings relational databases, NoSQL systems, and object storage into one consistent, developer-friendly platform including the API layer, schema discovery, access control, multi-tenant isolation, and the SDKs other teams build on. This is a deep systems-design role for someone who has built platform infrastructure before, not only application features.

What Youll Do

• Design and build a pluggable connector framework for multiple data sources.
• Build unified REST / GraphQL APIs for interacting with different databases and storage systems.
• Implement schema discovery, metadata management, and query-abstraction layers.
• Build connectors for relational databases (PostgreSQL, MySQL), NoSQL systems (MongoDB, DynamoDB), and object storage (S3, CDN-based storage such as Bunny).
• Design and implement authentication, authorization, and access control across connectors.
• Optimise the performance, scalability, and reliability of data access.
• Implement logging, monitoring, retries, and failure handling.
• Ensure secure handling of credentials and strong multi-tenant isolation.
• Collaborate with frontend and platform teams to enable low-code and internal-tools use cases.
• Build reusable SDKs and developer tooling for consuming the platform.

What Were Looking For

This is a senior, systems-heavy role. We want someone who has designed and shipped platform or infrastructure software — not only application features on top of a single database.

7+ years of backend / platform engineering experience, including systems you designed and owned end to end.

• Deep database expertise — PostgreSQL and MySQL, advanced SQL, query optimisation, indexing, and performance tuning.
• Hands‑on experience with NoSQL systems (MongoDB and DynamoDB).
• Strong backend development in Python, and strong API design (REST and/or GraphQL).
• Experience designing multi‑tenant systems and connector / plugin‑based architectures.
• Data abstraction across heterogeneous systems, plus schema discovery and metadata management.
• Experience with event‑driven and async processing.
• AWS (RDS, S3, Lambda, ECS) and Docker, with a track record of building for reliability — logging, monitoring, retries, and failure handling.

This Role Is Not a Fit If

• You have only built application features on top of one database, with no platform or infrastructure design experience.
• You rely on ORMs and cannot reason about SQL, query plans, or performance at a low level.
• You have worked only with relational databases — no NoSQL or object storage.
• You have never designed for multi‑tenancy, or thought hard about credential security and isolation.
• You have not worked with AWS.