About

I’m a Systems Administrator, Full-Stack Developer, and EdTech Specialist with 8+ years of experience building secure, practical systems that keep organizations running—and make complicated workflows feel simple. My work lives at the intersection of infrastructure and software: backend logic, database design, UI flow, automation, and long-term maintainability.

Over the years, I’ve supported teams by turning scattered processes into role-based platforms with clear data models, reliable reporting, and interfaces people actually use. I’m TEFL-certified (Level 5) and bring a calm, structured instructional style that translates well to documentation, training, and educational workflows.

What I build

  • Operational platforms that replace spreadsheets, email chaos, and manual reporting
  • Admin portals & internal tools with clean UX and “real-world constraints” in mind
  • Role-based access control (RBAC), permissions, and multi-level user models
  • Workflow systems (intake → review → action → resolution) with accountability and auditability
  • Dashboards & reporting that improve visibility for staff and leadership
  • Gamified systems (points, ranks, achievements, unlocks, progression logic) when motivation and engagement matter

Flagship work

One of my flagship platforms is FMMS (Forfeiture Management & Monitoring System)—a custom internal case management system I architected and built for a regulated, multi-location operation. FMMS centralized deadlines, financial exposure, documentation, workflow status, and internal reporting into a single production platform designed for high-accountability environments.

Note: FMMS is privately owned by the client and is not available for public demonstration. I’m happy to discuss the architecture, data model approach, and the kinds of workflows it supports.

How I work

I’m opinionated about the foundations: data integrity first, clear roles, and systems that stay maintainable as requirements grow. I like measurable outcomes—fewer manual steps, faster onboarding, fewer errors, and reporting that doesn’t require heroics.

  • Clarity: I write documentation and build interfaces that reduce cognitive load.
  • Structure: I favor normalized relational models, reusable service logic, and predictable workflows.
  • Pragmatism: I optimize for real users and real constraints, not idealized demos.

Education, language, and teaching

My academic background is in International Relations with minors in French and Cultural Anthropology. I’m fluent in French and conversational in Spanish, and I enjoy working in multilingual environments.

Recently, I’ve stepped into a new chapter as a university language-center professor in Latin America. I’m especially interested in the overlap between teaching and systems: placement workflows, assessment tooling, curriculum support platforms, and modern EdTech that actually helps instructors and students. Long-term, I’m working toward deeper coordination work in educational technology—building the systems that make learning programs run well.

Outside of work

I’m a builder in the literal sense, too. I run climate experiments and long-term data tracking in a greenhouse in the Tennessee hills, where “systems thinking” turns into sensors, automation, observation, and iteration over time.

I also love being outside—gardening, hiking, fishing, and the occasional skiing trip when I can get up to mountains. Travel has shaped my perspective as much as tech has: I’ve visited 23 countries outside the U.S. and explored 40 out of 50 U.S. states. Seeing how people live, learn, and work in different places is a constant reminder that good systems should be resilient, human-friendly, and culturally aware.

What I’m looking to build next

I’m drawn to work where I can bridge infrastructure, software, and institutional workflows—especially in education, operations, and organizations that value clean data and thoughtful UX. If you need a system that replaces chaos with clarity, I’m probably in my element.

If you’d like to collaborate—or just want to talk through an operational problem—reach out via the contact page.