Skip to content
Mario Montano

Mario Montano, full-stack engineer

Systems that keep complex work moving.

I build product software and automation for workflows where context, reliability, and the next action matter.

Currently building internal automation at Ventura Travel. Previously, I built healthcare systems from the ground up at Omniwound.

See current experienceEmail Mario

Scheduled safeguard

A timed check becomes clear, owned work.

Animated examples show a signal entering an automation layer, passing through validation, branching into coordinated actions, and converging on a completed outcome. The examples are generalized and contain no production data or system topology.

Experience

From care systems to global operations.

The domain changed, but the responsibility did not: understand the work, preserve its context, and build systems people can trust when the next action matters.

  1. - Present

    Ventura Travel

    Current

    Full-Stack Developer, Automations

    Build the automation layer that turns business events into coordinated operational work.

  2. -

    Omniwound

    Full-Stack Developer -> Senior Software Engineer

    Joined as a founding engineer, built a healthcare platform from the ground up, and later led architecture, delivery, and developer guidance.

Ventura Travel / current work

What happens after the event.

At Ventura Travel, I build the automation layer that turns business events into coordinated operational work.

A signal can require communication, task creation, provider follow-up, and an internal handoff. The system carries the context so specialists can focus on human judgment.

Current stack: TypeScript, Node.js, GraphQL, PostgreSQL, cloud infrastructure, Docker, and CI/CD.

Live execution00:00.2

Event coordination

Business event received.

  1. 1. Business event: signal received
  2. 2. Context resolution: related records joined
  3. 3. Required email: prepared and sent
  4. 4. Operational task: created with context
  5. 5. Provider follow-up: waits, then resumes
  6. 6. Internal handoff: owner informed
  7. 7. Human-ready outcome: clear next action

The email, task, follow-up, and handoff run in parallel before the workflow produces a clear next action.

Selected systems.

Work where privacy, reliability, and operational speed have real consequences. Product evidence is visible first; deeper walkthroughs stay optional.

DemoEHR, sanitized product environment. Select the image to inspect the gallery.

Production system protected by NDA. Demo uses sanitized data.

Enterprise EMR Platform

A multi-facility clinical platform built for the daily work of care teams.

Led architecture and full-stack delivery across charting, scheduling, prescriptions, labs, billing workflows, audit trails, and role-based access. Managed the path from requirements to production while guiding a three-person development team.

Architecture, full-stack delivery, and technical leadership

100K+
patients supported
100+
healthcare providers
  • TypeScript
  • Next.js
  • React
  • PostgreSQL
  • PHP

InsVerify, sanitized product environment. Select the image to inspect the gallery.

Production system is confidential. Demo uses sanitized data.

Insurance Verification Automation

A web application and automation worker that turned an eight-hour queue into focused exception review.

Designed the dual-system architecture, built eligibility checks and batch processing, and created clear manual-review paths for cases automation could not resolve. Led a three-person team while owning critical implementation work.

System design, automation, product delivery, and team leadership

200+
verifications per day
90%+
automatic success rate
<1 hr
daily exception review
150+
manual hours saved monthly
  • TypeScript
  • Node.js
  • PostgreSQL
  • Puppeteer
  • Next.js

Other shipped work

Client proprietary application

Healthcare Provider Mobile App

Built a native iPad application for patient visits, including offline-first records, wound photography and measurements, prescriptions, and scheduling with EMR synchronization.

Swift, SwiftUI, REST APIs, offline synchronization

Pulse

A product-storytelling experiment built with Astro, GSAP, canvas frame sequences, and scroll-driven interaction.

Open live project
Pulse smart ring product landing page

Ownership, not handoffs.

I started building software in 2017. Since 2019, my work has moved from building a healthcare platform from the ground up to coordinating global travel operations through automation.

Across both domains, I work through product decisions, architecture, implementation, releases, and production support. Reliability, privacy, and operational context are product requirements from the start.

Architecture
Turn ambiguous requirements into system boundaries, data models, APIs, and practical delivery plans.
Delivery
Build critical features, make tradeoffs visible, and stay responsible through release and production support.
Technical leadership
Guide developers, align stakeholders, and create enough structure for teams to move without losing quality.

Tools follow the problem.

My deepest experience is in TypeScript product systems. I also work across operational automation, cloud services, native iOS, and inherited platforms when the product requires it.

Product systems

  • TypeScript
  • React
  • Next.js
  • Node.js
  • PostgreSQL

Operational automation

  • GraphQL
  • Hasura
  • Hono
  • Trigger.dev
  • ClickUp API
  • Google Cloud

Delivery and range

  • Docker
  • GitLab CI/CD
  • Vercel
  • Swift
  • SwiftUI
  • PHP

Have a hard system problem?

Send me context if you want to compare notes on product systems, automation, or high-stakes operational workflows.

Start a conversation
GitHubLinkedIn