LanjutATS resume example, section by section
By Rizki Citra · Updated
Below is one complete résumé, the sample that ships with Lanjut, in five of its twenty templates. Click any one to see every page. Under them is the same résumé as plain text. That text is what an applicant tracking system (ATS) works from. If it reads in the right order, the résumé does its job.
On this page
- Awal
- Tebal
- Klasik
- Ketik
- Tegas
- See all twenty templates
What makes this example ATS-friendly
The five templates above look different, but the plain text under them is the same for all five, and for the other fifteen too. That is the whole idea. A template may change the type, the spacing, and the accents. It never changes the order of what you wrote.
The example follows five rules:
- One column. The text runs from top to bottom. A two-column layout can make a parser mix lines from both columns into one.
- Standard headings. Summary, Experience, Education, Skills. A parser looks for these words to sort your text. “My journey” or “What I bring” does not match anything.
- Real text. Every word is text that can be selected and copied. Nothing important sits inside an image, a chart, or a text box.
- One date format. Each entry uses the same pattern, such as “Mar 2022 – Present”. Mixed formats make dates harder to read in order.
- Contact details as text. The phone number, email, and links are written out in the header, not hidden behind an icon alone.
The header
The header holds the name, a job title, and contact details: phone, email, a website, LinkedIn, GitHub, and a city. Put the job title you are applying for, not a slogan. “Software Engineer” helps a recruiter search. “Passionate problem solver” does not.
A photo is optional. In Lanjut it is off by default. Many companies outside Indonesia prefer no photo, and a photo never changes the text a parser reads.
The summary
Two or three lines about who you are and what you are good at. The example opens with years of experience and the main tools:
Software engineer with 8+ years building reliable web services and applications for fintech and SaaS.
Write it last, after the rest of the résumé. Then you can pick the two or three facts that matter most for the job you want.
Experience
Each job has the same parts in the same order: job title, company, location, dates, then a short list of what you did. Start each line with a verb, and give a number where you can:
Cut p95 API latency 55% with query tuning and caching, bringing it from 480ms to 210ms.
The number tells a recruiter the size of the work. It also gives an ATS a clear line to match against the job description. Keep three to six lines for a recent job, and fewer for older ones. Lanjut sorts entries by date, newest first, so the order stays right as you add jobs.
Education, certifications, skills, and languages
These sections are short and factual. Education lists the school, the degree, and the dates. Certifications list the name and who issued it. Skills and languages list a name and, if you want, a level such as “Advanced” or “Native”.
Write a skill the way the job ad writes it. If the ad says “PostgreSQL”, write “PostgreSQL”, not only “SQL databases”.
If you are a fresh graduate
You may have little or no work experience. That is fine. The same rules apply, with different sections doing the work:
- Internship for internships, with the same format as a job.
- Projects for course, thesis, or personal projects. Say what you built and what it did.
- Organizations for student groups and volunteer roles. One line with a number is enough, such as “Grew the club from 30 to 120 members.”
If your skills are stronger than your experience, open the Section order menu in Lanjut and choose Skills first. Your entries still keep their date order.
Mistakes this example avoids
- A table to line up dates or skills. Tables often come out of a parser in the wrong order.
- Text in the page header or footer area, which some systems skip.
- Contact details that exist only as icons.
- A creative heading where a standard one is expected.
- A scanned PDF. A scan is an image, so there is no text to read at all.
How to check your own résumé
Open your PDF, select all the text, and paste it into a plain text editor. If the result reads in the right order, with your name first and each heading followed by its entries, a parser can read it too. The home page of Lanjut runs this same check on a real PDF while you watch.
Use this example
Open the editor and choose the sample as your starting point. Replace the text with your own, section by section. The readiness meter in the editor shows what is still missing, and it counts only your own words, not the sample’s.