The most comprehensive bank Interview Answer Review tooling available online.

Yes, i coached an engineer to progress into a manager role with an ownership of delivery responsibility for an entire customer account and managing 3 teams. This progression happened in a course of 3 years. This was during the time when I was leading embedded sw organisation, and while building the time I hired this senior engineer.

He showed good promise and transitioned into top performer with good hold on technology, communication skills and mentoring and helping others. We identified dealing with ambiguity as one of the improvement ares and he systematically addressed that. Cleint communication was next identified target area and he improved on that too.

To help him get better, i provided his opportunities at project work, connected him to mentors and also suggested trainings that he can leverage.

Based on his interest to lead a team, we identified team management as learning focus area.

I started him with a small team of 3 memeber s, gave him autonomy to lead and drive his charter interacting with his team, but with regular check-in to assess how he is doing.

This way he made good use of opportunities provided to him and grew in his cadre. At each growth level, we identified opportunities to improve on and facilitating him with various support parameters including regular feedback mechanism and course correction I was happy to grow a senior engineer to a client account manager

Well mistakes are inevitable but i believe in following processes which can reduce mistakes and also we can foresee and plan to avoid them.

Engineering team should follow below processes:

1.  Thorough Requirement Analysis

2. Design and code review

3. Incremental development and testing

4. Automated testing

5. Monitoring and alerting system on production

6. Post deployment support with retrospective and RCA

I was handling one project where we were integrating a 3rd party api for payment processing and we misunderstood a crucial part of their rate limiting policy of api and didn't implement exponential back off correctly.

During high traffic event, out application hit the rate limit and instead of retrying with exponential backoff we keep retrying immediately which caused a spike in failed transaction and customer complained.

We immediately halt affected service and rollback previous stable version.  We had analysed logs and confirmed that issue and changed logic and implemented exponential backoff retrying and simulated testing with high traffic and documented this as lesson learned .

We learned a lesson that rate limiting is resilience not performance and also not to assume api behaviour based on doc. try and check edge cases to avoid such issues. we have  added this learning in onboarding manual for new developers.