Coding Isn’t the Hard Part Anymore

Adam Kirk, CTO and cofounder of Jump, joins The Tech Trek to talk about what it really takes to build AI native products for people who do not want to think like technologists.Jump serves financial advisors, a market where ease of use, trust, workflow fit, and domain context matter as much as the model itself. Adam shares how his team validates product ideas, uses coding agents across engineering, and is rethinking how technical teams build, review, and hire in the AI era.What You’ll Take Away• AI native products still win or lose on adoption. If the user feels like they are programming, the product is already too complicated.• The engineering bottleneck is moving. AI can generate code faster, but teams still need humans to review, validate, and understand the tradeoffs.• Product teams can now get closer to the build. PMs using AI to prototype create sharper product definition, even when engineers still rebuild the final version properly.• Technical debt is not disappearing. Code may be cheaper to write, but data models, migrations, architecture, and judgment still carry real risk.• Engineering interviews are breaking. If engineers use AI every day, hiring teams need better ways to assess ownership, judgment, and technical taste.Timestamped Highlights00:38Adam explains how Jump helps financial advisors turn client meetings into notes, CRM updates, and advisor specific workflows02:20Why less technical users force better product validation, and why a flexible interface can still feel like programming.07:00How Jump uses coding agents across the engineering team, and why code review matters more as AI generated code improves.11:15Why PMs vibe coding product ideas can help engineers understand what needs to be built.14:08Where AI is creating real productivity gains, and where human coordination still slows things down.18:00Why some technical debt may get easier to manage, but data modeling and migrations remain hard.20:51How AI is forcing engineering leaders to rethink coding interviews, referrals, and what great engineers should be measured on.One Line That Stuck“Generating code is really not the bottleneck anymore. It is validating the code, reviewing the code, and sharing the context around to the team.”Practical Takeaways• Test product ideas with real users before engineering builds too far.• Treat AI prototypes as product definition, not production architecture.• Use coding agents to speed up the work, but do not skip review.• Assess engineers for judgment, ownership, and decision quality, not just raw syntax.Follow The ShowSubscribe to The Tech Trek for more conversations with technical leaders building the next generation of AI native products, teams, and workflows.