Irene Martin

Irene Martin

I build, test and support business applications — sign-in and permissions, databases, domains, integrations, and the people who use them.

Before that, I worked in operations — setting up accounts, training staff and keeping a team of up to 50 working with its tools.

Based in
Orlando, Florida
Languages
English and Spanish
Irene Martin, smiling, in a black top against a dark background

Selected work

M.D. Sky OS

mdskyos.com (opens in new tab) ↗

A dispatch and operations platform for a trucking company. The owner, dispatchers, drivers and customers each sign in to their own interface, working from the same shipment records.

Who sees what — simplified
OwnerEverything; manages users and roles
DispatcherOpen and active loads; assigns drivers
DriverOnly their assigned loads; updates status from a phone
CustomerOnly their own shipments and where each stands
What I did
Designed and built it; configured Google sign-in, the Supabase/PostgreSQL database and the domain and DNS on Cloudflare; ran testing and releases with the owner.
Key decision
Access is enforced where data is read and written, not by hiding menu items — so a driver or customer who edits a URL still only reaches their own records.
Testing
After each change I sign in as every affected role and check what it can do — and what it should be refused. Changes are tracked in Git, so a broken release can be rolled back.
Status
Live: role-based app, sign-in, core dispatch workflows, hosting and domain. In progress: further third-party integrations, including transportation-management, and full rollout with the client’s team.

Supabase · PostgreSQL · Google OAuth · Cloudflare · GitHub — built through eBuilt.app

My Sweet Pawtner

mysweetpawtner.com (opens in new tab) ↗

The public website and booking system for a mobile pet-grooming business in Miami-Dade, with an admin portal where the owner manages incoming requests.

  1. Service info
  2. Booking
  3. Pickup & drop-off details
  4. Admin portal
What I did
Built the site, the booking flow and the admin portal, and tested them end to end.
Key decision
The form asks for what the owner needs to deliver the service, including pickup and drop-off, so each request arrives complete instead of as a thread to follow up on.
Testing
I submit bookings as a customer would, then check the admin side to confirm every detail arrived complete and correct.
Status
Live: website, booking flow and admin portal. Not yet operational: Square payments and automated follow-ups.

Built through eBuilt.app

Experience

eBuilt.app

Owner · builds and supports business software

  • Build, test, deploy and support web applications and operational workflows for small businesses.
  • Set up sign-in and role permissions, databases, domains and DNS, and third-party integrations.
  • Work directly with clients to understand how they operate, fix problems they report, and walk them through changes.

Prime Healthcare

Agent operations & sales manager · team of up to 50

  • Set up employee accounts and application access, and troubleshot login and platform problems.
  • Onboarded and trained staff, and wrote the procedures and documentation they worked from.
  • Ran tracking for licenses, certifications and payroll details; coordinated compliance requirements and process changes.

The two jobs meet in the same place: someone can’t log in, a record is wrong, a process breaks. At Prime I handled those as the person closest to the team; at eBuilt I handle them as the person who built the system.

Built
Web applications in JavaScript and React, role-based access, booking and admin workflows
Configured
Supabase and PostgreSQL, Google OAuth, Cloudflare domains, DNS and hosting, GitHub
Used & supported
Google Workspace, Microsoft 365, RingCentral, Priority1, Sircon, insurance carrier platforms, QuickBooks, Square, Wix — as a user and helping colleagues with access, not administering their infrastructure
Learning
Enterprise systems administration — directory services, Windows and Linux servers, network infrastructure — which I haven’t administered yet

How I troubleshoot

  1. Scope it

    Who is affected, since when, and what exactly do they see? One user and twenty users are different problems.

  2. Check the layers

    Connectivity, sign-in, permissions, recent changes, and whether the service itself is behaving — in roughly that order.

  3. Test one thing at a time

    Pick the most likely explanation, test it, and change one thing — with a way to undo it.

  4. Verify and write it down

    Confirm with the person who reported it, record the cause and fix, and escalate when it’s beyond my access or role.

This is how I work on the applications I build and support. In a larger IT team, I’d follow its own runbooks, change process and escalation paths.

About

I was born in Cuba and lived in Chile, where I studied two years of pre-med, before moving to Florida. I came to software through operations work, and I still think about technology from the side of the people who have to use it. I’m looking for a team where I can put what I’ve built to work and learn how a larger IT environment is run.