TL;DR
Lead with your primary language at expert depth, not a laundry list. Quantify scale: requests/second, data volume, uptime. Show system design thinking through architectural decisions. Demonstrate database expertise beyond basic CRUD.
Language and Framework Skills
Backend development spans many languages and paradigms. The key is showing depth in your primary stack while demonstrating adaptability.
Example Technical Skills Section:
Languages: Go (expert), Python (advanced), TypeScript/Node.js, SQL
Frameworks: Go standard library, Echo, FastAPI, Express.js
Databases: PostgreSQL, Redis, MongoDB, DynamoDB, Elasticsearch
Infrastructure: AWS (ECS, Lambda, SQS, S3), Docker, Kubernetes, Terraform
Messaging: Kafka, RabbitMQ, AWS SQS/SNS
Observability: Datadog, Prometheus, Grafana, OpenTelemetry, PagerDuty
Practices: REST API design, gRPC, microservices, event-driven architecture, TDD
Language Strategy
- Lead with the job's primary language. If the posting says "Go," make Go your first listed language.
- Show proficiency levels. "Go (expert), Python (advanced)" is more useful than a flat list.
- Go is surging in demand for backend roles in 2026, especially at infrastructure and platform companies.
- Rust is a differentiator for performance-critical systems. List it even as "familiar" if you have exposure.
- Java/Spring still dominates in enterprise. Do not dismiss it-many high-paying roles require it.
API Design Experience
API design is a core backend responsibility. Your resume should show you think beyond just writing endpoints-you design contracts that other teams depend on.
Weak:
Built REST APIs using Node.js and Express
Strong:
Designed and built RESTful API layer (50+ endpoints) serving mobile and web clients, implemented versioning strategy, rate limiting, and OpenAPI documentation-adopted by 4 internal teams and 15 external partners
Weak:
Created microservices
Strong:
Decomposed order management monolith into 6 microservices (Go, gRPC), reducing deployment time from 2 hours to 8 minutes and enabling independent scaling of payment processing during peak traffic (10x normal load)
Weak:
Worked on API integrations
Strong:
Architected third-party integration layer handling 20+ payment and shipping providers, implementing circuit breakers and retry logic that maintained 99.95% uptime despite external service failures
Database Expertise
Backend developers are expected to understand data modeling, query optimization, and choosing the right database for the job. Show that you think about data, not just code.
Database Experience Examples:
- Designed PostgreSQL schema for multi-tenant SaaS application serving 500+ organizations, implementing row-level security and partitioning for query performance
- Migrated from MongoDB to PostgreSQL for transactional data (5TB), maintaining zero downtime through dual-write strategy over 3-month rollout
- Implemented Redis caching layer reducing database load by 70% and p95 API latency from 200ms to 15ms
- Optimized slow queries identified through pg_stat_statements, reducing p99 response time from 2s to 100ms for product search endpoint serving 1M daily queries
Database Skills That Stand Out
- Query optimization: Show you can profile and fix slow queries, not just write them.
- Data modeling: Schema design decisions for performance, flexibility, and integrity.
- Migration experience: Moving between databases or versions with zero downtime.
- Polyglot persistence: Choosing the right database for the job (relational, document, key-value, search).
Infrastructure and Scalability
Modern backend developers are expected to understand deployment, scaling, and infrastructure. The line between backend developer and DevOps is blurring.
Weak:
Deployed services on AWS
Strong:
Designed auto-scaling infrastructure on AWS ECS handling traffic spikes from 5K to 50K requests/second during product launches, maintaining p99 latency under 100ms with zero downtime
Weak:
Set up CI/CD pipelines
Strong:
Built CI/CD pipeline (GitHub Actions) with automated testing, security scanning, and canary deployments, reducing release cycle from 2 weeks to multiple deploys per day with rollback capability
Infrastructure Metrics to Include
- Throughput: Requests per second, messages processed per day
- Latency: p50, p95, p99 response times and improvements
- Reliability: Uptime percentage, MTTR, incident reduction
- Efficiency: Infrastructure cost optimization, resource utilization
- Scale: Users served, data volume, traffic patterns handled
If your work leans more toward infrastructure, deployment pipelines, and reliability than application code, see our DevOps engineer resume example for how to frame that as its own specialization rather than a backend sub-skill.
Example Resume: Mid-Level Backend Developer
Full Resume Example:
Marcus Thompson
Austin, TX | [email protected] | linkedin.com/in/marcusthompson | github.com/marcust
Technical Skills
Languages: Go (expert), Python (advanced), TypeScript, SQL
Frameworks: Go stdlib/Echo, FastAPI, Express.js
Databases: PostgreSQL, Redis, DynamoDB, Elasticsearch
Infrastructure: AWS (ECS, Lambda, SQS, RDS), Docker, Terraform
Practices: Microservices, event-driven architecture, REST/gRPC, TDD
Experience
Senior Backend Engineer | Payments Company | 2023 – Present
- Own payment processing service handling $200M+ monthly transaction volume with 99.99% uptime
- Redesigned transaction pipeline from synchronous to event-driven (Kafka), improving throughput from 500 to 5K transactions/second
- Built idempotency layer preventing duplicate charges, eliminating $50K/month in manual refund processing
- Implemented distributed tracing (OpenTelemetry) across 12 microservices, reducing mean time to resolution from 45 minutes to 8 minutes
- Mentor 3 junior engineers and lead architecture review sessions
Backend Developer | E-Commerce Platform | 2021 – 2023
- Built inventory management service (Go) processing 10M SKU updates daily across 200 merchant accounts
- Designed PostgreSQL schema with partitioning for order history (500M+ rows), maintaining query performance under 50ms
- Implemented Redis caching strategy reducing database load by 65% and API latency by 80%
- Created integration testing framework using Docker Compose, reducing QA cycle from 2 days to 2 hours
System Design Projects
Real-time Notification Service | github.com/marcust/notify
- Designed and built notification service handling 1M+ daily deliveries across email, SMS, and push channels using Go, Kafka, and AWS SES/SNS
Education
B.S. Computer Science | University of Texas at Austin | 2021
System Design on Your Resume
System design is a top interview topic for backend roles, and your resume should demonstrate this skill before you even get to the whiteboard.
Showing System Design Thinking
- Describe architectural decisions. "Chose event-driven architecture to decouple services and improve resilience" shows intent, not just implementation.
- Mention tradeoffs. "Selected DynamoDB over PostgreSQL for session storage due to sub-millisecond latency requirements at 100K concurrent users."
- Include migration stories. Monolith-to-microservices, database migrations, and protocol changes all demonstrate design skill.
- Show production awareness. Monitoring, alerting, runbooks, and incident response are part of system design.
Common Backend Resume Mistakes
Mistakes That Get Backend Resumes Rejected
- No scale indicators. Backend work is defined by scale. Include request volumes, data sizes, user counts.
- CRUD-only descriptions. "Built REST API for user management" is table stakes. Show complexity.
- Missing database depth. Listing "PostgreSQL" without showing optimization, modeling, or migration skills.
- No reliability metrics. Uptime, latency, error rates-these show production awareness.
- Language laundry list. "Python, Java, Go, Rust, C++, Ruby, PHP" suggests mastery of none.
- Ignoring testing. No mention of testing signals you might ship untested code to production.
Build your backend developer resume
MORT's Resume Builder creates ATS-optimized resumes tailored to specific backend engineering job descriptions. Import your LinkedIn, add the job posting, and get a customized resume that highlights your systems expertise.