Portfolio

Projects & experience

Internal applications and automation I built, followed by the operations and leadership experience behind them. Outcomes are reported estimates from the work described below.

Systems & operations

Selected work

Built systems

Project 01

Accounts Payable Automation

Purpose
Cut repetitive encoding so ops and accounting keep judgment work.
Problem
Manual supplier-invoice to books work burned about two hours every day across many channels.
Solution
A Ruby on Rails tool uses Selenium to process supplier invoices across vendor and accounting platforms. People review the results.
Outcome
About 2 hours/day down to about 10 minutes.
When things change
Run history shows what succeeded and failed. Reviewers handle exceptions, and the team can fall back to the manual process when a supplier site changes.
Ruby on RailsSeleniumPostgreSQL
Read the project story →

Project 02

ERP Inventory Automation

Purpose
Keep ERP stock aligned with real sales so profit and operations stay honest.
Problem
Point-of-sale did not update ERP stock. Branches spent more than 40 hours a week on manual adjustments.
Solution
Browser automation posts stock adjustments through an ERP with no usable API. Analysts review exceptions and decide when figures need attention.
Outcome
Manual updating previously took more than 40 hours/week. About 40% of that time remains for analysis and waiting on the ERP.
When things change
When ERP screens change or maintenance interrupts automation, operations can return to the manual process while the tool is updated.
JavaScriptBrowser AutomationERP integration
Read the project story →

Project 03

Timekeeping & IT Asset Management

Purpose
Give ops, HR, and management one place to see who is working, what they use, and where assets live.
Problem
Attendance and assets lived in separate, mostly manual workflows — hard to reconcile people, workstations, and equipment.
Solution
In-house kiosk timekeeping integrated with asset tracking, including a visual seat plan that maps people and workstations to their assets.
Outcome
Saved $43,200/year vs a subscription timekeeping product; faster onboarding accountability; clearer ownership for IT and HR.
React.jsRuby on RailsPostgreSQLRedisActive JobNode.js
Read the project story →

Project 04

Event Organizer

Purpose
Help ops and management run large recurring events and understand engagement — not just headcount.
Problem
Paper sign-offs and manual meal/raffle flows burned staff time and left no useful view of participation patterns.
Solution
Rails/React event system with seating, meal/raffle flows, calendar heatmaps, engagement insights, and v1 per-user profiling.
Outcome
Supports 300+ people across multi-day weekly events; saved up to 10 hours weekly vs signature sheets; leaders see who engages and when.
React.js on RailsPostgreSQLAnalytics

Project 05

Server Room Monitoring

Purpose
Give management and IT planning visibility into environmental risk — not only a live temperature number.
Problem
Point-in-time sensor checks missed patterns that drive overheating risk and capacity planning.
Solution
Real-time temperature/humidity monitoring plus time-based and seasonal heatmaps for hour/day trends.
Outcome
Earlier detection of risky conditions and clearer capacity planning; avoided commercial monitoring spend while improving preventive maintenance.
Ruby on RailsPostgreSQLIoTHeatmaps

Project 06

Access Control System

Purpose
Secure facility entry while feeding unified attendance data.
Problem
Commercial access control was costly and disconnected from timekeeping.
Solution
Hardware/software access system integrated with the timekeeping stack.
Outcome
Saved $4,406.77 vs commercial alternatives; unified entry and attendance records.
Python 3SQLiteKeycard Integration

Project 07

Uptime Monitoring

Purpose
Alert ops when devices and production services fail.
Problem
Downtime was discovered late, slowing incident response.
Solution
Proactive availability alerting for on-prem devices and production apps.
Outcome
Faster detection and shorter resolution paths for service incidents.
MonitoringAlerting

Operations & leadership

Experience 01

Network Management & Security

Purpose
Keep a 300+ user network performant and segmented.
Problem
Growth exposed bottlenecks and weak segmentation without HA planning.
Approach
pfSense with HA load balancing, VLANs, QoS, and regular audits; bare-metal AD support.
Outcome
Stable connectivity for 300+ users with clearer security boundaries.
pfSenseActive DirectoryBare Metal

Experience 02

Technical Training & Knowledge Sharing

Purpose
Raise baseline IT independence across departments.
Problem
Level 1 issues concentrated on a small support group.
Approach
Training on pfSense, Active Directory, and IT practices; invited talks at alma mater.
Outcome
Fewer Level 1 tickets; broader cross-team technical confidence.
MentorshipActive Directory

Experience 03

Google Workspace Admin & IT Audits

Purpose
Protect company identity and data for 300+ users.
Problem
Account sprawl and policy violations created security and reputation risk.
Approach
Workspace administration plus internal audits and digital forensics when needed.
Outcome
Stronger access hygiene and faster resolution of policy incidents.
AdministrationSecurity

At work

Photos & stories

A few experiences that shaped how I work, from building infrastructure to learning directly from the people who use the software I build.

Melquizedek working at a network rack in a server room

Building a server room from the ground up

I was part of a team that built a server room from scratch under the guidance of an experienced network engineer. We worked on equipment procurement, network cabling, firewalls, routers, switches, and power infrastructure.

The experience showed me how infrastructure decisions affect availability, security, and the people who rely on those systems every day.

Melquizedek presenting about building software products to students

Building software products: an engineer's perspective

Inspired by Michael Seibel's Building Product talk at Y Combinator, I shared my perspective on building software products beyond writing code. We discussed how to understand users' problems, ask better questions, and turn real needs into product decisions.

Actual users change how we build. Their feedback and daily experience challenge assumptions and show us what matters.

Melquizedek with students and organizers after an engineering seminar

Systems thinking: from business problems to working solutions

With students and organizers, I used a smart parking management system to explore systems thinking. We started with the business problem, compared possible solutions and their tradeoffs, then translated those decisions into requirements, user stories, and user experience.

I also demonstrated how an IoT device can communicate with a Ruby on Rails application, connecting hardware and software in a practical example.

People reviewing a registrar workflow together at a laptop

Registrar workflow: shaping software through teamwork and feedback

Our team presented an early version of a custom application to technical and non-technical people involved in registrar operations. Together, we explored how it fit their workflows, gathered feedback, and identified where it could better support their daily work.

This project taught me that leading a team means helping each person contribute where they excel. Our success came from that teamwork and from listening to users as we refined the application together.

Have a similar problem?

Tell me about the workflow or system you want to improve.

Get in touch →

© 2026 Melquizedek Felix. All rights reserved.

Privacy