Role-specific evidence guide

Show where engineering terms appear in real work.

Technology names help with retrieval, but credible engineering evidence also explains what you built, the constraint you handled, and the result you observed. Use the target role to decide which details deserve space.

Languages and frameworks

List a language or framework when you can connect it to a project, production responsibility, or meaningful learning experience. Avoid adding a technology solely because the posting mentions it.

  • Application language and runtime
  • Frontend, backend, mobile, or data framework
  • Testing, build, and dependency tooling
  • Cloud platform and deployment environment

Systems and reliability

Job descriptions may use terms such as distributed systems, scalability, observability, security, availability, or incident response. Support them with architecture scope, traffic shape, reliability work, or an operational decision you can explain.

Delivery and collaboration

Engineering work includes review, design discussion, documentation, mentoring, and cross-functional delivery. State your role accurately: leading a design differs from contributing feedback or implementing one component.

  • Technical design and architecture decisions
  • Code review and engineering standards
  • CI/CD, release processes, and automation
  • Mentoring and collaboration with product or design

Use outcomes you can defend

Latency, throughput, error rate, deployment time, cloud cost, support load, and developer productivity can make impact concrete. Include numbers only when you know their source and the contribution is described honestly.

A safe tailoring sequence

  1. Separate required technologies from preferred or adjacent ones.
  2. Find the project or role where each supported technology was actually used.
  3. Add system context, constraints, and outcomes rather than repeating the tool name.
  4. Mark true gaps for learning or discussion instead of concealing them with keywords.

Questions, answered

Frequently asked questions

Should every technology go in a skills section?

No. Prioritize technologies relevant to the target role and reinforce important ones with evidence in project or experience bullets.

Can I include a tool I used only in a personal project?

Yes, if you label the context accurately and can discuss what you built. Do not present personal-project use as production employment experience.

What if the posting asks for a similar framework, not the one I used?

Show the transferable concept and name the framework you actually used. Let the reader evaluate adjacency instead of claiming direct experience you do not have.