VRO Engineer Offboarding

Editors: Any new additions to offboarding that require the reverse process for onboarding should be added to VRO Engineer Onboarding.

Scope:

This document is specifically designed for Engineers offboarding from the VRO (Virtual Regional Office) software project.

For onboarding process, see VRO Engineer Onboarding.

Offboarding checklist

• Remove from recurring team meetings
• Remove from VA-ABD-RRD team, VA-ABD-RRD GitHub team, and Benefits VRO Engineers
• Update status as deactivated on OCTO Benefits Portfolio roster
• If onboarded to VFS Platform:
  • Open a Platform ticket to offboard user. This includes stuff like Slack, SOCKS, AWS, team roster spreadsheet – pick and choose as needed.
  • If leaving vets-api codebase:
    • Open a PR to remove email from flipper.admin_user_emails in config/settings.yml
    • If staying at VA, ask them to leave Sidekiq team (otherwise, removal from GH org takes care of this)
• If not onboarded to VFS Platform, the Platform offboard ticket template can still be used. But we can also open a separate ticket to remove user from GitHub org.
• Remove from on-call rotation for VRO Benefits