Team Lead - Connectors

Tech Lead — Connectors

Location: Hyderabad (Work from Office) | Type: Full-time, 5 days a week | Experience: 8–10 years

About Bluecopa

At Bluecopa, we are building a finance operations platform for high-growth companies. We help finance teams automate their work, analyse their data, and make decisions faster.

We are a small, product-focused team working on hard data integration problems. If you like building reliable connectors and moving data between enterprise systems at scale, we would like to talk to you.

About the Role

As Tech Lead for Connectors, you will lead the team that builds and runs Bluecopa's data integration platform. This is a hands-on role: you will write code, review designs, and guide a team of engineers building integrations with ERPs, SaaS applications, databases, payment platforms, APIs, and file storage systems.

Your success will be measured on three things: how quickly the team can launch new connectors, how reliably those connectors run in production, and how easily other teams can use the data they produce.

What You Will Do

Connector Platform

• Design the connector platform so that a new production-ready connector can go from planning to launch in weeks, not months.
• Build a shared framework that handles the common parts of every connector — authentication, schema discovery, extraction, pagination, incremental sync, retries, checkpointing, and error handling — so engineers write only the source-specific logic.
• Set clear standards for how connectors are built, tested, monitored, and updated, and make sure the team follows them through design and code reviews.

Enterprise Integrations

• Build and ship connectors for systems such as SAP S/4HANA, Oracle Fusion, NetSuite, Microsoft Dynamics, Salesforce, HubSpot, QuickBooks, Zoho Books, Stripe, and PayPal, each supporting both full and incremental sync.
• Make sure every connector handles API rate limits, pagination, retries, partial failures, and long-running sync jobs on its own, so customer syncs finish without anyone stepping in manually.
• Build integrations across REST/SOAP APIs, SDKs, webhooks, SFTP, relational databases (PostgreSQL, MySQL, Oracle, SQL Server), and file storage (GCS, S3, Azure Blob, Google Drive, OneDrive).

Data Correctness and Incremental Sync

• Design CDC and incremental sync patterns (using Debezium, Kafka, or similar) so that data moves exactly once — no duplicates, no gaps, no silent data loss when a job fails and restarts.
• Build checkpointing and recovery so that connectors resume safely after failures and keep working when a source system changes its schema.
• Deliver clean, validated data into BigQuery, Snowflake, or Databricks that finance and product teams can use without double-checking it.

Data Models and Contracts

• Map source-specific objects to Bluecopa's standard business entities, including custom fields, custom objects, and metadata.
• Define and maintain schemas and data contracts so that connector output stays consistent and predictable — a breaking change should never surprise a downstream team.

Reliability, Monitoring, and Cost

• Set and meet clear targets for sync success rate, data freshness, and time to recover from failures.
• Add monitoring to every connector — health, sync latency, API failures, throughput, and data quality — so the team finds problems before customers do.
• Build automatic data checks and reconciliation that catch errors at the point of ingestion, not during a customer's month-end close.
• Keep API usage and cloud costs under control as data volumes grow.

Team Leadership

• Lead and mentor a team of connector engineers through code reviews, pairing, and clear standards.
• Turn the integration roadmap into a realistic plan and deliver it on schedule, balancing new connectors against platform and reliability work.
• Make the final technical calls for the connector area, lead design reviews for complex integrations, and solve problems that cut across multiple connectors.
• Work with Product, Customer Success, and data teams to decide which integrations matter most to customers, and clear blockers quickly when things escalate.

What We Are Looking For

• 8–10 years in data engineering, data integration, or backend engineering, including at least 2 years leading engineers or being fully responsible for a technical area.
• A history of building and running production integrations or data pipelines — systems you can point to that worked reliably for years.
• Strong hands-on Python and SQL, with a solid understanding of relational databases.
• Experience building API integrations (REST and/or SOAP) that deal with real-world problems: rate limits, pagination, retries, checkpointing, idempotency, error handling, schema changes, and data validation.
• Hands-on experience with an integration framework such as Airbyte, Singer, CData, or Meltano.
• Experience loading and modelling data in BigQuery, Snowflake, Databricks, or a similar platform.
• Working knowledge of at least one major cloud (GCP, AWS, or Azure).
• Good engineering habits: Git, CI/CD, automated testing, monitoring, and handling production incidents.

Nice to Have

• Direct integration work with SAP S/4HANA, Oracle Fusion, NetSuite, Microsoft Dynamics, Salesforce, or similar enterprise applications.
• Experience with Debezium, Kafka, or other CDC/streaming systems.
• Experience with dbt and modern ELT pipelines.
• Experience with Temporal, Airflow, Prefect, or similar orchestration tools.
• Kubernetes experience.
• Experience designing standard data models and data contracts.
• Experience handling custom fields, custom objects, and metadata in enterprise applications.
• Experience with webhooks and event-driven integrations.
• Time spent at a SaaS or high-growth startup.

What Success Looks Like

• In 90 days: You have shipped or unblocked at least one major connector, set up a regular design-review process, and picked the top three framework improvements that will speed up future launches.
• In 6 months: New connectors launch faster than before, sync reliability is tracked against clear targets on a dashboard, and the team works to standards you have set.
• In 12 months: Customers can turn on new integrations in days, production issues are rare and fixed quickly, and the team you have built ships good work without needing you in every decision.