Onboarding & Offboarding
This section covers the complete employee lifecycle at EGI (EGIntegrations), from the first day of onboarding through to offboarding and knowledge transfer. These procedures ensure every team member is set up for success and that transitions are handled cleanly to protect both the individual and the company.
Process Overview
EGI operates alongside two sister companies -- Mast (systems efficiency) and Anchor MSP (managed services). Onboarding procedures are tailored to the role being filled, but the core timeline and expectations are consistent across the organization. Every new hire follows a structured ramp-up period designed to balance learning with early contribution.
Onboarding Timeline
Week 1: Accounts, Tools, and Orientation
- Day 1: Welcome meeting with manager, company overview, and mission briefing
- Day 1: Provision all accounts (GitHub, Slack, Vercel, email, SuiteDash, PostHog) per the Account Access guide
- Day 1-2: Hardware and software setup per the Tools Required guide
- Day 2-3: Orientation sessions covering EGI culture, the three-company model, and communication norms
- Day 3-4: Introduction to active projects and repositories
- Day 5: End-of-week check-in with manager to address questions and confirm account access
Week 2: First Tasks and Buddy Pairing
- Buddy assignment: Each new hire is paired with an experienced team member who serves as a day-to-day resource (see Employee Setup)
- First tasks: Small, well-scoped issues or documentation tasks to build familiarity with the codebase and workflow
- Codebase walkthrough: Buddy-led tour of key repositories, architecture patterns, and deployment pipelines
- Process introduction: First exposure to sprint ceremonies, PR review expectations, and documentation standards
- End-of-week check-in: Review progress on first tasks, adjust pace as needed
Month 1: Independence and First Deliverable
- Weeks 3-4: Transition from guided tasks to independent work on a meaningful feature or improvement
- First deliverable: Complete at least one PR that ships to production, demonstrating understanding of the full development lifecycle
- Documentation contribution: Add or improve at least one piece of internal documentation (see Documentation Expectations)
- 30-day review: Formal check-in with manager to discuss performance, comfort level, and goals for the next quarter
Offboarding Timeline
Offboarding is equally structured to protect company assets, ensure knowledge transfer, and maintain a professional relationship.
| Timeframe | Action |
|---|---|
| Notice received | Manager notifies operations lead; offboarding checklist initiated |
| First 48 hours | Knowledge transfer sessions scheduled; documentation review assigned |
| 1 week before departure | All account access reviewed; handoff documentation finalized |
| Final day | Access revoked across all services; equipment returned; exit interview conducted |
| Post-departure | Audit of all shared credentials; update of team access matrices |
See Offboarding Procedures for the complete checklist.
Section Contents
- Employee Setup -- Day-1 checklist, orientation, and buddy assignment
- Account Access -- Service accounts by role, provisioning steps, and naming conventions
- Tools Required -- Required software and tools organized by role
- Documentation Expectations -- What, when, and how to document
- Offboarding Procedures -- Account revocation, knowledge transfer, and exit process
Responsibilities
| Role | Onboarding Responsibility |
|---|---|
| Hiring Manager | Initiates onboarding, conducts orientation, assigns buddy, runs 30-day review |
| Operations Lead | Provisions accounts, handles equipment, manages offboarding checklist |
| Assigned Buddy | Day-to-day guidance, codebase walkthroughs, answers questions |
| New Hire | Completes setup, asks questions, delivers first tasks, documents learnings |