Akhilesh's Profound AI Rep
Akhilesh designs complex operational workflows, builds with AI tools, and spots where interaction design works against the product.

Akhilesh Joglekar
Edges
Akhilesh designs enterprise tools that consolidate fragmented operational processes into coherent, usable systems. He works on the parts of a product that run the business quietly: supplier workflows, procurement communication, returns processes, and sourcing dashboards. At Walmart, he redesigned the Collab tool from a code management system into a procurement orchestration layer, and led the end-to-end redesign of Makro's Returns and Refunds journey, a process driving tens of thousands of monthly contact center calls. Both projects required mapping complex multi-stakeholder ecosystems before a single screen was designed. His approach is to understand the full operational picture first, then build something generic enough to adapt across workflows while specific enough to be immediately useful.
Spotted in 2 Stories
Akhilesh uses AI tools as a building medium, not just a productivity aid. He reaches for them when a problem is interesting and the path is unclear, and he ships working outputs rather than stopping at the concept stage. At Walmart, he used internal AI agents and MCP integrations to build a design deviation detection tool in a single day, unprompted, after a colleague asked if it was possible. Outside of work, he is designing a memory mapping layer for AI conversations, using Claude to close the gap between what he can design and what he needs to understand technically to build it. The pattern is consistent: he picks up a new AI capability, applies it to a real problem he has encountered, and builds until something works.
Spotted in 1 Story
Akhilesh reads products for the places where the interaction design works against the business model or the user's intent. He does this unprompted, as a user, before anyone has asked him to. When he used Centa, a job application platform, he identified that the swipe interaction was conditioning users to burn through paid credits without intention, that color coding was creating false signals borrowed from traffic lights and OS conventions, and that failed application states gave users no actionable feedback. He sent the analysis to the founder unsolicited. This is the same instinct that drove the Collab orchestration layer: seeing that a tool designed for one purpose was actually the right skeleton for a much larger workflow.
Spotted in 1 Story