MAPBU Software Delivery Program Engineering Lead
- Toronto, Canada
The primary purpose of the Engineering Lead (EL) role is to provide project leadership to an area consisting of multiple product teams. Specifically, this Delivery Program Engineering Lead role pairs with the Balanced Leadership Team (BLT) and provides engineering leadership to the teams in the Delivery Program, along with any future teams that may emerge in this area.
For more details on the day-to-day expectations of the role, refer to the section below: What will this Engineering Lead do on a day-to-day basis?
We are looking for someone to fill the role of Engineering Lead for the Delivery Program for a minimum of 18 months and ideally longer. This timeline is based on our observations that it takes multiple months for individuals to become fully productive both on the problem domain of the specific area as well as on the leadership aspects of the role.
FAQIs this role open to distributed applicants?
Yes, this role is open to full-time distributed applicants whose working hours overlap 9am-5pm EST and who are able to travel to the Toronto office regularly (e.g. about one week in six). Historically for Engineering Lead roles we have been looking for individuals to be based in the same office as their teams, as this improves the feedback loops between local teams and local leadership. However, for this role we can support distributed leadership as some teams in the Delivery Program are already, or have been, fully distributed.
That being said, as Delivery Program team members report to managers based in the Toronto office, and the EL will report to a Toronto-based Engineering Program Support, being physically present in Toronto regularly is necessary in order to establish relationships with Toronto Managers and Directors. As a result, preference will be given to candidates who are willing and able to relocate to Toronto.
What are the prerequisites for applying for this role?
Successful candidates will be expected to demonstrate the following:
- Successful anchorship of multiple projects
- Proven ability to coach anchors
- Successful navigation of cross-team dependencies and effective enablement of flow across multiple teams.
- Proven ability to give critical feedback in a timely, actionable, specific, and kind manner
- Strong knowledge of Cloud Foundry, BOSH, and Tanzu - both from an engineering perspective as well as a customer/business perspective
- Demonstrated focus on business-oriented outcomes over technical preferences
- Strong experience in the process of delivering software at scale in terms of visibility, security, and performance
- Strong experience in forming internal release process interfaces for teams to consume
- Developing and navigating intra-MAPBU relationships (i.e. across teams within MAPBU) and intra-company relationships (i.e. between MAPBU and the larger VMWare)
The day-to-day experience of an Engineering Lead varies, but typically there will be some amount of pairing with the BLT, engineers on teams, as well as working with anchors, designers, and PMs across teams to provide area-wide leadership and technical direction. As the engineering interface for the Program, there will also be a substantial amount of time spent not pairing - e.g. in collaborative meetings with other Programs and Business Units, customer calls, etc. The Engineering Lead will also be expected to acquire deep relevant domain experience for the teams in the area.
This Engineering Lead will be expected to represent the health of the teams in the Delivery Program to Toronto managers and directors in the weekly allocations meeting. They will also be expected to identify and rectify team issues (e.g. observing a need to improve psychological safety and hosting a psych. safety workshop; rotating individuals between teams in the area according to product needs and team health needs).
Effective project leadership naturally requires some degree of people-management skills, although this role is not a formal people-management role. There is no expectation that applicants have prior management experience, but successful candidates will need to demonstrate empathy, advocacy, and the ability to receive and deliver critical feedback.
For a deeper dive into this topic, please read the Program-Related Roles and Responsibilities.
VMware is an Equal Opportunity Employer and Prohibits Discrimination and Harassment of Any Kind: VMware is committed to the principle of equal employment opportunity for all employees and to providing employees with a work environment free of discrimination and harassment. All employment decisions at VMware are based on business needs, job requirements and individual qualifications, without regard to race, color, religion or belief, national, social or ethnic origin, sex (including pregnancy), age, physical, mental or sensory disability, HIV Status, sexual orientation, gender identity and/or expression, marital, civil union or domestic partnership status, past or present military service, family medical history or genetic information, family or parental status, or any other status protected by the laws or regulations in the locations where we operate. VMware will not tolerate discrimination or harassment based on any of these characteristics. VMware encourages applicants of all ages. VMware will provide reasonable accommodation to employees who have protected disabilities consistent with local law.
Back to top