The following people are permanent members of the Create:Editor BE Team:
|Darva Satcher||Engineering Manager, Create:Knowledge & Create:Editor|
|Francisco Javier López||Senior Backend Engineer, Create:Editor|
|Mark Chao||Backend Engineer, Create:Editor|
|Alex Pooley||Backend Engineer, Create:Editor|
|Markus Koller||Backend Engineer, Create:Editor|
|Amparo Luna||Backend Engineer, Create:Editor|
|Alexander P.||Backend Engineer, Create:Editor|
The following members of other functional teams are our stable counterparts:
|Achilleas Pipinellis||Technical Writer, Create, Package, Monitor, Secure, Defend|
|Marcia Ramos||Technical Writer, Create, Release|
|André Luís||Frontend Engineering Manager, Create|
|Paul Slaughter||Senior Frontend Engineer, Create:Editor|
|Marcel van Remmerden||Interim UX Manager, Dev & Senior Product Designer, Create:Editor & Search (Interim)|
|Tomislav Nikić||Software Engineer in Test, Create:Knowledge, Create:Editor, Gitter|
|Denys Mishunov||Senior Frontend Engineer, Create:Editor|
|Himanshu Kapoor||Senior Frontend Engineer, Create:Editor|
|Kai Armstrong||Product Manager, Create:Editor|
|R. K.||Frontend Engineering Manager, Create|
A full-featured Integrated Development Environment (IDE) built into GitLab so you can start contributing on day one with no need to spend days getting all the right packages installed into your local dev environment.
Store and share bits of code and text with other users. This category is at the "minimal" level of maturity.
Do pair programming directly in the Web IDE. This category is planned, but not yet available.
This chart shows the progress we're making on hiring. Check out our jobs page for current openings.
The following Create:Editor BE Team vacancies are overdue to be filled. They are counted toward today on the chart above.
|Backend Engineer, Create:Editor||2019-09-01|
There is a general onboarding issue assigned to all GitLab team members by People Ops on your first day.
All GitLab Team members are expected to follow the General GitLab communications guidelines.
In general, we use the standard GitLab engineering workflow. To get in touch
with the Create:Editor BE team, it's best to create an issue in the relevant project and add the
~backend labels, along with any other
appropriate labels. Then, feel free to ping the relevant Product Manager and/or
Engineering Manager, as listed above.
For more urgent items, feel free to use #g_create_editor on Slack.
Career development conversations in the Create:Editor BE team are centered around a Career Development Sheet that is based on the Engineering Career Matrix for Individual Contributors. The sheet lists the expected current level behaviors on the left, the next level behaviors on the right, and uses colored columns in between to visually represent the extent to which the individual has shown to have grown from the current level to the next. Columns to the right of a next level behavior are used to collect specific examples of that behavior, which serve as evidence of the individual's growth.
Both the matrix and the sheet are Works in Progress; the development of the career matrix is tracked in an epic, and as the matrix evolves, the sheet will be updated to match.