Senior Full Stack Software Engineer - ClickPipes Platform

This role is suitable for a Senior full-stack engineer with 5+ years of experience, deep expertise in React, TypeScript, HTML/CSS, JavaScript, DOM, HTTP, and production web applications.

The candidate should be skilled in automated testing, CI/CD, REST or GraphQL APIs, backend services, system integrations, and distributed-team collaboration, with Go, Node.js, cloud infrastructure, Terraform, or data-platform experience as advantages.

They should be familiar with designing scalable, data-intensive interfaces, managing asynchronous and real-time workflows, owning features from design through maintenance, and handling monitoring, debugging, performance, reliability, and production incidents.

How would you design a React and TypeScript interface for managing long-running ClickPipes data ingestion jobs?

I would model each job as an explicit state machine, such as provisioning, running, paused, failed, and completed. The UI would use typed API contracts, resilient polling or server-sent events, optimistic updates where safe, and clear loading, retry, and error states.

How would you efficiently render and interact with millions of records in a data-heavy web interface?

I would avoid loading the entire dataset into the browser and rely on server-side pagination, filtering, sorting, and aggregation. For large visible result sets, I would use virtualization, memoized rendering, stable keys, and careful measurement of network and rendering performance.

How would you handle real-time state changes from asynchronous connector operations?

I would combine an initial state fetch with a subscription mechanism such as WebSockets or server-sent events, with polling as a fallback. Updates should be idempotent, ordered or versioned when necessary, and reconciled against the current client state to avoid stale transitions.

What principles would you apply when designing REST or GraphQL APIs for ClickPipes workflows?

I would define explicit resource models, consistent error formats, validation rules, pagination semantics, and idempotency for operations that create or modify connectors. Contracts should be versioned and documented, with authorization and observability considered as part of the API design.

How would you implement reliable error handling for a connector creation workflow?

I would distinguish validation, authorization, dependency, and transient infrastructure errors so the UI can provide actionable feedback. Retryable operations would use bounded exponential backoff and idempotency keys, while non-retryable failures would preserve user input and explain the required remediation.

How would you test a full-stack feature that creates and monitors a ClickPipe?

I would use unit tests for state transformations and validation, integration tests for API and service boundaries, and end-to-end tests for the critical user workflow. Tests should cover success, retries, partial failures, permission errors, cancellation, and asynchronous status transitions within CI.

How would you investigate a production incident involving slow or failing ClickPipes UI requests?

I would first examine dashboards, logs, traces, error rates, latency percentiles, and recent deployments to identify the failing layer. I would mitigate customer impact through rollback, feature flags, throttling, or a targeted fix, then perform a root-cause analysis and add preventive monitoring or tests.

What frontend performance techniques are most important for a high-velocity, data-intensive application?

I would measure before optimizing, then address bundle size, unnecessary re-renders, network waterfalls, expensive computations, and excessive polling. Code splitting, caching, virtualization, debouncing, memoization, and efficient query invalidation can improve responsiveness without sacrificing correctness.

How would you ensure security when building a frontend that manages data integrations?

I would enforce authorization on the backend rather than trusting UI checks, use secure authentication and session handling, and avoid exposing credentials or sensitive connector configuration in logs or client state. Inputs must be validated and encoded, and CSRF, XSS, secret handling, and least-privilege access should be addressed.

How could Go, Node.js, Terraform, and cloud infrastructure knowledge support this role?

Go or Node.js experience helps with backend APIs, workers, and integration services, while cloud knowledge supports debugging networking, storage, queues, and service limits. Terraform enables repeatable infrastructure changes, with reviews, state management, and observability treated as part of the delivery process.

ClickHouse is hiring a Senior Full Stack Software Engineer to build ClickPipes, a high-scale data integration platform powering seamless ingestion into ClickHouse. You’ll create React and TypeScript interfaces for large datasets and real-time workflows while contributing to APIs, backend services, testing, monitoring, and production reliability across the stack, with opportunities to use Go, Node, Terraform, and cloud technologies. This is a full-time, fully remote role open across the United States and Canada, offering $147K–$215K in general U.S. locations or $167K–$238K in premium markets, plus equity. Apply to work autonomously on petabyte-scale systems, solve challenging data engineering problems, and make a visible impact on a globally distributed team.