{"id":12298,"date":"2026-03-13T14:02:46","date_gmt":"2026-03-13T13:02:46","guid":{"rendered":"https:\/\/jobwinner.ai\/resume-examples\/it-site-reliability-engineer\/"},"modified":"2026-03-13T14:02:48","modified_gmt":"2026-03-13T13:02:48","slug":"ingenieur-en-fiabilite-des-sites-informatiques","status":"publish","type":"resume-examples","link":"https:\/\/jobwinner.ai\/fr\/exemples-de-cv\/ingenieur-en-fiabilite-des-sites-informatiques\/","title":{"rendered":"Exemples et bonnes pratiques de CV pour un ing\u00e9nieur en fiabilit\u00e9 des sites informatiques"},"content":{"rendered":"<div class=\"wrap\">\n<section id=\"example\">\n<p style=\"margin:0 0 14px; max-width:84ch;\">\n      If you need an IT Site Reliability Engineer resume example you can directly adapt, you are in the right place. Below you\u2019ll see three full samples plus a concise, actionable playbook to sharpen bullet points, quantify impact, and tailor your SRE resume to any job post\u2014no exaggeration required.\n    <\/p>\n<h2>1. IT Site Reliability Engineer Resume Example (Full Sample + What to Copy)<\/h2>\n<p>If you searched \u201cresume example,\u201d you\u2019re likely seeking two things: a concrete sample to modify and precise guidance on how to personalize it. The Harvard-style layout below is a trusted default for IT Site Reliability Engineers because it\u2019s scannable, clean, and typically ATS-compliant.<\/p>\n<p>Use this as a model, not a script. Mirror the organization and level of detail, then substitute in your authentic experience. If you\u2019d like a jumpstart, try the <a href=\"https:\/\/jobwinner.ai\/resume-builder\/\">resume builder<\/a> or <a href=\"https:\/\/jobwinner.ai\/resume-tailoring\">tailor your resume for an IT SRE job<\/a> instantly.<\/p>\n<div class=\"visual quickstart-box\">\n<h3>Quick Start (5 minutes)<\/h3>\n<ol>\n<li>Pick one resume example below similar to your SRE focus<\/li>\n<li>Transfer the structure, swap in your real achievements<\/li>\n<li>Reorder bullets to display your top impact first<\/li>\n<li>Run the ATS check (section 6) before submitting<\/li>\n<\/ol><\/div>\n<h3>What you should copy from these examples<\/h3>\n<ul>\n<li><strong>Header with proof links<\/strong>\n<ul>\n<li>Share your GitHub, technical blog, or monitoring dashboards that reinforce your expertise.<\/li>\n<li>Keep header links straightforward to maximize clickability in PDFs.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Evidence-driven bullets<\/strong>\n<ul>\n<li>Highlight tangible outcomes (uptime, incident reduction, deployment speed, cost savings) beyond daily duties.<\/li>\n<li>Seamlessly mention key SRE tools (monitoring, IaC, cloud) within the bullet.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Skills organized by domain<\/strong>\n<ul>\n<li>List areas like Automation, Monitoring, Cloud, Scripting for fast review.<\/li>\n<li>Prioritize the tools and platforms that match the SRE job requirements, not every tool you\u2019ve ever touched.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Below are three resume samples in distinct formats. Choose the one closest to your level and specialization, then personalize the content to match your actual background. To explore more <a href=\"https:\/\/jobwinner.ai\/resume-examples\">role-specific resume samples<\/a>, visit our resource hub.<\/p>\n<div class=\"visual resume-card\" tabindex=\"0\" aria-label=\"IT Site Reliability Engineer resume example, classic Harvard style\">\n<div class=\"resume-base resume-classic\">\n<p class=\"name\">Jordan Kim<\/p>\n<p class=\"title\">IT Site Reliability Engineer<\/p>\n<p class=\"contact\">\n          jordan.kim@example.com \u00b7 555-111-2222 \u00b7 New York, NY \u00b7 linkedin.com\/in\/jordankim \u00b7 github.com\/jordansre\n        <\/p>\n<div class=\"sec\">\n<p class=\"sec-title\">Professional Summary<\/p>\n<div class=\"rule\"><\/div>\n<p class=\"summary-p\">\n            IT Site Reliability Engineer with 7+ years ensuring robust service delivery for mission-critical cloud platforms. Skilled in automating infrastructure, managing incident response, and driving reliability improvements using Python, Terraform, and AWS. Recognized for building proactive monitoring solutions and reducing operational burden through sensible automation and process refinement.\n          <\/p>\n<\/p><\/div>\n<div class=\"sec\">\n<p class=\"sec-title\">Professional Experience<\/p>\n<div class=\"rule\"><\/div>\n<div class=\"row\">\n<div><strong>CloudOps Solutions<\/strong>, IT Site Reliability Engineer, New York, NY<\/div>\n<div class=\"right\">Mar 2019 to Present<\/div>\n<\/p><\/div>\n<ul class=\"bullets\">\n<li>Automated deployment pipelines with Terraform and Jenkins, decreasing deployment time by 60% and cutting human error.<\/li>\n<li>Engineered monitoring and alerting using Prometheus and Grafana, resulting in 45% fewer critical incidents over 12 months.<\/li>\n<li>Created self-healing scripts in Python that remediated common node failures, improving system uptime to 99.98%.<\/li>\n<li>Collaborated with product and dev teams to implement SLOs and error budgets, aligning reliability goals across departments.<\/li>\n<li>Led incident response drills and blameless postmortems, lowering MTTR by 30% and increasing on-call readiness.<\/li>\n<\/ul>\n<div class=\"row\">\n<div><strong>DataGrid Technologies<\/strong>, Systems Engineer, Jersey City, NJ<\/div>\n<div class=\"right\">Jun 2016 to Feb 2019<\/div>\n<\/p><\/div>\n<ul class=\"bullets\">\n<li>Maintained Linux-based infrastructure supporting SaaS apps for 10k+ users, with uptime consistently above 99.95%.<\/li>\n<li>Deployed configuration management via Ansible, standardizing server builds and reducing provisioning times by 50%.<\/li>\n<li>Integrated centralized log aggregation using ELK Stack, accelerating root cause analysis during outages.<\/li>\n<li>Documented standard operating procedures that improved onboarding efficiency for new SRE team members.<\/li>\n<\/ul><\/div>\n<div class=\"sec\">\n<p class=\"sec-title\">Skills<\/p>\n<div class=\"rule\"><\/div>\n<div class=\"two-col\" aria-label=\"Skills in two columns\">\n<div><strong>Automation:<\/strong> Python, Bash, Ansible<\/div>\n<div><strong>Cloud\/Infra:<\/strong> AWS, Terraform, Docker, Kubernetes<\/div>\n<div><strong>Monitoring:<\/strong> Prometheus, Grafana, ELK Stack<\/div>\n<div><strong>Practices:<\/strong> Incident Response, CI\/CD, SLO\/SLA Management<\/div>\n<\/p><\/div>\n<\/p><\/div>\n<div class=\"sec\">\n<p class=\"sec-title\">Education and Certifications<\/p>\n<div class=\"rule\"><\/div>\n<div class=\"row\">\n<div><strong>Stevens Institute of Technology<\/strong>, BSc Information Systems, Hoboken, NJ<\/div>\n<div class=\"right\">2016<\/div>\n<\/p><\/div>\n<div class=\"row\" style=\"margin-top: 6px;\">\n<div><strong>Google Professional SRE Certification<\/strong>, Online<\/div>\n<div class=\"right\">2021<\/div>\n<\/p><\/div>\n<div class=\"row\" style=\"margin-top: 6px;\">\n<div><strong>AWS Certified SysOps Administrator<\/strong>, Online<\/div>\n<div class=\"right\">2022<\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<p>      <a class=\"resume-overlay\" href=\"https:\/\/app.jobwinner.ai\/register\" target=\"_blank\" rel=\"noopener\" aria-label=\"Go to JobWinner to enhance this resume\"><br \/>\n        <span class=\"cta-btn\">Enhance my Resume<\/span><br \/>\n      <\/a>\n    <\/div>\n<p>If you favor a streamlined, contemporary style with the same ATS compatibility, the next sample features a modern layout and a slightly different skills-to-proof hierarchy.<\/p>\n<div class=\"visual resume-card\" tabindex=\"0\" aria-label=\"IT Site Reliability Engineer resume example, modern minimal style\">\n<div class=\"resume-base resume-modern\">\n<div class=\"top\">\n<div>\n<p class=\"name\">Priya Verma<\/p>\n<p class=\"title\">Cloud Site Reliability Engineer<\/p>\n<p>            <span class=\"pill\">Kubernetes \u00b7 observability \u00b7 automation<\/span>\n          <\/div>\n<p class=\"contact\">\n            priya.verma@example.com<br \/>\n            555-333-4455<br \/>\n            Toronto, Canada<br \/>\n            linkedin.com\/in\/priyaverma<br \/>\n            github.com\/priyaverma\n          <\/p>\n<\/p><\/div>\n<div class=\"sec\">\n<p class=\"sec-title\">Professional Summary<\/p>\n<div class=\"rule\"><\/div>\n<p class=\"summary-p\">\n            SRE specializing in cloud-native operations, with 5+ years deploying scalable systems in AWS and GCP. Adept at Kubernetes admin, automated incident response, and designing dashboards for actionable observability. Known for reducing toil and increasing deployment safety through infrastructure-as-code and robust monitoring.\n          <\/p>\n<\/p><\/div>\n<div class=\"sec\">\n<p class=\"sec-title\">Professional Experience<\/p>\n<div class=\"rule\"><\/div>\n<div class=\"row\">\n<div><strong>BluePeak Digital<\/strong>, Cloud Site Reliability Engineer, Toronto, Canada<\/div>\n<div class=\"right\">May 2020 to Present<\/div>\n<\/p><\/div>\n<ul class=\"bullets\">\n<li>Implemented end-to-end monitoring for microservices using Prometheus, driving a 40% faster response to production alerts.<\/li>\n<li>Automated cluster scaling and node health checks with Kubernetes operators, supporting traffic spikes with zero downtime.<\/li>\n<li>Built CI\/CD workflows with GitHub Actions and ArgoCD, reducing manual deployment steps and increasing team release frequency.<\/li>\n<li>Defined SLOs and SLIs with engineering teams to better align service metrics with business reliability goals.<\/li>\n<li>Orchestrated blameless retrospectives post-incident, resulting in 25% reduction in recurring outages.<\/li>\n<\/ul>\n<div class=\"row\">\n<div><strong>CoreStack IT<\/strong>, DevOps Engineer, Montreal, Canada<\/div>\n<div class=\"right\">Sep 2017 to Apr 2020<\/div>\n<\/p><\/div>\n<ul class=\"bullets\">\n<li>Migrated legacy on-prem apps to AWS, using Terraform for reproducible, secure cloud environments.<\/li>\n<li>Optimized build pipelines, cutting average deployment time from 40 minutes to under 10 minutes per release.<\/li>\n<li>Created automated rollback scripts for failed releases, reducing customer-facing incidents by about 30%.<\/li>\n<\/ul><\/div>\n<div class=\"sec\">\n<p class=\"sec-title\">Skills<\/p>\n<div class=\"rule\"><\/div>\n<div class=\"two-col\">\n<div><strong>Automation:<\/strong> Bash, Python, Terraform<\/div>\n<div><strong>Cloud\/Infra:<\/strong> AWS, GCP, Docker, Kubernetes<\/div>\n<div><strong>Monitoring:<\/strong> Prometheus, Grafana, Datadog<\/div>\n<div><strong>Practices:<\/strong> CI\/CD, SLI\/SLO Management, Incident Response<\/div>\n<\/p><\/div>\n<\/p><\/div>\n<div class=\"sec\">\n<p class=\"sec-title\">Education and Certifications<\/p>\n<div class=\"rule\"><\/div>\n<div class=\"row\">\n<div><strong>University of Toronto<\/strong>, BSc Computer Engineering, Toronto, Canada<\/div>\n<div class=\"right\">2017<\/div>\n<\/p><\/div>\n<div class=\"row\" style=\"margin-top: 6px;\">\n<div><strong>CKAD: Certified Kubernetes Application Developer<\/strong>, Online<\/div>\n<div class=\"right\">2021<\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<p>      <a class=\"resume-overlay\" href=\"https:\/\/app.jobwinner.ai\/register\" target=\"_blank\" rel=\"noopener\" aria-label=\"Go to JobWinner to enhance this resume\"><br \/>\n        <span class=\"cta-btn\">Enhance my Resume<\/span><br \/>\n      <\/a>\n    <\/div>\n<p>If your specialty is automation or high-velocity incident management, recruiters expect direct evidence of reducing toil, improving reliability, and using core SRE tooling. The next compact sample is optimized to foreground technical proof and reliability wins.<\/p>\n<div class=\"visual resume-card\" tabindex=\"0\" aria-label=\"IT Site Reliability Engineer resume example, compact technical style\">\n<div class=\"resume-base resume-compact\">\n<div class=\"header\">\n<p class=\"name\">Samuel Lee<\/p>\n<p class=\"title\">Automation Site Reliability Engineer<\/p>\n<p class=\"contact\">\n            samuel.lee@example.com \u00b7 555-888-7777 \u00b7 Austin, TX \u00b7 linkedin.com\/in\/samuellee \u00b7 github.com\/samuelsre\n          <\/p>\n<\/p><\/div>\n<p class=\"tagline\">Focus: Automation \u00b7 Python \u00b7 Cloud Monitoring \u00b7 Incident Response<\/p>\n<div class=\"sec\">\n<p class=\"sec-title\">Professional Summary<\/p>\n<div class=\"rule\"><\/div>\n<p class=\"summary-p\">\n            Automation-focused SRE with 6 years of experience building resilient infrastructure and incident response tooling. Improved system reliability and reduced operational workload through Python scripting, advanced monitoring (Datadog, ELK), and proactive process automation. Collaborates with cross-functional teams to deliver continuous improvement in uptime and recovery.\n          <\/p>\n<\/p><\/div>\n<div class=\"sec\">\n<p class=\"sec-title\">Professional Experience<\/p>\n<div class=\"rule\"><\/div>\n<div class=\"row\">\n<div><strong>Phoenix Systems<\/strong>, Automation SRE, Austin, TX<\/div>\n<div class=\"right\">Feb 2019 to Present<\/div>\n<\/p><\/div>\n<ul class=\"bullets\">\n<li>Developed automation scripts for routine maintenance tasks, reducing manual intervention by over 70%.<\/li>\n<li>Designed real-time alerting with Datadog, helping cut average incident detection time to under 3 minutes.<\/li>\n<li>Led root cause analysis sessions, driving actionable fixes and reducing repeated outages.<\/li>\n<li>Improved on-call quality of life by introducing automated runbooks and failover scripts.<\/li>\n<li>Worked directly with engineering to implement blue\/green deployments, raising release reliability and reducing downtime for end-users.<\/li>\n<\/ul>\n<div class=\"row\">\n<div><strong>Netwise IT<\/strong>, Junior DevOps Engineer, Dallas, TX<\/div>\n<div class=\"right\">Jul 2016 to Jan 2019<\/div>\n<\/p><\/div>\n<ul class=\"bullets\">\n<li>Maintained cloud environments in AWS and Azure for SaaS clients, ensuring consistent uptime over 99.9%.<\/li>\n<li>Deployed centralized logging with ELK and built custom dashboards for faster troubleshooting.<\/li>\n<li>Assisted in introducing infrastructure as code with Terraform, improving reproducibility and version control.<\/li>\n<\/ul><\/div>\n<div class=\"sec\">\n<p class=\"sec-title\">Skills<\/p>\n<div class=\"rule\"><\/div>\n<div class=\"two-col\">\n<div><strong>Automation:<\/strong> Python, Bash, Ansible<\/div>\n<div><strong>Cloud\/Infra:<\/strong> AWS, Azure, Docker<\/div>\n<div><strong>Monitoring:<\/strong> Datadog, ELK Stack<\/div>\n<div><strong>Practices:<\/strong> Incident Response, CI\/CD, SLA Management<\/div>\n<\/p><\/div>\n<\/p><\/div>\n<div class=\"sec\">\n<p class=\"sec-title\">Education and Certifications<\/p>\n<div class=\"rule\"><\/div>\n<div class=\"row\">\n<div><strong>University of Texas at Austin<\/strong>, BSc Information Technology, Austin, TX<\/div>\n<div class=\"right\">2016<\/div>\n<\/p><\/div>\n<div class=\"row\" style=\"margin-top: 6px;\">\n<div><strong>Microsoft Certified: Azure Administrator Associate<\/strong>, Online<\/div>\n<div class=\"right\">2020<\/div>\n<\/p><\/div>\n<\/p><\/div>\n<\/p><\/div>\n<p>      <a class=\"resume-overlay\" href=\"https:\/\/app.jobwinner.ai\/register\" target=\"_blank\" rel=\"noopener\" aria-label=\"Go to JobWinner to enhance this resume\"><br \/>\n        <span class=\"cta-btn\">Enhance my Resume<\/span><br \/>\n      <\/a>\n    <\/div>\n<p>What these examples share: each highlights a distinct SRE specialization, leverages measurable impact (uptime, MTTR, manual steps removed), groups related skills for easy scanning, and includes links for proof. Formatting differences aside, the substance is always anchored in evidence and relevance to SRE hiring criteria.<\/p>\n<p class=\"note\">Tip: For a stronger GitHub, pin scripts or monitoring configs relevant to SRE (e.g., incident automation, Terraform modules), and write a README describing intent and setup.<\/p>\n<h3>Role variations (pick the closest version to your target job)<\/h3>\n<p>Many \u201cIT Site Reliability Engineer\u201d jobs actually represent specialized focuses. Select the version that best matches your background and use its language and bullet structures for your real experience.<\/p>\n<h3>Cloud SRE variation<\/h3>\n<p><strong>Keywords to include:<\/strong> Kubernetes, Terraform, Cloud Monitoring<\/p>\n<ul>\n<li><strong>Bullet pattern 1:<\/strong> Automated <em>cloud infrastructure<\/em> provisioning using [tool], reducing manual deploy effort by [metric].<\/li>\n<li><strong>Bullet pattern 2:<\/strong> Deployed and maintained <em>containerized workloads<\/em> in [cloud], improving uptime by [percentage] and scaling for [traffic\/load].<\/li>\n<\/ul>\n<h3>Automation\/DevOps SRE variation<\/h3>\n<p><strong>Keywords to include:<\/strong> CI\/CD, Scripting, Toil reduction<\/p>\n<ul>\n<li><strong>Bullet pattern 1:<\/strong> Developed <em>automation scripts<\/em> in [language] to replace [manual process], reducing toil by [metric] and increasing consistency.<\/li>\n<li><strong>Bullet pattern 2:<\/strong> Built <em>CI\/CD pipelines<\/em> with [tool], improving deploy velocity and incident rollback speed by [amount].<\/li>\n<\/ul>\n<h3>Monitoring\/Incident Response SRE variation<\/h3>\n<p><strong>Keywords to include:<\/strong> Monitoring, Reliability, MTTR<\/p>\n<ul>\n<li><strong>Bullet pattern 1:<\/strong> Designed <em>monitoring and alerting systems<\/em> with [tool], enabling [faster detection\/response] and lowering MTTR by [metric].<\/li>\n<li><strong>Bullet pattern 2:<\/strong> Led <em>incident management<\/em> processes, running postmortems and reducing repeated errors by [percentage].<\/li>\n<\/ul>\n<\/section>\n<section id=\"recruiter-scan\">\n<h2>2. What recruiters scan first<\/h2>\n<p>Most recruiters only spend a few seconds on each resume at first. They\u2019re searching for immediate signals you fit the SRE requirements and back them up with evidence. Run through this list to quickly improve your odds.<\/p>\n<ul>\n<li><strong>Role match in first section:<\/strong> job title, summary, and skills clearly align to the SRE posting and stack.<\/li>\n<li><strong>Most compelling evidence up top:<\/strong> your lead bullets in each job relate directly to reliability, automation, or monitoring impact.<\/li>\n<li><strong>Concrete metrics:<\/strong> each position includes at least one measurable outcome (uptime, incident count, deployment time, cost, response speed).<\/li>\n<li><strong>Proof or portfolio:<\/strong> GitHub, blog, or monitoring dashboards are accessible and support your claims.<\/li>\n<li><strong>Straightforward layout:<\/strong> standard headings, clear dates, and nothing that confuses parsing or reading order.<\/li>\n<\/ul>\n<p class=\"note\">If you do just one thing, move your most relevant and impactful bullet to the top of every experience section.<\/p>\n<\/section>\n<section id=\"structure\">\n<h2>3. How to Structure a IT Site Reliability Engineer Resume Section by Section<\/h2>\n<p>Resume structure is essential since reviewers are skimming for essential qualifications. A strong IT Site Reliability Engineer resume highlights your focus area, technical stack, and impact within seconds.<\/p>\n<p>You don\u2019t need to list every detail. The goal is to showcase the most pertinent details, organized for rapid review. Your resume is an entry point to your expertise: bullets outline your achievements, and linked repositories or dashboards provide validation.<\/p>\n<h3>Recommended section order (with what to include)<\/h3>\n<ul>\n<li><strong>Header<\/strong>\n<ul>\n<li>Name, intended title (IT Site Reliability Engineer), email, phone, city + country.<\/li>\n<li>Links: LinkedIn, GitHub, (monitoring dashboards or blog if relevant).<\/li>\n<li>No need to list your full home address.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Summary (optional)<\/strong>\n<ul>\n<li>Helpful for clarifying your SRE specialization (cloud, automation, monitoring, incident response).<\/li>\n<li>Keep to 2\u20134 lines: your focus, main technologies, and 1\u20132 accomplishments (uptime, incident reduction, automation wins).<\/li>\n<li>Draft a concise version with a <a href=\"https:\/\/jobwinner.ai\/resume-tailoring\/professional-summary-generator\/\">professional summary generator<\/a> first, then personalize it for accuracy.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Professional Experience<\/strong>\n<ul>\n<li>List roles in reverse-chronological order, including dates and locations.<\/li>\n<li>3\u20135 tailored bullets per job, reordered so the most relevant and impressive come first.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Skills<\/strong>\n<ul>\n<li>Group skills: Automation, Cloud, Monitoring, Practices.<\/li>\n<li>Focus on tools relevant to the target posting\u2014avoid outdated or irrelevant tech.<\/li>\n<li>If uncertain which skills are in demand, use the <a href=\"https:\/\/jobwinner.ai\/skills-insights\/\">skills insights<\/a> tool to analyze postings and see what hiring managers want.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Education and Certifications<\/strong>\n<ul>\n<li>Include cities for degrees and &#8220;Online&#8221; for remote certifications.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<\/section>\n<section id=\"bullets\">\n<h2>4. IT Site Reliability Engineer Bullet Points and Metrics Playbook<\/h2>\n<p>Effective SRE resume bullets do three things: they show you drive reliability, automate away toil, and use industry-standard tools. To quickly improve your resume, focus on making your bullets outcome-driven and specific.<\/p>\n<p>If your bullets mostly say \u201cmaintained\u2026\u201d or \u201cresponsible for\u2026\u201d, your impact is likely hidden. Shift the wording to emphasize positive change: incident reductions, faster recovery, improved deployment, and quantifiable results using modern SRE tooling.<\/p>\n<h3>A simple bullet formula you can reuse<\/h3>\n<ul>\n<li><strong>Action + Scope + Stack + Outcome<\/strong>\n<ul>\n<li><strong>Action:<\/strong> automated, deployed, architected, monitored, improved, remediated.<\/li>\n<li><strong>Scope:<\/strong> system, infrastructure, pipeline, dashboard, service, on-call process.<\/li>\n<li><strong>Stack:<\/strong> AWS, Terraform, Kubernetes, Python, Datadog, Prometheus, Ansible.<\/li>\n<li><strong>Outcome:<\/strong> uptime, incident rate, MTTR, deployment speed, error reduction, cost savings.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3>Fast ways to find SRE-relevant metrics<\/h3>\n<ul>\n<li><strong>Reliability:<\/strong> Uptime %, MTTR, MTTD, incident frequency, number of SEVs, SLO compliance<\/li>\n<li><strong>Automation impact:<\/strong> Manual steps eliminated, scripts\/processes automated, time saved, error reduction<\/li>\n<li><strong>Deployment:<\/strong> Release frequency, mean deploy time, rollback speed, failed deploy reduction<\/li>\n<li><strong>Monitoring:<\/strong> Alert accuracy, time to detection, number of actionable alerts, noise reduction<\/li>\n<li><strong>Cost:<\/strong> Cloud spend reduced, resource allocation efficiency, abandoned legacy infra<\/li>\n<\/ul>\n<p><strong>Where these numbers come from:<\/strong><\/p>\n<ul>\n<li>Observability tools (Datadog, Prometheus, CloudWatch, ELK, Grafana)<\/li>\n<li>Deployment logs and CI\/CD tools (Jenkins, GitHub Actions, ArgoCD)<\/li>\n<li>Incident management (PagerDuty, Opsgenie, postmortems)<\/li>\n<li>Cloud provider dashboards (AWS, GCP, Azure)<\/li>\n<\/ul>\n<p>Want more SRE bullet ideas? Browse <a href=\"https:\/\/jobwinner.ai\/resume-tailoring\/responsabilities-bullet-points\/\">impactful bullet points<\/a> and adapt their logic with your genuine data.<\/p>\n<p>Below is a before-and-after table showcasing how to upgrade IT Site Reliability Engineer bullets.<\/p>\n<div class=\"visual tablewrap\" role=\"img\" aria-label=\"Before and after bullet point examples for IT Site Reliability Engineer resume\">\n<table>\n<thead>\n<tr>\n<th><span class=\"bad\">Before<\/span> (weak)<\/th>\n<th><span class=\"good\">After<\/span> (strong)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Monitored cloud servers and fixed issues as needed.<\/td>\n<td>Engineered automated server health checks and remediation in Python, increasing uptime to 99.99%.<\/td>\n<\/tr>\n<tr>\n<td>Helped with infrastructure deployments.<\/td>\n<td>Automated AWS infrastructure builds using Terraform, reducing provisioning time from 5 hours to under 30 minutes.<\/td>\n<\/tr>\n<tr>\n<td>Supported on-call rotation and responded to incidents.<\/td>\n<td>Led incident response and improved alerting, lowering mean time to resolution by 35% over 6 months.<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<h3>Frequent mistakes and ways to improve them<\/h3>\n<p><strong>&#8220;Responsible for monitoring\u2026&#8221;<\/strong> &rarr; Show the reliability uplift<\/p>\n<ul>\n<li>Weak: &#8220;Responsible for monitoring infrastructure&#8221;<\/li>\n<li>Strong: &#8220;Enhanced infrastructure monitoring with Prometheus and custom alerts, reducing false positives by 40%&#8221;<\/li>\n<\/ul>\n<p><strong>&#8220;Worked as part of SRE team\u2026&#8221;<\/strong> &rarr; Emphasize your personal contribution<\/p>\n<ul>\n<li>Weak: &#8220;Worked as part of SRE team to maintain uptime&#8221;<\/li>\n<li>Strong: &#8220;Developed predictive failure scripts and led outage reviews, keeping uptime above 99.97%&#8221;<\/li>\n<\/ul>\n<p><strong>&#8220;Helped automate\u2026&#8221;<\/strong> &rarr; Specify what, how, and the impact<\/p>\n<ul>\n<li>Weak: &#8220;Helped automate deployments&#8221;<\/li>\n<li>Strong: &#8220;Automated blue\/green deployments with Ansible and Jenkins, halving production deploy failures&#8221;<\/li>\n<\/ul>\n<p class=\"note\">Approximations like \u201cabout 30%\u201d are acceptable if based on reasonable evidence. Be ready to explain your calculation in an interview.<\/p>\n<\/section>\n<section id=\"tailor\">\n<h2>5. Tailor Your IT Site Reliability Engineer Resume to a Job Description (Step by Step + Prompt)<\/h2>\n<p>Tailoring moves your SRE resume from generic to a close match for a specific role. It\u2019s about pinpointing your most relevant work and describing it using the employer\u2019s language\u2014never exaggerating your experience.<\/p>\n<p>Want to make this easier? <a href=\"https:\/\/jobwinner.ai\/resume-tailoring\">Tailor your resume using JobWinner AI<\/a> as a first draft, then make it 100% truthful before applying. For better summaries, draft one with the <a href=\"https:\/\/jobwinner.ai\/resume-tailoring\/professional-summary-generator\/\">summary generator<\/a> and personalize it.<\/p>\n<h3>5 steps to tailor truthfully<\/h3>\n<ol>\n<li><strong>Identify key terms<\/strong>\n<ul>\n<li>Look for repeated SRE tools, platforms, scripting languages, infrastructure, and reliability goals.<\/li>\n<li>Highlight cloud providers, monitoring tools, automation frameworks, and any SLO\/SLI language.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Map keywords to your actual work<\/strong>\n<ul>\n<li>For each keyword, tie it to a bullet, project, or role where you have hands-on experience.<\/li>\n<li>If you\u2019re light in an area, shift focus to related strengths or adjacent technologies.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Update the first section<\/strong>\n<ul>\n<li>Ensure your title, summary, and skills reflect the targeted SRE focus (e.g., automation, cloud, monitoring).<\/li>\n<li>Move the most relevant tools and specialties to the top of your skills list.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Prioritize your best bullets<\/strong>\n<ul>\n<li>Make sure the top bullets for each job are the ones most relevant to the target SRE job.<\/li>\n<li>Remove bullets that distract from your SRE focus or add no value for this posting.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Verify every claim is solid<\/strong>\n<ul>\n<li>Each bullet should be defensible\u2014be able to explain the context, approach, and what changed.<\/li>\n<li>If you can\u2019t provide details for a claim in conversation, rephrase or cut it.<\/li>\n<\/ul>\n<\/li>\n<\/ol>\n<h3>Obvious tailoring mistakes (avoid these)<\/h3>\n<ul>\n<li>Copying extensive phrases from the job ad word-for-word<\/li>\n<li>Claiming deep proficiency with every listed technology<\/li>\n<li>Adding a skill you don\u2019t currently use or used once years ago<\/li>\n<li>Altering your real job title to exactly match the posting<\/li>\n<li>Overstating results or metrics you can\u2019t back up<\/li>\n<\/ul>\n<p>Effective tailoring means making your most relevant SRE proof crystal clear, not faking new experience.<\/p>\n<p>Want an instant draft you can refine? Copy the prompt below and use it to generate a tailored SRE resume version you can honestly submit.<\/p>\n<div class=\"visual prompt-box\" aria-label=\"Copy and paste resume tailoring prompt\">\n<div class=\"prompt-head\">\n        <button class=\"prompt-copy-btn\" type=\"button\" onclick=\"jwCopySection('tailor-prompt', this)\">Copy prompt<\/button>\n      <\/div>\n<pre><code id=\"tailor-prompt\">Task: Tailor my IT Site Reliability Engineer resume to the job description below without inventing experience.\n\nRules:\n- Keep everything truthful and consistent with my original resume.\n- Prefer strong action verbs and measurable impact.\n- Use relevant keywords from the job description naturally (no keyword stuffing).\n- Keep formatting ATS-friendly (simple headings, plain text).\n\nInputs:\n1) My current resume:\n&lt;RESUME&gt;\n[Paste your resume here]\n&lt;\/RESUME&gt;\n\n2) Job description:\n&lt;JOB_DESCRIPTION&gt;\n[Paste the job description here]\n&lt;\/JOB_DESCRIPTION&gt;\n\nOutput:\n- A tailored resume (same structure as my original)\n- 8 to 12 improved bullets, prioritizing the most relevant achievements\n- A refreshed Skills section grouped by: Automation, Cloud\/Infra, Monitoring, Practices\n- A short list of keywords you used (for accuracy checking)<\/code><\/pre>\n<\/p><\/div>\n<p class=\"note\">If a job post emphasizes reliability, scale, or automation, make sure at least one bullet highlights a relevant tradeoff or technical challenge you addressed\u2014if it\u2019s true for your experience.<\/p>\n<\/section>\n<section id=\"ats\">\n<h2>6. IT Site Reliability Engineer Resume ATS Best Practices<\/h2>\n<p>ATS-friendly resumes are all about clarity and reliable parsing. An IT Site Reliability Engineer resume can appear modern and polished as long as information is consistently formatted, plainly grouped, and easy for software to read.<\/p>\n<p>Think of the ATS as a strict parser: it wants predictable sections, clear job titles and dates, and keyword-rich skills in text\u2014not graphics. Always test your resume in an <a href=\"https:\/\/jobwinner.ai\/ats-resume-checker\/\">ATS checker<\/a> before you apply to prevent silent rejections.<\/p>\n<h3>Principles for a resume that works for both ATS and humans<\/h3>\n<ul>\n<li><strong>Use universally recognized headings<\/strong>\n<ul>\n<li>Professional Experience, Skills, Education, Certifications.<\/li>\n<li>Avoid creative or unusual labels that could break parsers.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Maintain a straightforward layout<\/strong>\n<ul>\n<li>Uniform spacing, readable font sizes, and no sidebars for key content.<\/li>\n<li>All critical info should be in the main column.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Provide proof links up top<\/strong>\n<ul>\n<li>Put GitHub, blog, or monitoring dashboards in the header.<\/li>\n<li>Never hide important links inside images or icons.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Keep skills as readable plain text<\/strong>\n<ul>\n<li>Avoid charts or skill ratings\u2014just use grouped keywords.<\/li>\n<li>Group by automation, cloud, monitoring, and practices for fast review.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<p>Review the ATS dos and don\u2019ts below for SRE roles to catch common issues.<\/p>\n<div class=\"visual tablewrap\" role=\"img\" aria-label=\"ATS do and avoid checklist for IT Site Reliability Engineer resumes\">\n<table>\n<thead>\n<tr>\n<th>Do (ATS friendly)<\/th>\n<th>Avoid (common parsing issues)<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Standard headings, even spacing, simple design<\/td>\n<td>Icons as substitutes for section names, graphics with text, creative layouts<\/td>\n<\/tr>\n<tr>\n<td>Grouped, keyword-rich skill lists<\/td>\n<td>Skill level bars, colored graphs, or star ratings<\/td>\n<\/tr>\n<tr>\n<td>Evidence-focused, concise bullets<\/td>\n<td>Long, dense paragraphs that obscure tools and results<\/td>\n<\/tr>\n<tr>\n<td>PDF file (unless asked for DOCX)<\/td>\n<td>Images, non-standard formats, or scanned documents<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<h3>Quick ATS check you can do in minutes<\/h3>\n<ol>\n<li>Export your resume as PDF<\/li>\n<li>Open PDF in Google Docs<\/li>\n<li>Select all text and copy<\/li>\n<li>Paste into a plain text editor<\/li>\n<\/ol>\n<p>If your skills, titles, or dates get jumbled, or text is unreadable, simplify the format until everything pastes logically. ATS bots will make the same errors humans do here.<\/p>\n<p class=\"note\">Always paste your resume into a plain text box before submitting. If it\u2019s messy, revise your formatting for clarity.<\/p>\n<\/section>\n<section id=\"optimize\">\n<h2>7. IT Site Reliability Engineer Resume Optimization Tips<\/h2>\n<p>Optimization is your final quality check before applications go out. The aim is to make relevance unmistakable, evidence obvious, and every section easy to defend in an interview.<\/p>\n<p>Work through your resume in layers: top third (header, summary, skills), then experience (clarity and impact), then polish (consistency and proofread). For each role you pursue, adapt the top section and reorder bullets for relevance.<\/p>\n<h3>High-leverage changes that boost SRE resumes<\/h3>\n<ul>\n<li><strong>Make SRE fit clear within 10 seconds<\/strong>\n<ul>\n<li>Match title and summary to the role (cloud SRE, automation SRE, incident response SRE, etc.).<\/li>\n<li>Move matching tools (Kubernetes, Terraform, monitoring) to the top of your skills.<\/li>\n<li>Highlight your biggest proof bullet up front for each job.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Strengthen bullet proof<\/strong>\n<ul>\n<li>Swap general claims for measurable outcomes and tool details.<\/li>\n<li>Add at least one metric per job (uptime, incidents, cost, deployment speed).<\/li>\n<li>Cut repetitive bullets that describe similar work.<\/li>\n<\/ul>\n<\/li>\n<li><strong>Surface proof fast<\/strong>\n<ul>\n<li>Pin a relevant GitHub repo, link a monitoring dashboard, or summarize your automation scripts.<\/li>\n<li>Reference public talks, incident postmortems, or blog posts if they showcase your SRE expertise.<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h3>Common SRE resume mistakes that lower quality<\/h3>\n<ul>\n<li><strong>Burying your best SRE achievement:<\/strong> Most impressive bullet is hidden in the middle or end of a job entry<\/li>\n<li><strong>Switching tense and perspective:<\/strong> Inconsistent use of past\/present, or shifting from \u201cI\u201d to \u201cwe\u201d<\/li>\n<li><strong>Duplicate bullets:<\/strong> Listing \u201cimproved uptime\u201d multiple times for different jobs<\/li>\n<li><strong>Duty-driven opening bullets:<\/strong> Leading with tasks, not results<\/li>\n<li><strong>Unfocused, generic skills:<\/strong> Including basics like \u201cMicrosoft Office\u201d or \u201cEmail\u201d<\/li>\n<\/ul>\n<h3>Resume anti-patterns to avoid<\/h3>\n<ul>\n<li><strong>Copy-paste templates:<\/strong> \u201cResults-oriented professional with excellent communication skills\u201d<\/li>\n<li><strong>Vague scope:<\/strong> \u201cWorked on several projects\u201d (Be specific: what projects? what stack? what results?)<\/li>\n<li><strong>Overlong tech lists:<\/strong> Dozens of keywords, no grouping, no context<\/li>\n<li><strong>Duties disguised as accomplishments:<\/strong> \u201cMaintained monitoring\u201d (Show improvement, not only maintenance)<\/li>\n<li><strong>Unverifiable superlatives:<\/strong> \u201cWorld-class engineer\u201d \u201cIndustry-leading system\u201d<\/li>\n<\/ul>\n<h3>Self-review scorecard for a fast final pass<\/h3>\n<p>Use this grid to spot improvement opportunities. If you need a quick boost, start by clarifying relevance and improving impact. Or use <a href=\"https:\/\/jobwinner.ai\/resume-tailoring\">JobWinner AI tailoring<\/a> for a strong first draft.<\/p>\n<div class=\"visual tablewrap\" role=\"img\" aria-label=\"IT Site Reliability Engineer resume optimization scorecard\">\n<table>\n<thead>\n<tr>\n<th>Area<\/th>\n<th>What strong looks like<\/th>\n<th>Quick fix<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Relevance<\/td>\n<td>Title, summary, and top skills match SRE job<\/td>\n<td>Update summary and reorder skills for the job<\/td>\n<\/tr>\n<tr>\n<td>Impact<\/td>\n<td>Bullets feature real, measurable results<\/td>\n<td>Add at least one metric per job (reliability, automation, response)<\/td>\n<\/tr>\n<tr>\n<td>Evidence<\/td>\n<td>Links to scripts, dashboards, or public SRE work<\/td>\n<td>Pin one repo and mention a monitoring dashboard or write-up<\/td>\n<\/tr>\n<tr>\n<td>Clarity<\/td>\n<td>Simple layout, grouped skills, tidy dates<\/td>\n<td>Reduce dense text and standardize headings\/dates<\/td>\n<\/tr>\n<tr>\n<td>Credibility<\/td>\n<td>Specific, defensible claims\u2014no exaggeration<\/td>\n<td>Edit any vague or unprovable bullets for truthfulness<\/td>\n<\/tr>\n<\/tbody>\n<\/table><\/div>\n<p class=\"note\"><strong>Last step:<\/strong> Read your resume aloud. If any bullet sounds generic or unprovable, rework it for accuracy and detail.<\/p>\n<\/section>\n<section id=\"beyond\">\n<h2>8. What to Prepare Beyond Your Resume<\/h2>\n<p>Your resume will help you land interviews, but you need to be ready to elaborate on everything it contains. The best candidates treat their resume as a roadmap to deeper conversations. Once you have interviews lined up, use <a href=\"https:\/\/jobwinner.ai\/interview-preparation\/\">interview practice tools<\/a> to rehearse telling your SRE impact stories clearly.<\/p>\n<h3>Be prepared to explain every bullet<\/h3>\n<ul>\n<li><strong>For every claim:<\/strong> Be ready to discuss the problem, your approach, alternatives, and results<\/li>\n<li><strong>For metrics:<\/strong> Know how you quantified improvements\u2014be transparent if they\u2019re estimates<\/li>\n<li><strong>For SRE tools listed:<\/strong> Expect to answer questions about your experience with specific automation, monitoring, or deployment tools<\/li>\n<li><strong>For major projects:<\/strong> Prepare a summary: why it mattered, what you\u2019d do differently now, and what you learned<\/li>\n<\/ul>\n<h3>Collect your SRE proof artifacts<\/h3>\n<ul>\n<li>Update your GitHub with relevant scripts, configs, and automation projects (with clear READMEs)<\/li>\n<li>Compile dashboards, architecture diagrams, or postmortem write-ups for complex systems<\/li>\n<li>Pick code samples (without proprietary data) to demonstrate your skills and approach<\/li>\n<li>Be able to walk through a significant technical challenge and your reasoning<\/li>\n<\/ul>\n<p class=\"note\">A winning interview happens when your resume sparks curiosity and you have the substance and stories to back up each claim.<\/p>\n<\/section>\n<section id=\"checklist\">\n<h2>9. Final Pre-Submission Checklist<\/h2>\n<p>Take a moment for this 60-second review before you submit:<\/p>\n<div class=\"visual checklist-box\">\n      <label><br \/>\n        <input type=\"checkbox\"> Top third (header + summary + skills) align directly with the SRE job requirements<br \/>\n      <\/label><br \/>\n      <label><br \/>\n        <input type=\"checkbox\"> First bullet for each job is your strongest, most SRE-relevant achievement<br \/>\n      <\/label><br \/>\n      <label><br \/>\n        <input type=\"checkbox\"> At least 3\u20135 bullets use quantifiable outcomes<br \/>\n      <\/label><br \/>\n      <label><br \/>\n        <input type=\"checkbox\"> All portfolio or GitHub links are up-to-date and relevant<br \/>\n      <\/label><br \/>\n      <label><br \/>\n        <input type=\"checkbox\"> Passed ATS copy-paste test (text pastes cleanly)<br \/>\n      <\/label><br \/>\n      <label><br \/>\n        <input type=\"checkbox\"> No spelling errors, consistent tense, uniform date styles<br \/>\n      <\/label><br \/>\n      <label><br \/>\n        <input type=\"checkbox\"> File named professionally (FirstName_LastName_Resume.pdf)<br \/>\n      <\/label><br \/>\n      <label><br \/>\n        <input type=\"checkbox\"> Ready to discuss and defend every claim in detail<br \/>\n      <\/label>\n    <\/div>\n<\/section>\n<section id=\"faqs\">\n<h2>10. IT Site Reliability Engineer Resume FAQs<\/h2>\n<p>Use these as your last sanity check before sending off your resume. These cover the most frequent SRE resume questions from job-seekers looking for a strong example to personalize.<\/p>\n<div class=\"visual\" role=\"img\" aria-label=\"IT Site Reliability Engineer resume FAQs accordion\">\n<div style=\"padding: 14px;\">\n<details>\n<summary>How long should my IT Site Reliability Engineer resume be?<\/summary>\n<p>\n            For most SRE candidates with less than 6 years\u2019 experience, a single page is best. Two pages are fine for senior-level, complex, or hybrid roles\u2014but keep the highest-value SRE content on page one and trim repetitive or outdated details.\n          <\/p>\n<\/details>\n<details>\n<summary>Is a summary necessary?<\/summary>\n<p>\n            It\u2019s optional but useful, especially to clarify your SRE specialization (cloud, automation, monitoring, etc.). Limit yourself to 2\u20134 lines, stating your focus, core platforms\/tools, and a couple of measurable achievements. Skip vague buzzwords unless you support them with concrete evidence.\n          <\/p>\n<\/details>\n<details>\n<summary>How many bullets per job are ideal?<\/summary>\n<p>\n            Generally, 3\u20135 strong, non-redundant bullets per job make for easy reading and better ATS parsing. If you have more, keep only the ones that match the SRE job and add unique value. Aim for each bullet to provide new evidence or context.\n          <\/p>\n<\/details>\n<details>\n<summary>Are GitHub or monitoring links required?<\/summary>\n<p>\n            Not required, but highly recommended. Share repositories, monitoring dashboards, or technical blogs that demonstrate relevant SRE work. If your contributions are private, link to write-ups, public scripts, or general descriptions\u2014showing proof of capability, not just participation.\n          <\/p>\n<\/details>\n<details>\n<summary>What if I don\u2019t have exact metrics?<\/summary>\n<p>\n            Use the operational metrics you can support: improved uptime, reduced incidents, faster deployments, less manual toil, shorter recovery time, etc. If you estimate, clarify how (e.g., \u201creduced manual steps by about 70% through automation\u201d). Be prepared to explain your calculation method if asked.\n          <\/p>\n<\/details>\n<details>\n<summary>Should I list every tool I\u2019ve touched?<\/summary>\n<p>\n            No\u2014focus on the tools and platforms relevant to the SRE job. Overlong, ungrouped lists dilute your credibility and can confuse ATS matching. Group tools by function (e.g., automation, monitoring) and prioritize those that appear in the job posting.\n          <\/p>\n<\/details>\n<details>\n<summary>Should contract or freelance SRE work be included?<\/summary>\n<p>\n            Absolutely, if the work is substantial and relevant. List contract roles like regular jobs, specifying client type and duration. If you\u2019ve had many brief contracts, group similar ones and feature the most impactful projects. Highlight complexity, scale, and results, not just the nature of the engagement.\n          <\/p>\n<\/details>\n<details>\n<summary>How do I showcase impact as a newer SRE?<\/summary>\n<p>\n            Emphasize improvements, even on a small scale. For example: \u201cCut deployment time by 60% after automating configuration\u201d or \u201cRaised monitoring coverage from 40% to 85%.\u201d Note participation in on-call, postmortems, and learning new stacks\u2014the capacity to improve is highly valued for early-career SREs.\n          <\/p>\n<\/details>\n<details>\n<summary>How do I describe SRE work under an NDA?<\/summary>\n<p>\n            Focus on scope, scale, and results without specifics. Instead of \u201cBuilt monitoring for [Product],\u201d use \u201cDeveloped monitoring for a high-traffic SaaS platform (5M+ daily requests).\u201d Explain your technical approach and outcomes without naming products or disclosing confidential info. Clarify in interviews that you\u2019re bound by NDA and focus on your technical contributions.\n          <\/p>\n<\/details><\/div>\n<\/p><\/div>\n<p class=\"note\">\n      Looking for a clean SRE layout to start with? Explore ATS-friendly <a href=\"https:\/\/jobwinner.ai\/resume-templates\/\">resume templates<\/a> here.\n    <\/p>\n<\/section>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>D\u00e9couvrez des exemples de CV d&#039;ing\u00e9nieur en fiabilit\u00e9 des sites informatiques, les meilleures pratiques en mati\u00e8re de syst\u00e8mes de suivi des candidatures (ATS) et des conseils d&#039;experts pour adapter votre candidature aux exigences sp\u00e9cifiques du poste, vous aidant ainsi \u00e0 vous d\u00e9marquer dans le paysage technologique concurrentiel d&#039;aujourd&#039;hui.<\/p>","protected":false},"author":3,"featured_media":0,"parent":0,"template":"","type-resume-example":[108],"class_list":["post-12298","resume-examples","type-resume-examples","status-publish","hentry","type-resume-example-information-technology"],"_links":{"self":[{"href":"https:\/\/jobwinner.ai\/fr\/wp-json\/wp\/v2\/resume-examples\/12298","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jobwinner.ai\/fr\/wp-json\/wp\/v2\/resume-examples"}],"about":[{"href":"https:\/\/jobwinner.ai\/fr\/wp-json\/wp\/v2\/types\/resume-examples"}],"author":[{"embeddable":true,"href":"https:\/\/jobwinner.ai\/fr\/wp-json\/wp\/v2\/users\/3"}],"wp:attachment":[{"href":"https:\/\/jobwinner.ai\/fr\/wp-json\/wp\/v2\/media?parent=12298"}],"wp:term":[{"taxonomy":"type-resume-example","embeddable":true,"href":"https:\/\/jobwinner.ai\/fr\/wp-json\/wp\/v2\/type-resume-example?post=12298"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}