Back-End Engineer
Resume Template

A free Back-End Engineer resume, pre-filled and ready to edit. Replace the highlighted placeholders (languages, frameworks, databases, messaging, metrics) using the side panel on the left, and the resume rewrites itself as you type. Save as PDF when you're done.

Emmanuel Gendre - Former Google Recruiter and Tech Resume Writer

Authored by

Emmanuel Gendre

Tech Resume Writer

Last updated: May 7th, 2026 | Free, ATS-friendly, no signup

Get a Free Back-End Engineer Resume Review

I review personally all resumes within 12 hrs

PDF, DOC, or DOCX • under 5MB

Want to read more first? See how the resume review works →

Interactive resume template generator

Interactive Back-End Engineer Resume Template

Edit the side panel. The resume rewrites itself live. Save as PDF when you're done.

Edits update live as you type. Toggle Edit to rewrite paper text directly.

Edit mode is on. Click anywhere on the resume to rewrite text. Side-panel placeholders still update live.

Marcus Wells Back-End Engineer

Seattle, WA • backend@gmail.com • +1 6666-2222

Profile Summary

  • Back-End Engineer with 7 years of experience designing and operating large-scale services across e-commerce platforms, developer tools, and B2B SaaS, specializing in distributed systems, API contract design, and high-throughput data persistence.
  • Solid technical background across languages (Go, Python, Java), frameworks (gRPC, FastAPI, Spring Boot), data stores (Postgres, DynamoDB, Redis), messaging (Kafka, RabbitMQ), and cloud (AWS, GCP) with strong fundamentals in SQL and Linux internals.
  • Deep expertise in domain-driven design, event-sourced architectures, idempotent processing, and zero-downtime migrations, leveraging methodologies such as hexagonal architecture and CQRS to drive maintainable, scalable, and observable services.
  • Engaged collaborator working cross-functionally with Product, Mobile, and Platform teams in Agile environments, contributing to API contract reviews, RFC discussions, and on-call retrospectives with a pragmatic, ownership-first mindset.
  • Emerging leader who shares technical excellence and fosters a culture of operational rigor and code quality through PR reviews and runbooks, while leading backend guild sessions and authoring widely adopted service templates.

Technical Skills

Languages & Scripting:
Go, Python, Java, SQL, Bash
Frameworks & APIs:
gRPC, FastAPI, Spring Boot, GraphQL, REST
Databases:
PostgreSQL, MySQL, DynamoDB, Redis, MongoDB
Messaging & Async:
Kafka, RabbitMQ, SQS, Pub/Sub, Celery
Performance & Caching:
Redis, Memcached, CDN, connection pooling
Cloud Platforms:
AWS (ECS, Lambda, RDS, S3, IAM), GCP (GKE, Cloud SQL)
Testing & Quality:
PyTest, JUnit, Postman, Pact, k6
DevOps & CI/CD:
Docker, Kubernetes, Terraform, GitHub Actions, Datadog

Education

Georgia Institute of Technology B.S. in Computer Science
Atlanta, GA • Sep 2014 - May 2018

Work Experience

GitHub Back-End Engineer
Seattle, WA • Sep 2021 - Present
  • Own service architecture for the GitHub Issues platform supporting 120M+ MAU, leading end-to-end design and operation across API contracts, read/write throughput, and on-call reliability within a polyglot service mesh.
  • Designed and shipped a GraphQL API for issue search and triage, defining schema versioning, deprecation conventions, and persisted-query support, reducing client payload size by 42% and cutting average query latency from 380ms to 120ms across 8 internal consumers.
  • Architected a partitioned PostgreSQL schema for issue activity history, using range partitioning by month, covering indexes, and a logical-replication-based zero-downtime migration, reducing p99 query time on 2B+ rows from 2.4s to 180ms.
  • Built an event-driven notification pipeline in Go on Kafka with at-least-once delivery, idempotent consumers, and consumer-side dedup, processing 400M+ events/day at 99.99% delivery success and sub-second end-to-end fan-out.
  • Optimized hot-path API endpoints through Redis read-through caching, connection-pool tuning, and EXPLAIN ANALYZE query plans, lifting throughput by 3.5x (from 2k to 7k RPS) and cutting p95 latency by 58% during peak load.
  • Instrumented services with OpenTelemetry traces, structured JSON logs, RED dashboards in Grafana, and SLO-based alerting via Prometheus, reducing mean time to detect from 18 minutes to 90 seconds and time to resolution by 62% across 6 incident drills.
  • Refactored the billing-events domain using hexagonal architecture with adapter-port boundaries, command handlers, and aggregate-root invariants, eliminating 15 long-standing race conditions and shipping the largest domain rewrite in 4 years without a customer-visible regression.
Atlassian Back-End Engineer
Boston, MA • Jun 2018 - Aug 2021
  • Implemented OAuth 2.1 + PKCE authentication for the public Jira API, building scoped JWT tokens with refresh-token rotation, token introspection, and rate-limited brute-force protection, hardening the auth surface against OWASP Top 10 risks and powering 5,000+ active integrations.
  • Established the team's testing strategy with JUnit (unit), ephemeral Docker stacks (integration), and Pact (contract), raising overall service test coverage from 47% to 88% and catching 22+ regressions during pre-release cycles.
  • Owned CI/CD pipelines for 8 backend services, automating canary rollouts on Kubernetes with schema-migration gating and post-deploy smoke checks, reducing deploy lead time from 4 hours to 22 minutes and rolling back 3 silent regressions within minutes.
  • Worked closely with Product, Mobile, and SRE teams across 3 product surfaces to negotiate API contract changes, deprecation timelines, and migration paths, authoring 15+ technical RFCs that shaped the org's backwards-compatibility policy and onboarding 9 new engineers.

Done editing? Download as a real, vector PDF. Selectable text, ATS-friendly, US Letter format.

About this template

A Back-End Engineer
Resume Template, by a Technical Resume Writer.

Up front: 14 years recruiting in tech, plenty of those at Google. I now offer technical resume writing services exclusively for IT and engineering candidates, and Back-End rewrites are a big chunk of my weekly load. The result is I read these resumes from the recruiter's seat several times a week, not from the candidate's. Useful when you're trying to figure out what actually lands.

Most clients pay for the full custom rewrite. The work is collaborative: your real services, the architectural calls you made, the throughput and latency wins worth highlighting. The output is a resume a backend hiring manager scans in 30 seconds and wants to interview. If a strong skeleton is enough, this template is exactly that. ATS-compliant, free, no signup. Run with it!

How it works

How to use this template
to write a Back-End Engineer resume

The structure here was written by a former Google recruiter. The placeholders force you to be specific exactly where it matters: languages, services, architecture, and metrics.

Strong Back-End resume bullets aren't written in a single pass. They build through five stages. Stage one names the task. Stages two and three add the languages you used and the services that ran them. Stage four shows the architectural decision behind the work. Stage five quantifies the result. Bullets that complete stage five are the ones a hiring manager flags for the phone screen. The complete framework lives in How to Write Bullet Points for Tech Resumes.

  1. 01 Task What you did
  2. 02 Languages Go, Python, Java
  3. 03 Services APIs, queues, dbs
  4. 04 Architecture How you designed
  5. 05 Metric Quantified impact

This template hard-wires the five stages into your bullets so the framework runs in the background. The side panel maps clean: language picks fill stage 2, service and infra picks fill stage 3, the architectural-pattern fields fill stage 4, the metric inputs land at stage 5. The sentence skeletons cover stage 1. Why this matters: you only need to drop in real tools and real numbers. The structure handles the rest, and the resume reads at stage 5.

  1. Pick your stack

    Tap a chip to swap Go for Python, Postgres for MySQL, Kafka for RabbitMQ, gRPC for REST. Every mention updates at once.

  2. Drop in your numbers

    RPS, p99 latency, deploy lead time, throughput multiplier, MTTD/MTTR. Don't know yours yet? The defaults pass for a senior Back-End resume.

  3. Save as PDF

    Click Download. The page generates a real vector PDF with selectable text and clean US Letter formatting. ATS-parsable.

Resume Sample

Back-End Engineer Resume Examples

Three sample back-end engineer resumes at different career stages: a junior bootcamp grad pivoting from finance, a senior distributed-systems IC at a SaaS scaleup, and a staff engineer leading trading-platform work at a Fortune 100 bank. Use them as inspiration when filling the template above.

Entry-level Backend Engineer Resume Sample 2 years

Junior Back-End Engineer Resume Example

Bootcamp grad pivoting from finance analyst. Hands-on with Node, Postgres, and REST APIs at a fintech scaleup.

David Park

Junior Back-End Engineer

New York, NY · david.park@gmail.com · +1 646-555-0134 · linkedin.com/in/davidpark

Profile Summary
  • Junior Back-End Engineer with 2 years of experience building internal-facing services in fintech, transitioning from a finance-analyst background with strong fundamentals in data modeling and clear business communication.
  • Hands-on coverage across Node.js, Express, PostgreSQL, Redis, and Jest, with foundational exposure to AWS Lambda, DynamoDB, and Docker.
  • Eager collaborator working with senior engineers, SRE, and Product in two-week sprints, contributing to PR reviews, RFC comments, and incident retros with curiosity-first energy.
  • Career changer bringing 3 years of financial-analyst experience at a hedge fund, fluent in SQL, modeling, and translating ambiguous business asks into testable requirements with backend teams.
Technical Skills
Languages:
JavaScript, TypeScript (proficient), Python (basic), SQL
Backend & APIs:
Node.js, Express, REST APIs, JSON Schema, JWT, basic gRPC
Data & Storage:
PostgreSQL, Redis, DynamoDB (basic), Prisma, raw SQL
Cloud & DevOps:
AWS Lambda, S3, CloudWatch (intro), Docker, GitHub Actions
Testing & Tooling:
Jest, Supertest, Postman, ESLint, Prettier, Git
Observability:
Datadog (intro), structured logging, basic alerting
Education
Hack Reactor Software Engineering Immersive New York, NY · Jul 2023 - Sep 2023
NYU Stern School of Business B.S. in Finance New York, NY · Sep 2016 - May 2020
Work Experience
Robinhood Junior Back-End Engineer New York, NY · Oct 2023 - Present
  • Built 11 REST endpoints on internal trading-tools services in Node.js and Express, backed by PostgreSQL, shipped under senior code review across 6 sprints.
  • Contributed to the rewrite of the legacy notifications service into a new Node.js + Redis stack, owning 4 of 14 endpoints and pair-programming the queue-consumer module with a senior engineer.
  • Wrote Jest and Supertest unit and integration tests, lifting coverage on owned modules from 52% to 78% and catching 6 bugs before code review.
  • Closed 32 small bugs across the brokerage onboarding service, including input-validation gaps, race conditions, and timezone-handling edge cases surfaced by QA.
  • Onboarded onto Datadog, set up 4 dashboards and 3 alert thresholds for owned endpoints, and now participates in the team's daytime on-call rotation under senior backup.
Equinox Financial Analyst New York, NY · Jun 2020 - Sep 2023
  • Owned monthly revenue and membership reporting for 40 club locations, writing SQL queries against Snowflake and building reusable Excel and Looker dashboards for ops leadership.
  • Partnered with the data-engineering team on 2 ETL pipeline reviews, contributing schema-quality feedback that reduced reporting reconciliation errors by 30%.
  • Self-taught Python and JavaScript outside of work, completed 4 personal projects on GitHub, and was accepted into Hack Reactor's immersive program in 2023.

Senior Backend Engineer Resume Sample 6 years

Senior Back-End Engineer Resume Example

Distributed-systems IC at a SaaS scaleup. Go services, Kafka pipelines, and platform-grade observability.

Aisha Bello

Senior Back-End Engineer

San Francisco, CA · aisha.bello@gmail.com · +1 415-555-0162 · linkedin.com/in/aishabello

Profile Summary
  • Senior Back-End Engineer with 6 years of experience building distributed services at SaaS scaleups, specializing in Go, distributed systems, and platform reliability.
  • Hands-on coverage across Go, Node.js, gRPC, PostgreSQL, Redis, Kafka, Elasticsearch, Docker, Kubernetes, and AWS.
  • Deep expertise in service decomposition, event-driven architecture, idempotency and retry semantics, and OpenTelemetry instrumentation, applying saga patterns and outbox tables in production checkout and sync flows.
  • Engaged collaborator working cross-functionally with Frontend, SRE, Data, and Product in continuous-delivery environments, leading code reviews, RFCs, and weekly on-call rotations.
  • Emerging leader who mentors 3 mid-level engineers, authors 4 RFCs per year, and runs a monthly distributed-systems reading group attended by 18 engineers.
Technical Skills
Languages:
Go, Node.js, TypeScript, Python, SQL
APIs & Protocols:
gRPC, REST, GraphQL, WebSockets, Protocol Buffers, OpenAPI
Data & Storage:
PostgreSQL, Redis, Elasticsearch, DynamoDB, S3, schema migrations
Streaming & Async:
Kafka, SQS, Temporal, idempotency keys, outbox pattern, sagas
Cloud & Infra:
AWS (EKS, RDS, S3, Lambda), Docker, Kubernetes, Terraform, ArgoCD
Observability:
Datadog, OpenTelemetry, Sentry, structured logging, SLOs, runbooks
Testing & Quality:
Go test, testify, Jest, contract testing, load testing (k6), chaos drills
Leadership:
RFC authorship, mentorship, on-call leadership, incident command (IC2)
Education
Howard University B.S. in Computer Science Washington, DC · Sep 2015 - May 2019
Work Experience
Notion Senior Back-End Engineer San Francisco, CA · May 2022 - Present
  • Owned the real-time sync service in Go, including 22 gRPC endpoints and the Kafka-backed change-fanout pipeline serving 3M+ collaborative editing sessions per day.
  • Led the migration from a monolithic Node.js service to 4 Go microservices, cutting p99 sync latency from 320ms to 95ms and reducing infra spend on the service by 38%.
  • Designed and shipped the idempotency layer for the public API using Redis-backed request keys, eliminating 4 categories of duplicate-write incidents that previously generated 60+ support tickets per quarter.
  • Drove OpenTelemetry adoption across 12 backend services, replacing ad-hoc Datadog APM tagging with consistent traces and lifting trace-coverage on critical paths from 40% to 92%.
  • Authored 5 RFCs on event-schema versioning, retry budgets, and the outbox-pattern rollout; chair the bi-weekly Backend Architecture review.
  • Mentored 3 mid-level engineers through promotion-track 1:1s and PR reviews, and led the team's chaos-engineering Game Day program (4 drills per year).
Algolia Back-End Engineer San Francisco, CA · Jul 2019 - Apr 2022
  • Built and operated 3 ingestion services in Go and Node.js that fed the hosted search index, handling 2.4B documents indexed per month with at-least-once delivery semantics.
  • Designed the multi-tenant rate-limiter in Redis using token-bucket plus sliding-window logic, protecting downstream services and cutting noisy-neighbor incidents by 70%.
  • Migrated 18 PostgreSQL tables to a partitioned schema with online dual-write cutover, eliminating a class of long-query incidents and trimming average query time by 45%.
  • Owned the team's load-testing harness in k6, establishing a baseline that caught 7 regressions before production and was adopted by 2 sibling teams.

Lead Backend Engineer Resume Sample 11 years

Lead Back-End Engineer Resume Example

Trading-platform tech lead at a Fortune-100 bank. Java, low-latency services, regulatory-grade systems.

Hiroshi Tanaka

Staff Back-End Engineer

New York, NY · hiroshi.tanaka@gmail.com · +1 212-555-0119 · linkedin.com/in/hiroshitanaka

Profile Summary
  • Staff Back-End Engineer with 11 years of experience leading low-latency trading and risk platforms at top-tier investment banks, specializing in JVM performance, regulatory-grade systems, and multi-team platform ownership.
  • Hands-on coverage across Java 21, Kotlin, Go, Spring Boot, gRPC, Kafka, IBM MQ, Oracle, PostgreSQL, Cassandra, and Kubernetes.
  • Deep expertise in sub-millisecond p99 services, FRTB and MiFID II reporting pipelines, JVM tuning (ZGC, G1), and on-prem + AWS hybrid deployments on regulated infrastructure.
  • Cross-functional leader partnering with Quant Research, Risk, Compliance, and Front-Office Trading to shape platform roadmaps, run quarterly architecture reviews, and brief Managing Directors on system risk.
  • Tech lead and architect for the FX e-trading platform, owning 10 engineers across 3 squads, authoring the org's Java service playbook, and chairing the firm-wide Backend Guild (220 engineers).
Technical Skills
Languages:
Java 21, Kotlin, Go, Python, SQL, C++ (legacy)
Frameworks & APIs:
Spring Boot, Spring WebFlux, gRPC, REST, FIX 4.4, Vert.x
Data & Storage:
Oracle, PostgreSQL, Cassandra, Redis, kdb+ (intro), schema governance
Streaming & Messaging:
Kafka, IBM MQ, Solace, Aeron, Chronicle Queue
Infra & CI/CD:
Kubernetes (on-prem + EKS), Docker, Jenkins, ArgoCD, Terraform, Vault
Performance & JVM:
ZGC, G1, JFR, async-profiler, off-heap caching, lock-free queues
Regulatory & Risk:
FRTB, MiFID II, Volcker, audit trails, deterministic replay, SOX controls
Leadership:
RFC governance, architecture review, mentorship, hiring loops, exec briefings
Education
Cornell University B.S. in Computer Science Ithaca, NY · Sep 2010 - May 2014
Work Experience
Goldman Sachs Staff Back-End Engineer, FX e-Trading New York, NY · Mar 2021 - Present
  • Tech lead for the FX e-trading order-management platform, owning 14 Java services, 10 engineers across 3 squads, and architecture decisions across 5 trading desks handling 200B notional per day.
  • Led the migration from Java 11 (G1) to Java 21 (ZGC) across the platform, cutting p99 order-ack latency from 1.4ms to 480us and eliminating stop-the-world pauses on the critical path.
  • Architected the FRTB-compliant risk-replay service in Java and Kafka, delivering deterministic intraday replay for 2.3M trades per day within regulator-mandated SLAs.
  • Drove the Kafka-based event spine that replaced 6 legacy IBM MQ topologies, reducing message-broker incidents by 72% and unblocking 4 downstream analytics teams.
  • Defined the org's Java service RFC process, shepherding 18 RFCs through firm-wide review; chair the bi-weekly Backend Architecture forum across 220 engineers.
  • Built the cross-team latency-budget program: each service ships against a p99 budget with budget enforcement in CI, cutting latency-regression incidents by 55%.
  • Mentored 6 senior engineers through VP-promotion trajectory; led 12 internal architecture reviews and authored the firm's Java 21 + Spring Boot 3 migration playbook.
  • Briefed Managing Directors and the divisional CTO quarterly on platform health, regulatory posture, and the multi-year cloud-hybrid roadmap.
Bloomberg LP Senior Back-End Engineer New York, NY · Jul 2014 - Feb 2021
  • Owned the fixed-income pricing service in Java and C++, serving 40k+ Terminal users with p99 sub-2ms latency across global data centers.
  • Led the migration from Solaris to Linux + Kubernetes for 8 pricing microservices over 14 months, modernizing the deploy pipeline and cutting release time from 3 weeks to 2 days.
  • Built the deterministic-replay framework used by the MiFID II audit team, indexing 1.8B price ticks per day into a replay-friendly Cassandra schema.
  • Mentored 5 mid and senior engineers, ran the bi-weekly JVM performance reading group, and contributed to 8 senior hiring loops as a technical interviewer.
  • Authored the off-heap cache library adopted by 6 pricing teams, eliminating a class of GC-induced p99 spikes during market-open volume.

Filled the template? Get a recruiter's eyes on it.

The template gives you a recruiter-vetted skeleton. The next step is making sure your specific bullets, metrics, and stack hold up under a 6-second screen.

Free, personally reviewed within 12 hours by a former Google recruiter.

Get a Free Resume Review today

I review personally all resumes within 12 hrs

PDF, DOC, or DOCX · under 5MB

Want to read more first? See how the resume review works →

Frequently asked

Your Questions about the Back-End Engineer Resume Template, Answered

Yes, free of charge. Nothing to sign up for, no email required, no upgrade tier hidden behind it. Just open it, fill it, and download.

Yes. The exported PDF is single-column with the standard section headers ATS systems expect (Profile Summary, Technical Skills, Education, Work Experience), and contains no tables, images, or column splits. Workday, Greenhouse, and iCIMS parse it cleanly. You can drop the export into our ATS Checker afterward to double-check.

You can. Toggle Edit at the top of the resume preview, then click directly into any sentence to type whatever you want. The side-panel-driven placeholders still update with your inputs; everything else is plain editable text.

Hit the Download button. The PDF gets generated by your browser on the spot, with no print dialog, no signup, and no server in the loop. The result is real vector text on US Letter, which means ATS tools read it the same way they would a Google Docs export.

Yes. The defaults are Go, Postgres, Kafka, and gRPC because those show up the most in 2026 Back-End job descriptions, but every one of them is a placeholder. Swap Go for Python or Java or Node, Postgres for MySQL or DynamoDB, Kafka for RabbitMQ or SQS, gRPC for REST or GraphQL. Type the swap in the side panel and the resume updates everywhere it appears.

No. Hiring managers screen on substance: the systems you actually owned, the API contracts you negotiated, the throughput and reliability wins you can defend in a screen. Layout origin is not what they evaluate. What does hurt is a template padded with vague bullets, which is exactly what this one is structured to prevent. The skeleton came from a former Google recruiter; the substance is yours.

Yes, free. Drop your PDF into the review form on this page and a former Google recruiter (me, personally) will read it and send line-by-line notes back within 12 hours. No upsell after, no hidden cost.

Why trust this template

Emmanuel Gendre, former Google recruiter and tech resume writer

Emmanuel Gendre

Former Google recruiter · Tech resume writer

I built this Back-End Engineer template from the patterns I saw work, not from generic advice. Below is the data behind every bullet, skills line, and metric placeholder.

  • Experience 1,000+ Back-End Engineer resumes screened across distributed-systems, e-commerce, and developer-platform stacks during my Google recruiter years and at TechieCV. The Profile Summary and Skills sections mirror what survived the 6-second screen.
  • Expertise Bullets modeled on senior offers. The GitHub section is structured the way IC4-IC6 Back-End candidates write their experience when they land FAANG and scaleup interviews: contract-driven API ownership, throughput-and-latency wins, and zero-downtime migration craftsmanship.
  • Trust Stack reflects the 2026 hiring bar. Go + gRPC + Postgres + Kafka is what hiring managers expect today; suggestion chips cover realistic alternatives (Python, FastAPI, MySQL, RabbitMQ) so you can match your real toolchain without losing keyword fit.
Read my full story →

More resources

Other Back-End Engineer Resume Resources

Resume Guide

Back-End Engineer Resume Guide

The full walkthrough from format to skills, by an ex-Google recruiter.

Skills

Back-End Engineer Resume Skills & Keywords

The exact stack and ATS keywords that pass the screen in 2026.

Resume Metrics

Back-End Engineer Resume Metrics

Which numbers to put on your resume: benchmarks for what's average, good, and great.

Tool

Free ATS Checker

Upload your resume and see what an ATS actually parses (and silently drops).

Browse all templates

Every role, organized by family.

Same editor, same export, tailored to each role. Switch templates anytime.

Software Engineering 6 templates
Front-End Developer Back-End Engineer Full-Stack Developer Software Architect Mobile Engineer Web Developer
Hardware & Firmware 6 templates
Embedded SWE Systems Engineer Hardware Engineer Electrical Engineer FPGA Engineer ASIC Engineer
Data, ML & AI 7 templates
Data Analyst Data Engineer Data Scientist ML Engineer AI Engineer MLOps Engineer BI Developer
Cloud, DevOps & SRE 6 templates
DevOps Engineer Cloud Engineer SRE Infrastructure Engineer Platform Engineer DevSecOps Engineer
IT & Networking 6 templates
SysAdmin Network Engineer Network Admin IT Support Database Admin IT Manager
CyberSecurity 7 templates
Security Engineer SOC Analyst Penetration Tester GRC Analyst Cloud Security AppSec Engineer IR Engineer (DFIR)
Testing & QA 4 templates
QA Engineer SDET Performance Engineer QA Manager
Product 3 templates
Product Manager Product Owner Technical Product Manager
Projects & Programs 7 templates
Business Analyst Program Manager Project Manager Scrum Master Agile Coach Delivery Manager Technical Program Manager
Engineering Leadership 5 templates
Tech Lead Staff Engineer Engineering Manager Director of Engineering CTO
Game Development 4 templates
Game Developer Engine Programmer Graphics Engineer Technical Artist
Solutions & Sales Engineering 5 templates
Sales Engineer Solutions Architect Forward-Deployed Eng (FDE) Customer Success Eng (CSE) Post-Sales Engineer
Design 5 templates
UX/UI Designer Product Designer UX Researcher Design Systems Designer Interaction Designer
Dev Rel & Documentation 4 templates
Developer Advocate DevRel Engineer Technical Writer Docs Engineer

Disclaimer. This template is a starting point. Defaults are illustrative; replace every metric and tool with values that reflect your real work. Tailor wording to each job description.