DEV Community: Muhsin m

Use AI to Edit Your Resume, Not Invent Your Experience

Muhsin m — Sun, 11 Oct 2026 13:18:00 +0000

A better sentence is still a bad resume bullet if it describes something you never did.

That's the check worth making before you paste an AI rewrite into your resume. Does it sound good? Fine. Is it true, right down to the verb? More important.

You don't have to choose between using AI and writing an honest application. Give it real material to work with, then review the changes before they become your claims.

Start with the messy facts

Before asking for polished wording, write down what actually happened.

What was the task? What did you personally do? Which tools did you use? What was finished? What result can you support?

Plain notes are enough. For example, here's an invented student-project note:

Four-person class project. I cleaned the survey spreadsheet, removed duplicate responses and made two charts in Excel. We used the charts in our final presentation. No business impact measured.

There is useful material there. It doesn't need a revenue figure or a leadership title added to it.

Try this prompt:

Suggest two short resume bullets using only the facts below. Don't add numbers, tools, responsibilities or results. If useful information is missing, ask me instead of filling it in. Keep my individual contribution separate from the team's work.

Then add your notes, with personal and confidential information removed.

Treat that instruction as a starting point, not a guarantee that the output will follow it. You still need to check the answer.

Read the verbs before the adjectives

Here's an illustrative rewrite that stays within those notes:

Cleaned survey data in Excel by removing duplicate responses and created two charts for a four-person class project's final presentation.

Now compare it with this invented overstatement:

Led a data analytics initiative that improved business decision-making through advanced Excel reporting.

It sounds more important. It also changes the facts.

"Led" claims responsibility the notes don't establish. "Improved business decision-making" adds an outcome nobody measured. "Advanced" adds a level of expertise the example hasn't shown.

Check verbs such as led, owned, managed, built and supported. They aren't interchangeable. Choose the one that describes your part, even when another one sounds more impressive.

Use the job description to find relevant evidence

A job description can help you decide which real experience to explain. It cannot supply experience you don't have.

For a fictional junior role asking for Excel and data cleaning, the survey project is worth considering. If the same listing asks for SQL and you haven't used SQL, rewriting an Excel task won't close that gap.

You can ask:

Compare this job description with my factual notes. Identify requirements my notes support and requirements they don't establish. Quote the supporting note for each match. Don't treat a related skill as proof that I have the requested skill.

Read the comparison yourself. Use it to choose what deserves space on the resume, and to spot questions or gaps you need to address honestly.

Skip requests for a guaranteed ATS score or the exact words that will get you shortlisted. This exercise is about checking fit and explaining relevant work, not predicting an employer's decision.

Check the application rules and the information you share

Before using AI on an application, read the employer's instructions. Don't assume every employer permits the same use.

Harvard's AI guidance for resumes and cover letters recommends starting with your own material, treating generated text as suggested edits and checking organization guidelines on AI use. It also cautions against sharing personal or proprietary data.

For editing practice, leave out your phone number, home address and other unnecessary identifiers. Don't paste confidential internship notes or private client information into a tool. If a detail isn't yours to share, leave it out of the prompt.

Give the final version a spoken check

Read each bullet aloud, then ask yourself:

Can I explain exactly what I did?
Can I back up the number or outcome?
Is my contribution distinct from the team's?
Would I use these words in an interview?

If you need to explain that "managed" really means "helped once," change it now.

And check the final document, not only the chat response. Make sure the version you're uploading has the corrected facts, readable formatting and working links.

AI can help you try different ways to describe your work. The decision about what belongs on the resume stays with you.

Keep the sentence you can explain, even if the other one sounds grander.

Author bio: I'm building Cloud9Profile, a career toolkit for early-career job seekers.

5 Job Search Mistakes Freshers Keep Making (and the Boring Fixes)

Muhsin m — Tue, 06 Oct 2026 15:43:00 +0000

You're not unlucky. You might just be playing a numbers game with the wrong numbers.

Here are five mistakes that come up again and again with early-career job seekers. None need talent. They need a bit of patience.

Mistake 1: Applying to everything

It feels productive. Fifty applications in a weekend. But if you send the same resume to roles that don't fit, you get fifty near-misses.

Fix: pick a short list of roles you'd actually take, and aim for fewer, better applications. Ten that fit beat fifty that don't.

Mistake 2: One resume for every job

Different postings stress different things. A resume that never changes can look like it was written for nobody.

Fix: keep a master version with everything, then trim and reorder for each role. Move the most relevant project to the top. Use the posting's wording wherever it's honestly true.

Mistake 3: Describing duties, not results

"Responsible for social media" tells the reader you had a job. For example, "Posted three times a week and grew the page from 300 to 800 followers" tells them what happened. Use real numbers only. If you don't have one, say what changed or who used it.

Mistake 4: Never following up

Many people send an application and wait. A short, polite note a week or so later is normal and rarely seen as pushy. Keep it two or three lines: who you are, the role, and one sentence on why you fit.

Fix: when you apply, write the date and the role in a simple list. A week later, check the list and send the note where you have a name or an address to send it to.

Mistake 5: Treating rejection as a verdict

A no usually means "not this one, not now". It might be timing, someone internal, or a better match. It rarely says anything about your worth.

Fix: after each rejection, ask one question. Would a different resume, a different role or a different company have fit better? Change one thing, then try again.

The boring summary

Fewer applications. A tailored resume. Bullets that say what happened. A short follow-up. A thick skin.

It isn't glamorous. It works better than refreshing job boards at midnight.

Which of the five is hardest for you right now? Tell me in the comments.

I'm building Cloud9Profile, a career toolkit for early-career job seekers.

I Rewrote a Fresher's Resume Line by Line. Here's What Changed (and Why It Got Better)

Muhsin m — Sat, 03 Oct 2026 17:09:23 +0000

Your resume probably says you "worked on" things. That's the problem.

Let me show you what I mean. Below is an invented example, a composite of the kind of fresher resume that comes up a lot. It isn't a real person. Call her Asha, a fresh computer science graduate applying for a junior data analyst role.

THE BEFORE

Objective: "Seeking a challenging position in a reputed organisation where I can utilise my skills and grow."

Project: "Worked on a sales dashboard using Excel and SQL."

Internship: "Responsible for data entry and helping the team with reports."

Skills: "MS Office, Excel, SQL, Python, Communication, Teamwork, Hard working, Leadership, Quick learner, Power BI, Tableau, R"

Nothing here is false. It's also nothing a recruiter can picture. Let's go through it.

FIX 1: Replace the objective with a two-line summary

"Seeking a challenging position" tells the reader what you want. They already know, you applied. They want to know what you bring.

After: "Computer science graduate with project experience in SQL and Excel reporting. Built a sales dashboard from a 20,000-row dataset and looking for a junior data analyst role."

(Only use a number like that if it's true for you. If you don't remember the size of your dataset, go and look. It takes two minutes.)

FIX 2: Turn "worked on" into what you did and what came out of it

"Worked on a sales dashboard" could mean you built it or you watched someone build it. Try this shape: action, tool, result.

After: "Built a sales dashboard in Excel with SQL queries, showing monthly revenue by region. Helped the class team spot the two weakest-selling product lines."

If you don't have a result with a number, a plain outcome is still better than nothing: who used it, what decision it informed.

FIX 3: Make the internship bullet visible

"Responsible for data entry" describes a duty. Describe what you actually did.

After: "Entered and cleaned weekly sales records in Excel, fixing duplicate and missing entries before the team's Friday report."

Notice nothing got inflated. Same job, clearer picture.

FIX 4: Cut the skills dump

Twelve skills, two of them adjectives ("Hard working", "Quick learner"). Adjectives are claims. Evidence is bullets. Keep tools you can talk about in an interview, and group them:

After:

Data: SQL, Excel

Programming: Python

Visualisation: Power BI

(Drop Tableau and R unless you've used them for something real. If an interviewer asks about them and you freeze, the list hurt you.)

THE SIMPLE TEST

Read each line and ask: could someone ask me a follow-up question about this? If yes, keep it. If you'd have to bluff, cut it or learn it.

THE WHOLE CHECKLIST

Summary says what you bring, not what you want.
Every bullet: action, tool, result.
Duties become things you did.
Skills are tools you can defend, not adjectives.
Nothing on the page that you couldn't talk about for two minutes.

Fresher resumes don't fail because the person lacks experience. They fail because the experience is hidden behind vague words. You probably already have the material. It just needs to be said plainly.

Try rewriting just one bullet today. Drop it in the comments and I'll tell you what I'd tighten.

I'm building Cloud9Profile, a career toolkit for early-career job seekers.

"The ATS Rejected Me" Is Usually Only Half the Story. Here's What Happens to Your Resume

Muhsin m — Fri, 02 Oct 2026 12:19:50 +0000

Before you blame the robot, check whether it could even read you.

I hear this one constantly: "I applied to 80 jobs, the ATS must be eating my resume." It's a comforting story. Sometimes it's true. Often it's something more fixable, and believing the simple version keeps you from finding the real problem.

First, what an ATS (applicant tracking system) does. It stores your application, parses your resume into fields, and lets recruiters sort and search. Some employers also set automated screens: knockout questions about work authorization, a required licence, minimum experience. Those can and do filter people out. But a lot of rejections people blame on "the ATS" are really two other things.

Problem 1: The resume was hard to read.

Two-column layouts, icons, skill bars, text inside images. They look great to a human and can confuse a parser. Your job title lands under "Education", your dates disappear. Nobody judged you. The system just couldn't read you properly, so the recruiter sees a messy profile.

Problem 2: The resume didn't match the role.

Search and ranking vary a lot between systems, and some match related terms. Still, if the posting says "stakeholder reporting" and your resume says "made presentations for managers", a recruiter's search can miss you, or a matching feature may not rank you highly. Same experience, different words.

And a note on keyword stuffing: pasting a wall of skills at the bottom doesn't help. The human who opens it will see spam. Use the posting's words where they're true, inside real bullets: what you did, with what, and what changed.

What actually helps:

Keep the layout simple. One column, standard headings (Experience, Education, Skills), a normal font.
Use the file format the employer asks for. If they don't say, check the posting before assuming.
Mirror the job's language honestly. Only claim what you've actually done.
Put numbers or outcomes in your bullets where you have them.
Read the job description against your resume, line by line. Note which important terms and skills you've covered and which you haven't, and tailor a version for each application.

Step 5 takes an evening, not a week, and it beats sending one perfect generic resume everywhere.

So the honest summary: automated screens exist, but plenty of "ATS rejections" are really "hard to read" or "didn't match the role". Both are things you can fix.

Pick the one job you want most this week and try it. Tell me in the comments what you changed.

I'm building Cloud9Profile, a career toolkit for early-career job seekers.