Build Competencies

From Open Source Ecology
Revision as of 17:55, 7 August 2025 by Marcin (talk | contribs)
Jump to navigation Jump to search

There are 6 levels of competency, where pay for work-study time depends on competency:

  1. Technical Competency - Related to technical skill. Ability to execute in a controlled environment of the RLF, doing a task solo or with other dedicated support team members. This emphasizes controlled environment as the data point in extreme cases.
  2. Tactical Competency - Related to context switching. Tested when context switching is applied in the field or in the RLF when transitioning from one task to another, so that good self-management, organization, tool awareness, preparation, cheatsheets, etc come into play in a team scenario.
  3. Peak vs stable - Peak competency is one-off best when everything is perfect. However, the situation is rarely perfect, thus it matters how one negotiates imperfection. Stable competency is what one can do day in and day out.
  4. Sequencing competency - having a good awareness of build order, such that at any given build stage, one can determine the critical next step with precision
  5. Sourcing Competency - ability to follow BOMs, vBOMs, and other instructions for acquiring materials. Determining admissible parts.
  6. Ergonomic Design Competency - ability to design workflows for efficient builds
  7. Executive Competency - ability to make decisions on enterprise aspects, backing them up with back-of-the-envelope cash flow analysis