None that I can tell. Except, it's so inefficient that you can technically do nothing as long as you send out some reports which nobody reads or understands.
Top to bottom, here are the cons:
Stop working on your career at Wells, which has nothing at the end, and do something good while working.
I applied and got a couple of phone interviews. The first one was a generic one, just to get a sense of who I was. The second phone call was more of a technical call, asking a lot of questions. After that call, I went in to do a meet and greet.
Got a vendor call, and they asked me about my experience. Next, they scheduled my interview for 3 days later. I had an interview with 3 people. All went well, but they needed a more experienced person. So, no luck.
The interview was smooth but hard. It evolved around your experience with data structures and data analytics. The interviewer asked about relational databases, data security, and optimization. The interview was concise but quick.
I applied and got a couple of phone interviews. The first one was a generic one, just to get a sense of who I was. The second phone call was more of a technical call, asking a lot of questions. After that call, I went in to do a meet and greet.
Got a vendor call, and they asked me about my experience. Next, they scheduled my interview for 3 days later. I had an interview with 3 people. All went well, but they needed a more experienced person. So, no luck.
The interview was smooth but hard. It evolved around your experience with data structures and data analytics. The interviewer asked about relational databases, data security, and optimization. The interview was concise but quick.