Where do I access the Codvo AI Hub?
You'll get the link on day one with your account activation email. The Hub contains onboarding materials, documentation, best practices, and team resources. Bookmark it—you'll visit it frequently.
What's the difference between NDA, PHI, and PII data rules?
NDA data: Client work under confidentiality agreements—stays in your Codvo account, never shared externally. PHI (Protected Health Information): Healthcare data—never pasted into Claude or any external tool. PII (Personally Identifiable Information): Names, emails, IDs of individuals—never pasted without written clearance. Your Client Data card explains when and how to work with real data.
How do I run ./setup.sh from codvo-workbench?
Clone the codvo-workbench repository to your machine, then run ./setup.sh from the root directory. It provisions the codvo-suite skills to your Claude seat, configures your environment, and sets up MCP servers. Ask your tech lead for the repository URL if you don't have it.
What are the four Codvo Academy courses?
All available at accelerate.neio.ai: (1) Claude Code in Action, (2) Building with the Claude API, (3) Introduction to MCP, (4) Introduction to Agent Skills. You'll complete all four in your first 30 days. They're tracked in accelerate.neio.ai for your manager and the engineering function head.
Who is my function head and what do they do?
Your function head leads the engineering function at Codvo. Every engineer reports up through your function head, directly or indirectly. They present the engineering year at the all-hands Functional Update. They're your escalation path for engineering strategy, resource, and career questions.
What's the Functional Update and when do I attend?
The all-hands Functional Update is where each function (engineering, product, design, data, etc.) presents their year—goals, initiatives, and wins. You'll attend your first one by the end of week 4. It's a great way to understand what the whole company is building.
What's codvo-suite and how do I use it?
codvo-suite is a set of Codvo-specific skills and tools provisioned to every Claude seat. It includes best practices, code standards, internal tools, and company playbooks. It's automatically added when you run ./setup.sh from codvo-workbench.
How do I submit my first PR and what should it be?
Your tech lead will pair with you on a small, achievable first PR (usually documentation or a tiny bug fix) in week 2. By week 4, you should be comfortable picking your own features from the backlog and shipping them. All PRs go through code review—that's normal and expected.
Who should I ask if I'm stuck or confused?
Start with your tech lead or a peer Sr. Full Stack Engineer. If you need engineering leadership input, reach out to your function head. For HR, onboarding, or Codvo-wide questions, ask People Ops. Everyone's here to help—asking questions is always the right move in week 1.
What happens after 30 days?
By day 30, you should be shipping features independently and feeling like part of the team. Your manager will schedule a check-in to review your onboarding, celebrate wins, and set goals for your next quarter. This is just the beginning—you'll keep growing and learning for months to come.