Abhishek Arun
I build products end to end and ship them — three live, a fourth in pilot, all solo. Now an Associate Product Manager at Internshala, learning how those calls get made inside a team.
Selected work
Four products, built solo.
Approach
How the work runs.
Four steps, in order. Skip the first and you build the wrong thing beautifully — which is the most expensive mistake there is.
-
01
Discover
Talk to the people who have the problem. Find the opportunity worth pursuing before writing anything down.
-
02
Define
Frame the problem, set priorities, and decide what the solution is — and, just as explicitly, what it isn't.
-
03
Execute
Turn intent into something engineering and design can build, then build alongside them.
-
04
Iterate
Learn from outcomes, feedback and data. Find out what you got wrong, then go fix it.
Path
Where I've been.
Associate Product Manager
It's a recent move, so there's no shipped work to point to there yet. Right now I'm learning the product, the users, and how the team works.
Product Manager Intern · TruckHai
Worked across product discovery, scoping and shipping. Left on strong terms with an endorsement from the people I worked alongside.
Product Management Intern · WebMobi
My first product role — requirements, specs, and working alongside engineering to get things out the door.
Building independently · four products
SpendFlow, Afterward, Focus Docs and Tesseract — each one a bet on what to build and what to cut. The page you're reading is one of them.
B.Tech, Computer Science · SRM IST
Spent the degree building real products rather than waiting for permission. The engineering background is why I can write a spec an engineer doesn't have to translate.
“Thanks Abhishek for the good work you did — I'd recommend you can be a good product manager.”
“It was great working with you, Abhishek. All the best for your future endeavours.”
Craft · five layers
What I can actually do.
Open a layer, then tap anything inside it. Each item says what it is, why it matters and where I've used it — nothing listed that I haven't.
The product thinking lab
Nine products I didn't build, taken apart.
A teardown is cheap practice for expensive judgment. Each one ends on the tradeoff I'd have accepted and the pattern underneath it.
Working notes
What I'm doing and thinking.
Written by hand, not generated. Includes the decisions I'd defend and the things I haven't done yet.
Credentials
Certificates, for completeness.
Useful, not load-bearing. The four products are the real evidence.
Contact
Let's buildsomething.
Open to roles and collaborations. I usually reply within 24–48 hours.