Job brief: Professional Services Technical Architect - West

GitLab · Remote, Canada · facts as of 2026-11-22. Anyone can open this page; no account needed.

Is it still open? · Checked by JoRoute

Still listed. JoRoute saw it on GitLab's own job board 3 hours ago; the employer first posted it on 2026-11-20.

What JoRoute checked · Checked by JoRoute

  • Listed on GitLab's own job board. JoRoute does not take listings from job ads or recruiters.
  • First seen by JoRoute 2026-11-21 (1 day ago); last confirmed on the board 2026-11-22.
  • The apply link opens job-boards.greenhouse.io, the address GitLab's board gives for this job.
  • No other listing with this title and place on this board in the last 90 days.
  • No layoff notices (WARN) under this name in the state files JoRoute reads.

What the listing says · Employer's own words, not checked

  • Pay: Not published
  • Job type: Not stated
  • Where: Remote · Remote, Canada · United States of America
  • Posted: 2026-11-20

What the job asks · Employer's own words, not checked

Level: Not stated. The posting does not state a level or years of experience.

Must have

  • Fortune 500® is a registered trademark of Fortune Media IP Limited, used under license.
  • Work closely with customer project teams to ensure accurate task-level articulation of work required
  • Comfort working in a remote, asynchronous environment, using documented decisions (e.g., issues, proposals, and runbooks) to keep work unblocked across time zones while collaborat…
  • many successful candidates do not meet every single requirement.

Conditions

  • Prefer location in PST, MST or CST timezone alignment. Comfortable with up to 30% travel at times.

Main duties

  • Lead the full technical delivery lifecycle for GitLab Professional Services engagements, from early scoping and technical discovery through implementation an…
  • Deploy and configure GitLab in customer environments, including on-premises and major cloud providers, using Terraform, Ansible, and the GitLab Environment T…
  • Plan and execute source system migrations to GitLab using Congregate, partnering closely with customer stakeholders to reduce risk, protect data integrity, a…
  • Coordinate and oversee implementation work across GitLab team members, partners, and customer points of contact (POCs), ensuring clear asynchronous communica…
  • Mentor Professional Services and partner consultants by contributing documentation, delivery kits, and training materials, and by leading enablement sessions…

Lines copied from the posting, not rewritten. "Preferred" or "nice to have" items are not listed as must-haves.

How it compares · Compared by JoRoute from listings

  • Across GitLab's 48 open listings, 4% of those with a posting date were first posted more than 60 days ago. How GitLab hires

What nobody outside the employer knows · Not known

  • Whether the role is already filled or on hold: employers often leave listings up.
  • How many people applied, and who reads the applications.
  • The pay an offer would carry.

Ask before you apply

  1. What is the pay range for this role?
  2. Is the role fully remote, and from which states can I work?
  3. What are the interview steps, and when should I expect to hear back?

Share this brief

Send it to someone whose opinion you trust. They can open it without an account, and nothing about you is in the link.

Email itText it

To keep a copy, use your browser's Print or Share button.

Next steps

Apply on the employer's page Full listingDoes my CV fit?Practise the interviewShould I apply?

Got a message about this job asking for money or documents? Check the message first.

Keep looking

A summary of facts and listings, not a verdict that this job or employer is safe. JoRoute is not affiliated with GitLab. How JoRoute checks listings · Original posting