Integration Engineer

ComplyDP is a DPDP Act compliance platform. Live, revenue-generating,

backed by NVIDIA Inception, Google Cloud for Startups and T-Hub.

We are hiring founding engineers to own the data-discovery connectors

that run in our cloud, in a customer VPC, and on-prem inside regulated

networks.

Bengaluru-based, hybrid. Expect periodic travel to client sites, mostly

Mumbai, and Delhi for deployment work.

THE CONSTRAINT IS THE INTERESTING PART

Our connectors describe what a customer's systems hold — schemas,

columns, metadata — without reading values. No row samples, no cell

contents, nothing that could carry personal data back out. That refusal

is enforced by guards in the pipeline, not by convention, and it is the

reason a bank will let us inside their perimeter at all.

The other half of the job is real deployment. Our product runs inside

regulated clients infrastructure: jump hosts, change tickets, security

reviews, air-gapped installs, read replicas, service accounts scoped to

the week. You will be the person who makes a connector work on someone

else's network, on their terms.

WHAT YOU WILL DO

- Build, test and deploy connectors across cloud SaaS, enterprise APIs

 and on-prem databases

- Implement REST integrations with OAuth, pagination, retries and rate

 limits, and report honestly when a walk stopped early rather than

 claiming it finished

- Package connectors with Docker so the same job runs in our cloud, a

 customer VPC, or fully air-gapped

- Write automated tests for auth, pagination, partial failure and rate

 limits, and ship them through CI

- Leave logs and failure modes that explain a broken sync without

 opening a production shell, because on a client site you often cannot

WHAT YOU BRING

- This is connector and deployment work, not data pipeline engineering.

 If your experience is Spark, Databricks, ADF or warehouse ETL, it is

 probably not the right fit.

- 3–7 years building integrations or connectors, in Python or Java

- REST APIs, OAuth, SQL and Docker, used on systems you shipped

- Production connectors in both a cloud environment and an on-prem or

 VPC environment

- Automated tests and a CI path you have used to deploy an integration

 change

- Comfort reading an unfamiliar schema and working out what it holds

- Willingness to travel to client sites for deployment

BONUS

- Data classification, DLP, or a discovery scanner you operated in

 production

- Packaging an on-prem agent, or running connectors on Kubernetes

- BFSI exposure: core banking, lending, wealth or insurance systems

- Privacy, consent or data-governance products

WEAKER FIT

- Primarily data pipeline / ETL engineering, ML research, frontend,

 analytics or BI

- Primarily ML research, frontend, analytics or BI

- DevOps or platform work without substantial connector and API

 development

- Work that is mostly configuring an iPaaS rather than building

 connectors

We hire people who have written integrations and debugged them in

production. Configuring an integration platform, without building the

connector underneath, is a weaker fit.

Founding role. Direct work with the founders, no layers.

₹18–32L plus ESOP, depending on depth.

TO APPLY

Email your CV to [Confidential Information] with one paragraph: describe a

connector you built, what broke in production, how you found out, and

what you changed so it could not happen silently again.

We read that paragraph before the CV.