Pavan Kumar did not set out to become a software engineer. He graduated with a degree in electrical engineering, and by conventional logic, that should have pointed him somewhere else entirely. But software had a pull that his degree did not account for, and rather than follow the expected path, he followed his curiosity.

That decision led him to LTIMindtree, where he spent his first years working on .NET and Azure-based applications. The technical foundation was valuable, but what shaped him even more was what happened early in his time there. After about three months of onboarding, he joined a large project alongside engineers with considerably more experience. Instead of trying to prove himself, he paid attention. He watched how they approached problems, reviewed code, and thought through design decisions before writing a single line. That experience quietly became one of the most formative chapters of his career.

When Pavan joined WellSky as a software engineer, the work felt different. Building healthcare software meant the applications he developed supported providers caring for real patients, giving his work a sense of purpose beyond the technology itself. Today, he works across the full application stack, maintaining and extending business-critical applications using modern web technologies, cloud services, and enterprise software. Over time, he has taken on greater ownership, worked through production issues alongside teammates, collaborated across teams, and begun exploring where AI tooling can support the development workflow.

Two recognitions have meant the most to him so far: the Scout of WellSky Award and the High Impact Team Award. He also presented a demo at a WellSky Hackathon, an experience that required a different kind of preparation than the work that typically comes across his desk. He talks about those moments not as endpoints, but as motivation to keep learning and improving.

What Pavan describes as his unique contribution is something that doesn't always appear in a job description. He wants to understand the business problem before tackling the technical one. Requirements first, then code. That mindset has made him a more effective collaborator and a more practical problem solver. It's also the same discipline that has helped him stay consistent with fitness while balancing a full workload. Patience, he'll tell you, is something you can practice.

Outside of work, Pavan is usually on a cricket field, at the gym, reading, or planning his next long-weekend adventure. Mythology and adventure stories take up most of the space on his bookshelf, while trekking is how he spends his longer vacations. And if there's a cricket match on, he's either watching it, or at the very least, talking about it.

‍