All-day pair programming is the worst, and most teams expect you to pair all the time. It’s very exhausting to have to pair with another engineer all day. It can be difficult to think clearly when someone is watching you, or you end up succumbing to groupthink. If you lean introverted, then software engineering at Ford may not be right for you.
Please, please, please stop enforcing all-day pairing on software engineers. It should be up to software engineers to decide when it's right to pair on a task instead of just having it be the default way of working. Some things are appropriate to pair on, while other things are not.
Four people interviewed and asked their own questions. You answer them one by one. Some questions were not clear. Whatever you have prepared, you cannot pass an Indian interview if you are not an Indian.
The interview was good. I was asked core Java and Spring-related questions. You need to have an understanding of microservices in addition. The interviewer's attitude was really good. Database knowledge and cloud experience will be an extra benefit.
2 Video Call Interviews 1. Front-end user story implementation. Javascript frameworks and libraries. 2. Back-end user story implementation. Kotlin frameworks and libraries. All implementation must be done using TDD. For the back-end, make sure to
Four people interviewed and asked their own questions. You answer them one by one. Some questions were not clear. Whatever you have prepared, you cannot pass an Indian interview if you are not an Indian.
The interview was good. I was asked core Java and Spring-related questions. You need to have an understanding of microservices in addition. The interviewer's attitude was really good. Database knowledge and cloud experience will be an extra benefit.
2 Video Call Interviews 1. Front-end user story implementation. Javascript frameworks and libraries. 2. Back-end user story implementation. Kotlin frameworks and libraries. All implementation must be done using TDD. For the back-end, make sure to