5/22/2025 at 2:35:32 AM
This would be fun to work on.But, as an over-30 on HN, I'd be afraid that having the word "mainframe" on my resume would alienate a 20-something co-founder or hiring manager. :)
OK, OK, I did once do a little bit of mainframe-related work. It was reverse-engineering a small part of a certain domain-specific mainframe network protocol, with the goal of replacing at least one of the companies' mainframes with... 21st century Linux servers running... Lisp. (IMHO, the HN karma should at least balance out there by using Lisp, like the post did by using Rust.)
by neilv
5/22/2025 at 3:20:41 PM
I’m mid 40s, had mainframe on my resume from probably 15 years in financial services (not the exciting, high paying kind either). I moved into tech in my mid 30s and am now in a fairly senior leadership role. But that person that gave me a shot in tech, at a YC company that pretty much everyone here has heard of, was in their 20s! I tell you this to encourage you to do interesting things, whatever you think those are. You wouldn’t want to work with a founder or manager who dismisses you because your keywords don’t overlap theirs. You want to work with the founder or manager who asks questions and wants to understand what you learned and how that experience helps you now.Mainframes may not be what you’d work on at a startup today, but they’re complicated pieces of engineering, and writing software for them requires you to understand a lot about how they work. Updating or rewriting their software further requires you to understand how the people before you _thought_ they worked. That’s how I tell that story.
by SmellTheGlove
5/22/2025 at 8:44:26 AM
Just say you worked on an on-prem private cloud.by ahoka
5/22/2025 at 9:40:19 PM
With 99.99999% availability guaranteedby rbanffy