Responsibilities / Introduction Defining reality. That includes providing a clear example of technical excellence and productivity for the rest of the team. The team should be looking at the technical leader as somebody to emulate and follow. Leading by example is crucial in software engineering.Maintaining the project technical vision clear for everyone, from beginning to end. When the team has questions about a particular project or a technical direction, the leader needs to have answers or ways to get answers. A leader without answers is a bottleneck.Keeping in mind most engineering details of a project or system. Developers building parts of a project must keep a focus on what they are doing. It is up to the technical leader to keep in mind the big picture and most of the high-level engineering details. Without that view, the team risks making inconsistent or even incompatible choices.Answering the technical questions that team or stakeholders have. The technical leader needs to help the team to stay focus. One way of doing it is by answering most technical questions coming from team members or external stakeholders. Answering the questions not only provides the proper flow of information, it also informs the leader of what is important in the eyes of others.Helping the team resolve difficult engineering problems. When engineers are in the middle of a difficult problem, they often need a sounding board for technical brainstorming. The technical leader should be naturally seen as the ideal candidate for such discussions and should be able to provide suggestions on how to solve engineering challenges.Reviewing the decisions the team makes to ensure consistency and alignment with the vision. As the keeper of the overall high-level technical knowledge for a project or a system, a technical leader is in the best position to ensure a consistency of direction. Reviewing decisions and adjusting them using suggestions and direction is a key responsibility for a technical leader.Translating engineering realities into simple terms for non-technical stakeholders. Engineers are knee-deep in the details of the code and should not worry about translating details into non-technical language if that doesn’t come naturally to them. A technical leader needs to be able to provide such translation, adjusting the level of detail depending on the audience.Allow the team to make progress by staying out of their way and protecting them from distractions. A technical leader needs to fulfill his or her responsibilities and, at the same time, stay out of the way of the team. He or she must allow other engineers to be as productive as they can be by limiting needless distractions. This is a tricky balance that takes time to master and can definitely swing too far in either direction.Knowing team members strengths and weaknesses. It is a technical leader responsibility to know his or her players and understand their technical strengths and weaknesses. With that knowledge, a lead is able to farm out the work appropriately to the right people.Mentoring team members. A technical leader needs to be seen as a mentor for team members; somebody that can help other engineers improve and move forward in their technical journey. Saying, “Thank you” to the team. A leader guides people to a path, and then let his or her people do the work. When the work gets done, the leader must thank them for their efforts and results achieved. A leader who does not show gratitude to the team is not going to be respected in the long term by the team. Requirement Engineering Manager4+ years of relevant engineering work experience and 2+ hands-on technical management experienceGood JavaScript coding abilities and experience with architectural patterns of large, high-scale application4. sTrack record with HR in recruitment to build incredible engineering teamsActively coached and mentored team members in their careersWork with PM to Organize Weekly scrum, track and audit progress.Been actively involved in setting product strategyReview Code and actively promote refactoring code for re-usability and literacy. 10.Independently started self-sustaining teams11.Consistently made culture sensitive choices that positively impact all of engineering Shipped several projects with multiple dependencies across teamsStack we use include Reactjs, Nodejs, Ejabberd(XMPP), Loopback, Graphql, Hyperledger, Swift, Java
