Back End Developer

Company Description

ComplyDP is a DPDP compliance platform. We connect to enterprise systems read-only, discover where personal data lives, and produce audit-grade records of processing, without ever copying client data. Backed by NVIDIA Inception, Google Cloud for Startups, T-Hub and DST. Clients include listed manufacturing groups, global research firms and regulated financial entities.

Role Description

You will build the connector layer: the part of the product that reaches into a client's estate, reads structure and metadata, and returns an inventory. Zero replication is architectural, not aspirational. Connectors operate on metadata and counts only.

Indian enterprise estates are not cloud-native. A large share of what we need to reach sits on-prem, including SQL Server, Oracle, file shares, Active Directory and legacy line-of-business systems. Reaching it, outbound-only and without asking a client's network team to open anything inward, is a defining part of this role.

What you'll build

• Read-only connectors into cloud storage, SQL/NoSQL databases and SaaS APIs
• On-prem and legacy connectors: agents deployed inside client networks, operating outbound-only
• Schema and metadata introspection that identifies personal-data columns without reading records
• Detection of India-specific identifiers (Aadhaar, PAN, GSTIN) via pattern and checksum logic
• Vendor and data-exchange mapping: what personal data enters and leaves each third-party processor
• Repository configuration analysis to surface undeclared flows

Qualifications

• 3 to 7 years backend engineering, with real depth in third-party API integration
• Strong Python: asyncio, FastAPI, SQLAlchemy
• Production OAuth 2.0: authorization code and client credentials, token refresh, webhook signature verification
• Database metadata introspection: information_schema, pg_catalog, read-only role provisioning
• REST API fluency: pagination, rate limits, backoff, idempotency
• Docker, working Linux networking, and an understanding of what enterprise IT will and will not permit
• Azure or AWS, secrets management, managed identity
• Judgment about credentials. You will hold read-only access into regulated enterprises. Security instinct is the non-negotiable

Preferred

Prior connector work at an iPaaS, ETL, data-discovery or enterprise security vendor. Experience with on-prem sources such as SQL Server, Oracle, SMB/NFS file shares or LDAP/Active Directory. Exposure to privacy or security tooling.

Note on scope

This is not a data engineering role. No pipelines, no warehouses, no Spark. The problem is breadth of systems and correctness of access, not volume of data. Consuming dozens of unfamiliar third-party APIs is different work from building your own, and that difference matters here.

• Apply with a short note on a connector or integration you shipped: what system it read from, how you authenticated, and how you got schema or metadata out without pulling the underlying records.