WorkWithJuno

I built WorkWithJuno because I was tired of managing ten browser tabs during my own job search.

Not ten metaphorical tabs — ten actual ones. LinkedIn. A spreadsheet. Three different versions of my resume. A notes file full of company research I kept forgetting to use. Every time I applied to a role, I rebuilt context from scratch. Which resume did I send? What did I write in that cover letter? Did I follow up?

I’m a software engineer. I build systems for a living. And I was managing one of the most important processes in my career like it was 2009.

What it does

WorkWithJuno is a job search platform for engineers. The core idea is simple: store achievements once, tailor them per role, and keep application context in one place instead of scattered across files and tabs.

Features in progress or shipped:

• Achievement storage so you’re not reconstructing bullets from memory every six months
• Job-aware resume tailoring — surface the right experience for each posting
• Outreach and application tracking without a second spreadsheet

Technical approach

TypeScript and React on the front end, Laravel and PostgreSQL on the back end. OpenAI integrations for analyzing job descriptions against stored work history. Async queues for anything that shouldn’t block the UI.

I’m keeping the stack boring on purpose — fewer moving parts while the product is still finding its shape.

Status

Still early. I’m building in public and learning what it needs to be. The problem is real and I’ve lived it — that’s why I started.

workwithjuno.com