Integration ownership
I take protocol integrations through the full lifecycle: onboarding, credentials, validation, synchronization, and the inevitable edge cases that appear in production.
OCPI · APIs · partner workflows
Arjun Rishi / Software Engineer
I build systems that connect the real world.
I’m a backend-focused engineer working at the intersection of software, charging infrastructure, and partner networks. I turn complex protocols into services people can rely on.
INTEGRATION / 001 PRODUCTION-MINDED
01 / EDGECharging hardwarecommands · telemetry · sessions
02 / COREBackend servicesstate · APIs · reliability
03 / NETWORKPartner ecosystemscredentials · roaming · data
DESIGN FOR THE BOUNDARIES
01 / About
Curious about the parts that have to work together.
I like the engineering problems that appear at the boundaries: between services, between organizations, and between software and physical devices.
My current work centers on EV charging interoperability. I build and operate backend integrations, trace production issues across systems, and think carefully about how data and state move from one side of a network to the other.
I also enjoy explaining difficult systems clearly, whether that means documenting an incident, discussing a design with teammates, or helping someone debug a problem they have not seen before.
02 / What I bring
Good engineering lives in the details.
My strongest work combines backend implementation, domain understanding, and day-two operational thinking.
Backend reliability
I work on multi-tenant services that need predictable behavior under real traffic, with attention to data models, PostgreSQL performance, observability, and failure recovery.
Java · Spring Boot · Node.js · AWS
Hardware-aware systems
Charging software has to reflect what devices actually do. I work with charger communication, remote commands, telemetry, and the authorization-to-session lifecycle.
OCPP · charging operations
Clear collaboration
I care about shared understanding: documenting decisions, explaining complex behavior, mentoring builders, and making technical knowledge useful to the team.
Debugging · documentation · mentoring
Domain knowledge
Deep in EV charging. Comfortable beyond it.
Protocols matter because they shape the driver experience, partner operations, and the reliability of every session.
01OCPI
Roaming & interoperability
OCPI credentials, locations, tariffs, tokens, sessions, and partner onboarding.
02OCPP
Charger communication
Remote operations, telemetry, and lifecycle events between chargers and management systems.
03Beckn
Energy exchange
Participant discovery, price negotiation, and settlement flows in interoperable energy systems.
03 / Engineering work
Problems I’ve helped solve.
Representative work, described without internal product or partner names.
Connecting charging networks
Different operators need to exchange trusted, consistent data before a driver can roam between networks. I own OCPI onboarding and integration flows, including credentials and synchronization of locations, tariffs, tokens, and sessions.
Scope: integrations with 5+ charge point operators and 15+ mobility service providers.
Starting a charge without an app
A charging session should not depend on installing an app first. I’ve helped design backend authentication, authorization, and transaction flows that let drivers begin a session at the charger.
Focus: less friction for drivers and a dependable service-side session flow.
Making energy exchange interoperable
I built foundational marketplace workflows for participant discovery, price negotiation, and transaction settlement using the Beckn protocol and India’s energy stack.
Focus: a practical path from protocol design to a working peer-to-peer flow.
Public builds
Things you can inspect.
Outside of production work, I build tools for problems I care about.
Swift / macOS
AI Usage Widgets
Native menu-bar apps that show AI tool usage, reset times, and pacing guidance. Built around local snapshots and a small, focused interface.
Web / personal software
Second Brain
A personal writing and task space that stores entries as Markdown in a separate private repository, with version history provided by Git.
04 / Background
A career still early, with real systems behind it.
Aug 2025 — now
Software Developer, SDE-1
Steam-A
Backend and protocol integration work across EV charging and partner networks.
Jan — Aug 2025
Graduate Developer Intern
Steam-A
Learned production engineering through hands-on delivery; recognized with an internship performance award.
2023 — 2024
Innovation Fellow
House of Metazord
Explored full-stack development and smart contracts, including a blockchain-based e-learning prototype.
2021 — 2025
B.E. Computer Science
KGiSL Institute of Technology
Graduated with a CGPA of 8.1.
05 / Toolkit
Tools I reach for.
Backend
Java 17+, Spring Boot, Node.js, TypeScript, Express, FastAPI
Data & infrastructure
PostgreSQL, MySQL, MongoDB, AWS, Docker, RabbitMQ
Frontend & quality
React, HTML, CSS, Jest, Playwright, GitHub Actions
Protocols
OCPI 2.2.1 / 2.3.0, OCPP 1.6 / 2.0.1 / 2.1, Beckn V2
06 / Writing & community
Learning sticks when I share it.
I’ve written beginner-friendly technical articles, led a student technology chapter, and mentored hackathon teams.
2023 / EssayThe Learning Algorithm
2023 / TutorialDiving Into Django: Your First Project
Beyond writing
Mentored roughly 10 teams at a 2026 hackathon and chaired the student chapter of the Indian Society for Technical Education during college.
07 / Contact
Let’s build something that holds up.
Interested in backend engineering, EV infrastructure, or a problem at the edge of multiple systems? I’d be glad to talk.