<aside> 💡 Build a more impactful & reliable product while making the job of our developers more engaging.

</aside>

Role and responsibilities

What the Tech Holder is

• The Tech Holder is a project-based position. Projects typically last from 2 to 6 weeks, and every developer will have the opportunity to take on this role at some point.
• The Tech Holder is in charge of managing the project. She will work closely with the Product Manager from kick-off through to delivery.
• She should challenge the Product Manager to define the scope, propose solutions while maintaining our coding standards for performance, quality, and maintainability.

What the Tech Holder is not

• The Tech Holder is never the sole developer on a project.
• She is not an Engineering Manager or a Tech Lead.
• The Tech Holder must not be confused with the Product Manager, although the role does involve challenging the Product Owner.

Three big phases

<aside> 🧯 In the "old-school" V-model, it's estimated that fixing an error identified during the design phase costs 30 times less than fixing it after release.

</aside>

Before development

The main role of the Tech Holder is to evaluate, minimize uncertainty, and anticipate any risks. This require an good understanding of the needs and the current state of the product. Then she will create a set of tasks to achieve the project.

Th will be recorded in a Design Document (‣).

At first, the Tech Holder won’t have all of the answers. That's why she can rely on the whole product team and tech team. However, it is her responsibility that the project starts under the best conditions.

The Tech Holder must:

• Understand the feature (The Study):

  This will constitute the forewords of the ‣

  • Why we want to introduce the feature in our product
  • Define the affected OKR(s)
  • Challenge the cost / benefit of the feature
  • Summarize it in a document to be presented to the team

• Define an action plan (The Plan)

  This will constitute the body of the ‣

  • Define small and incremental tasks needed to achieve the needs
  • Get challenged by the team to make sure the tasks answer the need

During development

During the development phase, the Tech Holder is the main point of contact for any questions regarding development.

She should review ALL PRs related to the project.

During daily meetings, the Tech Holder must:

• Synchronize the work of the team
• Ensure that no one is having trouble
• Ensure that everyone is focused and looking ahead towards the release date

After development

Once the code is rolled out, the Tech Holder becomes the main point of contact for the product team during Acceptance Tests if something does not behave as expected.

Once deployed in production, she is also responsible for errors or performance degradation reported by the Bat·wo·man.