Resume-backed technical portfolio

Fermin Quant

Senior software engineer for backend platforms, cloud systems, and delivery modernization.

I build production-facing systems for enterprise and consulting environments, with the strongest public inspection path currently centered on backend APIs, workflow behavior, and code-to-test reasoning.

Open resume Inspect API walkthrough Browse skills

Resume Backend APIs Approval workflow walkthrough

Current inspection Approval workflow API walkthrough

All examples

Inspect first

Approval workflow API walkthrough

Guided scenarios, request/response behavior, code excerpts, mapped tests

Primary path

Resume -> Backend APIs -> Walkthrough

Start with the CV summary, then open the example where the claim becomes concrete

Best for

Hiring managers and engineers

Fast summary on the left, technical inspection surface on the right

Scenario preview

What a reviewer can inspect in minutes

POST /approval-requests

Create a request and derive the first workflow state.

POST /approval-requests/:id/approve

Inspect approval authority, state transitions, and business-rule failures.

POST /approval-requests/:id/reject

Inspect rejection handling, audit notes, and testable failure paths.

Operating areas

Where the portfolio gets concrete fastest

The site is meant to let a reviewer move from claim to inspection with as little hunting as possible. These are the best current entry points.

Area

Backend APIs

Contracts, workflow rules, structured errors, authorization boundaries, tests

Inspect the API walkthrough

Area

AWS serverless systems

Multi-region delivery, cloud patterns, event flows, infrastructure decisions

Read the resume context

Area

Delivery modernization

CI/CD, trunk-based development, release cadence, refactoring, test improvements

Jump to experience

Review path

Start with the resume. Use the walkthrough when the claim matters.

Read the resume like an executive brief.

Use it to understand scope, role types, and where the strongest delivery themes live.

Open the backend API walkthrough.

That is the clearest public example of contracts, workflow rules, code structure, and tests.

Use skills and examples to go deeper.

The supporting paths are there when a reviewer wants specificity instead of overview.