Java Developer

About the Team

Our Connector Engineering group builds and operates data connectors that bring customer data from hundreds of third-party API-based systems into warehouses. Engineers use an internal declarative framework, authoring structured connector definitions for entities, endpoints, authentication, and sync behavior that the shared framework executes, tests, and runs in production.

The framework powers several hundred production connectors. Connector engineering pods own portfolios of live connectorsbuilding new ones, extending existing ones, fixing bugs, and handling incidents.

What You'll Do

• Build and ship connectors: Design, author, and maintain connector definitions for third-party REST and GraphQL APIs owned by your team, from requirements through General Availability.
• Extend existing connectors: Add new tables, entities, endpoints, and feature flags to live connectors in response to customer requests and support escalations — for example, adding a new API object, supporting a new region or credential format, or enabling a new sync mode.
• Own production health: Triage and resolve incidents on your team's connectors, debug sync failures across a distributed system, and drive root-cause fixes.
• Work within the connector framework: Write connector definitions following the framework's syntax and rules, validate changes with the framework's validation and local-testing tooling, and write hybrid backend code for logic that can't be expressed declaratively.
• Handle auth and credentials: Implement OAuth and other authentication flows for new connectors, and run credential migrations safely across existing production connections.
• Partner with the platform/framework team: Work with the team that owns the shared connector framework when a requirement needs a new framework capability (e.g., custom report support, new deployment modes), and help evaluate framework-based vs. fully custom build decisions for new connectors.
• Test and validate: Write and maintain automated tests (unit, integration, and build-system-level test suites) and support workflow/orchestration-based sync testing for your connectors.
• Collaborate cross-functionally: Work with Product, Support, and Technical Writing to scope new connectors, resolve customer-impacting issues, and keep setup/overview documentation accurate.

What We're Looking For

• 2–3 years of professional software engineering experience, ideally building backend services, third-party API integrations, or ELT/data-pipeline connectors.
• Strong proficiency in Java (or a comparable statically typed backend language); comfort picking up a declarative or functional DSL used for connector definitions.
• Solid understanding of REST and GraphQL APIs: authentication (OAuth 2.0 and others), pagination, rate limiting, and webhooks.
• Working knowledge of data sync/ELT concepts — incremental vs. historical sync, schema design, and idempotency.
• Strong debugging skills: comfortable reading logs, tracing failures through a multi-service system, and root-causing production incidents under time pressure.
• Experience with Git-based workflows and collaborative code review.
• Clear written communication — this role works closely with Support, Product, Technical Writing, and the platform team, often asynchronously.

Nice to Have

• Exposure to large-scale build systems (e.g., Bazel, Gradle, Maven).
• Familiarity with workflow-orchestration frameworks (e.g., Temporal, Airflow, Step Functions).
• Prior experience maintaining SaaS/API connectors or working on an integrations team.
• Interest in AI-assisted engineering tooling for connector generation or documentation.

Success in the First 3 Months

• Independently triage, debug, and resolve incidents on the team's owned connectors.
• Navigate the connector definition, validation tooling, and test suites without heavy hand holding.
• Build working relationships with the platform/framework team, Support, and Product stakeholders.