I'm Raj — a Software Engineer on the Performance and Scale team at Red Hat. My day job? Pushing OpenShift clusters to their limits, finding where they crack, and making sure they don't crack for you.
Think of me as a professional chaos creator with a purpose: massive workloads, thousands of pods, Kafka streams on fire, and me with Grafana dashboards asking "but can it go faster?"
When I'm not hunting latency ghosts, I'm exploring LangChain + LLMs and figuring out how AI fits into the performance engineering world.
My mantra: If you can't measure it, you can't scale it.
- 🔭 Currently taming scale at Red Hat — Performance and Scale team
- 🌱 Currently exploring LangChain, LLMs & AI-augmented testing
- 💬 Ask me about Python, Kafka, OpenShift, Performance Testing
- 📫 Reach me at chauhanraj3103@gmail.com
- ⚡ Fun fact: I find slow APIs personally offensive
Scale-tested daily: OpenShift • Kafka • Elasticsearch • CI/CD pipelines • Linux perf tooling
1. Build cluster 2. Flood it 3. Watch it cry
[ OpenShift ] → [ 10x load ] → [ Grafana 📈🔥 ]
|
4. Fix & tune ← 5. Repeat until ← ───┘
[ p99 ↓ ] [ "can't break it" ]
Most developers ship features. I ship confidence that features survive Monday morning.
| # | Confession |
|---|---|
| 1 | I've said "works on my machine" — then reproduced it with 500 nodes just to prove a point |
| 2 | My love language is a flat latency graph |
| 3 | I dream in Kafka consumer lag alerts |
↑ that snake has better uptime than most staging environments
💡 Working on something that needs to survive scale, chaos, or Kafka? My inbox is open.