"Success can be measured in various forms, both quantitatively and qualitatively.
How many projects were delivered on time?
Is the team tracking well against timelines? How often do they need to be course corrected?
How much of the architecture is scalable when features are built on top of their work?
What is the technical quality of the work produced by the team?
How often are engineers from the team looped in for advice, mentorship outside the team?
How often & why are interp"
MM4 - "Success can be measured in various forms, both quantitatively and qualitatively.
How many projects were delivered on time?
Is the team tracking well against timelines? How often do they need to be course corrected?
How much of the architecture is scalable when features are built on top of their work?
What is the technical quality of the work produced by the team?
How often are engineers from the team looped in for advice, mentorship outside the team?
How often & why are interp"See full answer
"I gave an example of a situation where on the project we needed to onboard 110 applications into the system to get their account and entitlement information for quarterly access review work stream. Traditionally we could have gone manual route and could have done it manually one by one which would have required more time and resources. I actually understood the applications and how they are built by talking to application owners and then based on the data bucketed them and found the pattern that"
Neo S. - "I gave an example of a situation where on the project we needed to onboard 110 applications into the system to get their account and entitlement information for quarterly access review work stream. Traditionally we could have gone manual route and could have done it manually one by one which would have required more time and resources. I actually understood the applications and how they are built by talking to application owners and then based on the data bucketed them and found the pattern that"See full answer
"I faced twice and it always slows down the career trajectory of engineers with complete context loss of previous hard earned projects"
Graig - "I faced twice and it always slows down the career trajectory of engineers with complete context loss of previous hard earned projects"See full answer
"Depends on the kind of goals they are trying to pursue. I would clarify with the interviewer.
. if you work for say a fintech, and are trying to create say a real-estate app with company resources - no go
. if you want to write a book on management say while being an EM, then there's some wiggle room here. As long as you get the book approved by your IP team, should be ok
. if you want to work on a hackathon project on something tangentially related to your team, still ok as long as the concept"
Musa G. - "Depends on the kind of goals they are trying to pursue. I would clarify with the interviewer.
. if you work for say a fintech, and are trying to create say a real-estate app with company resources - no go
. if you want to write a book on management say while being an EM, then there's some wiggle room here. As long as you get the book approved by your IP team, should be ok
. if you want to work on a hackathon project on something tangentially related to your team, still ok as long as the concept"See full answer
"When talking about my role in current team, I talked following things:
High level technologies used.
Collaboration work I did with PM and Design counter parts.
Web UX features that we built.
Hiring and boot strapping team from 0.
Given that there is straight match to the profile hiring manager was looking for, he got pretty excited and spent time selling the job."
Sudhakar P. - "When talking about my role in current team, I talked following things:
High level technologies used.
Collaboration work I did with PM and Design counter parts.
Web UX features that we built.
Hiring and boot strapping team from 0.
Given that there is straight match to the profile hiring manager was looking for, he got pretty excited and spent time selling the job."See full answer
"• Leadership and Team Management:
• Lead, mentor, and develop a team of software engineers, fostering a collaborative and high-performance work environment.
• Conduct regular one-on-one meetings, performance reviews, and career development sessions with team members.
• Facilitate effective communication and collaboration within the team and with other departments.
• Project Management:
• Oversee the planning, execution, and delivery of engineering projects, ensuring they are completed on time, w"
Scott S. - "• Leadership and Team Management:
• Lead, mentor, and develop a team of software engineers, fostering a collaborative and high-performance work environment.
• Conduct regular one-on-one meetings, performance reviews, and career development sessions with team members.
• Facilitate effective communication and collaboration within the team and with other departments.
• Project Management:
• Oversee the planning, execution, and delivery of engineering projects, ensuring they are completed on time, w"See full answer