A useful starting point
Prove data, APIs, reliability. Name stores and queues you ran in production. Two pages. Skip frontend decoration. Skip this page if you are a full-stack generalist applying to a full-stack seat — use that example so the UI work is not missing.
These examples illustrate structure, not a real applicant’s history. Replace every sample detail with your own evidence. Follow the employer’s instructions on qualifications, registration, document length and file format.
Evidence to consider
- API style (REST, gRPC)
- Datastore
- Observability
- A reliability number you can defend
Illustrative achievement bullets
- Designed a REST API in Java/Spring used by 4 client teams
- Migrated 120m rows to Postgres with a dual-write week and zero lost orders
- Added tracing; dropped time-to-diagnose timeouts from hours to 20 minutes
- Wrote idempotent consumers on Kafka for billing events
Relevant skills to substantiate
Java · Spring · PostgreSQL · Kafka · gRPC · Observability
What to leave out
- Buzzword clouds
- Photos
- Unmeasured “scaled the platform”
Choose a layout
Explore the tech template or use it in the CV builder. This is a suggested layout; follow the vacancy’s requirements.