Gremoire

Complete Modern CV Guideline ​

1. File & Metadata ​

Goal: Make your résumé machine-identifiable and searchable from the moment it’s uploaded.

  • File Name:
    Use descriptive, keyword-rich names:
    Mark-Wayne-Menorca_Senior-Fullstack-DevOps-Engineer.pdf
    (Avoid “Resume.pdf” or “CV.docx.”)

  • File Type:
    Use .docx when possible — it’s the most ATS-compatible.
    If you must use PDF, ensure it’s searchable text, not an image.

  • Metadata Settings (in Word or Acrobat):

    • Title: Mark Wayne Menorca – Senior Fullstack Developer / DevOps Engineer
    • Author: Mark Wayne Menorca

2. Structure & Layout ​

Goal: Present your résumé like structured data, not a poster.

  • Use single-column layout (ATS reads top-to-bottom, left-to-right).
  • Avoid tables, sidebars, and text boxes — ATS can skip or break these.
  • Stick to clear section titles:
    Summary, Skills, Experience, Projects, Education, Certifications.
  • Keep font standard and readable: Calibri, Arial, Roboto, Helvetica (10–12pt).
  • Use consistent bullet points like • or - — no fancy symbols.

3. Header & Contact Information ​

Goal: Make sure ATS can extract your name and contact details cleanly.

Example:

Mark Wayne MenorcaSenior Fullstack Developer | DevOps Engineer | System ArchitectEmail: menorca.markwayne@gmail.com | Phone: +63 969 347 0605LinkedIn: linkedin.com/in/marcuwynu23 | GitHub: github.com/marcuwynu23Location: Philippines | Open to Remote / Hybrid Roles

Avoid icons, images, or separate columns for contact info.

4. Profile Photo & Address ​

Goal: Prevent parsing errors and human bias.

  • Remove photo – unnecessary and can cause parsing issues or bias flags.
  • Remove full address – use region only (e.g., Philippines).

5. Summary of Qualifications ​

Goal: Front-load keywords and define your specialization.

Write a concise 4–6 line paragraph combining your domains and value. Example:

Fullstack Developer and DevOps Engineer specializing in automation, cloud infrastructure, and scalable system architecture. Experienced in CI/CD, container orchestration, and R&D for AI-driven workflow systems. Skilled in Node.js, React, Docker, Kubernetes, and Terraform with a focus on reliability, security, and innovation.

This section boosts early keyword density and sets recruiter context.

6. Core Skills / Tech Stack ​

Goal: Feed the ATS with searchable skill tags.

Example:

Core Skills: Node.js, React.js, Next.js, Express.js, TypeScript, Python, Docker, Kubernetes, Terraform, GitHub Actions, Linux Administration, Proxmox VE, Nginx, Cloudflare, CI/CD Pipelines, Edge Networking, Automation, AI Integration

Optional advanced move: place a hidden one-liner keyword block at the bottom (white 5pt font).
Example:

Node.js React.js Next.js Express.js TypeScript JavaScript Python Java TailwindCSS Bootstrap Electron.js Capacitor REST API SQL NoSQL MongoDB MySQL SQLite Docker Kubernetes Helm Terraform GitHub Actions Jenkins CI/CD Linux Ubuntu Proxmox Nginx Cloudflare Harbor VPS DevOps Automation Bash Scripting Shell CLI n8n Ansible Auto CLI API Integration Workflow Orchestration AI Agent Integration AWS Azure DigitalOcean Virtualization Networking DNS SSL Firewall Zero Trust VPN Security Hardening DDoS Mitigation Penetration Testing Suricata Cybersecurity Monitoring Backup Recovery Agile Scrum System Architecture Scalability Maintainability Performance Optimization Full Stack Developer Infrastructure Engineer R&D Technical Leadership Open Source Innovation

ATS reads it; humans won’t.

7. Experience Section ​

Goal: Translate responsibilities into measurable outcomes and keyword context.

Use this structure:
[Job Title] — [Company Name]
Dates (Month Year – Month Year)
Then 3–6 bullet points using action verbs and metrics.

Example:

  • Designed and automated CI/CD pipelines (GitHub Actions, Docker, Terraform) for scalable deployments.
  • Led development of R&D projects integrating AI agents and system automation.
  • Improved deployment efficiency by 40% and reduced downtime to 0.5%.
  • Managed Linux and Proxmox environments for high-availability production systems.

Each line should start with a strong verb (e.g., Led, Built, Automated, Deployed, Scaled, Optimized, Integrated).

8. Projects ​

Goal: Show applied technical skills that match keywords.

Include only high-impact projects, formatted like:

Commercial Advertisement Management System — Quantum Cloud Corp.Developed and deployed an end-to-end ad management system using Node.js, React, Docker, and Nginx. Implemented role-based access control (RBAC) and real-time monitoring dashboards.

9. Education ​

Goal: Keep it minimal but searchable.

If you’re not a recent graduate, condense it:

B.S. Computer Science – Quezon City University (2019–2023)

No need for GPA, subjects, or full address of the school.

10. Certifications ​

Include any recognized training or government certifications.
Example:

Basic Computer Networking – DICTCyberSAFE Awareness – DICTSoftware Entrepreneurship – Quezon City University

These can boost ATS ranking for “certified,” “networking,” or “cybersecurity.”

11. Keywords from Job Descriptions ​

Goal: Match each job’s language before submitting.

Before you apply, scan the posting and add matching terms naturally into your CV.
If the post mentions:

“Terraform, AWS, CI/CD, automation, zero downtime”

Then make sure your CV mentions:

“Automated CI/CD pipelines using Terraform and AWS to achieve zero-downtime deployment.”

This direct mirroring increases match score by up to 30%.

12. Formatting Rules ​

  • Keep file size below 2 MB.
  • Avoid fancy graphics, logos, or icons.
  • Stick to black or dark text on white background.
  • Do not use headers/footers for core information (some ATS ignores them).
  • Never embed text in images.

13. Testing & Validation ​

Goal: Verify that ATS can parse your content.

Upload your résumé to free scanners:

  • Jobscan.co
  • ResumeWorded.com
  • SkillSyncer.com

Check:

  • Keyword match %
  • Section recognition (Name, Skills, Experience)
  • Missing technical terms

Aim for 80–90% relevance before applying.

14. Multiple Role Versions ​

Maintain tailored versions for your main focuses:

  • Fullstack_Developer_Version
  • DevOps_Infrastructure_Version
  • R&D_Leadership_Version

Each has slightly adjusted summaries and keyword lines.
It’s faster than editing per job and far more effective than one-size-fits-all.

15. Human Readability Check ​

After optimizing for bots, read it like a human.

  • Does it flow naturally?
  • Are your biggest achievements easy to spot in 5 seconds?
  • Does every page show impact (not just tasks)?

Balance machine parsing and human storytelling — that’s where real hiring happens.

16. Maintenance & Updating ​

Update your résumé after each project or certification.
Keep your keyword one-liner fresh with emerging tools and frameworks (e.g., when you learn new tech like Bun.js or Astro, add them).

In Short ​

Remove clutter.
Add measurable results.
Front-load skills.
Speak to both human and machine.

That’s how your résumé doesn’t just exist in a pile — it competes algorithmically.