About Jeff Trotman

Student code in orbit

A classroom STEM platform where students wrote Python in a browser and the application multiplexed an entire class onto a single Raspberry Pi with a custom sensor board at the front of the room.

Platform builds were deployed to flight hardware, and student-written code executed on payloads aboard the International Space Station. I inherited the whole stack — React and Django REST on Azure — after the only technical staffer left, then absorbed a second acquired product on an entirely separate stack (Arduino, Angular.js and Ruby on Rails) and ran both in parallel.

A portal that had to stay inside its own borders

A crewed space mission included a science session for students in a country whose law required citizen data to remain physically in-country.

At the time, only one major cloud provider had a data center there — so the portal was built and hosted on Oracle Cloud Infrastructure rather than the stack we'd otherwise have used, translated into Arabic, and sized for up to a million participants.

Finishing the last ten percent

A life sciences compliance product had a development team and had been near-complete for a long time.

I served as technical counterpart to a non-technical co-founder, got the product launched and into production with domestic and international customers — including on-site implementation abroad — and then ran it: cloud hosting, a migration to a new authentication system, enterprise SSO negotiated with each customer's IT department, and integrations with expense and e-signature platforms. The company was later acquired.

When the team leaves and the revenue doesn't stop

A revenue-generating application lost its entire development team.

I took over as the only technical resource — feature development, hosting operations, reconciling payments against the books, and customer support — and kept it running without interruption.

Archiving that can't go dark

A medical records archiving platform on AWS had to keep running through a corporate merger after its head of technology departed.

Continuity wasn't a preference; records retention is a legal obligation, and the system stayed up through the transition.

Standing up a practice that had just lost its IT department

A medical practice separating from the hospital that had owned and supported it needed its own technology from nothing — ten locations, more than a hundred employees, plus a billing company and a non-profit.

I built out IT and telecom across all of it, and brought two new clinics and two imaging centers online as they were constructed, working from plans and coordinating wiring and specifications with contractors.