Truly attempts to uphold what Amex calls "Blue Box Values." Not just lip service.
With recent transformations, especially using the technology-first approach, the company has molted from its state in the first decade of the millennium.
Like with any very large global corporation, you cannot expect the agility of a startup, but the company places very high value on agility and speed of decision-making.
You are treated as a person, not just a body with a brain and hands.
Senior management takes employee feedback seriously.
Very large, matrixed, global, multinational corporation. This makes it a challenge to get a grasp on the who's-who in the company.
Being a bank-holding company, technology decision-making does get impeded due to strict government regulations around the finance sector.
Keep up the good work. Focus on completing the transformation at all levels of organizational hierarchy that was started earlier this decade and has worked wonders thus far in preparing the company for what lies ahead.
It was pretty straightforward. I came on as a contractor initially, then transitioned after two years. It was more of an on-the-job interview. The move to employee was seamless, with the same job and same leader.
Interviewed for the React Engineer position. The first 20-30 minutes included questions about React and general coding practices, such as: * React hooks * Class vs. functional components * How you approach code reviews The coding portion involved f
This was a pure technical interview. It featured mostly technical questions, with not many "get to know you" questions. It felt very much like a test, with questions fired for about an hour. All questions were Java-related, at least for this positio
It was pretty straightforward. I came on as a contractor initially, then transitioned after two years. It was more of an on-the-job interview. The move to employee was seamless, with the same job and same leader.
Interviewed for the React Engineer position. The first 20-30 minutes included questions about React and general coding practices, such as: * React hooks * Class vs. functional components * How you approach code reviews The coding portion involved f
This was a pure technical interview. It featured mostly technical questions, with not many "get to know you" questions. It felt very much like a test, with questions fired for about an hour. All questions were Java-related, at least for this positio