Integration Engineer - 2
Engineering · Bengaluru · Office, client premises when needed
₹18–32L plus ESOP, depending on depth
Build, test, and deploy the data-discovery connectors that run in our cloud, in a customer VPC, and on-prem inside regulated networks.
About the role
ComplyDP turns data-governance and DPDP obligations into product. You will own the connectors that describe what a customer's systems hold (schemas, columns, metadata) across SaaS tools and across systems that cannot leave a customer network.
The constraint is the interesting part. Our connectors describe structure 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. If you find constraints like that interesting rather than annoying, you will enjoy this.
The other half of the job is real-world 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.
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.
What you will do
- Build, test, and deploy connectors for data discovery 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 on-prem
- 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
- 3–7 years building integrations or connectors, in Python or Java
- REST APIs, OAuth or API authentication, 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
- Depth in AWS, Azure, or GCP, plus a database or enterprise API you connected yourself
- Comfort reading an unfamiliar schema and working out what it actually holds
Bonus
- Data classification, DLP, or a discovery scanner you operated in production
- Packaging an on-prem agent, or running connectors on Kubernetes
- Privacy, consent, or data-governance products
- BFSI exposure: core banking, lending, wealth, or insurance systems
Weaker fit
- Primarily ML or AI research, frontend, generic analytics, or BI
- DevOps or platform work without substantial connector and API development
- Work that is mostly configuring an iPaaS rather than building connectors
Standard vesting
ESOP grants vest over four years from the start date in the grant. Nothing vests in the first year. One quarter vests on the first anniversary, then an equal part each month.
| When | Vested |
|---|---|
| Months 0–11 | 0% |
| Month 12 | 25% of the grant |
| Each month from 13 to 48 | 1/48 of the grant |
| Month 48 | 100% |
On a grant of 48 options: none until month 12, then 12, then 1 each month through month 48. The offer sets the number of options.