← 목록

I Rewrote My Resume Once and Stopped Getting Ghosted. Then Oracle Called

devto 2026-08-02 원문 보기 ↗

For months, my resume was a list of things I had touched. React. Java. SQL. Docker. All true, all useless.

I sent it out. Nothing came back. Not rejections — silence, which is worse, because a rejection at least tells you someone read the thing.

Then I rewrote it. Same person, same internship, same side project, same six months of work. The second version got interviews, and eventually the offer from Oracle.

Nothing about me changed. What changed was that the second resume made a claim, and the first one only made a list.

Here are both versions, and exactly what I did between them.

Version 1: the one that got ghosted

Two-column layout. Skills sidebar down the left. Everything I knew how to do, stacked vertically like a receipt.

Here is my entire internship section, word for word:

Intern, Belke — Jan 2026 – Jun 2026, Remote

Three bullets. Six months of work. Read them as a recruiter for five seconds and ask what you learned about me.

You learned that I was present while software was written.

That's it. There's no scale ("many clients" is not a number), no outcome, no indication of whether I shipped anything or fixed anything or was simply nearby. The third bullet isn't even a sentence — it's a fragment describing a technology, not an action.

My project section had the same disease:

resume AI — Dec 2024 – Present

I built and ran a real product with real users, and I described it as a stack. Three bullets, all inputs, zero outputs. A person reading this cannot tell whether the site has 20,000 users or zero.

That was the core problem, and it took me embarrassingly long to see it: I was describing what I used, not what happened because I used it.

Version 2: the one that worked

I rebuilt it from a blank page on meniacv.com, which is the resume builder I work on — so I'll say up front that I'm not a neutral party here. But it's genuinely what I used, and using my own tool on my own resume is the reason half the fixes below are in the product now. Nothing exposes a weak feature like needing it yourself at 1am.

Same internship. Same project. Here's what the Belke section became:

Intern, Belke — Jan 2026 – Jun 2026, Remote

Nothing here is invented. The conversion number existed the whole time — I just never thought to put it on a resume, because in my head it was "the client's number," not mine. The 12-developer team detail was sitting in my memory doing nothing. The component library was the thing I was proudest of and I had left it off entirely.

And the project section:

Same project. Suddenly it reads like a business instead of a tutorial I followed.

The six changes that did the work

1. Result first, method second

This is the whole thing. Every bullet in v2 follows the same shape:

[What changed, with a number] by [what I did] using [tech].

The tech is still there. It just stopped being the point. Recruiters skim the first four or five words of each bullet — so those words should carry the outcome, not the framework name.

2. I mined my own memory for numbers I already had

I didn't fabricate a single metric. I sat down and asked, for each thing I built: did anything get measurably better? Almost every time, the answer was yes and I had simply never written it down.

If you truly have no numbers, you still have scale and scope: team size, number of clients, how long it ran, how many people use it now. "On a 12-developer team" is a fact, costs nothing, and instantly tells the reader what kind of environment I can function in.

One warning, and it's the most important line in this post: only write numbers you can defend out loud. Assume you will be asked how you measured the 350ms and where the 27% came from. If the answer is decoration, the interview ends there — and you'll have burned a real opportunity on a number you didn't need in the first place.

3. I killed the sidebar

Version 1 used a two-column layout with a narrow left rail. It looked designed. It also meant my summary was squeezed into a column about six words wide, and half my page was whitespace I couldn't use.

Version 2 is one column, full width. Less pretty, more room for evidence. For engineering roles, evidence wins — and single-column survives applicant tracking systems, which have a habit of scrambling multi-column PDFs into nonsense. This is the failure mode I see most often in resumes people send me: a layout that looks beautiful in Figma and arrives at the recruiter as interleaved garbage.

4. I cut skills instead of adding them

Version 1 listed twelve skills including Htm/Css. Version 2 lists twelve too, but different ones — HTML and CSS are gone, and Next.js, Prisma, and SEO are in.

Nobody is hiring a full stack developer on the strength of HTML. Listing it signals that I'm padding. Meanwhile SEO, the skill responsible for my most impressive number, wasn't on version 1 at all.

The rule I now use: if a skill isn't backed by something in the bullets above it, it's noise.

5. I added the links

Version 1 had my email, phone, and city. No GitHub. No LinkedIn.

I had a public repo and a live product, and I made recruiters take my word for it. Version 2 has both links in the header. Free credibility, thirty seconds of work.

6. I fixed the small stuff, because the small stuff is a signal

Version 1 said physic sciences. Lowercase casablanca. capabilitiesfor and asfront with the spaces eaten. Fullstack. Ai in three different capitalizations.

None of these individually cost me a job. Collectively they told a story: this person doesn't proofread. For a role where I'm claiming to care about detail, that's an expensive impression to leave.

I read version 2 out loud, backwards, line by line. Found four more.

What actually happened

The response rate flipped almost immediately. The first version went out and came back as silence. The second one started producing replies within weeks — including the process that ended at Oracle.

I want to be careful about the lesson here, because "I rewrote my resume and got hired" makes it sound like the document was magic. It wasn't. The interviews were still hard. I still had to answer for every number on the page.

What the rewrite actually did was get me into rooms I was already qualified for. The skills were identical in both versions. Version 1 just failed to prove it, and nobody has time to give you the benefit of the doubt.

Steal this checklist

Before you send your next application, go bullet by bullet:

If a bullet fails the first two, don't delete it — interrogate it. The number is usually there. You just have to remember it.

Jawad El yousfi — full stack developer, Casablanca. 1337 / UM6P. I build meniacv.com.