Back

Lead/Senior Software Engineer, Zalo

Hồ Chí Minh
Full-time

🤖 What you will do

  • Design and maintain high-performance microservices for large-scale data storage, focusing on ultra-low latency and high throughput.
  • Help shape the direction of features like metadata indexing, object lifecycles, and multi-region replication.
  • Analyze system bottlenecks (disk I/O, network saturation) and improve service quality through better concurrency models and resource management.
  • Produce maintainable and well-tested code with understanding how your code interacts with the hardware.
  • Integrate secure coding practices and handle complex authentication layers (like AWS SigV4)

👾 What you will need

  • 5+ years of professional experience with a focus on backend systems; should have a deep mastery of Go, C++, or Java.
  • Proven experience with async IO, high-throughput networking (gRPC, HTTP/2/3), and under-the-hood optimizations (epoll, zero-copy).
  • Understand Linux kernel, memory management, and disk I/O effect on database-driven applications.
  • Professional experience using AWS S3 or other object stores; understand buckets, prefixes, and basic IAM/Bucket policies from a developer's perspective.
  • Experience with NoSQL or distributed databases and a strong understanding of schema design for performance.

Preferred Qualifications

  • Familiarity with storage engines or distributed filesystems (e.g., MinIO, Ceph, SeaweedFS, or HDFS).
  • Knowledge of consensus protocols (Raft/Paxos), replication strategies (Quorum, Erasure Coding), or CAP theorem trade-offs.
  • Experience building RESTful APIs that follow strict compatibility standards (e.g., S3-compatible layers).
  • Experience using Prometheus/Grafana or similar tools to debug complex distributed systems.

Take a look inside
<vhfihrtipnmg__ypyrcovctensqs/>

Our interview process is all about getting to know each other. Come prepared to showcase your hard work, skills, and achievements, and get a better understanding of what it’s like to work at Zalo group.

Why
<zcbhjowogsye/>
Zalo?

Life at <jZraylto/>