3 ms·
I actually worked with Ben for a couple of my formative years as a software engineer - he's an extremely smart guy. I'm no longer with Amex (still up for debat
by Ancalagon 3y ago
I actually worked with Ben for a couple of my formative years as a software engineer - he's an extremely smart guy.
I'm no longer with Amex (still up for debate in my mind if that was a good idea to leave or not), but last I heard the department was very successful in onboarding a lot of their Java engineers to Go and transitioning to a Golang microservice architecture.
- kylehotchkiss 3y agoI find as an end user/consumer that Amex has one of the best web/app experiences of all the traditional financial companies I've interacted with. How did it feel working on it? I get the sense a lot of banking software is makeup on an ancient mainframe but not with Amex. Was it a fairly good environment for developers?
- bob1029 3y agoAre you sure that isn't the case for Amex as well? I recall being forced to use a very particular set of legal characters when defining my password for use with Amex online account services. The exact same constraints I have with several other financial institutions. I suspect that somewhere in the heart of the beast there still lurks an IBM-branded system of record. Just because a machine from the 90s is running the database doesn't mean you can't put a webGL frontend on top of it.
- cempaka 3y agoI used to write for a service that submitted transactions to AmexDirect. It's still done in EBCDIC, an encoding which famously led to a lawsuit against a European bank by a customer who couldn't create an account with his real name.
- Ancalagon 3y agoAmex is probably the one company of my three previous jobs I'd gladly work for again.