About
From first line of code to leading engineering teams — and everything I learned in between.
Technical Lead at iLink Digital. 10+ years across full-stack engineering, performance work, and team leadership. Writing about what I learn in public.
About
Technical Lead at iLink Digital. 10+ years across full-stack engineering, performance work, and team leadership. Writing about what I learn in public.
I started my engineering career in 2016 at ContinuousExcellence, where I quickly moved from writing code to leading a team — driven not by a title change, but by a natural instinct to unblock people, improve processes, and take ownership beyond my role.
That pattern became the foundation of my career.
At GoFloaters, I joined as one of the earliest engineers and helped build the platform from the ground up. Being part of a founding team taught me what full ownership really means — not just writing features, but caring about the product as if it were my own.
At FirstCry, I designed user journey tracking systems and marketing automation logic that personalized campaigns for millions of users. The work connected engineering directly to business impact, and it changed how I think about what "good software" really means — it's not just clean code, it's measurable outcomes.
At Hinge Health, I tackled a performance problem the team had lived with for months. By optimizing GraphQL queries and restructuring API data flows, I reduced P95 latency by 60.5% (from 3.8s to 1.5s). That project reinforced something I carry with me: the highest-impact work is often the work nobody else wants to dig into.
Today, I'm a Technical Lead at iLink Digital Solutions, leading a team of 9+ engineers delivering features for enterprise clients in the oil & gas industry. I own the architecture, the quality bar, and the delivery rhythm. But the part of leadership I find most meaningful is investing in engineers — helping them develop stronger technical instincts, take on bigger challenges, and step into ownership of their work.
I don't claim to have all the answers. I'm still learning — about scaling teams, about staying technical in a leadership role, about where AI genuinely helps versus where it just adds complexity. What I do have is ten years of building real things with real teams, a deep respect for the craft, and the drive to keep getting better.
I'm writing publicly now because I believe the most useful career insights come from people who are still doing the work — not from people who stopped building years ago and started advising. This blog is my way of sharing what I learn, as I learn it.
Building the systems, standards, and team habits that make delivery consistent and predictable for a major enterprise client, even when requirements shift.
Moving beyond surface-level AI adoption to understanding where these tools create genuine engineering leverage. I share what I learn — both what works and what doesn't.
After a decade of doing this work privately, I'm documenting my lessons, decisions, and honest reflections where they can help other engineers and aspiring leaders.
Dan Fink
Product Analyst · Product Development Expert
“I hired Darshana as an independent contractor in 2018. Little did I know how lucky it was to come across such an extraordinary professional. I was equally impressed with her emotional intelligence and how she leverages it to benefit users — particularly rare for developers. Darshana earns my highest recommendation.”
Shyam Sundar Nagarajan
Founder · GoFloaters
“Darshana was one of the first few members of the GoFloaters tech team and was instrumental in laying the foundational elements of the platform. A highly talented and committed full stack developer who came up with a lot of interesting suggestions and features.”
Harshavardhan Jadhav
Software Engineer · Facile (ex-FirstCry.com)
“Darshana's expertise in full stack development and project management was instrumental in our success. Her ability to seamlessly integrate technical knowledge with effective leadership consistently impressed me. She managed projects with remarkable skill and dedication.”
I'm open to conversations about engineering leadership, team building, or what it's actually like to go from IC to lead. If something I wrote was useful, I'd genuinely like to hear about it.