skip to content
Eric Cortés
Frontend Engineer & Visual Communication
serviceswork
ende
Frontend Portfolio / 2026

Frontend Engineer

A selection of projects built across product development, systems, creative work, and independent projects.

Focus
  • Frontend: React, Next.js, TypeScript, Tailwind
  • Systems: Storybook, Orval, TanStack React Query, Zustand
  • Delivery: GitHub Actions, Playwright E2E, AWS, PHP
  • Creative: Framer Motion, Three.js / React Three Fiber
Eric Cortés - Frontend Engineering
01 / Ordio

Staff scheduling, workforce management, and frontend delivery.

Ordio helps businesses manage staff and daily operations. I worked on the frontend for scheduling and workforce management, integrating with a PHP-based backend. I also built GitHub Actions workflows for automated testing, preview environments, and AWS deployment.

My roleFrontend development, automated testing, and deployment workflows
StackNext.js, React, TypeScript, GitHub Actions, Playwright, Docker, AWS Amplify

The challenge

  • Make complex schedules and staff data easy to read
  • Translate business rules into clear forms and interactions
  • Test changes against deployed environments before release
  • Support feature-branch testing alongside staging and production releases

My contribution

  • Built interfaces for staffing and scheduling tasks
  • Worked with backend developers to integrate product features
  • Automated AWS Amplify previews and Playwright tests for pull requests, including environment cleanup
  • Built Docker image workflows for staging and production, connecting to the shared release pipeline
  • Worked on feature-branch deployments and release-test workflows with combined reports and failure diagnostics
Ordio1
02 / Remondis UI Library + Neos

A shared component library for REMONDIS Neos.

I worked on UX/UI and frontend development for REMONDIS Neos. Alongside product screens, I built reusable components and documented them in Storybook so common interface patterns could be used across the application.

My roleUX/UI design, frontend development, and shared components
EvidenceReusable components for forms, layouts, and feedback states, documented in Storybook
StackNext.js, Storybook, Tailwind CSS, TanStack React Query

What I built

  • Reusable components for forms, layouts, and feedback states
  • Storybook documentation for shared components
  • Product screens built around common UI patterns

Why this approach

  • Avoid rebuilding the same elements for each screen
  • Keep the interface consistent across features
  • Make existing components easier to find and reuse
Remondis UI Library + Neos2
03 / RawTherapy

AI patient simulation for psychotherapy training.

I designed and built RawTherapy, a platform for practising therapeutic conversations with simulated patients in English, German, and Spanish. Patient profiles define their history, personality, and communication style. A rule engine tracks trust, stress, and openness during the conversation, shaping how readily patients share information and how they respond to the trainee’s approach.

StackReact, TypeScript, Vite, TanStack Router, Zustand, Fastify, PostgreSQL, Redis, OpenAI-compatible language models, Voxtral, Docker
My roleProduct design and full-stack development, including the React interface, simulation engine, voice integration, and evaluation workflow

The challenge

  • Make patient behaviour respond to the conversation rather than follow a fixed script
  • Bring patient settings, training goals, chat, and voice into one usable interface
  • Handle interrupted connections without losing or duplicating conversation history
  • Make feedback traceable to specific moments in the session

My approach

  • Combined AI-generated dialogue with explicit rules for trust, stress, and disclosure; patients can open up, withdraw, or ask to end a session
  • Built configurable training settings that influence the patient’s starting state and response guidance
  • Implemented streaming chat and audio, mobile audio handling, and recovery after interrupted requests
  • Stored sessions in PostgreSQL and pinned them to patient-profile versions so later edits do not change ongoing conversations
  • Required self-reflection before revealing reports, with feedback linked to verified transcript references
  • The scoring rubric is a draft requiring clinical review; production scoring requires approval records for the relevant assessment materials
RawTherapy3
04 / Leica Q Campaign for Virtue Worldwide

An image-led campaign website for Leica Q.

I built the frontend for a Leica Q campaign for Virtue Worldwide. The work focused on image presentation, responsive layouts, and subtle motion.

TypeVisual campaign / branded experience
My roleFrontend development, responsive layouts, and image presentation

My contribution

  • Built layouts that give the photography room to stand out
  • Adapted spacing and image placement for different screen sizes
  • Used motion to support the content without distracting from it

Approach

  • Used image-led storytelling with a clear hierarchy across sections
  • Preserved the campaign’s visual rhythm across screen sizes
  • Kept the interaction restrained so the photography remains the focus
Leica Q Campaign for Virtue Worldwide4
05 / Eric Cortés

A portfolio for photography, design, and frontend experiments.

I designed and built this website with Next.js, React, Framer Motion, and Three.js. It brings together image-led projects, galleries, and interactive experiments.

Project rangeCosta Nostra, Valencia Street, Orgullo, LIM, and other editorial and experimental gallery work
My roleDesign and frontend development
StackNext.js, React, TypeScript, Tailwind CSS, Framer Motion, Three.js, React Three Fiber, Vercel

What I built

  • Different navigation styles for different parts of the site
  • Project galleries with layouts tailored to the images
  • Animated transitions and interactive 3D elements
  • Responsive pages for photography and editorial work

Approach

  • Used route-level presentation choices for different navigation modes
  • Built project-specific gallery systems for image-heavy pages
  • Used motion and interactive elements to support the editorial content
Eric Cortés5
Closing Note

How I work.

Start with the task

I focus on what people need to do, then build interfaces that make the steps clear.

Build for reuse

I use shared components and documentation to keep interfaces consistent as features are added.

Work beyond the frontend

My work also includes API integration, backend development, automated testing, and cloud deployment.

Pay attention to design

Layout, typography, images, and motion are part of the build, not finishing touches.

Eric Cortés6