For more details about the product vision for Fulfillment, see our Fulfillment page.
The Utilization group manages the Utilization category.
|Chase Southard||Backend Engineering Manager, Fulfillment:Utilization|
|Jason Goodman||Backend Engineer, Fulfillment:Utilization|
|Krasimir Angelov||Backend Engineer, Fulfillment:Utilization|
|Etienne Baqué||Backend Engineer, Fulfillment:Utilization|
|Vijay Hawoldar||Senior Backend Engineer, Fulfillment:Utilization|
|Amanda Rueda||Product Manager, Fulfillment:Utilization|
|Teresa Tison||Senior Product Manager, Fulfillment:License|
|Tatyana Golubeva||Principal Product Manager, Fulfillment:Purchase|
|Timothy Noah||Senior Product Designer, Fulfillment|
|Emily Sybrant||Product Designer, Fulfillment|
|Matthew Nearents||Senior Product Designer, Fulfillment|
|Suzanne Selhorn||Senior Technical Writer, Verify (Runner), Fulfillment|
|Rubén Dávila||Backend Engineer, Fulfillment:License|
|James Lopez||Backend Engineering Manager, Fulfillment:License|
|Mark Chao||Backend Engineer, Fulfillment:License|
|Dan Davison||Senior Software Engineer in Test, Fulfillment:License|
|Reuben Pereira||Backend Engineer, Fulfillment:Purchase|
|Ryan Cobb||Backend Engineer, Fulfillment:Purchase|
|Qingyu Zhao||Senior Backend Engineer, Fulfillment:Purchase|
|Tyler Amos||Senior Backend Engineer, Fulfillment:License|
|Vitaly Slobodin||Senior Frontend Engineer, Fulfillment:Purchase|
|Andrew Kelly||Senior Security Engineer, Application Security, Growth (Activation, Conversion, Expansion, Adoption), Fulfillment (Purchase, License, Utilization), Enablement (Distribution, Geo, Memory, Global Search, Database)|
|Ammar Alakkad||Frontend Engineer, Fulfillment:Purchase|
|Chris Baus||Backend Engineering Manager, Fulfillment:Purchase|
|Ragnar Hardarson||Frontend Engineering Manager, Fulfillment:Purchase|
|Amparo Luna||Backend Engineer, Fulfillment:License|
|Shreyas Agarwal||Senior Backend Engineer, Fulfillment:Purchase|
|Corinna Wiesner||Backend Engineer, Fulfillment:License|
|Andrei Stoicescu||Frontend Engineer, Fulfillment:Purchase|
|Josianne Hyson||Backend Engineer, Fulfillment:Purchase|
|Vincy Wilson||Quality Engineering Manager, Growth, Fulfillment & Protect|
|Vladlena Shumilo||Backend Engineer, Fulfillment:License|
|Chloe Liu||Senior Software Engineer in Test, Fulfillment:Purchase|
|Michael Lunøe||Senior Frontend Engineer, Fulfillment:Purchase|
|Angelo Gulina||Senior Frontend Engineer, Fulfillment:Purchase|
|Justin Farris||Group Manager, Product Management, Fulfillment|
We try to work async as much as possible. However, there are occasions where synchronous communication might be better suited for the task. Our Weekly Team Sync meeting is one of those occasions where we can celebrate wins, collaborate quickly over a number of issues, and generally have some face-time in an all-remote environment.
The Utilization Team meets weekly on Tuesdays alternating each week between at 9:30 AM (6:30 AM PT // 2:30 PM UTC) and 4:00 PM US Eastern Time (1:00 PM PT // 9:00 PM UTC // Wednesday 10 AM NZT) to accommodate teammates in their timezones via Zoom.
[REC] meeting prefix, the meeting is automatically uploaded into the GitLab Videos Recorded folder in Google Drive on an hourly basis via a scheduled pipeline. All teammates are set as alternate hosts and should be able to record the meeting is the Engineering Manager is not present. The recording link will be placed into the agenda after the recording is available.
All team members are encouraged to add topics to the weekly agenda async. In the unlikely event that the agenda is empty, we'll cancel the meeting.
Engineers are responsible for providing async issue updates on active, assigned issues when progress is made. Following the template and guidance for async updates for the entire Fulfillment Sub-department, updates should be made at least weekly. These updates help keep collaborators, stakeholders, and community contributors informed on the progress of an issue.
The Engineering Manager will report before the end of each week on milestone progress in the current milestone planning issue on the following topics:
**Total Weight Closed** XX **Total Weight Open** XX (XX in dev) **Deliverable Weight Closed** XX **Deliverable Weight Open** X (XX in dev; X blocked) **Blocked Issues** X issue(s) (X weight) link, description
It is important to take time off so that you can rest, reset, avoid burnout, take care of loved ones, etc. You are encouraged to take time for yourself or your family following our sub-value of Friends and Family First, work second.
When going out of office, please be sure to clearly communicate your availability with other people. The following steps are required when submitting a PTO notification.
In PTO Ninja, select a role as your backup during your PTO. Please assign the team slack channel #g_utilization as your backup to help distribute the workload. Consider if your current work in progress requires a substitute DRI and assign a single person for those specific issues.
Add the Fulfillment Shared Calendar to your PTO Ninja settings so your PTO events are visible to everyone in the team. The calendar ID is:
email@example.com Read more about PTO in the handbook.
Update your GitLab.com status with your out of office dates by clicking on your profile picture and selecting "Edit Status." For Example:
OOO Back on yyyy-mm-dd Adding
OOO to your status message will keep you from appearing in the reviewer roulette.
~Utilization - BElabel. Issues are arranged in priority order top - down.