Easton Francis
Software engineer. Infrastructure included.
I run technology end to end at Rapid Radios, a nationwide communications business supporting 150K+ customers and 1M+ deployed devices. Promoted from Lead Developer to owning all of it: software, cloud, network, security, and the incidents in between.
- Application
- API
- Database
- Cloud
- Network
- DNS
- Identity
- Endpoint
- Vendor
150K+
customers supported by Rapid Radios
1M+
devices deployed nationwide
30 days
from intern to full-time lead
NASA, Delta Air Lines, PepsiCo, U.S. federal agencies
environments supported
The short version.
Promoted to company-wide technology owner
Went from Lead Developer to owning software, cloud, network, security, and IT for the whole of Rapid Radios — and kept shipping code.
Stopped an email attack before customers saw it
Detected an active business-email-compromise and spoofing attack and contained it before any customer impact.
Intern to lead engineer in 30 days
Started at Wolverine Coil Spring as a software quality engineering intern; promoted to full-time Lead Software Engineer within a month.
Led a department-wide overhaul
Ran a four-person team replacing a client's legacy software and infrastructure, from planning through rollout.
Where I've done the work.
Rapid Radios
IT Operations Manager & Lead Developer
Jan 2026 – Present (current role)
Promoted from Lead Developer to company-wide technology owner
- Own the full technology function for a nationwide communications business supporting 150K+ customers and 1M+ deployed devices: software, cloud, infrastructure, networking, security, data, employee technology, vendors, and technical strategy.
- Set the platform roadmap, architecture, technical standards, and reliability priorities, and hire developers — while staying hands-on in production engineering, deploys, and debugging.
- Own critical incidents and root-cause analysis across application, API, database, cloud, network, DNS, identity, email, endpoint, and vendor layers, from diagnosis through prevention.
- Run core IT and security operations: Microsoft 365, identity and access, endpoints, email security, backups and disaster recovery.
- Lead enterprise and government delivery from requirements and security review through deployment and production support.
- Detected and contained an active business-email-compromise and spoofing attack before any customer impact.
Lead Developer
Oct 2024 – Dec 2025
- Built and scaled Rapid OPS, the internal operations platform the company runs on — device provisioning, customer and group administration, carrier and SIM lifecycle, renewals, self-activation, billing, support workflows, migrations, and bulk remediation.
- Architected production integrations across carrier APIs, payments, e-commerce, communications, and support: Simbase, Stripe, Shopify, SendGrid, RingCentral, ShipStation, Slack, and Zendesk.
- Designed high-volume automation for provisioning, migrations, reconciliation, and cleanup across customer, device, carrier, and billing records, replacing fragmented manual work with repeatable software.
- Owned application architecture, database-backed workflows, production debugging, and reliability for systems used daily across the business.
Confidential client (NDA)
IT Project Manager (Contract)
Feb 2024 – Oct 2024
- Led a four-person team through a department-wide technology overhaul, replacing legacy software and infrastructure — planning, migration, rollout, testing, and stakeholder communication.
Wolverine Coil Spring
Lead Software Engineer & IT Analyst
May 2022 – Jan 2024
Promoted from Software Quality Engineering Intern within 30 days
- Designed and delivered automation, production monitoring, process control, reporting, data, and backup and recovery systems used across manufacturing and engineering.
- Paired software development with hands-on IT and production support, replacing repetitive operational work with custom tooling.
Grand Valley State University
IT Technician II
Sep 2020 – Dec 2021
- Supported campus-wide hardware, software, identity, endpoints, classroom technology, and device deployment alongside faculty and staff.
NASADelta Air LinesPepsiCoU.S. federal agenciesNDA-protected global enterprises
Environments supported through my work at Rapid Radios, not employers or clients in their own right.
B.S., Computer Science
Grand Valley State University 2019 – 2023
Information Technology & Web Development Certification
Careerline Tech Center 2017 – 2019
Across the stack means across the stack.
No project gallery here — the point isn't what I've shipped on the side, it's what I've been trusted to run. That means understanding how these pieces connect, not just using each one in isolation.
Applications
- Frontend systems
- Backend services
- APIs
- Authentication
- Databases
- Internal tools
Infrastructure
- Linux
- Docker
- DNS
- Cloud hosting
- Reverse proxies
- Networking
- VPNs
Production
- Deployments
- Monitoring
- Incident response
- Debugging
- Vendor failures
- Reliability
Business Systems
- Stripe
- Shopify
- Simbase
- SendGrid
- RingCentral
- ShipStation
- Zendesk
- Microsoft 365
Technical breadth, by domain.
Software
TypeScript · JavaScript · Python · C# · C/C++ · React · Next.js · Node.js · Flask · REST APIs · OAuth 2.0 · Webhooks
Data
PostgreSQL · MySQL · SQL · Supabase · Data modeling · ETL · Migrations · Reconciliation
Cloud & Linux
AWS · Vercel · Cloudflare · Docker · Linux · Ubuntu · Nginx · Backup & disaster recovery · SSL/TLS
Networking
TCP/IP · DNS · DHCP · VLANs · UniFi · pfSense · Firewalls · NAT · VPN / Tailscale · Windows Server · Active Directory
Security
IAM / RBAC · MFA · WAF · SPF / DKIM / DMARC · Email & endpoint security · Incident response · Phishing & BEC response · Hardening
Leadership
Technical strategy · Architecture ownership · Roadmaps · Developer hiring · Vendor management · Enterprise & government delivery · Incident leadership
Platforms
Stripe · Shopify · Simbase · SendGrid · RingCentral · ShipStation · Slack · Zendesk · Microsoft 365
How I think about the work.
01
Own the whole failure path
Problems rarely stay inside one layer. I trace them through code, database, infrastructure, DNS, network, and vendor systems until I find what actually broke.
02
Prefer understandable systems
I'd rather run a boring system that works than add complexity that isn't earning its place.
03
Automate repetition
Anything done by hand more than a few times is a candidate to become software.
04
Production is part of engineering
Shipping is the easy half. Operating, debugging, and maintaining what's live is the rest of the job.
What does that actually mean?
In practice: I can work the application layer, trace a failing API call, check the database, SSH into the server, fix a broken deploy, check DNS, isolate a network issue, and explain what happened once it's resolved. Most problems don't announce which layer they're in.
I've always been drawn to the parts of engineering where software meets the systems underneath it — building applications, running the infrastructure they depend on, automating the tedious parts, and figuring out what actually broke when something does.