Portcraft layouts and project evidence

Backend Engineer Portfolio Template

Explain API design, consistency, queues, and operational trade-offs in a text-first backend engineering portfolio with Noir.

Who this portfolio is for

Backend engineers presenting systems whose value is better shown through contracts, tests, and operational reasoning than interface screenshots.

Why choose Noir?

Noir keeps the project list compact and readable, so API behavior and engineering explanations are not crowded out by visual effects.

Upload a PDF or DOCX resume, review the extracted content, then choose Noir from Templates in the builder. This page does not replace your saved design or resume.

  • API design
  • SQL
  • Queues
  • Observability
Noir builder preset with fictional sample content
Actual Noir layout preview with fictional sample content, not a customer portfolio. This is a free preset; hosted publishing is separate.

Project stories worth including

The following are fictional project ideas, not claims about your experience. Replace them with work you can explain and evidence you are allowed to publish.

Idempotent job processor

A fictional queue worker that processes jobs with explicit states and durable deduplication.

Evidence to include

Show a duplicate-delivery test, retry limits, and how an uncertain external result avoids an unsafe automatic replay.

Event audit service

A fictional append-only event API with filtering and bounded pagination.

Evidence to include

Document request contracts, access controls, indexes, and behavior when the persistence layer is unavailable.

Review before you publish

  • Explain delivery and consistency guarantees without claiming exactly-once behavior you cannot prove.
  • Publish API examples with fake tokens and synthetic payloads only.
  • Connect observability screenshots to a concrete diagnosis.
Read the full portfolio launch checklist →

Technical questions and answers

How do I show backend work without screenshots?

Use a short architecture explanation, a sample API contract, a reproducible test, and a permitted repository or walkthrough. Make the failure behavior and your contribution explicit.

Should I publish production logs as evidence?

No. Use synthetic or carefully sanitized examples. Never expose credentials, customer records, session tokens, or confidential infrastructure.