Wore every hat : QA, Product & Operations

Bangalore Urban

Bengaluru







Bachelor of Engineering, Electrical and Electronics Engineering
Rungta College of Engineering & Technology Kohka-Kurud Bhilai

Higher Secondary, Physics & Mathematics
kendriya vidyalaya
Join PRAMISH and 10k+ other professionals on
Tal is the app where bosses meet engineers & builders directly, without middlemen
Download Tal BossWore every hat : QA, Product & Operations
I spent two years at LocalWell with a QA title but honestly the job description wrote itself differently every week. Some weeks I was deep in Postman validating APIs, other weeks I was sitting with the Sales team trying to understand why customers were leaving, and somehow that turned into me owning the retention strategy. Nobody handed me that it just needed to be done and I was the one asking the right questions. The role taught me that the most important problems in an early-stage startup rarely live inside a single function. Churn isn't a customer success problem. Slow bug resolution isn't just an engineering problem. Bad onboarding isn't just a product problem. They're all connected, and if you're willing to sit at the intersection long enough, you start seeing things others miss. I'm not going to pretend everything I did was perfectly planned. A lot of it was figuring things out as I went, talking to the right people, and building just enough structure to make things less chaotic than they were before. But the outcomes were real and more importantly, the way I think about problems changed completely.
Bengaluru
antigravity
claude code
claude
cursor
ollama
OpenRouter
QAE at Slikk, Apr 2026 - Present · 5 mos, Bangalore Urban, Embedded across the full fulfilment stack from consumer app through warehouse ops and last-mile delivery acting as the quality and ops bridge between product, engineering, and ground teams. 1. Owned the end-to-end order fulfilment and return flows, validating every state transition across Picker App, Rider App, and backend from order placement through refund trigger 2. Led QR-based package validation across the logistics chain, replacing manual handoff checks and closing delivery and packaging leakage gaps at the ops layer 3. Collaborated with warehouse teams to validate Picker App releases against operational requirements before every go-live 4. Partnered with the Rider App team on a full UI overhaul driven by direct rider feedback translating last-mile friction into product changes 5. Building an AI-powered search relevance pipeline across a 180K+ SKU catalogue auto-generating queries, validating product tags via vision models, and scoring relevance at scale
QA Engineer at LocalWell®, Apr 2024 - Apr 2026 · 2 yrs 1 mo, Bengaluru, Honestly, the title said QA Engineer but the role was something else entirely. Yes, I tested features but most of my time went into figuring out why things were breaking at a process level, not just a product level. I ended up owning retention workflows, redesigning onboarding, managing feedback loops between Sales, Product, and Engineering, and occasionally just building things from scratch because nobody else was going to. It was early-stage startup energy you either picked things up or they didn't get done. 1. Bugs were taking 10 days to close on average mostly because nobody really owned the process. Set up a proper triage workflow, wrote test cases to reproduce issues cleanly so devs weren't guessing, and got resolution time down to 2 days. 2. We were losing 120 businesses every single month and nobody had really sat down to figure out why so I dug into the patterns, segmented the users, and built workflows to catch people before they left. Got it down to 30–35 a month. 3. The platform was running slow and nobody quite knew why. Turned out the reporting workflows were doing way more work than they needed to, and APIs were being called unnecessarily. Fixed both, cut compute load by 30%. 4. Also designed how orders get allocated on their pharmacy marketplace figuring out which pharmacy gets which order, compliance checks, how close they are to the customer, scoring them on fulfillment quality, all of that. Wrote test scenarios to validate the logic end to end before it went live. 5. At some point I floated a credit-based model for report consumption because the current setup was being abused and it was killing infrastructure costs. Tried to connect the monetization angle with the ops problem
Bachelor of Engineering, Electrical and Electronics Engineering, Rungta College of Engineering & Technology Kohka-Kurud Bhilai
Higher Secondary, Physics & Mathematics, kendriya vidyalaya
github: https://github.com/PramishKumarSharma