8 Reviews
Pay was better than most Tier 4 companies. Like 30k more than what PNC or BNYM was offering in the area, but, it's NOT worth it at all. Take the job with PNC or BNYM instead. Or better yet, improve your interviewing skills and get a much better job with a top tier tech company (FAANG or unicorn startup etc).
- No equity or stock options - Terrible 401k match. - Worst management I've ever seen in my 10+ years at several different companies. - No documentation. Not even an emphasis on documentation. They don't care about Unit Tests and they definitely do not have any automated integration testing. - We did not even have a DEV environment that we could deploy to using CI/CD whenever we wanted. We treated QA like it was DEV and it was a hurry up and wait approach. Sometimes PRs would sit for hours or days before they'd get approved and then it would be your fault that the code was late. Give me a break. - Political decisions are made over technology decisions. Example: this one project, even though the product team KNEW the data from this one vendor was bad, we were told we had to use this vendor because it was a sister company also owned by FNF AND our vendors are using it. So it would look bad if we did not use something our competition was using. Who cares??? Make the better technical choice! - Poor architecture. They don't understand what a microservice is supposed to be and they use pub/sub for ALL messages between microservices. It's like nobody there has taken an architecture or system design class. Microservices are supposed to be self contained business objects. Example anything dealing with People gets it's own microservice. Now if you had a reason to scale, let's say your reads were 1,000,000 per second and your writes were small, like 100,000 per second. MAYBE you can then justify splitting it into a "PeopleReadSvc" and a "PeopleWriteSvc". But here, multiple business objects are often grouped in the same microservice, or, the same business object is split out across multiple microservices. Either way, there's no thought given to it. - User Stories and requirements are extremely vague and as you develop solutions, the answers change as the week goes on but the dates remain the same. Then the product team acts like you didn't understand it the entire time. - Release dates are selected without the input of engineering. You're forced to meet them at any cost. This means logging on early (1 to 3 hours early) and staying late (1 to 6 hours late). This can also mean working a full day on Saturday as well. - Due to the poor architecture and design and the use of pub/subs between each microservice, this code is virtually impossible to do any sort of integration testing locally. And as I said, without a proper DEV environment, you have to deploy to QA directly and hope it works. Not good. - This also leads to rushed code getting installed and then you spend the next 3 to 4 weeks doing hot fixes to try to patch it. You get extremely burned out very quick. - Only people left there are foreign with work visas. I feel so bad because they're stuck since it's extremely hard to get another company to sponsor you. So you're left with a lot of people from India who can't really leave and they're stuck working these 12-14 hour days (and Saturdays).
The latest news from the world of investing. If you have an investment story, email: amichael@forbesadvisor.com 18 October: Watchdog Blocks One-In-Five
The latest news from the world of investing. If you have an investment story, email: amichael@forbesadvisor.com 12 October: ‘Patience Pays’ For Long-Ter