Software Engineer at Physics Wallah
Software Engineer at Physics Wallah. Focused on backend architecture, system design, and AI systems.
Backend
Architecture-first engineering
Scale
Systems that hold under load
AI
Product thinking with AI systems
About
I’m a backend engineer focused on building scalable systems and designing reliable software architectures. Currently working as a Software Engineer at Physics Wallah, building backend systems for real-world scale. I started with competitive programming, which built strong problem-solving skills, and transitioned into backend engineering and system design. I’m currently exploring distributed systems, real-time architectures, and AI-powered applications.
I prefer systems that communicate their intent clearly: fewer moving parts, better boundaries, and predictable behavior under load.
My work sits at the intersection of APIs, distributed workflows, and product-aware engineering. I care about the path from request to response as much as the architecture that supports it.
Backend
Architecture-first engineering
Scale
Systems that hold under load
AI
Product thinking with AI systems
Work
A vertical timeline that focuses on how I think about production software rather than just listing tasks.
Systems
The diagram stays sticky while the narrative unfolds on the left. Each step highlights a distinct layer of the request lifecycle, from user input to scaling behavior.
Architecture diagram
User
01API Gateway
02Queue + Workers
03Database
04Response Flow
05Scale Out
06Projects
Each scroll segment surfaces the problem, the response, the system shape, and the outcome. These are temporary placeholders you can edit later from the projectSegments array.
Project segment
Problem
Large-scale search latency made retrieval feel slow and inconsistent.
Solution
Optimized indexing and query shaping to keep retrieval focused and fast.
Architecture highlight
API -> Search Layer -> Database
Impact
Reduced latency and improved the usability of history-heavy workflows.
Active project
FocusedSignal
Project segment
Problem
Incoming work needed to be processed quickly without blocking the user path.
Solution
Split the flow into queue-driven workers with clear back-pressure.
Architecture highlight
API -> Queue -> Worker Pool -> Persistent Store
Impact
Kept the request path lightweight while scaling background execution.
Active project
FocusedSignal
Project segment
Problem
AI features needed a stable integration model, not a fragile demo layer.
Solution
Added guardrails, deterministic fallbacks, and response shaping.
Architecture highlight
Client -> Orchestrator -> Model + Cache + Policy Layer
Impact
Delivered useful AI capabilities with production discipline.
Active project
FocusedSignal
Project segment
Problem
Notification spikes caused retries, duplicate sends, and delayed delivery.
Solution
Introduced idempotent workers and batched dispatch with retry policies.
Architecture highlight
API -> Queue -> Worker -> Provider Adapters -> Logs
Impact
Improved delivery consistency and reduced duplicate notification events.
Active project
FocusedSignal
Contact
If you’re working on interesting systems or need help building scalable backend solutions, feel free to reach out.