Cricinfo
A small Python interface over Cricbuzz for live scores, commentary, match summaries, and scorecards. Designed to return regular Python data that can move cleanly into scripts, notebooks, APIs, or dashboards.
Mumbai, India · open to backend roles
Backend engineer working across Python services, risk-heavy workflows, distributed systems, and the infrastructure that makes software dependable.

Selected work
A small, deliberate set of projects. Shipped software first; experiments labeled honestly.
A small Python interface over Cricbuzz for live scores, commentary, match summaries, and scorecards. Designed to return regular Python data that can move cleanly into scripts, notebooks, APIs, or dashboards.
A production-minded Rust service foundation with structured logs, distributed traces, Prometheus metrics, health checks, safe errors, and a local Grafana stack.
An architecture study for image processing: Rust gateways and workers, typed gRPC, Temporal workflows, Redis deduplication, Postgres metadata, and object storage.
How I think about systems
Good backend work is often invisible. It is the idempotent retry, the trace that explains a slow request, the validation that prevents a bad state, and the clear boundary that lets a team change one part without fearing five others.
My strongest work lives where product rules meet reliability: lending workflows, decisioning, integrations, reporting, and the infrastructure around them.
Explicit rules, traceable decisions, and APIs that behave safely under retries.
Logs, metrics, traces, and useful failure states make systems operable.
Clear interfaces and documentation are force multipliers for small teams.
A little context
I’m Pranith, a backend engineer currently working as an SDE II at Apollo Finvest. I work mostly in Python and Django, building business-critical lending systems where edge cases matter and operational clarity is not optional.
Outside work, I use small projects to go deeper: Rust services, observability, gRPC, distributed workflows, and data interfaces. The thread through all of it is the same — understand the system, make the boundary clear, and leave it easier to operate than I found it.
Start a conversation ↗Backend systems · underwriting · KYC / fraud controls · async workflows
FastAPI · SQLAlchemy · payroll systems · immutable audit logs
Working toolkit