Skip to content

Roles and Positions

The “Roles and Positions” section helps you read the GitFlic documentation from the perspective of real work responsibilities: I am in this role or position—what processes do I need to build, what in GitFlic affects my results, and which scenarios make the most sense to start with?

The focus is on real roles and positions involved in development, delivery, change control, security, and operations.

Each role/position page shows:

  • which tasks and areas of responsibility are key;
  • what matters most in development and change delivery;
  • how GitFlic helps structure the workflow;
  • which strategic business scenarios should be reviewed first;
  • which practical steps in GitFlic are the best place to start.

How to read this section

There are two convenient ways to navigate:

  1. From role/position to tasks. Choose your role or position and see which processes are critical for it.
  2. From role/position to scenario. Each page includes links to the strategic business scenarios most closely tied to that area of responsibility.

Top Level

Middle Level

  • Product Manager — connects product initiatives with the delivery flow, change statuses, and release outcomes.
  • Engineering Manager — is responsible for the team’s day-to-day manageability: review rules, change quality, delivery cadence, and reducing operational chaos.

Operational Level

  • Developer — works within the main change flow: code, merge request, checks, artifacts, release, and quality feedback.
  • Platform Engineer / DevOps — owns CI/CD standards, templates, integrations, platform manageability, and a reusable approach for teams.
  • System Administrator — is responsible for installation, updates, backup, recovery, and the baseline resilience of the GitFlic environment.
  • QA / SDET Engineer — is responsible for change quality, built-in checks, test reproducibility, and clear results for the team.
  • Application Security Engineer (AppSec) — is responsible for built-in security practices, early checks, and reducing the risk of security defects in the development flow.
  • Security Operations Engineer (SOC / SecOps) — is responsible for event investigation, activity monitoring, response, and integrating the engineering environment with operational security processes.