Skip to content

Alejandro Ortiz Corrofull stack development

Central Belleza public page, the public brand of The Barber Central.
  1. Booking
  2. Operations
  3. WhatsApp

The Barber Central · Approaching productionBooking, WhatsApp and the daily operations of a beauty business.

See this work

I'm Alejandro Ortiz Corro, a software engineer with a strong frontend background. I build interfaces, backend features and integrations around the work people need to get done.

Five products, five real jobs

Each one started with something concrete someone needed to get done. Here is what it solves and what I built.

  1. The Barber Central

    Approaching production

    Booking, WhatsApp and the daily operations of a beauty business.

    Booking, staff availability, customer history and walk-in queues, connected to WhatsApp, payments and email.

  2. NutriPlan

    Testing & production preparation

    The nutrition consultation, and the patient’s follow-through between visits.

    Appointments, nutrition plans, exercise, progress tracking and a patient portal with controlled care-team access.

  3. ETERIA

    Client project · In production

    Event proposals and operations, from the first inquiry to closeout.

    Event operations connecting leads, proposal versions, pricing, inventory and closeout, with a native Swift/SwiftUI iPhone client.

  4. Casa Roca

    Live hospitality experience

    A hospitality website and the reservations its staff manage.

    A hospitality website with content-management and reservation workflows, including check-in, check-out and overlapping-booking checks.

  5. AOHYS website

    Public website and Development System

    This website, its CMS and the system I build with.

    The AI-native product-development lifecycle that carries business intent through domain, specs, agents, verification, preview, and production.

How I build

Start with the workflow.

Understanding the problem comes first. I work through the product and architecture, build in steps I can review, and check that the result supports the intended workflow.

  1. Understand the problem

    Who uses the system, what do they need, and what should happen next?

  2. Connect the product

    Bring the interface, data model and operating rules together around that workflow.

  3. Backend and integrations

    Connect permissions, payments, notifications and APIs to the part of the product that needs them.

  4. Work with coding agents

    Define the architecture and constraints, then divide implementation into tasks I can review.

  5. Check the result

    Review the work, integrate the parts and stay responsible for how the product behaves.

Career

On product teams since 2018; building my own with AOHYS since 2015.

  1. 2018NEORIS / CEMEXSenior Software Engineer
  2. 2018 – 2020AccentureApplication Development Senior Analyst
  3. 2020 – 2021Datazone / AutoZoneEngineer Associate System IT-Development
  4. 2021 – 2022PrenuvoSoftware Engineer
  5. 2022 – 2023DriftSenior Frontend Developer
  6. 2023 – PresentTalaSenior Frontend Developer
AOHYS2015 – Present

Founder · in parallel

Two ways to start

Pick the one that looks like what you need.

Join your team

Full stack software developer, strongest in frontend. I like understanding the business before writing code.

Build your product

If you have a process that lives in notebooks, messages or spreadsheets today, let’s talk about turning it into a custom system.