╔══════════════════════════════════════════════════════════════════════╗
║ Software Builder · Engineering Hospitality Technology ║
║ 5 demos · 15 essays · Engineering journal · Honest about gaps ║
╚══════════════════════════════════════════════════════════════════════╝
I'm a full-stack engineer with 5+ years building secure web, mobile, API, and AI systems now deliberately transitioning into hospitality technology.
I founded and ran an AR startup for three years as sole engineer and IT administrator. Then I looked at the hospitality industry still running on 1990s infrastructure and saw a precise engineering problem that matches exactly what I've spent five years learning to solve.
No hotel clients on my CV. Not pretending otherwise. Demos labeled as demos. Always.
const michelle = {
background: ['Web', 'Mobile', 'REST API', 'GraphQL', 'Secure Auth', 'AI / RAG'],
experience: '5+ years production systems · Founded AR startup (2020–2023)',
currentFocus: 'Hospitality Technology',
status: 'Open to roles, contracts & consulting',
locations: 'Dar es Salaam, Tanzania · Remote worldwide',
honesty: 'Demo projects labeled as demos. Always.',
}Languages & Frameworks
Data & Infrastructure
AI & Orchestration
Hospitality Domain (actively learning)
Learning artifacts built to encounter the domain's real complexity not to pad a portfolio.
| # | Project | What I learned | Stack |
|---|---|---|---|
| I | Digital Check-in Flow | Where UI polish ends and PMS integration complexity begins | Next.js · Supabase · PWA · QR auth |
| II | In-Room Ordering API | F&B workflow, reservation-scoped JWT, kitchen webhook events | Node.js · PostgreSQL · JWT · Webhooks |
| III | Housekeeping Task App | How staff UX differs fundamentally from guest-facing design | React Native · Expo · WebSocket · Offline-first |
| IV | Mock PMS Integration Layer | HTNG message formats, OTA_HotelResNotifRQ, reservation sync |
TypeScript · XML parsing · Event queues |
| V | AI Concierge & Staff Assistant | Where LLMs earn their place in hotel ops and where they break | Claude API · RAG · LangChain · pgvector |
✦ Security is my baseline not a feature
5 years building auth systems for production. Hospitality handles
payments and identity at scale. That transfers immediately.
✦ APIs other teams can actually integrate
Hospitality runs on integrations: PMS, POS, OTA, CRM, keylock.
I've designed production APIs for downstream consumers and consumed
badly documented external ones.
✦ Mobile-first is not new territory
Guest and staff apps live on phones with unreliable wifi.
Shipped native apps with offline-first architecture. Not on my
learning list.
✦ AI with proper grounding
Built RAG pipelines that say "I don't know" instead of hallucinating
hotel amenities. The hard part isn't the LLM it's the retrieval
architecture and the failure path.
✦ Honest about gaps
I'll tell you exactly what I know and what I'm still learning.
You'll never need to guess which is which.
I keep a public research log at michellevision.com/journal thoughts, notes, and technical deep-dives from the work of learning this domain.
Recent entries:
LOG-001· On learning a domain you can't work in yet ✦ ThoughtLOG-002· Finishing touches on architecture ◈ NoteLOG-003· Mock PMS Integration Layer Research & Development ⌁ ResearchLOG-004·LOG-005·
Essays on building in and for hospitality technology published as I learn, honest about what I don't know yet.
- What I learned trying to mock a PMS integration from scratch
- Where AI actually helps in hotel operations and where it breaks
- Why digital check-in keeps failing guests
- Offline-first architecture for hotel staff apps
- The legacy PMS grip and where it's actually loosening
- JWT auth tied to reservation IDs a pattern worth stealing
→ All 15 essays at michellevision.com/writing
I'm looking for my first real hospitality technology context as a full-time engineer, contractor, or consultant. Remote or relocation.
