Built for the role in data/role.txt, using onboarding-notes.md and your team's project. Tick things off as you go — it saves on this device.
Your browser isn't saving checkbox or note progress right now (private browsing or storage is blocked). Everything still works, it just won't remember between visits.
Overall
0/0
Week 1
0/0
Week 2
0/0
Week 3
0/0
Week 4
0/0
Week 1 · Access and orientation
Get your accounts working, meet your manager, understand where Pre_Offer sits.
Who you meet
Manasi Rane, Talent Acquisition Manager – I (your reporting line)check title fits your role
Teammates on Zoho Migration: Pre_Offer names not in data
What you read
Codvo AI Hub
Client Data do's and don'ts card
data/onboarding-notes.md
What you ship
Dev environment running locally
First commit on a sandbox branch
Week 2 · First contribution
Land a real change and learn how the team ships.
Who you meet
A teammate to pair with on your first ticket not named
Your function head, ahead of the next Functional Update not named
What you read
Existing Pre_Offer tickets and docs location not given
What you ship
First pull request merged into Pre_Offer
Week 3 · Ownership
Own something end to end, and get straight on the data rules before touching anything real.
Who you meet
Whoever owns the Pre_Offer roadmap, for a scope conversation not named
What you read
Client data rules again, before any real Zoho data touches your machine
What you ship
One feature or bug resolved and deployed deploy process not documented
Week 4 · Running on your own
Finish the Academy courses, run a sprint independently, check in with Manasi.
Who you meet
Manasi Rane, for your 30-day check-in
What you read
Your own week 1–3 notes, before the check-in
What you ship
One full sprint contributed on your own
30-day retro notes for Manasi
Questions a new joiner actually asks
What do I need working on day one?
Your Codvo account and Claude seat, both active on day one. Get the Codvo AI Hub and the Client Data do's and don'ts card read the same day.
What is the Codvo AI Hub?
The internal reference for how the org uses Claude and AI tooling. It's required reading in week 1, alongside the Client Data card.
What are the Client Data do's and don'ts, in short?
NDA data stays inside the Codvo account. PHI and PII never get pasted anywhere. Real client data only after you're cleared for it in writing. Read the full card, this is the short version.
What is codvo-workbench, and do I need to run setup.sh?
It's the team's local dev environment repo. Yes, run ./setup.sh from it in week 1 to get your environment working.
Are the Codvo skills already on my Claude seat?
The codvo-suite skills are provisioned to every Claude seat by default. Confirm yours has them; if not, that's a week 1 ticket, not something to build yourself.
Who do I report to, and where does my function fit in?
Your team sits under Manasi Rane, Talent Acquisition Manager – I, on Zoho Migration: Pre_Offer. Every function reports to a function head, who presents the year at the all-hands Functional Update. Confirm your specific function head in week 1 or 2, this page doesn't have that name.
What courses do I need, and where do I track them?
Four Claude Academy courses: Claude Code in Action, Building with the Claude API, Introduction to MCP, and Introduction to Agent Skills. Track progress at accelerate.neio.ai.
Can I use real client data while I'm learning?
Only once you're cleared in writing. Until then, work from sandbox data or the bundled samples. NDA data never leaves the Codvo account, and PHI or PII never gets pasted anywhere, seat or no seat.
What is Zoho Migration: Pre_Offer, and where do I fit?
It's your team's project. This page doesn't have the module's exact scope or tech stack. Get that from Manasi or your first pairing partner in week 1, and add it to your week 1 notes above.
What do I do if something on this page is wrong or missing?
Check the "What's missing" list below first, it's the known gaps. If it's something else, flag it to Manasi, and update this page for whoever joins next.
What's missing
No named teammates or tech lead on Pre_Offer to introduce by name in week 1.
No repo URL or ticketing system link for Zoho Migration: Pre_Offer.
No confirmed tech stack (languages, frameworks) for a Sr. Full Stack Engineer on this project.
No documented deployment or release process.
No named function head, only that one exists and presents at the Functional Update.
No fixed date or cadence for the Functional Update all-hands.
Manasi Rane's title is Talent Acquisition Manager – I. That's the reporting line the team data gives, but it's an unusual direct manager for a Sr. Full Stack Engineer role. Worth confirming whether Manasi is the actual manager or the project sponsor.