Technical Approach (iTAP)

Your technical approach should ensure high quality code development. Use techniques such as Test- and Behaviour-Driven Development to influence the design and implementation of your code. Component-Driven Development will help focus on maintainability and reusability.

LVL 2 - Engineer I

Writes code that adheres to existing code standards.

  • follows coding and styling standards for their framework, language, or project.
  • modifies existing components within an established project.

LVL 3 - Engineer II

Able to write basic tests and create simple components within an established project. Familiar with the goal of code and test standards to create and maintain robust features.

  • demonstrates and applies basic practical knowledge of test-driven approaches.
  • defines new components by following an already established project architecture.

LVL 4 - Senior I, TTL, SEM

Uses good technical approaches by default, relying on test coverage and good structure to create and maintain robust features. Knows how to effectively use these approaches for complex features, and makes recommendations to improve approaches on their project.

  • has leveraged automated testing tools on multiple projects.
  • has developed non-trivial features using TDD or BDD approaches.
  • prioritizes maintainability and reusability when defining components and guides other team members on how to adopt a modular and decoupled approach to development.
  • guides other team members on good technical approaches.

LVL 5 - Senior II

An authority, guiding others and recommending improvements to our technical approach on multiple projects.

  • has introduced a new automated testing technique or improved an existing one on a project (e.g. added better support for in-memory testing, suggested a new way of organizing test-related files, configured and enabled a new testing tool, enacted a performance optimization on the test suite).
  • guides others on automated testing techniques and writing pragmatic and effective tests.
  • has established a standard component-driven approach for certain development tasks and introduced it to multiple projects

LVL 6 - Principal

An evangelist for good technical approaches, actively promoting and supporting our use of TDD, BDD, and CDD.

  • is a notable promoter of good technical approach across our engineering team, actively guiding teams and individuals.
  • has led a component driven strategy across multiple technologies and influenced the modularity and maintainability of a full application stack (backend, frontend).
  • contributes to proposals for decoupled or headless projects and describes their benefit to non-technical stakeholders.
  • is aware of changes in this area outside of Inviqa, bringing topics for discussion and influencing our best practice as appropriate.