Man, I really like that company. From what I can pick up, they're doing neat stuff. It looks like they're trying to pull apart a monolith, and I'm pretty good a

Man, I really like that company. From what I can pick up, they're doing neat stuff. It looks like they're trying to pull apart a monolith, and I'm pretty good at that kinda work. strangle a subsystem, containerize and and such. I've got some experience integrating with bizarre old interchange systems (but not exactly what they touch). I can't figure out how they're keeping all the parts up to date - like, what's their approach to keeping all the libraries and language releases up to date, when the platform starts getting picked to pieces. Stuff like that's tricky and (I think) you really gotta think it through before you have that 1 stray unowned service that hasn't been updated in 2 years. It's weird. I'm a bit more cowboy than I'd like to admit, I'll throw code into prod that I'm not 100% sure of, but I can lay out why I'm not sure, these are the logs and metrics to watch, and this is the rollback plan. quantify the risks, show they payoff, roll the dice (or, not if it's too scary). I'm not super pro in their preferred language. I can mostly read it, I've done a little debugging in it. Open classes are scary, but I know how to grep a monorepo. Maybe I should try to interview there. I dunno, every time there's something that spooks me in the descriptions. I guess they ramp up random impostor syndrome feelings. Maybe I'm not as cowboy as I think I am.