Onboarding New Developers: Cloud Environment Setup Guide

Onboarding New Developers: Cloud Environment Setup Guide

Onboarding a new developer is a critical moment. Done well, they are productive and confident within days. Done poorly, they spend weeks asking questions, making configuration mistakes, and developing bad habits that persist.

Cloud environment onboarding has its own specific challenges: access control, environment parity, security, and the general complexity of distributed systems. This guide gives you a repeatable process.

Why Cloud Onboarding Fails

Most onboarding failures have one of three root causes:

1. 1Access delays: The new developer cannot access what they need and spends days waiting for permissions
2. 2Missing documentation: Setup steps are in someone's head, not written down
3. 3Environment inconsistency: What they set up locally does not match what runs in production

A good onboarding process is systematic and self-service — the new developer should not be blocked on another person for any part of the setup.

Before Day One: Prepare the Environment

Onboarding starts before the developer arrives. The hiring manager or team lead should complete these steps:

1. 1Create the user account and invite them to the organization — In PandaStack, go to your organization settings and invite the new developer with the appropriate role (Member for most new hires, Admin for senior engineers with deployment responsibilities)
2. 2Configure SSO access — If your organization uses Google Workspace or Azure AD, ensure SSO is configured so the developer logs in with their company credentials. PandaStack supports both Google and Azure/SAML SSO
3. 3Prepare the SETUP.md document — This should be in the repository, not a wiki. It should be runnable by someone with no prior knowledge of the project

Step 1: Access and Authentication (Day One, Hour One)

The developer's first task should be authenticating themselves, not waiting for someone to grant them access.

Checklist:

• [ ] Invited to the organization with correct RBAC role
• [ ] SSO configured — they can log in with company credentials
• [ ] GitHub account connected (PandaStack integrates with GitHub for deployments)
• [ ] Access to the relevant organization(s) confirmed — PandaStack supports multiple organizations, so confirm they can see the right projects

Do not share passwords or API keys during onboarding. If SSO and RBAC are properly configured, none of this is necessary.

Step 2: Local Development Environment Setup

Provide a reproducible local setup:

1. 1Clone the repository from GitHub
2. 2Install dependencies — document exact Node/Python/Go versions required, ideally via .nvmrc, .python-version, or similar
3. 3Set up environment variables — provide an .env.example file with all required variables documented. New developers should not have to ask what variables exist
4. 4Start local services — use Docker Compose to spin up any databases or dependencies locally
5. 5Run the test suite — confirm everything works with a single command

If any of these steps require asking someone for information, that information needs to go into the documentation.

Step 3: Understanding the Cloud Environment Structure

New developers need a mental map of your environments before they touch anything:

Document which GitHub branches map to which environments. If deployments are automated via GitHub integration, explain how — a developer should be able to trace a merge to a running deployment within their first week.

Step 4: First Deployment Walkthrough

Have the new developer make a trivial, low-risk change and deploy it end-to-end. The goal is not the change itself — it is confirming they understand the deployment process.

1. 1Create a branch in GitHub
2. 2Make a small change (a comment, a log line)
3. 3Open a pull request
4. 4Get it reviewed and merged
5. 5Watch the automated deployment trigger in PandaStack
6. 6Confirm the change appears in the staging environment

This builds confidence and catches configuration problems early.

Step 5: Introduce the On-Call and Incident Process

Even junior developers should understand what happens when something breaks:

• Where do alerts go?
• Who is the first on-call contact?
• Where is the runbook for common incidents?
• How do you roll back a deployment?

This is not about burdening new developers with responsibility — it is about ensuring they are not the last to know when something goes wrong.

Step 6: Security Baseline

Cover security expectations explicitly during onboarding:

• Never commit credentials or secrets to the repository
• Use environment variables for all configuration
• Do not share login credentials — everyone gets their own access via SSO
• RBAC roles define what you can do — if you need elevated access, request it through the team lead

The Onboarding Checklist

Keep this in your repository as ONBOARDING.md:

• [ ] Organization invite sent and accepted
• [ ] SSO configured and tested
• [ ] GitHub account connected
• [ ] SETUP.md followed successfully end-to-end
• [ ] Local environment confirmed working (tests pass)
• [ ] Cloud environment structure understood
• [ ] First deployment completed successfully
• [ ] Incident and on-call process explained
• [ ] Security baseline reviewed

Maintaining the Onboarding Process

Every new hire will find something confusing or missing. Make it standard practice: at the end of their first week, ask them to submit a pull request updating the documentation with anything they had to ask about. This compounds over time — each new hire improves the process for the next.

Get started with PandaStack at [dashboard.pandastack.io](https://dashboard.pandastack.io) or review the documentation at [docs.pandastack.io](https://docs.pandastack.io).