Deepak Nayak
Backend engineer, product builder, team lead
Most of my work is backend: integrations, sync paths, queues, retries, and the parts of a system that need to stay reliable. But I care just as much about whether the product is easy to use. If people cannot solve their problem cleanly, the backend work is not enough.
Based in Bengaluru, India
Most of it sits somewhere between product decisions, backend systems, and the operational details that start to matter once people depend on the product every day.
I like products that become part of the job instead of a thing people tolerate. The work is not just to ship features. It is to make the product useful enough, reliable enough, and clear enough that people keep leaning on it.
Most of the interesting problems for me are deep in the backend, but they always show up in the product eventually. Bad sync, slow jobs, unclear state, or brittle integrations always leak outward. I like fixing those at the root.
I tend to get pulled toward situations where the problem is still fuzzy, the boundaries are not clear yet, and several parts of the system are involved. That is usually where I do my best work.
Sometimes the right move is to go heads down on a hard problem. Sometimes it is to lead, set direction, make tradeoffs visible, and help the team move with more confidence. I like being useful in either mode.
I can work across the whole product when needed, go deep on a specific engineering problem, or lead a team through the work.
That usually means talking to customers, understanding what is actually painful, figuring out the system boundaries, building the backend and product flow, then staying close enough to learn what changed after release.
Some work needs broad ownership. Some work needs patience. I am comfortable staying with one difficult issue long enough to understand the failure modes, simplify the design, and make it reliable again.
I like leading teams in a hands-on way: reviewing designs, unblocking difficult decisions, helping engineers get sharper around ambiguous backend work, and stepping in directly when the problem needs it.
ClearFeed
Mar 2024 - Present
I lead backend engineering here now. The work stays close to the system: shaping product and integration flows, reviewing difficult designs, improving engineering habits, and helping the team turn unclear requirements into something we can trust in production.
ClearFeed
Aug 2021 - Mar 2024
I joined as the first engineer and built the backend from scratch. Ticketing on top of Slack and Teams, sync with tools like Zendesk, Jira, and Salesforce, event pipelines for analytics and SLAs, and early automation features that could classify requests, draft responses, create tickets, and trigger actions across other systems.
JaanSay
Aug 2020 - Jul 2021
Part of a two-person tech team building a hyperlocal platform from scratch with Flutter, Node.js, Nginx, and a tiny DigitalOcean budget. We handled product work, deployment, scaling, and customer onboarding ourselves, so every technical decision had to be simple and cheap enough to live with.
3D Usher
Dec 2020 - Feb 2021
Built a geometry-aware instant quoting system for 3D manufacturing instead of the usual bounding-box shortcuts. I had to learn enough about materials, manufacturing constraints, and pricing logic to make the Three.js interface and quoting flow produce numbers customers could actually trust.
Dreamsoft Innovations
Apr 2020 - Oct 2020
My first serious production work. I built the Flutter side of a kids' digital library app, handled responsive UI across devices, and wired Flutter into a Unity-based story engine so the app experience and backend stayed in sync.
Notes from backend work, integration problems, production issues, and things that only became clear after shipping.
Mar 31, 2026 | 7 min read
What helped while building a Teams integration for a real product, without pretending it is just one API and one happy path.
Jan 19, 2026 | 7 min read
The confusing part about shared channels in Teams is that your bot setup can be correct, reads can work, and regular message events can still fail unless the bot is explicitly mentioned.
May 05, 2025 | ClearFeed
A practical guide I wrote at ClearFeed on how engineering teams can test Slack apps without stepping on each other.
Contact
I am based in Bengaluru, India. I enjoy work where the problem is real, the system still needs structure, and the solution has to hold up in production.
Reach out