The Honest Approach to Resume Building on macOS
Most people waste two hours on a resume because they pick the wrong tool for the job. macOS comes with Numbers, Pages, and TextEdit, and each one solves a completely different problem. Picking the wrong one means your resume looks fine on screen and gets rejected by an ATS scanner in three seconds. Here is the way I actually do it. Start by opening Numbers from Applications. Yes, it is a spreadsheet program, and that is exactly why it works for resume layout. The grid gives you control over columns and spacing that Pages never offers without fighting you. I built dozens of resumes using Numbers because columns don't drift around when you tweak them. The one gotcha with Numbers is that it defaults to a very spreadsheet-y aesthetic. You will need to turn off gridlines, adjust cell heights manually, and format text to look like a document, not a table. If you want something faster and your resume is simple enough, open Pages. Go to File > New from Template Chooser and look under the Personal section. The resume templates there are clean and require almost zero formatting work. The downside is that once you start editing beyond the template text, you will find yourself wrestling with text boxes that behave unpredictably. They float where they want to float and refuse to stay aligned. For a one-page resume with standard sections, Pages is fine. For anything that needs precise control, switch to Numbers.
I ran into a specific problem last year that nobody warns you about. I built a resume in Pages using a two-column layout, exported it to PDF, and sent it to a candidate who was getting no interview callbacks. I spent an hour trying to figure out why. The issue was invisible text. Pages wraps column layouts in objects that some ATS parsers read as jumbled character sequences instead of actual text. The resume looked perfectly normal to a human eye. The scanner saw garbage. I exported the content as plain text using TextEdit, recreated it in Numbers with explicit table cells, and re-exported to PDF. The ATS parsed it cleanly after that. If you are targeting companies that use greenhouse, lever, or workday applicant tracking systems, do not use a multi-column Pages template without testing it against a free ATS checker first. TextEdit deserves a mention even though it sounds too basic. It handles plain text resumes flawlessly. Open TextEdit, go to Format > Make Plain Text, and type your resume. Save it as a .txt file. If a job posting asks for a text-only resume or you are pasting directly into a web form, this is your tool. There are no formatting bugs, no hidden characters, and no possibility of an ATS misreading your layout. It cannot handle any bolding or italics, which is both its limitation and its advantage. For the actual writing, keep the resume itself separate from the template. Write and edit all your content in a notes app or a plain text editor first. Once the content is solid, move it into Numbers or Pages. This way you are not constantly fighting the layout while also rewriting bullet points. Most people do it backwards and spend more time adjusting margins than they do improving their wording.
When you export from either Numbers or Pages, choose PDF. Both applications produce clean, compressed PDFs that are universally accepted. Do not export as a Word document unless a job posting specifically requests it. Mac-generated .docx files occasionally carry formatting artifacts from Apple's layout engine that Windows Word interprets differently, which can shift your alignment and make a polished resume look sloppy. If you need something more advanced and you already know LaTeX, MacTeX is available and produces publication-quality resumes. The learning curve is steep, but the output is consistent across every system in the world. This matters for academic and technical roles where resume formatting precision is actually evaluated. For most people, it is not worth the time investment. The whole process from blank screen to finished PDF usually takes about 45 minutes if you already have your content written. It can take three or four hours if you are figuring out the tool and the layout at the same time. Pick your tool based on how much control you need, write the content first, and export to PDF only after you have verified the ATS readability.
Common Mistakes That Ruin Your Resume on Mac
Exporting from Pages without checking the PDF output in Preview first is the most common error. Pages sometimes embeds fonts in a way that looks correct on your screen but renders differently when opened elsewhere. Always open the exported PDF in Preview and zoom in to check that spacing and alignment look identical to your working document. If they do not, your resume may look broken to whoever actually reads it. Another issue specific to Numbers is that the default row height and column width settings create awkward white space that makes your resume look sparse and underdeveloped. Adjust these manually to match standard resume margins rather than accepting the spreadsheet defaults. This typically cuts the number of pages needed by half for a two-page resume and keeps a one-pager looking dense and professional. If you are building a resume for a creative role, neither Numbers nor Pages gives you the control you would need for visual design work. In that case, use a dedicated tool like Canva or Figma. These are not Mac apps, but they handle design-level precision that the built-in Apple tools simply cannot match. The tradeoff is that creative resumes with heavy visual elements are often less ATS-friendly by design, so verify that you are submitting them through channels that accept visual formats rather than keyword parsers.
The template libraries built into Pages and Numbers include designs that look good but are difficult to customize without breaking the layout. When you deviate from the template structure, you frequently end up with text boxes that resize unpredictably or columns that collapse. My recommendation is to start with a blank canvas and build the layout from scratch using basic tables or text frames. It takes slightly longer upfront but saves you from the rearrangement headaches that come later when you update your resume for different applications.
A Quick Recommendation
Use Numbers for resumes that need precise layout control and ATS compatibility. Use Pages for quick, straightforward templates where formatting complexity is low. Use TextEdit if the receiving system requires plain text. Avoid exporting to Word format unless explicitly asked. Test any multi-column PDF through an ATS simulator before sending it to a real employer. The difference between a resume that gets read and one that gets filtered is rarely the content alone. It is the technical delivery. A well-written resume that an ATS cannot parse correctly is functionally the same as one that was never written. Pick the tool that minimizes delivery risk and spend the rest of your time on the actual writing.
Get the Full Details
