The interview process for this role involved 3 stages. 1. Coding assignment 2. Code Pairing and Technical Interview 3. Consultancy Round Overall experience: The coding assignment was take home assignment which was relatively very easy where the focus was more on TDD and how one adds tests, what all scenarios are covered, They expect postive as well as negative scenarios to be covered in the testing. If anyexternal service is involved its expected that you test it using mock. 2nd round was split into 45-45 mins. First 45 mins was paring session with extension to the coding assignment where they will ask you to add features cover scenarios using TDD which are not covered or will ask you to add new features. Next 45 mins were more on the existing projects you have done. Questions on architecture, user flows, scalability, error handling, fault tolerance mechanism and your contributions in the project

Given take home assignment. Actually what HR tells and what reviewer expects is totally different. As per HR the assignment should be in industry standard with all test cases covered. But reviewer thinks it has been over engineered. Unit test cases, Integration test cases and docker deployment given in solution. Added circuit breaker too that as a industry standard. As reviewer he/she thinks it should not be present in initial version. I guess they cannot expect a good code, either bad code. Only I agree may be circuit breaker might be a over engineered. Other than that everything was perfect and it is required.