Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Configure Frontend Team


The Configure frontend team works on the following Configure stage groups & GitLab projects:

Team Members

The following people are permanent members of the Configure Frontend Team:

Person Role
New Vacancy - Clement Ho (Interim) Frontend Engineering Manager, Configure
Mike Greiling Senior Frontend Engineer, Configure
Jacques Erasmus Senior Frontend Engineer, Configure
Enrique Alcántara Senior Frontend Engineer, Configure
Emily Ring Frontend Engineer, Configure

Stable Counterparts

The following members of other functional teams are our stable counterparts:

Person Role
Grzegorz Bizon Staff Backend Engineer, Configure:System
Taurie Davis Staff Product Designer, Configure
New Vacancy - Nicholas Klick (Interim) Engineering Manager, Configure:Orchestration
Nicholas Klick Engineering Manager, Configure:System
Daniel Gruesso Product Manager, Configure:Orchestration
Dan Davison Senior Software Engineer in Test, Configure:Orchestration
Evan Read Senior Technical Writer, Manage, Verify, Configure, Growth
Thong Kuah Senior Backend Engineer, Configure:Orchestration
James Fargher Senior Backend Engineer, Configure:Orchestration
Hordur Freyr Yngvason Backend Engineer, Configure:Orchestration
João Cunha Backend Engineer, Configure:Orchestration
Tiger Watson Senior Backend Engineer, Configure:Orchestration
Matt Kasa Senior Backend Engineer, Configure:System
Alishan 'Ali' Ladhani Backend Engineer, Configure:System
Alex Ives Senior Backend Engineer, Configure:System
Magdalena Frankiewicz Backend Engineer, Configure:System
Viktor Nagy Senior Product Manager, Configure:System Group
Maria Vrachni Senior Product Designer, Configure

Group focus

We work with both the group::orchestration and group::system backend engineering teams and to facilitate focus and priortization our team members are assigned to one of the two groups. Being assigned to a group doesn't mean you will exclusively work on that groups' work.

The intention is to allow the frontend engineers to focus on a smaller part of the product and optimize their learning and time spent in meetings. We also plan to rotate team members between the groups every few months.

Current group focus:

Team member Orchestration System
Mike Greiling  
Jacques Erasmus  
Enrique Alcántara  

Backend & Frontend Issue Collaboration

Our team follows the GitLab workflow guidelines for working in teams.

Given a reasonable sized issue, that requires UX, frontend and backend work, the preferred way to collaborate on the issue is as follow:

  1. Once an issue is labeled, workflow::ready for development , backend is usually able to start working on the issue.
    1. This is a good time to discuss and clarify interdependency between backend and frontend
  2. Most of the time, only once the issue is marked as UX Ready , is it ready for frontend development.
  3. Backend and frontend will work on the issue in separated branches
    1. Each will submit their own MR for review
    2. Frontend and backend will put the feature behind a feature flag
  4. Once both MRs have been merged, a third MR will be opened to integrate the work where backend and frontend will collaborate to:
    1. Remove the feature flag
    2. Add documentation
    3. Implement e2e tests for the feature

The above is a guideline and clear communication should be preferred over process to ensure the best collaboration strategy on an issue. For example on smaller issues, or where the frontend component of the work is minor, it may be feasible to work on the same branch.


Repos we own or use


Feature development

Our goal is to move towards a continuous delivery model such that the team completes tasks regularly and keeps working off of a prioritized backlog of issues and as such we default to team members self-scheduling their work:

Bug fixing and priortized work

In addition to the self-scheduling of feature development, the manager will from time-to-time assign bugs, or other work deemed important, directly to a team member.

Work prioritisation order

  1. Issues assigned directly to a team member by the manager
  2. Configure group issues
    1. Orchestration
    2. System issues
  3. Working group issues (for when a team member is part of an active working group)
  4. Docs project issues
  5. Pajamas Design System frontend issues

If stakeholders from the Docs or Pajamas Design System projects want an issue priortized above other work they should reach out to the manager who will in consultation with the PM make a determination as to when the work can be accommodated.