Professional summaries

A professional summary is a short paragraph at the top of your resume that tells the reader who you are, what you do best and what you bring to the job. It sits under your name and contact details and usually runs three to five lines.

A good summary does three things:

• States your professional identity, such as your role, field and level of experience.
• Highlights two or three strengths or results that matter for the job you want.
• Uses the language of the jobs you are applying for, so the reader sees the match quickly.

Example: "Payroll specialist with 7 years' experience in multi-site retail businesses. Process monthly payroll for around 600 staff across three countries, with a strong record of accurate, on-time runs. Skilled in SAP payroll, end-of-service calculations and audit preparation."

Think of it as a preview: it does not replace your experience section, it points the reader to the best parts of it.

Aim for three to five lines, or roughly 40 to 80 words. That is long enough to state your role, your experience and two or three strengths, and short enough to read at a glance.

Signs your summary is too long:

• It runs past five lines on the page.
• It lists duties that already appear in your experience section.
• It contains more than one or two adjectives about your personality.

Signs it is too short:

• It is a single vague line such as "Hard-working professional seeking growth".
• It does not say what job you do or what field you work in.

Senior candidates sometimes write a slightly longer summary, but even then a tight five lines usually works better than a block of text. If you have more to say, move it into your experience bullets or a key achievements list.

Not always, but most people benefit from one. A summary helps when your job title alone does not tell the full story, when you are changing direction, or when you have several years of experience to condense.

A summary is especially useful if you:

• Have many years of experience and want to point to the most relevant parts.
• Are changing careers and need to connect your past work to the new role.
• Are applying from another country and want to make your field and level clear at once.

You can skip it, or keep it to two lines, if you are a student with a short one-page resume and your education and projects already say everything. A weak, generic summary is worse than none, so only include one if you can make it specific to you and the job.

Write it after the rest of your resume is finished, then build it in four parts: identity, experience, strengths and proof.

• Start with your professional identity: your role and field, for example "Registered nurse in critical care" or "Junior data analyst".
• Add your level: years of experience, or "recent graduate" if you are starting out.
• Choose two or three strengths that the target job asks for. Read the job advert and pick the skills that appear most often.
• Add one piece of proof: a result, a scale of work or a notable responsibility.
• Read it aloud and cut any word that does not add information.

Example: "Procurement officer with 5 years' experience in facilities management. Manage purchasing for about 120 active suppliers and lead quarterly tenders for cleaning and maintenance contracts. Known for clear supplier negotiation and tidy, audit-ready records in Oracle."

Finally, check it against each job you apply for and adjust the strengths and keywords so they match that employer's needs.

Use the implied first person: write as if "I" is the subject, but leave the "I" out. This is the most common style on resumes in most countries, and it keeps sentences short.

Compare:

• Full first person: "I am a marketing executive with six years of experience. I manage campaigns..."
• Third person: "Sara is a marketing executive who manages..."
• Implied first person: "Marketing executive with 6 years' experience. Manage paid and organic campaigns for B2B software brands."

Third person can sound odd, as if someone else wrote about you, so most people avoid it on a resume. Full first person is acceptable in some places, such as a LinkedIn About section or a cover letter, but on a resume the implied style reads more cleanly. Whichever you choose, stay consistent across the whole summary.

It is not wrong, but it is usually unnecessary. Most resumes drop "I", "me" and "my" because the reader already knows the document is about you, and removing them saves space.

If your summary currently reads "I am an experienced accountant and I have worked in audit for eight years", rewrite it as "Accountant with 8 years in external audit."

There are a few cases where a light first-person voice can work:

• Creative fields where a friendlier tone suits the employer.
• Short, informal applications such as a café or a start-up.
• Countries or companies where the job advert itself is written in a personal style.

If you do use "I", use it sparingly and keep the rest of the resume consistent. Do not mix "I manage" in one sentence and "Manages" in the next.

Put it at the very top, directly under your name and contact details and before your experience or education. Its job is to set the context for everything below it, so it only works if it is read first.

A typical order is:

• Name, professional title and contact details.
• Professional summary.
• Work experience (or education first if you are a recent graduate).
• Skills, certifications and other sections.

Avoid placing the summary in a narrow side column of a two-column layout. It can get squeezed into short lines and some applicant tracking systems read columns in an unexpected order. A single-column layout keeps the summary in the main flow of text where both people and software find it easily.

Any of these is fine; choose a clear, standard heading and keep it short. "Professional Summary", "Summary" and "Profile" are all widely understood by recruiters and by applicant tracking systems.

Some regional habits:

• "Personal Profile" or "Profile" is common on UK and Irish CVs.
• "Professional Summary" or "Summary" is common in the US, Canada and the Gulf.
• "Career Summary" or "Executive Summary" is sometimes used by senior candidates.

Avoid creative headings such as "Who I Am" or "My Story". They can confuse software that looks for standard section names, and they add nothing for a human reader. You can also skip the heading altogether and let the paragraph sit under your name, but a heading makes the page easier to scan.

A short paragraph is the usual choice, but a short bulleted list can work well for senior or technical candidates. Pick the one that makes your strongest points easiest to see.

A paragraph works best when:

• You have three to five lines of connected information.
• You want a smooth, readable introduction.

Bullets work best when:

• You want to show three or four distinct highlights, such as major results or specialisms.
• Your experience spans several areas and a paragraph would turn into a long list.

A useful hybrid is one opening line followed by three bullets.

Example: "Operations manager with 12 years in third-party logistics." Then:

• "Run a 40,000 sq m warehouse with a team of about 150."
• "Led the move to a new warehouse management system in 2023."
• "Lean Six Sigma Green Belt."

Keep it to five or six lines either way.

Your first sentence should say what you are professionally: your role or field, your level and, if useful, your specialism. Think of it as the answer to "What do you do?"

Good first sentences:

• "Civil engineer with 9 years in road and drainage infrastructure."
• "Final-year BBA student specialising in finance, with two audit internships."
• "Bilingual (English/Arabic) customer service supervisor in telecoms."

Weak first sentences:

• "Highly motivated and passionate individual." (Says nothing about your work.)
• "Seeking a challenging position in a reputable company." (About your wishes, not your value.)

Use the job title you are targeting when it honestly describes you. If the advert asks for a "Logistics Coordinator" and that is what you do, use those exact words so the reader and any keyword search see the match straight away.

Yes. A graduate summary should lead with your degree, then show practical evidence such as internships, projects or part-time work, and end with the skills the job asks for.

Example (business graduate): "Business Administration graduate (2025) with a concentration in marketing. Completed a three-month internship supporting social media campaigns for a regional retail brand and led a final-year project on customer loyalty programmes. Confident with Excel, Canva and Meta Business Suite; fluent in English and Hindi."

Example (engineering graduate): "Mechanical engineering graduate with hands-on experience from a summer placement in HVAC maintenance. Built a solar-powered water pump as a capstone project with a team of four. Skilled in AutoCAD and SolidWorks and keen to develop in building services."

Tips:

• Mention your graduation year or expected date.
• Name one or two specific experiences rather than listing every course.
• Avoid filling space with traits like "passionate" and "eager"; show them through what you did.
• Keep it to three or four lines.

Base it on what you have done instead of paid work: your studies, school projects, volunteering, sports, clubs or family responsibilities. Then link those to the job you want.

A simple structure:

• Who you are now: "Recent secondary school graduate" or "First-year diploma student".
• What you have done: a project, volunteer role or responsibility.
• What you can offer: two or three practical skills.

Example: "Recent high school graduate looking for a first role in retail. Volunteered every weekend for a year at a community food bank, sorting donations and serving visitors. Comfortable with cash handling from helping in a family shop, and fluent in English and Tagalog."

Keep it honest and specific. A short, concrete summary shows maturity better than claims like "fast learner" or "hard worker" on their own.

At mid-career your summary should lead with your role and years of experience, then focus on your specialism and a couple of results. You no longer need to explain potential; you show a track record.

Example (finance): "Financial analyst with 7 years in FMCG, specialising in budgeting and monthly forecasting. Built the rolling forecast model now used by four country teams and present variance reports to the regional CFO each month. Advanced Excel, Power BI and SAP BPC."

Example (IT support): "IT support specialist with 6 years supporting offices of 200 to 500 users. Run the service desk for a group of private clinics, handling tickets, onboarding and device management in Intune. ITIL Foundation certified."

Points to include:

• Your specialism or industry, so you are not just "an analyst".
• One or two concrete results or responsibilities.
• The tools or certifications the target jobs mention.

Lead with your management scope: what you manage, how many people, and what kind of results you are responsible for. Hiring for a manager is about trust with people, money and outcomes, so the summary should show all three.

Include:

• Your title and the type of team or function you lead.
• The size of the team, budget or operation, if you can share it.
• One or two outcomes your team delivered under your leadership.
• A leadership strength, shown through an example rather than just named.

Example: "Customer service manager with 10 years in banking contact centres. Lead a team of 45 agents and 4 team leaders across two shifts. Introduced a coaching programme that cut repeat calls noticeably within six months, and oversaw the move to a new CRM without service downtime."

Avoid vague lines such as "dynamic leader with excellent people skills". Show the leadership with facts.

An executive summary should show the scale you operate at, the business results you are known for and the kind of organisation you lead best. Readers at board or senior level want strategic impact, not daily tasks.

Cover:

• Your level and function: "Chief Operating Officer", "Regional Finance Director".
• Scale: number of countries, sites, employees or the size of the business unit.
• Two or three signature results, such as a turnaround, expansion or major transformation.
• Your leadership style or specialism in a few words.

Example: "Regional operations director with 18 years in hospitality across the GCC. Lead 14 hotels and around 2,500 staff. Opened five properties on schedule, guided the portfolio through a full brand conversion and built a regional training academy. Known for steady, data-led decision-making and developing local talent."

Keep it to five or six lines, or one line plus three bullets. Use concrete scope instead of words like "visionary" or "transformational".

Start with the role you are moving into, then connect your past experience to it through transferable skills and any new training. The aim is to make the reader see you in the new job, not only the old one.

Structure:

• Target role plus your background: "Teacher moving into instructional design" or "Former sales executive transitioning to HR".
• The skills that carry over, with evidence.
• Any study, certification or project in the new field.

Example: "Secondary school teacher transitioning into learning and development. Designed and delivered a full year of curriculum for over 150 students, including online modules in Moodle. Recently completed a certificate in instructional design and built three e-learning courses in Articulate Rise as portfolio pieces."

Be honest that you are changing direction. Trying to hide it usually backfires, while a clear explanation shows planning and commitment.

Use the summary to lead with your skills and experience, and if you wish, add a brief, positive note about your return. The summary does not need to explain the break in detail.

Two approaches:

• Focus on experience: "HR generalist with 8 years in recruitment and employee relations in the construction sector." The dates in your experience section show the gap, and you can explain it in the cover letter or interview.
• Mention the return briefly: "...returning to work after a planned career break, with refreshed knowledge of current UAE labour practices through a recent HR course."

Either way, show you are up to date: a recent course, volunteering, freelance work or certification helps. Keep any reference to the break short and neutral. You do not need to give personal reasons on a resume.

Say what you are studying, when you graduate, what kind of internship you want and what practical skills you already have. Internship recruiters mainly want to see interest, basic skills and reliability.

Example (computer science): "Third-year computer science student (graduating 2027) seeking a summer software internship. Built a campus events app in React Native used by two student societies, and contributed small fixes to an open-source library. Comfortable with Python, JavaScript and Git."

Example (accounting): "Second-year accounting student at a university in Dubai, looking for an audit or tax internship. Treasurer of the university business club, managing the club budget and monthly reports. Strong Excel skills and working knowledge of QuickBooks."

Add your availability, such as "Available June to August 2027", because internship recruiters plan around dates. Keep it to two to four lines and make sure the projects you mention also appear lower on the resume with more detail.

A nursing summary should state your registration, your clinical area, your years of experience and a strength in patient care. Employers usually check specialism and licence status first.

Example (experienced): "Registered nurse with 6 years in medical-surgical and step-down units. Care for 5 to 7 patients per shift, including post-operative and diabetic patients. BLS and ACLS certified, experienced with Cerner electronic records, and a preceptor for new graduate nurses."

Example (newly qualified): "Newly registered nurse (BSc Nursing, 2025) with clinical placements in paediatrics, emergency and community health. Confident with medication administration, wound care and patient education. BLS certified."

Tips:

• Name your specialty clearly: ICU, ER, OR, paediatrics and so on.
• If your role or country requires a licence, list it in your certifications with its number and expiry as the regulator requires, and mention licence status briefly in the summary.
• Mention patient load or unit size to show your scale of work.

Lead with your engineering focus and level, name the main technologies you work with, and add one result that shows the scale or impact of your work.

Example (mid-level backend): "Backend software engineer with 5 years building payment and order systems in Java and Kotlin. Designed services handling a few million transactions a month on AWS, and led the move from a monolith to event-driven microservices. Comfortable owning features from design to on-call support."

Example (junior frontend): "Frontend developer with 1 year of professional experience in React and TypeScript. Built and maintain the customer dashboard for a SaaS logistics product, with a focus on accessibility and performance."

Tips:

• Put your main language or stack in the first line so a technical reader sees it immediately.
• Avoid long lists of every technology; keep those for the skills section.
• Mention the kind of product or industry you have worked in.

A sales summary should show what you sell, to whom and how well. Name the product or sector, the type of customer, and one result you can honestly stand behind.

Example (B2B): "Sales executive with 5 years selling fleet and telematics solutions to logistics and construction firms. Manage a portfolio of about 60 key accounts and consistently meet or exceed quarterly targets. Strong at long sales cycles, tender responses and C-level presentations."

Example (retail to field sales): "Customer-focused sales associate with 3 years in premium electronics retail. Regularly ranked among the store's top sellers and trained new joiners on product demos. Looking to move into field sales for consumer technology."

If you have target figures, put the exact numbers in your experience bullets, where there is room to give context such as the period and the size of the target.

Mention your subject and age group, the curriculum you teach, your years of experience and something that shows your impact on students or the school.

Example (secondary): "Mathematics teacher with 8 years teaching IGCSE and A Level in British-curriculum schools. Head of Year 10 and coordinator of the school's maths olympiad team. Use data from regular assessments to plan targeted support groups."

Example (early years): "Early years teacher with 4 years in EYFS classrooms in Abu Dhabi and London. Plan play-based learning for classes of up to 24 children and lead parent workshops on early reading."

Tips:

• Name the curriculum (British, American, IB, CBSE, national) because many schools hire for a specific one.
• Mention extra responsibilities like head of department, exam coordinator or club leader.
• Include your teaching qualification if the school asks for one.

Show the channels you handle (phone, chat, email, in person), the volume or type of customer, and a strength such as resolving complaints or staying calm under pressure.

Example: "Customer service representative with 3 years in a busy telecom contact centre. Handle around 60 calls and chats a day on billing and technical issues, and regularly receive positive customer feedback in quality reviews. Fluent in English, Arabic and Urdu."

Example (entry level): "Friendly, reliable retail cashier moving into customer support. Two years of daily customer contact, handling returns, complaints and loyalty sign-ups. Comfortable with POS systems and learning new software quickly."

Languages are a real strength in customer service, so mention them in the summary if the role serves a multilingual customer base.

Name your area of civil engineering, the type and size of projects, your role on them and any professional registration. Engineering managers look for relevant project experience first.

Example: "Civil engineer with 9 years in road and infrastructure projects in the UAE and India. Led site engineering on a 12 km highway upgrade and supervised drainage works for a new residential community. Experienced with AutoCAD Civil 3D, quantity take-offs and coordination with consultants and municipalities."

Example (graduate): "Graduate civil engineer with a year of site experience on a mid-rise residential project. Supported setting out, daily progress reports and quality inspections of concrete works."

Tips:

• Mention project types (roads, bridges, high-rise, utilities) and your role (design, site, planning, QA/QC).
• Include project scale through length, floors or value range only if it is accurate and not confidential.
• List registrations with an engineering body if you hold them.

Say which part of HR you specialise in (recruitment, payroll, employee relations, learning, generalist), the size and type of organisation, and a result or system you are known for.

Example: "HR generalist with 7 years supporting a workforce of about 1,200 in hospitality. Run end-to-end recruitment for frontline roles, onboarding and visa coordination, and handle employee relations cases. Implemented a new HRIS module for leave and attendance."

Example (recruiter): "In-house recruiter with 4 years hiring for technology and engineering roles. Fill around 80 positions a year and built a graduate hiring programme with three local universities."

Keep the language concrete. Phrases like "people person" add little; scope, systems and outcomes tell the reader more.