Infrastructure Architect

At OKX, we believe that the future will be reshaped by crypto, and ultimately contribute to every individual's freedom.

OKX is a leading crypto exchange, and the developer of OKX Wallet, giving millions access to crypto trading and decentralized crypto applications (dApps). OKX is also a trusted brand by hundreds of large institutions seeking access to crypto markets. We are safe and reliable, backed by our Proof of Reserves.

Across our multiple offices globally, we are united by our core principles: We Before Me, Do the Right Thing, and Get Things Done. These shared values drive our culture, shape our processes, and foster a friendly, rewarding, and diverse environment for every OK-er. OKX is part of OKG, a group that brings the value of Blockchain to users around the world, through our leading products OKX, OKX Wallet, OKLink and more.

Lead infrastructure architecture and core platform development for the AI Native era, covering CI/CD, AIOps, observability, and monorepo engineering. Build platforms that support multiple programming languages across host-based and containerized environments.

Use platform engineering, intelligent tooling, and automated quality controls to enable developers and AI agents to work together, improving developer productivity, software quality, and production reliability.

1. →
   Infrastructure Architecture and Evolution: Define platform architecture, technical standards, and roadmaps, balancing scalability, reliability, security, and cost. Lead critical component design, hands-on development, and implementation across teams.
2. →
   AI Native Engineering Capabilities: Connect code, documentation, dependencies, test results, and runtime data into usable engineering context. Expose capabilities through APIs, CLIs, and SDKs for developers and agents to understand and review code, run tests, and resolve issues. Establish task evaluations, output validation, and execution permissions.
3. →
   Infrastructure for Multiple Languages: Build extensible toolchains, dependency management, testing, and delivery capabilities for ecosystems such as Go, Java, Python, C++, and Rust. Use standard protocols and SDKs to support communication across languages, interface compatibility, and consistent telemetry, reducing platform integration effort.
4. →
   Monorepo and Build Systems: Define repository structure, module boundaries, dependency policies, and code ownership to support changes across modules and independent service releases. Apply practices from systems such as Bazel and Buck2 to deliver incremental and reproducible builds, affected-test selection, remote caching, and remote execution.
5. →
   CI/CD and Quality Engineering: Build shared platforms for builds, tests, artifacts, and releases across hosts and containers. Improve configuration governance, automated quality gates, progressive delivery, health verification, and rollback to shorten delivery cycles and reduce change risk.
6. →
   Observability and Reliability: Unify metrics, logs, traces, and profiling, linking telemetry to code, configuration, dependencies, and deployments. Establish SLIs, SLOs, error budgets, and alerting practices, and feed production findings back into engineering quality improvements.
7. →
   AIOps and Automated Remediation: Combine telemetry, topology, change history, and operational knowledge to enable anomaly detection, incident investigation, root cause analysis, and controlled remediation. Use incident replay, evaluation, and feedback to reduce recovery time and repetitive operational work.