Learning From Glide
Managing Technical Debt and Release Workflows with 40k users
This past week, Sameer Kapur, Saaniya Kapur, and I launched Glide, a free resume feedback tool that “debugs” your resume, and helps understand what an ATS sees during automated review. In under a week, we passed 40k page views, and have processed over 12k resumes!
Start to finish, we built the whole system in just 20 days. Sameer spearheaded design and growth and Saaniya and I developed the tool itself. However, we made some fundamental flaws relatively early that led to massive uncertainty and fatigue in the later days of our build.
I believe we made errors in 3 key areas:
- Defining project requirements
- Building abstracted & independent modules
- Automated testing in our CI/CD pipeline
Let’s dive in.
Requirements
From the outset, the idea of what we wanted to build was clear. We understood that automated tracking systems (ATS) were notorious for ghosting and auto-rejecting candidates, but exactly how this system worked was always a mystery. We wanted to shine some light into this black box, and give SWE candidates an idea of how these behave.
