Building a production ready SaaS Using Kiro with Zack and Shaf 🚀
Show notes from "The Builder Story" episode with Arshad Zackeriya, AWS Hero who built a feedback tool - feedback Feijoa as a SaaS and he vibe engineered all of it using Kiro
In this episode of "The Builder Story," im sitting down with Arshad Zackeriya (Zack), a New Zealand-based AWS Hero, to discuss his journey in tech and the creation of Fedjoa, a lightweight, production-ready feedback tool built using Kiro.
Top 5 Takeaways
- Start with the Problem, Not the Tool: Effective products solve a specific, painful problem rather than just layering on bloated features.
- Engineering is More Than Just Coding: Building with AI requires "steering"—using your architectural knowledge to guide the AI, set guardrails, and manage costs rather than just generating code blindly.
- Ship Faster and Iterate: Adopting a "bias for action" mindset allows you to get a prototype into the hands of users quickly, gather real feedback, and improve based on actual usage.
- Community as a Career Catalyst: Building genuine connections and contributing to communities (like AWS User Groups) is invaluable for professional growth, mentorship, and career opportunities.
- Be Patient and Keep Sharpening Your Axe: Career growth is a marathon. Focus on continuously sharpening your skills (learning Linux, networking, DevOps principles) before expecting to jump to the next level
The Story Behind Feijoa
Zack developed Feijoa after struggling to find a simple, cost-effective feedback tool for the AWS Community Days in New Zealand. Existing solutions were often bloated and expensive, far exceeding the requirements for community-driven events.
By using Kiro, Zack was able to architect a purpose-built, lightweight platform that collects insights without unnecessary complexity. He emphasizes that the tool's success came from his clarity on the problem statement and his active role in steering the AI to build functional, secure, and production-ready code.
Engineering with AI: The Power of "Steering"
Zack highlights a critical distinction between "vibe coding" and "vibe engineering." To him, using an AI tool like Kiro isn't just about dumping prompts; it’s about architecting the solution:
- Modular Specifications: He shows how to break down product requirements into modular, versioned specifications (e.g., specific UX enhancements, bug fixes, or new features), allowing for easier iteration.
- The "Steering" File: This is the most crucial part of his process. He uses a dedicated steering file to define guardrails, tech stacks, and deployment configurations. This prevents the AI from hallucinating or making errors, keeping the development environment distinct from production.
- Infrastructure as Code (IaC): Zack uses CDK for infrastructure, ensuring that his project is properly engineered, secure, and scalable.
Advice for Builders and Career Changers
For those looking to break into the industry or move between countries, Zack offers a few practical tips:
- Focus on Fundamentals: Even if you start in one domain (like PHP development), expand your knowledge into Linux, networking, and cloud best practices
- Find a Mentor: Don't try to navigate challenges alone. Actively seek out mentors who can provide guidance during difficult transitions
- The Value of Referrals: Almost all of Zack's international job opportunities came through community referrals, underscoring the importance of being an active, reliable member of professional communities
Enjoyed reading this content? Let the author know!
Your likes, comments, shares, and saves help creators reach more builders.
Loading recommendations
Loading article