On the latest episode of Tech Teams Today, I had an awesome chat with Sakshi Garg, who’s running engineering at Hydrolix.io. We covered AI, coding’s future, remote work, and what it’s like going from massive companies to scrappy startups. If you’re into tech, leadership, or just figuring out what’s next in your career, this one’s for you.
Should You Still Learn to Code in the Age of AI?
Here’s a big question that keeps popping up: with all the buzz around AI, is learning to code still worth it? She had an interesting take.
“In 10 or 20 years, coding might not be something people need to do anymore. But understanding how things work behind the scenes? That’s still going to matter.”
Sakshi compared coding to learning math. You might not solve equations every day, but the skills it gives you—problem-solving, logic, understanding systems—stick with you and help in all sorts of ways. Her advice? Learn the basics. Even if we’re in a world where AI’s writing all the code, the fundamentals will make you better at whatever comes next.
From Big Tech to Startups: Sakshi’s Career Playbook
Sakshi’s journey started at Adobe as an API developer, moved on to SignalFX (a startup that got scooped up by Splunk), and now she’s leading engineering at Oregon-based data management startup Hydrolix.io.
Her big career shift? Deciding between an MBA or jumping into a startup. She picked the startup route—and doesn’t regret it.
“I wanted to learn how the business side worked, not just the tech. A startup was the best way to get that experience.”
Now at Hydrolix, Sakshi’s building processes from scratch and tackling new challenges every day. It’s a step up from managing well-oiled machines at bigger tech companies and she’s loving it.
What Makes a Great Manager?
Sakshi didn’t set out to be a manager. It kind of happened naturally as she got deeper into projects and started leading teams. But making that leap from coding to leading wasn’t automatic—she had to work at it.
Sakshi’s secret? Never stop learning and improving.
“I read books, took courses, and talked to mentors. Every time I hit a snag—whether it was giving feedback or handling a team issue—I’d ask for advice, learn from it, and do better next time.”
For anyone stepping into leadership for the first time, her advice tracks: don’t try to figure it all out on your own. There’s no shame in leaning on mentors or frameworks.
The Remote Work Experiment: Lessons Learned
Hydrolix runs a fully remote engineering org, with most of the engineering team spread across the Americas. Sakshi’s a big fan of the flexibility it offers, but she’s also super aware of the challenges.
Her top tips for making remote work, well… work?
- Be crystal clear on goals. Everyone needs to know what’s expected and what success looks like.
- Overcommunicate. Regular check-ins and updates are a must.
- Don’t skip the face-to-face. Even in a remote setup, you need some in-person time. Hydrolix does annual off-sites where the team hangs out, plays games, and actually gets to know each other.
Final Thoughts
What stuck with me most from this chat? Sakshi’s perspective on how things are always changing—whether it’s the skills we need, the way we work, or how we lead. But instead of freaking out about it, she leans into learning and adapting.
If you’re curious about coding’s future, thinking about jumping to a startup, or just want to hear how a leader like Sakshi navigates this stuff, go check out the episode.
What do you think—should people still learn to code?
.webp){kind=small}
.png)
