The Tech Trek

In this episode, Amir sits down with Brent Keator, an expert advisor at Primary Venture Partners, to unpack one of the most debated engineering challenges: tech debt versus reengineering. They explore how to define tech debt, when to refactor versus rebuild, the ROI of revisiting old code, and how AI is (and isn't) changing the equation. This is a must-listen for engineering leaders navigating complex technical decisions in fast-moving environments.🔑 Key Takeaways:Tech debt isn't always bad—just misunderstood. Brent reframes it as part of the software evolution, often misjudged in hindsight with unrealistic expectations.Refactoring isn't an all-or-nothing decision. Brent recommends carving out 30–40% of engineering time for tech debt if possible, and viewing it as iterative maintenance tied to business value.Reengineering has a cost—evaluate wisely. Use the “better, faster, cheaper” test before replacing tools or platforms, and always account for hidden transition costs.AI can help but won’t eliminate tech debt. While AI improves productivity, Brent argues it doesn’t change the underlying truth: software is disposable, and architecture still needs discipline.⏱️ Timestamped Highlights:00:00 – Intro to Brent Keator and the episode focus: tech debt vs reengineering01:01 – Defining tech debt across code, products, and organizational habits02:53 – When reengineering tools goes too far or solves the wrong problem04:35 – The stigma of tech debt and how to rethink it08:55 – The cost of revisiting old code and the ROI on fixing the past11:12 – Why tech debt in engineering is fundamentally different than other domains12:44 – When to rebuild, how to evaluate tool replacements, and the abstraction advantage16:23 – Vetting open-source solutions: cost, support, and security risks18:36 – The emerging role of AI in engineering and why trust and testing still matter23:20 – Will AI help solve tech debt? Brent’s take on the future of disposable code24:46 – How to connect with Brent and final thoughts💬 Quote of the Episode:“What we write today is going to be gone tomorrow. Whether AI helps or not, we need to get comfortable with that.” – Brent Keator

In this episode, Amir Bormand sits down with Andy White, CEO of ClosingLock, to talk through his journey from PhD engineer to startup founder. Andy shares the aha moment that launched ClosingLock, a cybersecurity-focused platform protecting real estate transactions, and offers a transparent look at the early struggles of building trust in a skeptical industry. From pitching title companies with Chick-fil-A to learning an entirely new domain from scratch, this is a story about execution, humility, and listening harder than you pitch.📌 Key Takeaways:Execution > Ideas: Success came not from having a unique idea, but from executing better than competitors who had millions in funding.Talk It Out: Andy credits customer conversations—and even explaining problems to a rubber duck—with clarifying and improving his product thinking.In-Person Matters: Showing up with lunch and listening in-person proved essential in building trust with skeptical title companies.Start Simple, Iterate Fast: ClosingLock launched with just one feature: securely sharing wiring instructions. Growth came by solving one problem at a time, then listening for the next one.⏱️ Timestamped Highlights:[02:10] – Why a PhD wasn’t all that helpful in building a startup.[04:46] – Andy’s first “startup”—selling mazes in 2nd grade.[07:20] – The lightbulb moment: real estate wire fraud almost hits home.[11:15] – It’s not the idea—it’s the execution that matters.[16:46] – The “rubber duck method” for solving complex problems.[19:27] – Selling to skeptics: convincing title companies to try something new.[21:17] – Why email, fax, and phone still dominate real estate—and why that’s a problem.[25:49] – Would Andy build the same way post-pandemic? (Yes.)[28:03] – Avoiding the trap of planning too far ahead.💬 Quote:"Ideas are cheap. Execution is everything. Everyone saw the problem—very few stuck around to solve it better."

In this episode of The Tech Trek, Amir Bormand talks with Jason Wells, Head of Engineering at BrowserBase, about building a high-performance culture rooted in trust, emotional intelligence, and psychological safety. Jason shares how his unconventional path—including a six-year break from tech—helped shape a management philosophy that puts human connection at the center of engineering leadership. From dismantling blame culture to fostering self-compassion and authentic feedback loops, Jason offers a powerful framework for anyone looking to lead modern tech teams more intentionally.💬 Quote:“The best engineering is done by people who love their jobs. If you want the best output, you need a culture that makes people feel safe, trusted, and empowered.” — Jason Wells🔑 Key Takeaways:Trust is the foundation: Jason outlines how “boldly daring to trust” creates psychological safety—key to collaboration, innovation, and long-term performance.Blameless culture matters: Mistakes should be opportunities for learning, not shame. This leads to more ownership and less deflection in engineering teams.Emotional intelligence is a multiplier: Jason shares how his six-year break from tech helped him level up his emotional toolkit—skills he now actively brings into management.Every engineer is unique: One-size-fits-all management doesn’t work. Jason emphasizes individualized leadership rooted in curiosity, vulnerability, and compassion.🕒 Timestamped Highlights:00:00 – Intro & Jason’s background02:43 – What makes a great engineering culture04:40 – Why trust and psychological safety are non-negotiable06:59 – How BrowserBase screens for cultural alignment10:46 – Building an ideal environment from scratch12:27 – Jason’s early start: Atari, Oracle, and startups17:00 – Transition into management and leadership philosophy20:00 – Leaving tech for six years: self-actualization and purpose24:00 – Learning emotional intelligence and conflict resolution28:19 – Creating safe space for engineers with high expectations31:38 – Preventing burnout while maintaining performance33:38 – Leadership means knowing your people

In this episode, Amir Bormand sits down with Kieran Furlong, CEO and co-founder of Realta Fusion, to explore the unique path of a deep tech startup spun out of a university lab. They discuss building a fusion energy company, navigating complex stakeholder relationships with universities and government agencies, and keeping long-term mission-driven teams aligned. From licensing technology to managing a decade-long development cycle, this conversation reveals how Realta Fusion is working to change the world’s energy future.🔑 Key Takeaways:Deep tech startups require a different VC playbook: Realta Fusion operates on a decade-long roadmap that demands alignment with investors willing to play the long game.University spinouts bring both opportunity and friction: Leveraging academic research can be powerful but navigating bureaucracy and IP licensing adds layers of complexity.Mission-driven leadership is essential: With long timelines and uncertain outcomes, Kieran keeps his team focused through a relentless reminder of their shared purpose—commercial fusion energy.Energy abundance as a global equalizer: Fusion isn’t just a tech challenge—it’s a moral imperative to bring energy equity to the planet’s future 10 billion people.🕒 Timestamped Highlights:00:25 – Intro to Kieran Furlong and Realta Fusion's mission01:35 – Why Realta is a venture capital outlier: long timelines and deep capital03:46 – Spinning out of the University of Wisconsin and working with federal energy programs05:55 – Startup vs university culture clashes and how to navigate them08:07 – The race to meet fusion milestones by 203511:53 – Diplomacy in energy: balancing federal, academic, and private sector dynamics14:53 – The global case for fusion: climate, equity, and energy abundance16:05 – How to lead scientists toward a commercial goal without losing curiosity18:29 – Licensing tech the right way: aligning incentives for long-term success21:00 – Where to follow Realta Fusion and get involved💬 Quote:“You still want the creativity and curiosity of scientists—but you need to keep one eye on the destination: commercial fusion energy.” – Kieran Furlong

In this episode of The Tech Trek, Amir sits down with Clark Downum, CTO at Redox, to unpack the deeper dynamics between engineering, product, and business stakeholders. From tech debt and project delays to culture, communication gaps, and delivery trade-offs—this conversation is a candid exploration of how technical teams can drive impact without getting stuck in process perfection.Whether you're a tech leader or aspiring one, this episode offers a fresh lens on ownership, expectation-setting, and delivering what really matters.🔑 Key Takeaways:The cost of tuning out business context: Engineers often rush to solution-mode too early—Clark stresses the need for active listening before architecting.Tech debt is not a dirty word: Clark challenges traditional thinking—some tech debt is strategic, and discussing it in business terms builds clarity.Product owners need more support: Agile isn't just about shifting scope; engineering teams should help product leaders clarify and prioritize based on impact.Delivery ≠ Impact: Shipping on time is not enough. Clark urges teams to elevate conversations toward value, trade-offs, and business impact over output.⏱️ Timestamped Highlights:00:48 – What Redox does and the scale of its data exchange operations02:00 – Onboarding engineers in a complex healthcare ecosystem03:55 – Why stakeholders often only ask about engineering when things go wrong07:24 – Do engineers stop listening when they start solutioning too early?10:20 – Rethinking tech debt: What the business doesn’t know actually helps13:46 – Can we train engineers to prioritize “getting it done” over “doing it right”?17:36 – Agile as a response to imperfect plans, not bad estimates20:53 – Why scope, time, and quality are business trade-offs, not just engineering ones22:22 – "The burden is on engineering"—and why that might be the right mindset24:52 – Final thoughts on collaboration, failure, and owning outcomes💬 Quote of the Episode:“Don’t just ask, ‘Is this hard?’ Ask, ‘How hard should I work to make this easy?’ That’s where true collaboration starts.” – Clark Downham

In this episode of The Tech Trek, Daniel Whatley, co-founder and technical lead at Vividly, shares his journey launching a startup while still a student at MIT. From managing college life during COVID to navigating the CPG industry's digital transformation, Daniel reflects on what it meant to be the youngest in the room, how he grew into executive leadership, and what he wishes he’d known before co-founding a company. A candid look at growth, grit, and the impact of youth in a traditional space.🔑 Key Takeaways:Startups in school are possible: Daniel co-founded Vividly while at MIT, proving early-stage entrepreneurship can thrive during college years—even amid COVID.Tech-first in a non-tech industry: He leveraged his technical expertise to modernize trade spend management in consumer packaged goods.Being the youngest has its perks: Despite age differences, deep domain knowledge can earn respect and create opportunity.Hard lessons in leadership: Managing older employees taught Daniel resilience and the importance of learning on the job.💬 Memorable Quote:“Don’t give up. If something feels hard, remember you’ve solved a million problems before—this is just the million-and-first.” – Daniel Watley⏱ Timestamped Highlights:00:23 – 01:30 — Intro to Daniel and Vividly’s mission in CPG optimization03:39 – 05:18 — Launching a company as a student and the power of momentum06:27 – 08:13 — Choosing a startup over corporate offers post-graduation08:17 – 09:39 — Origin of the business idea from family connections10:20 – 12:18 — How COVID created unexpected demand for their product12:35 – 15:14 — Being the youngest in the room and embracing your technical edge15:17 – 17:57 — What’s changed: scaling, hiring, and engineering maturity18:32 – 21:34 — Learning management fast: handling tough dynamics with older team members21:53 – 24:11 — Daniel’s advice to aspiring founders still in school25:07 – 26:21 — Would he take the job if he could do it again? No regrets26:21 – 27:32 — Final thoughts and how to connect with Daniel

In this episode of The Tech Trek, Amir is joined by Jonathan Myron, VP of Engineering at Healthie, to dive into what it really takes to lead engineering teams inside startups. From aligning with founders' visions to building engineering cultures that thrive on autonomy and creativity, Jonathan shares hard-won lessons for engineers stepping into leadership. Whether you're building early-stage or scaling through growth, this episode delivers practical insights on driving value, developing team culture, and shaping your career path.🔑 Key Takeaways:Start with empathy for the founder’s vision. Engineering leaders must deeply understand why a company was started to effectively implement and scale that vision.Leadership is a behavior, not a title. Taking ownership, solving problems, and filling gaps earns trust and influence, especially in startup environments.Engineering culture thrives on transparency and purpose. Aligning product goals with team values keeps engineers motivated and connected to impact.Metrics are a story, not a scoreboard. Use developer experience surveys and team feedback—not just velocity or failure rate—to shape team performance meaningfully.⏱ Timestamped Highlights:00:00 – Intro to Jonathan and the theme: working with founders in startups01:48 – Why understanding the founder’s origin story matters for engineering leadership03:00 – Sussing out alignment during interviews with startup founders04:15 – Translating founder vision into engineering execution and culture05:19 – The role of metrics and surveys (like Westrom) in measuring alignment and team health06:49 – Why engineering is both a scientific and creative pursuit08:26 – Bridging founder imprint and engineering culture with empathy and clarity09:53 – Common traits of successful founders and how engineers can support them11:58 – Driving value by solving problems without waiting for instruction13:25 – Advice: “Put aside ego. Real leaders don't need titles.”15:08 – Thriving in ambiguous, high-impact startup environments16:54 – How to reach Jonathan on LinkedIn for career advice💬 Standout Quote:“Leadership is when somebody is a leader, everybody knows it—and you don't need a title for that.” – Jonathan Myron

What should you really be asking during your interview as a tech leader? And once you land the role, how do you manage expectations, reduce technical debt, and make meaningful impact fast?In this episode, Justin Nguyen, Technology Director of Enterprise Data & Analytics at Home Depot, shares hard-won insights from his recent leadership transitions. From assessing team maturity to setting realistic AI expectations, we unpack the tactical and strategic moves leaders need to thrive in the first 180 days of a new role.💡 Key Takeaways:Interview the Company Like a Pro: Ask about key initiatives, maturity of the org, and how they attract top talent—not just the role’s scope.Manage Expectations with Data: Use metrics and storytelling to align stakeholder expectations with technical realities.Build Trust First: Quick wins, especially those that align with long-term goals, are essential for establishing credibility early.Data's Real Value is Trust: The true measure of data success is stakeholder trust and consistent usage.Balance Training vs. Hiring: When evolving your team, identify real skill gaps and be transparent to maintain trust.⏱️ Timestamped Highlights:[01:18] – Three things to assess in interviews: org maturity, domain readiness, and team strength[03:30] – Why the presence of technical/data debt should be expected—not feared[06:28] – Aligning stakeholder expectations with reality to reduce frustration[09:27] – The real AI question: what not to do with it[11:17] – Spotting leadership dynamics during interviews[14:16] – Measuring your own leadership ROI in the first 90–180 days[17:19] – Short-term wins that support long-term strategic goals[19:44] – Measuring success in data through usage and trust[22:19] – Balancing team upskilling, outside hiring, and consulting🔖 Quote of the Episode:“Frustration is the delta between expectations and reality. The greater the gap, the greater the frustration. Your job is to close that gap.” – Justin Nguyen

In this episode of The Tech Trek, Brendan Grove, CTO and co-founder at PrizeOut, shares how his non-traditional background shaped his leadership style and hiring philosophy. Brendan dives into how being curious, humble, and pattern-aware has helped him scale teams and solve complex problems. He also unpacks how hiring for core traits like learning velocity and ownership can outperform chasing resumes full of surface-level skills. We also discuss tech debt, decision-making frameworks, and the role of engineering excellence in business success.Whether you're a startup founder, engineering leader, or aspiring technologist, this episode is a reminder that greatness often lies beyond the obvious checklist.🔑 Key Takeaways:Hire for Curiosity and Ownership: Brendan values engineers who "give a shit" more than those who just ace technical interviews. Passion, curiosity, and ability to learn fast are force multipliers.Non-Traditional Backgrounds Offer Valuable Perspective: Brendan's journey from mechanical engineering to CTO helped him build pattern recognition and a strong product-building instinct.Balance Autonomy and Accountability: Great leaders don’t need to be the expert—they need to empower others while knowing when to step in.Tech Debt Isn’t the Enemy—Stagnation Is: Tech debt becomes a problem only when it slows you down or introduces risk. Code should be easy to change without fear.⏱️ Timestamped Highlights:00:32 – What PrizeOut Does01:13 – Brendan’s Path from Mechanical Engineering to Tech02:59 – Humility and Curiosity as Tools for Problem Solving04:41 – Delegating While Still Leading06:46 – What Brendan Looks for When Hiring Engineers09:24 – Hiring Junior vs. Senior: A Strategic Approach to Ramp-Up11:56 – Giving Raw Talent a Chance: A Success Story15:08 – Code Quality vs. Business Value: Finding the Right Balance17:47 – Tech Debt: When It Matters and How to Approach It💬 Quote:"You should be able to make small changes without being scared. If you can't, it's not a testing problem—it's a code problem."

In this episode of The Tech Trek, Amir sits down with Ronak Vyas, Co-Founder and CTO of Lead Bank, to explore how leadership principles remain constant even as the problems — and companies — change. Ronak shares lessons from leading at Yahoo, Square, and now founding a fintech bank, reflecting on how to adjust to new environments, make high-stakes decisions, and transition from engineering leader to startup founder. If you’re a technology professional considering leadership or even starting your own venture, this episode is packed with real-world insights on navigating change, making smart decisions, and staying close to your craft.🔥 Key Takeaways:Leadership tools stay constant, but their application must adapt to different company cultures, industries, and scales.Prioritize understanding the business context before forming strong technical opinions.Speed of decision-making beats perfection — collect real-world data fast, iterate, and adjust.As a founder, decision-making carries broader consequences, making a deep business understanding essential beyond technical leadership.Retaining technical depth is critical as you move into higher leadership roles, especially when founding or joining small companies.🕰️ Timestamped Highlights:(00:42) – What Lead Bank does: Combining fintech innovation with banking infrastructure.(02:20) – How to adjust to new company cultures and identify first-order problems.(05:47) – Why leadership skills are constants — and how applying them evolves.(09:11) – Balancing gathering information with moving fast: an art, not a science.(13:39) – Why fast, iterative decision-making often beats chasing perfection.(15:12) – How decision-making changes when you're a co-founder vs an executive.(17:28) – Staying technically sharp: the importance of retaining depth as you grow.(21:18) – What Ronak wishes he had more exposure to before becoming a founder.💬 Memorable Quote:"Most often, it's better to make a good decision and iterate quickly than to wait for the perfect decision — real-world feedback is your best guide."