career_development: CTO / VP Of Engineering (#323)

engineering/methodology.md

@@ -11,6 +11,7 @@ Date: 2018-04-12
     * [How to pick next issues to worked on?](#how-to-pick-next-issues-to-work-on)
 * [Leads Meeting](#leads-meeting)
 * [Team Meeting](#team-meeting)
+* [CTO Sync Meeting] (#cto-sync-meeting)
 * [Standup](#standup)
 * [Demo](#demo)
 * [Keeping track of things](#keeping-track-of-things)
@@ -29,7 +30,7 @@ do not need to happen at the same time for all teams.
 
 Meetings for high-level sync including product direction, vision, etc are
 proactively scheduled by each Team Lead as needed. All Leads have periodical
-hands-on meetings with the CTO.
+hands-on meetings with the VP of Engineering.
 
 ## History
 
@@ -102,8 +103,11 @@ the issue, its context, and what will take to complete it.
 
 ## Leads Meeting
 
-Same as something called SoS (Scrum of Scrums) before - a weekly meeting on Tuesdays 14:30 for the CTO
-and all team leads to catch up on ongoing progress.
+Same as something called SoS (Scrum of Scrums) before - a weekly meeting on Wednesdays 17:30
+for the VP of Engineering, CTO and all team leads to catch up on ongoing progress.
+
+The Leads Meeting is defined as a meeting  of the VP of Engineering with their
+team, where CTO is invited to attend, to be synced with the daily basis developments.
 
 Each team lead will prepare:
 
@@ -115,9 +119,9 @@ Then grooming company’s backlog/epics from [Company Kanban](https://github.com
 
 ## Team Meeting
 
-A bi-weekly meeting of the CTO with the team lead and optionally with the full
+A bi-weekly meeting of the VP of Engineering with the team lead and optionally with the full
 team (to be decided by the lead), in order to comment the status of the
-projects. Scheduled with each team individually by CTO.
+projects. Scheduled with each team individually by VP of Engineering.
 
 ## Standup
 

engineering/workflow.md

@@ -148,9 +148,10 @@ problems are discovered, etc.
 ### Kickoff Meeting
 
 Once a solution is refined well enough to be worked on and iterations slow down,
-a kickoff meeting is prompted with presence of the leads, the CTO and relevant
-people from the teams to present it and organize the implementation, distribute
-responsibilities to teams and people, and break down tasks and dependencies.
+a kickoff meeting is prompted with presence of the leads, the VP of Engineering
+and optionally the CTO and relevant people from the teams to present it and
+organize the implementation, distribute responsibilities to teams and people,
+and break down tasks and dependencies.
 
 ### Issues/teams tasks
 

talent/career_development.md

@@ -87,18 +87,56 @@ and, in general, be able to make day-to-day work smooth for everyone in the team
 A Team Lead has also a major role in the hiring process (screening, initial calls, 
 code challenge reviews, etc).
 
-#### Head of Architecture
-
-The Head of Architecture provides decision-making inputs on technical issues
-that span across wide areas, as well as mentor, implement and steer development
-practices improvements.
+#### VP of Engineering
+
+The VP of Engineering manages the engineering team on a daily basis. Being 
+the following the primary responsibilities:
+
+- Focused on building and delivering products
+- Grows and manages the engineering team
+- Responsible for the practices and culture of the team
+- Assessing the time it will take to deliver features (or products)
+- Delivering quality releases on a schedule
+- Manager for the leads (this includes responsibility for quarterly one-on-ones)
+- Be part of pre/post sales when the customer requires it (occasionally customers require executive presence) 
+- Delivering quarterly OKR’s for the engineering organization
+
+Is responsible to keep the CTO up to date on decisions made that impact
+the way the team works and is structured; final decision power on these matters
+is with the VP of Engineering, but it’s expected that VP of Engineering seeks advice from the CTO when
+making big changes. The VP of Engineering is responsible to involve the CTO in 
+major architecture / technical decisions that impact the product architecture. 
 
 #### Chief Technology Officer
 
 The CTO is ultimately responsible for running the engineering department and
-providing global direction on development.
+providing global direction on development. Being the following their main responsibilities:
+
+- Have a strong vision, technology visionary of source{d}
+- Work on cutting edge prototypes for the future
+- Set the future technical direction of the company and products
+- Responsible for major long term impacting technical decisions
+- Deeply care about the quality of what we deliver and build
+- Define the product architecture
+
+CTO has final say on the product architecture but VP Of Engineering decides how, when and by
+whom it is implemented. VPEng has decision making power over the day to day
+engineering questions that come from the leads.
+
+CTO can never be a blocker to the VPEng, any decision can always be made by
+the VPEng to move delivering of product/OKR’s forward e.g. in the case of
+holidays or unavailability.
+
+The CTO / VP of Engineering pair can be resumed in these two phrases:
+
+> “The CTO makes sure the technical approach is correct and the VP Engineering makes sure the team is correct.”
+
+> “The CTO makes sure we know what to work on in 6-12 months, and the VP Engineering delivers what we need to do right now.”
+
+
+<hr>
 
-### Appendix - Machine Learning Team
+##### Appendix - Machine Learning Team
 
 <details>
   <summary>The following adds on bottom of the level descriptions to clarify the requirements for ML people.</summary>

talent/hiring_process.md

@@ -60,7 +60,7 @@ This document explains the internal hiring process at source{d} and the responsi
 
 - The interviews are the following:
 
-* Kickoff with the CTO. Duration 60'.
+* Kickoff with the VP of Engineering. Duration 60'.
 * QA: to know the developer better. Two interviewers should participate; one from the team that the developer is being interviewed for, and one from any other engineering or non engineering team (eg. Product, Talent). Duration 60'.
 * Design interview: to see how the developer would design a solution to a given technical problem working with several of our engineers. Each team has specific needs that should be properly covered during this interview. The interviewers are chosen by the lead of the team the developer is interviewed for. Duration 90'.
 * Logical thinking: to see how the developer solves an abstract problem in a logical way. At the moment is conducted by the Lead of Data Science, however it would be convenient to pass the knowledge of this interview to others for the future. Duration 60'.
@@ -84,4 +84,4 @@ This document explains the internal hiring process at source{d} and the responsi
 
 ### Feedback
 
- - After the coding challenge it's very important to obtain feedback from the CTO at each next step.
+- After the coding challenge, it's very important to obtain feedback from the VP of Engineering at each next step.