Job Description
Candidate (at least Senior Level) – must know the rationale/reason behind a particular architecture/technology choices. Example –
- Java 11 knowledge – in and out
- Vert.x or Spring 5 based Reactive programming
- Couchbase is an added advantage
- Why using Postgres and not MariaDB/MySQL (one reason could be enterprise unavailability)
- Why using Kafka – can we solve that same problem with other messaging queues?
- Clean code principle
- KISS (Keep it simple and stupid) – why it can be a choice while designing a complex system
- Debugging do’s and don’ts
- SOLID principle – specially Liskov’s substitution principle – How it can be a game changer
Key requirements
- Amex requires development engineering resources in both UK and India
- The project scope is Tokenization and entails migration of 2 services and associated data to India.
- The target environment is Hydra Cloud
- Amex needs to staff one (1) scrum team in UK and two (2) scrum teams in India. There will be 7 engineers in each team. So, a total of 21 engineers.
- Key tech skills
- Java 11 knowledge – in and out
- Vert.x or Spring 5 based Reactive programming.
- Couchbase is an advantage.
- Postgres
- Kafka
- Experience in high availability, scalable systems will be a plus.
- Amex’s UK requires the team to work 3 days a week on site. The India team allows 100% remote work.
- Amex will conduct only one round of interview. The interview will be a one-hour condensed conversation that covers technical and non-technical skills.
- Amex expects to have the team finalized by mid-March.
EY | Building a better working world
EY exists to build a better working world, helping to create long-term value for clients, people and society and build trust in the capital markets.
Enabled by data and technology, diverse EY teams in over 150 countries provide trust through assurance and help clients grow, transform and operate.