Przykład CV, WordPress Developer

Choose the right format for a WordPress Developer resume

Use a reverse-chronological format unless you are making a significant career pivot. Hiring managers at agencies and in-house teams expect to scan your most recent role first, and applicant tracking systems (ATS) parse this layout most reliably. Keep the document to one page if you have fewer than eight years of experience; two pages is acceptable beyond that.

Stick to a single-column layout for roles at larger companies that route applications through an ATS. A two-column design is fine when you are applying directly to a boutique agency or submitting a PDF to a human contact. Use standard section headings — Summary, Experience, Skills, Education — so parsers do not drop your data.

• File format: PDF unless the job posting explicitly requests .docx
• Font: Inter, Calibri, or Georgia at 10–12 pt; section headings at 13–14 pt
• Margins: 0.75–1 inch on all sides
• No photos, no icons, no QR codes — they confuse most ATS software

Write a professional summary that positions you immediately

Your summary sits below your name and contact line. It should run three to four sentences and answer: what kind of WordPress developer you are, your strongest technical differentiator, and the business value you deliver. Tailor it for each application by mirroring keywords from the job description — phrases like 'headless WordPress,' 'WooCommerce,' or 'performance optimization' should appear here if they appear in the posting.

Example: "WordPress Developer with seven years building custom themes and plugins for e-commerce and media clients. Specialize in WooCommerce customization, REST API integrations, and Core Web Vitals optimization, routinely cutting page load times by 40 percent or more. Comfortable owning full project cycles from discovery through deployment on WP Engine and Kinsta. Seeking a senior role where performance engineering and scalable architecture are priorities."

Write work-experience bullets that prove impact with numbers

Each bullet should follow an action-verb → task → result structure. Vague bullets like 'maintained WordPress sites' are invisible to both recruiters and ATS. Quantify wherever possible: page-speed scores, uptime percentages, revenue figures, number of plugins built, team size managed, or client count. If you do not have a hard number, use a reasonable range or a before/after comparison.

Pull your metrics from Google Search Console, Lighthouse audits, WooCommerce revenue dashboards, or client reports before you write the resume so you are not guessing.

• Rebuilt a WooCommerce storefront on a headless WordPress + Next.js stack, improving Largest Contentful Paint from 6.2 s to 1.8 s and lifting conversion rate by 22 percent over 90 days.
• Developed and maintained 14 custom Gutenberg block plugins for a digital-publishing client, reducing editorial production time by 35 percent and eliminating a $28,000/year third-party page-builder license.

List the skills and certifications recruiters and ATS actually search for

Create a dedicated Skills section and populate it with the specific tools and technologies that appear in job postings for your target roles. Do not pad it with soft skills — those belong in your bullets or summary. Certifications carry real weight: WooCommerce's official developer certification, Zend PHP Engineer certification, and AWS Certified Developer (if you handle cloud infrastructure) are all recognized. Yoast's SEO for Developers course is worth listing for content-heavy roles.

Group skills by category so a recruiter can scan them in under ten seconds.

• Core: PHP 8.x, JavaScript (ES6+), HTML5, CSS3/Sass
• WordPress-specific: Custom theme development, plugin architecture, Gutenberg/Block Editor, WP-CLI, WordPress REST API, WooCommerce, ACF Pro, Elementor (Pro)
• Headless/decoupled: Next.js, React, GraphQL, WPGraphQL
• DevOps & hosting: Git/GitHub, Docker, WP Engine, Kinsta, Cloudflare, CI/CD pipelines
• Performance & SEO: Lighthouse, Google Search Console, Core Web Vitals, Yoast SEO, caching (Redis, Varnish, W3 Total Cache)

Handle education, licenses, and extras correctly

A bachelor's degree in Computer Science, Information Technology, or a related field is preferred at enterprise employers but is not a hard requirement at most agencies and startups. If you are self-taught or boot-camp trained, list the program name, the credential earned, and the completion year. Place education below Skills unless you are within two years of graduation.

Add a Portfolio or Projects section immediately after Experience if your GitHub profile or live sites demonstrate work that your job titles do not. List the URL, the stack used, and one measurable outcome per project. A link to a live WooCommerce store you built is worth more than a degree line to most hiring managers in this field.

• Relevant certifications to list: Zend Certified PHP Engineer, WooCommerce Developer Certification, AWS Certified Developer – Associate, Google Analytics Certification
• Always include a GitHub URL and a portfolio URL in your contact header
• Open-source contributions to WordPress core or popular plugins belong in a separate 'Contributions' line — they signal credibility immediately

Mistakes to avoid

• ×Listing WordPress as a single skill without specifying whether you build custom themes, custom plugins, headless architectures, or WooCommerce stores — specificity is what gets you past ATS keyword filters.
• ×Using page-builder buzzwords like 'Elementor expert' as your primary differentiator when the role requires PHP and plugin development, which signals you cannot code at the level the job requires.
• ×Omitting Core Web Vitals scores or performance benchmarks from your experience bullets, even though site speed is one of the most measurable and valued skills in modern WordPress development.
• ×Including a portfolio link that goes to a broken site, a password-protected staging URL, or a GitHub profile with no README files — always verify every URL before submitting the resume.

Frequently asked questions

Do WordPress Developer resumes need a portfolio link?

Yes — treat the portfolio URL as mandatory, not optional. Most hiring managers will look at live sites or a GitHub profile before they finish reading your resume. If your portfolio is not ready, link to your best single project rather than leaving the field blank.

Should I list WordPress page builders like Elementor or Divi on my resume?

List them only if the job description mentions them or if the role is clearly a site-builder position rather than a developer role. For custom-theme and plugin development jobs, leading with page builders can signal that you rely on visual tools instead of writing PHP, which may disqualify you before a phone screen.

How do I show WordPress experience if most of my work is under NDA?

Describe the project type, scale, and outcome without naming the client — for example, 'enterprise healthcare portal serving 200,000 monthly users.' You can also build one or two public side projects specifically to demonstrate your technical range and link to those in a Projects section.