Resume Before & After: How We Customised a Software Developer’s Resume for a Singtel Singapore Vacancy

Expert Q&A Guide by CV Writer Singapore

Two resumes. Same candidate. Same career history.

One describes what a Software Developer has done over the course of his career.

The other makes it easier to understand why that experience is relevant to a particular Software Developer vacancy at Singtel Singapore.

What’s interesting about this example is that the candidate wasn’t changing careers. He wasn’t applying for a management position or trying to move into an entirely different profession.

He was already a Software Developer, applying for another Software Developer position.

So why would his resume need to change?

Because two jobs with the same title don’t necessarily have the same requirements.

One employer may place greater emphasis on Java and Spring Boot. Another might prioritise React, API integration, database development or experience maintaining enterprise applications.

Your resume may contain all the right experience. But if that experience is scattered across several pages of responsibilities, the recruiter may not immediately recognise how well you fit the position.

To illustrate the difference, we took an original Software Developer resume and customised it for a Singtel Singapore vacancy.

The candidate and employment details have been adapted for demonstration purposes, including the example achievements.

Here’s what we changed, why we changed it and what other job seekers can learn from the comparison.

Q1. What was wrong with the original Software Developer resume?

Nothing fundamentally wrong.

That’s worth establishing.

The original resume had a straightforward employment history, technical skills, qualifications and descriptions of the work the candidate had performed.

It showed experience at Northstar Digital Solutions, Vertex Technology and several earlier employers.

The candidate had worked with JavaScript, React, Node.js, Java, Spring Boot, REST APIs, SQL, MySQL and other development technologies.

He’d also participated in Agile development, application troubleshooting, testing, deployments and production support.

There was relevant experience throughout the document.

The problem was how that information was presented.

The resume went straight into employment history. Most of the content described day-to-day responsibilities.

A recruiter would need to read through the employment entries and piece together the candidate’s technical strengths.

For a busy recruiter reviewing multiple applications, that creates unnecessary work.

Q2. Why did we add a Professional Summary?

The original resume began with the candidate’s employment history.

We introduced a Professional Summary to establish his technical background before the reader reached the individual jobs.

The revised summary positioned him as a Full-Stack Software Developer with more than nine years of experience in enterprise web applications and backend services.

It highlighted Java, Spring Boot, React, RESTful APIs and SQL-based systems.

These weren’t technologies invented for the new resume.

They were already reflected in his career history.

The difference was that the reader no longer needed to search through several positions to understand his technical background.

A good Professional Summary should answer a fairly simple question:

Why should I keep reading this resume?

For a Software Developer, that usually means establishing the relevant technical background, development experience and type of applications worked on.

A summary filled with phrases such as “passionate team player” or “highly motivated professional” would have added considerably less value.

Q3. Why did we introduce an Areas of Expertise section?

The original resume already had a skills section.

It listed programming languages, tools and general competencies.

That was useful, but it didn’t fully explain how the candidate used those technologies.

We introduced an Areas of Expertise section organised around three areas:

Frontend Development

React interfaces, reusable UI components, JavaScript and enterprise web applications.

Backend Development

Java, Spring Boot, RESTful API design, service integration, SQL and MySQL.

Engineering Delivery

Agile/Scrum, code reviews, testing, Jenkins, AWS migration support and debugging.

This gave the reader a more structured picture of the candidate’s experience.

There’s a difference between knowing that someone has used Java and understanding that they’ve developed Java-based backend applications supporting enterprise business systems.

Both matter.

The first tells you which technology appears in their background.

The second begins to explain what they’ve actually done with it.

Q4. Why did we keep a separate Technical Competencies section?

Because technical skills are particularly important when recruiting Software Developers.

A recruiter may be checking for Java, Spring Boot, React or SQL before reading the employment history in detail.

The revised resume therefore retained a dedicated Technical Competencies section.

It grouped the candidate’s skills into programming languages, frameworks and databases, and cloud and delivery tools.

This made the technologies easier to locate.

It also allowed us to be more precise.

For example, the candidate’s AWS experience was described as migration support rather than suggesting he had extensive cloud architecture expertise.

That distinction matters.

A resume should make relevant skills visible without exaggerating the depth of experience behind them.

Q5. What changed in the employment history?

The original resume contained substantial information about the candidate’s responsibilities.

At Northstar Digital Solutions, he developed and maintained web applications, worked with product managers, built components, maintained REST APIs, investigated defects and supported deployments.

At Vertex Technology, he worked on Java and Spring Boot applications, API integrations, database functions, testing and AWS migration support.

All of that was useful.

But the responsibilities appeared as a long series of bullet points.

In the customised version, we made the descriptions more focused and organised them around the development experience relevant to the target position.

The Northstar role placed greater emphasis on React interfaces, reusable components, RESTful APIs and SQL.

The Vertex role highlighted Java, Spring Boot, backend applications, integrations and enterprise systems.

The employment history became easier to scan for the particular experience the employer was likely to be evaluating.

Q6. Why did we separate responsibilities from achievements?

This was one of the most important changes.

A responsibility tells the employer what you were employed to do.

An achievement or contribution provides evidence of what you delivered.

Consider the difference.

Original responsibility:

“Build and update web application components, forms, dashboards and reporting functions for different departments.”

That tells us what the candidate worked on.

The revised example included a contribution involving 12 reusable React components and shared validation logic, reducing duplicated development work.

Another example described SQL query optimisation that improved average page-loading time by approximately 30%.

A third described improvements to defect-checking and regression-test handover that reduced recurring production incidents.

These examples help a recruiter understand the practical contribution behind the development work.

The figures in this illustrative comparison were adapted for demonstration purposes. In an actual client resume, achievements and metrics need to be established from the candidate’s real experience.

Not every achievement needs a percentage.

A useful achievement might involve improving reliability, building reusable components, simplifying a process, delivering a difficult integration or resolving a recurring technical problem.

The important thing is to explain the contribution rather than merely repeat the job description.

Q7. How did we customise the resume for the Singtel Software Developer vacancy?

We used the target vacancy to determine which parts of the candidate’s experience deserved greater prominence.

The revised resume placed particular emphasis on:

• Java and Spring Boot development
• React and JavaScript interfaces
• RESTful API development and integration
• SQL and MySQL
• Enterprise application development
• Agile software delivery
• Testing, debugging and application support

These technologies and responsibilities were reflected in the candidate’s original background.

We then adjusted the Professional Summary, Areas of Expertise, Technical Competencies and employment history to make that experience more visible.

The objective wasn’t to repeat every phrase from the vacancy.

It was to help the employer recognise the connection between the job requirements and the candidate’s existing experience.

Q8. Does this mean you should copy keywords from the job description?

No.

There’s a difference between using appropriate technical terminology and inserting keywords simply because they appear in an advertisement.

If you’ve developed Java applications using Spring Boot, those technologies should be clearly stated.

If you’ve built RESTful APIs, don’t hide that experience behind a vague statement such as “supported backend development activities.”

But if you’ve never worked with Kubernetes, don’t add Kubernetes because the employer mentions it.

The same applies to AWS, microservices, CI/CD pipelines and other technical capabilities.

A recruiter may initially notice the keyword.

The hiring manager will eventually want to know what you’ve actually done.

A customised resume should make genuine experience easier to recognise, not create technical expertise that doesn’t exist.

Q9. Why did we shorten the older positions?

The candidate’s earlier positions included Junior Software Developer, Web Developer and IT Support Intern.

Those roles helped establish his career progression.

But they didn’t need the same amount of detail as his more recent development positions.

In the original resume, the earlier jobs contained numerous responsibility bullets.

The revised version condensed them.

That created more room for the Java, Spring Boot, React and enterprise application experience that was more relevant to the target vacancy.

This is particularly important for mid-career professionals.

A resume doesn’t need to give every job equal attention.

Your first position may explain how you entered the profession, but your recent experience will usually be more important when an employer is evaluating your current capabilities.

Q10. Did the customised resume change the candidate’s career history?

No.

Both versions retained the same underlying employment history and educational qualifications.

The candidate still had experience at Northstar Digital Solutions, Vertex Technology, Bluewave Systems, Orbit Web Studio and BrightPath IT Services.

His qualifications remained a Bachelor of Engineering in Information and Communications Technology from the Singapore Institute of Technology and a Diploma in Information Technology from Temasek Polytechnic.

The customised resume changed the organisation, emphasis and explanation of the experience.

It also introduced illustrative achievement examples to demonstrate how contributions could be presented.

In a real resume-writing engagement, any new achievement or metric would need to be confirmed with the candidate.

Customising a resume shouldn’t mean changing the facts of someone’s career.

Q11. Does a customised resume need a completely different format?

Not necessarily.

This comparison includes presentation changes, but the main objective was to improve the content.

A better-looking resume isn’t automatically a more effective resume.

You can have attractive formatting and still leave the recruiter unsure what you’re qualified to do.

Likewise, a relatively simple resume can work well if the relevant experience is clear, the career history is understandable and the achievements are convincing.

For this exercise, the important changes were the Professional Summary, Areas of Expertise, clearer technical competencies, more focused employment descriptions and separation of responsibilities from contributions.

Those are content decisions.

Formatting helps the reader navigate that content, but it doesn’t replace it.

Q12. Do I need a different resume for every Software Developer application?

Not necessarily.

If you’re applying for several positions with almost identical requirements, one well-positioned resume may be sufficient.

But consider these three vacancies:

Software Developer A: Primarily Java, Spring Boot and backend services.

Software Developer B: React, JavaScript and frontend application development.

Software Developer C: Full-stack development, REST APIs and enterprise system integration.

You might have experience in all three areas.

But one resume that gives equal weight to everything may not present your strongest evidence for each position.

For the backend role, your Java and Spring Boot experience may deserve greater prominence.

For the frontend role, React components and interface development may be more important.

For the full-stack role, you may want to demonstrate how your frontend and backend experience work together.

You haven’t become three different developers.

You’re presenting different aspects of the same technical background.

Final Thoughts

The difference between the original and customised Software Developer resumes wasn’t that one candidate suddenly became more qualified.

His career history remained the same.

The original resume contained relevant technologies, responsibilities and experience.

But much of that information was spread across the employment history.

The customised version made the technical background easier to understand, brought relevant experience forward and showed how professional contributions could be explained more clearly.

That’s what effective resume customisation should accomplish.

It’s particularly useful for mid-career professionals who have accumulated experience across several technologies, projects, employers or functions.

The challenge often isn’t finding more experience to include.

It’s deciding which experience matters most to the employer you’re approaching.

A resume can contain all the right information and still fail to communicate why you’re right for the job.

And that’s why two resumes belonging to the same candidate can create very different impressions.

View the Software Developer Resume Before & After Comparison

The accompanying five-page comparison shows the original Software Developer resume alongside the version customised for a Singtel Singapore vacancy.

The original resume appears on pages 2–3, while the customised version appears on pages 4–5.

Review both versions and compare how the Professional Summary, technical expertise, employment responsibilities and achievements are presented.

Note: This is an illustrative resume transformation. Candidate and employment details, including example achievements, have been adapted for demonstration purposes. It does not represent a verified hiring outcome or an endorsement by Singtel.

Need Help Customising Your Resume for Specific Job Applications?

WhatsApp us at +65 9681 2409

CV Writer Singapore helps mid-career professionals, Software Developers and other job seekers develop a strong master resume and customise their experience for the different positions, employers and career directions they’re targeting in Singapore.Software Developer Resume Before & After Comparison