ClickHouse

Solutions Engineer

• Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production
• Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it
• Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't
• Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked

Senior Software Engineer – Cloud Partner Integrations

• You'll own an integration end to end: the design, the code, and the production system that keeps running after launch.
• Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production
• Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it
• Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't
• Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked
• We'd also expect you to have opinions about where this should go, and to write them down. A lot of what shapes the team's direction starts as a doc.

• You'll own an integration end to end: the design, the code, and the production system that keeps running after launch. You're setting the technical defaults a growing team will inherit, so the early decisions matter.
• Day to day, that looks like:
• Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production
• Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it
• Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't
• Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked
• We'd also expect you to have opinions about where this should go, and to write them down. A lot of what shapes the team's direction starts as a doc.

• Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production
• Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it
• Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't
• Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked
• We'd also expect you to have opinions about where this should go, and to write them down. A lot of what shapes the team's direction starts as a doc.

• You'll own an integration end to end: the design, the code, and the production system that keeps running after launch.
• Owning the architecture: auth and identity flows, multi-tenancy, how data moves and where it's allowed to live, performance, and what happens in production.
• Running what you build. You'll be on-call for your own work from early on, before there's a dedicated platform to lean on, which means owning the infrastructure, CI, deployment, and observability behind it.
• Working on top of external platforms you can't change, and being straight about which risks are yours to manage and which aren't.
• Partnering closely with the internal teams whose services you depend on: asking clearly, agreeing on interfaces, and finding ways to keep moving instead of waiting around to be unblocked.
• Expecting you to have opinions about where this should go, and to write them down.

QA Automation Engineer

• Build a Universal Provisioning Engine and custom integration layers that satisfy external auditors while keeping internal teams focused on shipping features.
• Eliminate the engineering "interruption tax," provide leadership with a real-time, data-driven view of our risk posture, and ensure continuous compliance with zero audit surprises.
• Engineer a centralized security telemetry system that programmatically captures control evidence and health in real-time, transitioning from manual snapshots to continuous data streams for an 'always-on' view of our security posture.
• Architect solutions for systems that lack native IGA support.
• Partner with our risk management function to build a secure mechanism to generate agentic risk assessments workflows using the data and results from what is collected.

Senior Security Automation Engineer

Cloud Engineer

• Take an active part in determining the roadmap for the Product Metrics team
• Work closely within the team to deliver new features, iterate and improve them
• Design, build, operate, and maintain business-critical petabyte-scale systems
• Be responsible for the performance, reliability, availability and cost-efficiency of the Product Metrics systems
• Mentor and support other team members, participate in design discussions and collaborate with the team
• Be a part of on-call rotation and take ownership of the services you're running

Senior Cloud Engineer – Product Metrics

Full-stack Engineer

• Design and build the platform services that power authentication, authorization, and audit across ClickHouse Cloud. This includes a unified RBAC/ReBAC service, token issuance and session handling, and the SDKs that product teams embed to make authorization decision.
• Model permissions and access control primitives (resources, roles, relationships, policies) that work across ClickHouse, SQL Console, ClickPipes, and HyperDX. Ship the libraries and APIs that other engineers build against.
• Implement protocol-level support for SAML, SCIM, OIDC, OAuth2, and MFA/passwordless flows. Own the integrations that make enterprise SSO and provisioning work end to end.
• Build the audit and authorization-decision telemetry pipeline so every access decision is observable, queryable, and surfaceable to customers.
• Partner with product engineering teams to migrate bespoke per-product auth implementations onto the shared platform, and design APIs that make adoption straightforward.
• Carry the platform on-call rotation and own production reliability for systems on the critical path of every customer request.

Senior Software Engineer – Identity & Authorization Platform

• Design and build the platform services that power authentication, authorization, and audit across ClickHouse Cloud. This includes a unified RBAC/ReBAC service, token issuance and session handling, and the SDKs that product teams embed to make authorization decisions.
• Model permissions and access control primitives (resources, roles, relationships, policies) that work across ClickHouse, SQL Console, ClickPipes, and HyperDX. Ship the libraries and APIs that other engineers build against.
• Implement protocol-level support for SAML, SCIM, OIDC, OAuth2, and MFA/passwordless flows. Own the integrations that make enterprise SSO and provisioning work end to end.
• Build the audit and authorization-decision telemetry pipeline so every access decision is observable, queryable, and surfaceable to customers.
• Partner with product engineering teams to migrate bespoke per-product auth implementations onto the shared platform, and design APIs that make adoption straightforward.
• Carry the platform on-call rotation and own production reliability for systems on the critical path of every customer request.

People Operations

• Partner closely with APJ leaders and managers to drive organizational effectiveness, team health, and strong performance.
• Bring a thoughtful people lens to leadership decisions including team design, performance management, and talent development.
• Act as a trusted partner to leaders navigating complex employee situations and evolving organizational needs.
• Serve as the regional point of contact for employment practices and compliance across APJ.
• Partner with Legal and external advisors to ensure alignment with local employment laws and regulatory requirements.
• Ensure global people programs and policies are appropriately implemented and adapted to local requirements where needed.
• Own key People Operations processes across APJ, ensuring regional execution aligns with global standards while meeting local requirements.
• Lead the regional execution of core people programs, including performance cycles, compensation processes, and talent initiatives.
• Identify opportunities to improve the scalability and effectiveness of regional people processes.
• Support the operational needs of the region including vendor coordination, documentation practices, and local employment process management where applicable.
• Act as the bridge between APJ and the global People organization, bringing regional insight into company-wide initiatives.
• Collaborate closely with cross-functional partners including Legal, Finance, and leadership teams.
• Ensure APJ perspectives are incorporated into global people strategies and programs.

People Business Partner Lead – APJ

Engineer

• Project Engineering & Consulting (50%): Serve as a team member on customer projects, focusing on design, architecture, integration, implementation, and documentation. This includes research, benchmarking, performance and functional testing, reference architectures, sizing, migration, integration, development, and tooling.
• Consultative Support (50%): Provide case-initiated consultative support to strategic users, customers, and prospects, assisting with implementation, onboarding, production launches, and Proof of Concepts (POCs).
• Provide architectural, technical, and migration assistance, including hands-on tasks.
• Work as a member of the Support Team, handling L1 to L3 cases and communications when not actively assigned to customer projects.
• Partner closely with ClickHouse Product Management, Engineering, and Sales to contribute to the product roadmap and account plans.
• Develop and assist with a wide range of content, including Public and Internal Documentation, Knowledge Base articles, ClickHouse Learning, Reference Architecture, blogs, and benchmark results.
• Assist with hiring and mentoring new team members as we grow and scale.
• Be available for scheduling and on-call needs to deliver high-quality 24x7 support in a global, distributed environment, including up to 35% estimated onsite regional travel.

Senior Consulting Engineer

Support Engineer

• Own the full lifecycle of customer issues for ClickHouse strategic accounts on Alibaba Cloud in the China region — from intake and reproduction through to root-cause analysis, resolution, and post-incident follow-up.
• Triage, classify, and track incoming cases; identify recurring patterns across customers and feed them back into knowledge base articles, runbooks, and product feedback for our Core, Cloud, and Engineering teams.
• Diagnose and resolve issues spanning SQL and query performance, schema and table-engine design, replication and sharding, ingestion pipelines, materialized views, resource utilization, and cluster operations.
• Advise customers on ClickHouse best practices, capacity planning, and configuration tuning for workloads running on cloud infrastructure.
• Escalate complex or product-level issues through the appropriate channels to our global Core Database and Cloud Engineering teams, while remaining the single point of contact for the customer until resolution.
• Partner with the China Engineering Manager and the global Support organization to define SLAs, on-call rotations, and escalation paths suited to the China region.
• Contribute to internal tooling, documentation (in both English and Chinese where helpful), and the broader ClickHouse community.

支持工程师 – 阿里云战略客户

• Build agents that investigate incidents. They surface anomalies, answer "why is production broken?", and use ClickStack as their substrate.
• Write skills, not just prompts. Build a library of reusable skills that captures how our team debugs, finds root causes, writes ClickHouse queries, and runs incident response, so agents pick up the right playbook instead of starting from scratch.
• Own the agent stack end-to-end. Context engineering, tool design, evals, tracing, cost. You're responsible for whether the agent works in production.
• Make ClickStack a great place to run AI workloads. Build the MCP servers, SDKs, and integrations that let customers' agents read telemetry, take action, and stay observable themselves.
• Work in the open. Collaborate with OSS contributors and customers, debug their problems alongside them, and feed what you learn back into the product.
• Tackle the hard parts. Latency, cost, context window limits, eval coverage, hallucinations on real telemetry.

AI Product Engineer

• Build agents that investigate incidents.
• Write skills, not just prompts.
• Own the agent stack end-to-end.
• Make ClickStack a great place to run AI workloads.
• Work in the open.
• Tackle the hard parts.