the anti job boardactive 4mo ago
Akshat Kumar
builder
Looking for
Preferences
Open to
Anywhere
The story
What Akshat is looking for
I want to work on products where I can own the experience end to end, not just the UI layer. I enjoy building systems where frontend, backend, and data flow all connect to shape how a user actually interacts with the product. I like working on interaction heavy features like chat systems, state driven interfaces, and real time or near real time experiences where small engineering decisions directly impact usability. A small team setup works best for me. I want to move fast, talk to users or at least understand their problems deeply, and ship things that actually get used. I do not want to just implement tickets that are already fully defined. I want to be involved in thinking through what should be built and why.
Why Akshat is exploring
I have learned a lot in my current role, especially on the frontend side, but I have started to feel like I am operating within a fixed boundary. Lately I have been naturally moving towards backend and system level thinking. I have been exploring APIs, pagination strategies, data modeling, caching patterns, and how systems behave under scale. That curiosity is not fully reflected in my current day to day work. I am looking for an environment where I can grow into a more complete engineer, someone who can think across the full stack and not just one layer. Right now I feel like I can take on more ownership and more complex problems than I am currently exposed to.
What won't fit on a resume
I tend to go deep on problems that interest me and I do not limit that to assigned work. I have spent time building chat style interfaces and thinking through details like message ordering, state management, interaction flows, and how to make the experience feel natural and responsive. That led me to think about how the backend should support these patterns, how data should be fetched, and how consistency is maintained. I have also been exploring AI related ideas, especially around memory and context in applications. I have looked into how a system could retain and use context over time rather than just respond statelessly. Apart from that I often pick apart systems just to understand them better. Whether it is how pagination works at scale, how caching like Redis helps with performance, or how APIs are designed for long term maintainability, I enjoy going down those rabbit holes. In general I like building things that connect product thinking with system design, not just writing isolated pieces of code.
Work & Projects
The Anti Job Board
Skip the application black hole. Get warm intros to founders hiring now.
Create your profile