I didn’t set out to build another resume generator. When I started working on ResumeOrbitz—a CV builder with ATS optimization, grammar checks, and cover letter support—I assumed the hardest part would be perfecting the design or refining the algorithms. Instead, the unglamorous technical hurdles reshaped how I think about software development entirely.
Choosing the Right Tools for the Job
Modern web frameworks make it tempting to default to React for interactive interfaces, and that’s exactly what I did. Pairing it with TypeScript added type safety without slowing down development, while Vite provided near-instant hot reloading during prototyping. For styling, Tailwind CSS delivered utility-first consistency without sacrificing speed.
On the backend, Supabase handled authentication and database needs effortlessly, integrating seamlessly with the frontend. Deploying the application on Netlify completed the stack, turning a side project into a fully functional tool with minimal friction.
The Silent Struggles Behind a Smooth UI
Anyone who has used a WYSIWYG editor knows the frustration of seeing your carefully crafted design render differently in the browser, the preview panel, and the final output. My case was no exception. The core issue stemmed from inconsistent DPI handling: browsers assume 96 DPI, while PDF standards default to 72 DPI. Even after accounting for this, subtle misalignments persisted.
To force consistency, I applied a CSS transform scale adjustment—specifically transform: scale(1.3333)—to align the document with Letter-size PDF output. The result was closer, but perfect pixel matching remains an ongoing challenge, proving that what users see isn’t always what they get.
From Polishing to Shipping: The Real Test
The most surprising obstacle wasn’t technical; it was psychological. Every time I reached a milestone—adding a new feature, fixing a bug, refining the UI—I found another “essential” enhancement to pursue. The project grew from a simple resume builder into a multi-tool with cover letter generation and ATS compatibility.
At one point, I realized I was building indefinitely rather than launching. The fear of releasing an imperfect product paralyzed progress. Finally, I forced myself to push ResumeOrbitz live despite minor inconsistencies, understanding that real-world feedback would guide future improvements more effectively than endless local testing.
What Comes Next for ResumeOrbitz
Now that the tool is public, the focus shifts from development to iteration. The goal isn’t to compete with established platforms but to offer a lean, developer-friendly alternative that values transparency over polish. Future updates will prioritize consistency between editor, preview, and PDF outputs, along with deeper ATS optimization features.
The most valuable lesson wasn’t technical—it was realizing how easy it is to over-engineer a product before anyone even uses it. Sometimes, shipping is the best way to learn what truly matters.
AI summary
Building a CV builder revealed hidden tech challenges like PDF rendering inconsistencies and shipping anxiety. Learn what developers overlook when turning ideas into real products.