r. rithvik senthilkumar Let’s talk
About / Rithvik Senthilkumar An ongoing practice

A long habit
of making.

02 / An inner compass
Curiosity gives direction

The throughline

I turn unclear problems into systems that hold up.

I’ve been writing code for over a decade. What stuck is the habit. Understand the problem, design around real constraints, build the solution, then improve it from evidence.

years writing code
10+
builds, experiments, and prototypes
100+
tools, languages, frameworks, and systems
30+

01 / Pattern

A long habit of making ideas real.

I’ve built countless projects over the years. Most were never published or polished into portfolio pieces. Small tools, bots, scripts, projects, rewrites, prototypes, and experiments taught me how to turn unclear problems into something concrete.

Along the way

Different settings.
The same curiosity.

From founding SureDroid and Xeno Industries to engineering at GoDaddy and Capital One, building has been the constant.

Still learning

Georgia Tech MS Computer Science · AI
In progress

UT Dallas BS Software Engineering · 2024

  1. July 2026 — present

    Capital One

    Senior Associate Software Engineer

    Previously Associate Software Engineer, February 2025 — July 2026.

  2. May — August 2024

    GoDaddy

    Software Engineering Intern

  3. 2021 — 2024

    Xeno Industries

    Founder

  4. 2018 — 2021

    SureDroid

    Nonprofit founder

02 / Judgment

The work starts before the code.

I start by understanding the problem, then compare designs against constraints like scalability, complexity, maintainability, and user impact. The goal is to find an architecture that fits the problem instead of forcing the first idea that works.

03 / Execution

Useful systems beat theoretical designs.

I care about building systems that hold up in practice. That means modern architecture, testing, CI/CD, feedback loops, and the patience to iterate when the first version exposes what the problem really needs.

04 / Ownership

I take ownership of outcomes.

I do not think the work is finished because code exists. I take responsibility for the outcome: whether the system is clear, useful, maintainable, and improving after it reaches real people.