Pujitha Sai Tulasi Muddhu

Software Engineer, AI/ML | Backend Systems + Test Automation at fintech scale | Ex-Groww, Bright Money

Boston, Massachusetts, United States of America

Leave a testimonial

Validated traits

Proactive
Adaptable
Thorough
Creative
Collaborative

Artifacts

Groww, India · SDET - I
Built an Internal Developer Tool That Accelerated PR Reviews by 2+ Hours Daily
At Groww, I identified a bottleneck in the pull request review process: reviewers and engineering managers had to manually navigate SonarQube to verify code quality metrics before approving changes. This slowed reviews and reduced visibility into the overall health of active projects. To streamline this workflow, I designed and developed a Slack bot that integrated Slack APIs and Slack Block Kit with SonarQube to automatically fetch and present key quality metrics - including code smells, bugs, vulnerabilities, security hotspots, and test coverage - for every active project. I also implemented logic to compare metrics across pull request builds, highlighting regressions and improvements before code reached production. To improve ownership and collaboration, the bot automatically routed project-specific reports to the appropriate engineering teams through dedicated Slack channels. By embedding actionable code quality insights directly into developers' existing workflow, the solution eliminated the need for manual SonarQube checks, reduced pull request review turnaround time by up to two hours, and helped engineering teams identify quality regressions earlier. The project improved development efficiency while reinforcing consistent code quality standards across multiple teams.
Validated by 1
SK
Stealth Startup · Founding Engineer
Drove Pivot to Vision-Language Models for Home-Inventory App
As Founding Engineer on a 3-person team at VaultlyAI, I owned the object-detection pipeline end to end for a home-inventory insurance app that lets users scan their belongings to auto-generate a structured, claim-ready inventory. Because accurate detection was the foundation of the entire product - a miscounted or misidentified item directly undermines an insurance claim - I was responsible not just for building the pipeline, but for validating its accuracy before anything reached production, drawing on my SDET background. For the MVP, I started with a fine-tuned YOLO model. Since public datasets like COCO, Objects365, Open Images, and LVIS poorly covered our long-tail household item classes, I built training data manually: gathering 200–300 images per class, using SAM (Segment Anything) to generate masks, and annotating/converting everything into YOLO format to produce a 10K+ image training set - cutting manual annotation effort by roughly 60% versus labeling from scratch. As I scaled this approach, three critical issues emerged: it was too slow to expand across new classes, accuracy fell short of the bar, and worst of all it produced duplicate detections that corrupted the generated inventory, since insurance claims can't list the same item twice. This led me to drive a pivot to Vision-Language Models. Rather than choosing a model on instinct, I built a benchmarking dashboard to evaluate several Gemini VLMs side by side on detection count, precision, latency, and cost, then integrated the winning model into the Python backend and connected it end-to-end with the React Native app. The result solved both problems at once: the chosen VLM outperformed the fine-tuned YOLO baseline on detection accuracy while running at essentially free cost at our volume - an unusual win on two axes that typically trade off against each other. Most critically, the duplicate-detection problem that had made the manual pipeline unusable was eliminated entirely. This pipeline was validated internally when the CEO and CTO reviewed the benchmarking results and confirmed the duplicate-detection issue was resolved, greenlighting it for production. That decision made the feature launch-ready, and the app shipped on the Apple App Store and Google Play. The app has been live for about a month, and while broader user feedback is still early-stage (I transitioned off the startup shortly after launch due to visa timing), the internal validation from the founding team confirmed the pivot had solved the core reliability problem that stood between the product and launch.
Validated by 2
PVEG
View all 2

Testimonials

P
Peter Zotto
Founder at Trove
Jul 31, 2026
S
Sahaja Kovuri
Peer
Jul 28, 2026
on “Built an Internal Developer Tool That Accelerated PR Reviews by 2+ Hours Daily”
View all 4

Work history

Stealth Startup

Groww, India

Bright Money

YAY! - Celebrating Education

The Sparks Foundation

Technocolabs Softwares Inc.

Stealth Startup

NOV 2025 - JUN 2026 · 8 months

Founding Engineer

NOV 2025 - JUN 2026 · 8 months

Drove Pivot to Vision-Language Models for Home-Inventory App

As Founding Engineer on a 3-person team at VaultlyAI, I owned the object-detection pipeline end to end for a home-inventory insurance app that lets users scan their belongings to auto-generate a structured, claim-ready inventory. Because accurate detection was the foundation of the entire product - a miscounted or misidentified item directly undermines an insurance claim - I was responsible not just for building the pipeline, but for validating its accuracy before anything reached production, drawing on my SDET background. For the MVP, I started with a fine-tuned YOLO model. Since public datasets like COCO, Objects365, Open Images, and LVIS poorly covered our long-tail household item classes, I built training data manually: gathering 200–300 images per class, using SAM (Segment Anything) to generate masks, and annotating/converting everything into YOLO format to produce a 10K+ image training set - cutting manual annotation effort by roughly 60% versus labeling from scratch. As I scaled this approach, three critical issues emerged: it was too slow to expand across new classes, accuracy fell short of the bar, and worst of all it produced duplicate detections that corrupted the generated inventory, since insurance claims can't list the same item twice. This led me to drive a pivot to Vision-Language Models. Rather than choosing a model on instinct, I built a benchmarking dashboard to evaluate several Gemini VLMs side by side on detection count, precision, latency, and cost, then integrated the winning model into the Python backend and connected it end-to-end with the React Native app. The result solved both problems at once: the chosen VLM outperformed the fine-tuned YOLO baseline on detection accuracy while running at essentially free cost at our volume - an unusual win on two axes that typically trade off against each other. Most critically, the duplicate-detection problem that had made the manual pipeline unusable was eliminated entirely. This pipeline was validated internally when the CEO and CTO reviewed the benchmarking results and confirmed the duplicate-detection issue was resolved, greenlighting it for production. That decision made the feature launch-ready, and the app shipped on the Apple App Store and Google Play. The app has been live for about a month, and while broader user feedback is still early-stage (I transitioned off the startup shortly after launch due to visa timing), the internal validation from the founding team confirmed the pivot had solved the core reliability problem that stood between the product and launch.

Validated by 2

PVEG

Groww, India

AUG 2022 - AUG 2023 · 1.1 years

SDET - I

AUG 2022 - AUG 2023 · 1.1 years

Built an Internal Developer Tool That Accelerated PR Reviews by 2+ Hours Daily

At Groww, I identified a bottleneck in the pull request review process: reviewers and engineering managers had to manually navigate SonarQube to verify code quality metrics before approving changes. This slowed reviews and reduced visibility into the overall health of active projects. To streamline this workflow, I designed and developed a Slack bot that integrated Slack APIs and Slack Block Kit with SonarQube to automatically fetch and present key quality metrics - including code smells, bugs, vulnerabilities, security hotspots, and test coverage - for every active project. I also implemented logic to compare metrics across pull request builds, highlighting regressions and improvements before code reached production. To improve ownership and collaboration, the bot automatically routed project-specific reports to the appropriate engineering teams through dedicated Slack channels. By embedding actionable code quality insights directly into developers' existing workflow, the solution eliminated the need for manual SonarQube checks, reduced pull request review turnaround time by up to two hours, and helped engineering teams identify quality regressions earlier. The project improved development efficiency while reinforcing consistent code quality standards across multiple teams.

Validated by 1