Backend engineer focused on building high-throughput, distributed systems.
I work on real-world scale problems involving:
- Millions of events per day
- IoT device communication
- Reliable data pipelines
- Fault-tolerant architectures
I care about performance, correctness, and system design, not just writing code.
- Designing Kafka-based event-driven systems
- Building IoT backend infrastructure (MQTT + brokers)
- Optimizing MongoDB & PostgreSQL queries at scale
- Implementing idempotent, fault-tolerant processing pipelines
- Handling high-volume ingestion (~millions of messages/day)
- Go (Primary)
- Python
- Distributed Systems Design
- Event-Driven Architecture
- Microservices
- Apache Kafka
- MQTT
- MongoDB (Bulk ops, schema redesign, performance tuning)
- PostgreSQL (Schema design, constraints, indexing)
- Redis (Caching, TTL-based workflows)
- GORM
- Docker (basic usage)
- System Design (Scalability, Fault Tolerance)
- Observability & Logging
-
System Design Thinking
I don’t just write APIs — I design systems that scale and survive failure. -
Performance Optimization
Reduced bottlenecks by replacing naive DB operations with bulk processing. -
Ownership
Designed Kafka infrastructure, retry mechanisms, and backfill systems from scratch. -
Deep Debugging Ability
Can read unfamiliar codebases (even in other languages) and extract logic quickly.
- Built a Kafka-MQTT pipeline handling device communication at scale
- Designed retry + DLQ mechanisms for failure handling
- Implemented bulk database operations to replace inefficient per-record updates
- Worked on IoT command dispatch systems for large fleets of devices
- Contributed to data modeling and schema evolution
If you're looking for someone who understands scale, failures, and systems, we should talk.