Why I BuiltCalwyn

A candid note about where it genuinely helps, where it does not, and the boundaries I won't let it cross.

Shivam SinghFounder8 min read

I'll keep this plain, because that's how I think about Calwyn.

I started building it after watching too many people, friends mostly, go through the same thing. They'd send out a hundred applications and hear back from one or two. Sometimes none. After a while they stopped being able to tell whether their résumé was bad, whether they were applying wrong, whether they weren't qualified, or whether anyone had even opened the thing. At that point the search stops feeling like effort and starts feeling like a coin flip.

I don't think the hardest part of finding a job is convincing someone to hire you. I think the hardest part is surviving the process long enough to get a real shot at it.

And the process is heavier than people give it credit for. One application isn't one thing. It's find the role, read the description, compare it to what you've actually got, tailor the résumé, write the cover letter, maybe draft an outreach message, save it somewhere, track it, remember to follow up, then prep for the interview if it ever comes. A thoughtful application runs twenty to thirty minutes. Ten a day is two to five hours, not learning anything, not getting better at the work itself, just managing the search. And most people aren't doing ten. They're doing hundreds.

Nobody designed that workflow. It just accreted. The résumé lives in Overleaf or a PDF editor, the tracking lives in Notion or a spreadsheet, interviews live in a calendar, contacts live in your head and scattered across LinkedIn and email. They need to juggle between different files and folders for each application. And create a webpage for sharing to recruiters manually from scratch or using an AI tool that further costs money. The person becomes the glue holding all of it together with a pile of subscription bills, and it gets hardest to manage exactly when there's the most of it to manage.

Let me be honest about what Calwyn is and isn't.

It is not a magic résumé button. A résumé only works if the skills underneath it are real. Optimization comes after that, not instead of it. What Calwyn does is take a job description and help you shape a résumé to it, with a Fit score, so that before you spend the energy you can tell whether a role is worth a real application or whether it's a long shot. I don't believe in spray-and-pray. When anyone can apply with one click, one more click is worth almost nothing. The applications that work are the ones carrying some intention: context, a reason to exist, a follow-up, sometimes a real person on the other end.

That's why outreach isn't a side feature for me. Plenty of people know they should message a recruiter or ask for a referral, and then freeze on the wording, or burn an hour on three sentences, or lose track of who they already spoke to. Calwyn helps draft those messages and keeps the contacts in one place, with a clear pipeline so you know who you've reached out to, who responded, and who referred you. Reaching out stops being the thing you quietly avoid.

Interview prep works the same way. I'm not going to pretend software can prepare for you. The STAR stories, the technical answers, that's your work, and it should be. What we can do is give you somewhere to practice: run the behavioral and technical questions as a quiz, whenever you want, until they're sharp.

A few things I care about that are easy to overlook.

The negotiation. Most people freeze when they get an offer. Not because they don't want more, but because they don't know how to ask, or they're scared of losing something that took months to earn. Calwyn takes your actual offer details, base, equity, bonus, deadline, and gives you a strategy grounded in those numbers. What to counter, how to frame it, which levers matter. You can regenerate it if the conversation changes. It's not a magic number. It's a starting point you can stand behind.

The portfolio. Most people don't want to build a personal website. They just need one clean link that represents them, their work, their résumé, their socials, that they can drop into a message without losing a weekend to it.

The timeline. People treat a job search as a temporary event and throw all of it away the moment an offer lands. I think that's a waste. Every search produces real knowledge: what worked, who replied, which message got an answer, which strategy turned into an interview. Calwyn keeps that, so the next search doesn't start from zero, and so, over time, the product itself gets better at telling what actually works for a given kind of role.

On privacy I'll be blunt. People hand their résumés to AI tools without a second thought, and a résumé is about as personal as a document gets. Your history, your contact details, your identity. So here is the honest version. When you upload a résumé, an AI reads the whole file to structure it. When Calwyn tailors your résumé or drafts a letter, it sends your professional content and your name, not your phone number, email, or social links. We use established providers under their terms, and we don't sell your data. I'd rather tell you exactly what happens than promise a level of anonymity the product doesn't deliver. That shouldn't be a line buried in a privacy policy. It's part of the product.

The last thing is where I think this is all heading.

More and more, people will let AI agents, Claude, ChatGPT, whatever they're paying for, handle the repetitive parts of a search: reading a posting, shaping the résumé to it, drafting the outreach, keeping track of who they talked to. The hard part was never whether the agents can do that. It's that they lose the thread. Sessions end, tools change, models change, and the context that mattered last time is gone, so you re-explain your whole history to every new agent, every time.

I want Calwyn to be the part that doesn't get lost. Not a layer hidden underneath your agent, but the place your search actually lives. The system of record your agent reads from and works inside. Calwyn keeps a structured knowledge graph of your career: your skills, your experience, the companies you've applied to, the people you've talked to, what worked and what didn't. It isn't a chat log. It's real structure that any agent can query efficiently. You connect your agent once through MCP (the open protocol that Claude, ChatGPT, and a growing number of tools support), set its scope, and your context is there, no matter what tool you use or how many sessions you start.

I'm strict about one thing there, though, and I think it's what separates this from reckless. Your agent works inside Calwyn, and you keep every move that reaches the outside world. It can tailor a résumé, draft a cover letter and an outreach message, save a recruiter, log an interview, set up your prep, generate a negotiation strategy. It cannot apply for you, and it cannot send anything as you. Those stay yours, after you've actually looked. Everything it does is a draft you review before it counts. You decide what it's allowed to touch and how far it can go. And you can see everything it's done. The agent takes the grind, you keep the judgment and the final word. That's the version of this I'd trust with my own search, and it's the only one I'll ship.

And one belief underneath all of it: a job search shouldn't be decided by where you happen to live. Borders are lines on a map. The work isn't.

In the end, nobody actually wants application-tracking software. Nobody dreams about résumé optimization. People want the outcome: a better job, a raise, real leverage walking into a review, a remote role, the dream company, a clean career switch, more options, more control. Everything else is just process. Calwyn exists to take that process off your plate so you can spend yourself on the thing that actually matters.

That's the whole idea. No magic promises, no scare tactics. Just steady, honest help for anyone trying to land something better.

ShivamFounder of Calwyn