Employee Setup

This document covers everything needed to get a new EGI team member fully operational on their first day and productive within their first week.

Day-1 Checklist

The following must be completed on or before the new hire's first day. The operations lead is responsible for preparing these items in advance.

Account Provisioning

Service	Action	Owner
Email	Create firstname.lastname@egintegrations.com account	Operations Lead
GitHub	Invite to EGI GitHub organization with appropriate team membership	Operations Lead
Slack	Invite to EGI workspace; add to relevant channels	Operations Lead
Vercel	Add to Vercel team with role-appropriate permissions	Operations Lead
SuiteDash	Create account for project management access	Operations Lead
PostHog	Invite to analytics dashboard (developers and PMs)	Operations Lead

All accounts must use the firstname.lastname naming convention. See Account Access for the full provisioning guide.

Hardware and Software Setup

• Confirm the new hire has a suitable development machine (company-provided or approved personal device)
• Install required software per the Tools Required guide for their role
• Verify Git is configured with their EGI email and GPG signing (if applicable)
• Confirm SSH keys are generated and added to GitHub
• Test that the new hire can clone, build, and run at least one active project locally

Access Verification

Before the end of Day 1, verify the new hire can:

1. Send and receive email from their EGI address
2. Access the EGI GitHub organization and see relevant repositories
3. Log in to Slack and post in their team channel
4. Access the Vercel dashboard for their assigned projects
5. Log in to any additional role-specific services

Orientation Agenda

The Day-1 orientation is conducted by the hiring manager and covers the following:

Company Overview (30 minutes)

• EGI mission: custom software and AI development
• The three-company model: EGI builds, Mast optimizes, Anchor operates
• How EGI projects typically flow from development through to Anchor-managed operations
• Current active projects and where the new hire fits

Culture and Communication (20 minutes)

• Communication norms: Slack for day-to-day, email for external, video calls for complex discussions
• Expected response times during business hours
• How to ask for help: post in the relevant Slack channel before DMing
• Meeting cadence: standups, sprint planning, retrospectives

Development Workflow (30 minutes)

• Git branching strategy and PR process
• Code review expectations and turnaround times
• Deployment pipeline overview (GitHub to Vercel, or project-specific)
• How to find and read existing documentation

Buddy Assignment

Every new hire is assigned a buddy for their first 30 days. The buddy is an experienced team member, ideally someone working on a related project.

Buddy Responsibilities

• Daily check-ins (15 minutes) during Week 1, tapering to every-other-day in Weeks 2-4
• Codebase walkthrough: Guide the new hire through key repositories, highlighting architecture decisions, common patterns, and areas of technical debt
• Process guidance: Help the new hire navigate sprint ceremonies, PR reviews, and documentation norms
• Availability: Respond to questions within a reasonable timeframe; escalate blockers to the manager

Buddy Selection Criteria

• At least 3 months of tenure at EGI
• Working on a project relevant to the new hire's assignment
• Willingness and capacity to dedicate time to mentoring

First-Week Milestones

By the end of Week 1, the new hire should have completed the following:

Milestone	Verification
All accounts provisioned and accessible	Operations lead confirms
Local development environment running	New hire demonstrates a successful build
At least one codebase walkthrough with buddy	Buddy confirms
Attended first standup or team meeting	Manager confirms
Submitted at least one small PR (documentation fix, minor improvement)	PR visible in GitHub
Read through this SOP section in full	New hire confirms

Escalation

If any part of the setup process is blocked (missing access, hardware issues, unclear instructions), the new hire should:

1. Notify their buddy immediately
2. Post in the #operations Slack channel if the buddy cannot resolve it
3. The operations lead is responsible for resolving setup blockers within 4 business hours