META-CHAIN

Product: High-load centralized crypto exchange (CEX) 
 

Responsibilities

• Build and operate wallet / blockchain integration services in Go:
  • deposits: ingestion of incoming transactions, confirmations, reorg handling;
  • withdrawals: transaction building/signing/broadcasting, fee management, queues, retries;
  • addresses & wallets: generation, assignment, monitoring, hot/warm wallet logic.
• Integrate with security infrastructure: HSM (e.g., Thales Luna), key policies, strict access control.
• Design high-throughput pipelines with Kafka: idempotent consumers/producers, delivery guarantees, deduplication.
• Develop internal gRPC/REST APIs for collaboration with balance, risk/AML, and admin services.
• Own observability & reliability: metrics, tracing, alerting, graceful degradation, load testing.
• Investigate incidents, perform RCA, and continuously harden reliability and security.

Tech stack

• Go (core services: wallets, blockchain integrations)
• PostgreSQL (transactional), Redis (caching/locks), Kafka (event bus)
• ClickHouse (analytics)
• AWS (MSK, ECS/EKS, S3, KMS, etc.)
• gRPC, CQRS/Event Sourcing, strict audit logging

Requirements (must-have)

• Strong Go fundamentals: concurrency (goroutines/channels), profiling, performance optimization, correct context/timeouts usage.
• Production-grade microservices experience: health checks, graceful shutdown, retries, rate limiting, circuit breakers.
• Kafka hands-on: consumer groups, offsets, idempotency patterns, application-level exactly-once strategies.
• PostgreSQL experience: transactions, locking behavior, indexes, migrations, handling contention.
• Security basics: secrets/keys handling, least privilege, audit trails, secure input processing.

Nice to have

• Blockchain integration experience (EVM/BTC/TRX/TON, etc.), reorg/mempool, fee strategy.all top 20 network
• HSM/KMS signing flows, key segregation, operational security procedures.
• Fintech/exchange background: double-entry accounting concepts, holds/reservations, dispute case handling.
• High-load systems: 10k+ msg/s pipelines, low-latency design, chaos testing, load testing methodology.

Why join

• Real security and money flows: strict controls, auditability, realistic threat models.
• High-load engineering challenges: idempotency, consistency, concurrency, failure handling.
• Architectural impact: influence standards, patterns, and core design decisions.