Home/Learn/Data Center Technician / Remote Hands / Hardware Engineer/30-day plan
30-day lab plan · 🏢 Data Center Technician / Remote Hands / Hardware Engineer

Become job-ready as adata center technician / remote hands / hardware engineer in 30 days.

One focused task a day, four weeks, ending with a portfolio and a mock interview. Built for students and engineers in India who learn by doing — about 2 hours a day on weekdays, a little more on weekends.

What you needInterview questions →Role path →
Your kit

Set up before day 1

Access to any server room or a home rack, an old server, cable tools, a label printer, and our physical data center explainer. Everything here is free or has a free tier; a laptop with 16 GB RAM is enough for most labs (32 GB for nested clusters).

  • Daily ruleFinish the task, write 5 lines of notes, commit to Git. Notes become your interview stories.
  • Weekend ruleDay 7 of each week is a review: redo the hardest task from memory.
  • Stuck rule30 minutes max, then ask in a community or our engineer network.
Week 1

Orientation

  1. Day 1Read our physical data center explainer; sketch the power chain grid→DG→UPS→PDU
  2. Day 2Rack maths: U, weight, kW; plan a 42U rack layout on paper
  3. Day 3Cable types and standards; make and test a Cat6 patch cable
  4. Day 4Labelling scheme; label everything in your lab
  5. Day 5ESD and safety; write your floor rules card
  6. Day 6Learn iLO/iDRAC/IPMI on an old server; remote console
  7. Day 7Review: one-page rack elevation drawing
Week 2

Hands-on hardware

  1. Day 8Disassemble/reassemble a server: RAM, CPU, risers, drives
  2. Day 9Install an OS via remote media; firmware update
  3. Day 10RAID controller: create array, fail/replace a disk
  4. Day 11Network: patch to a switch, configure port, verify with LLDP
  5. Day 12Power: A/B feeds, measure draw with a meter; calculate rack load
  6. Day 13Cooling: measure inlet/outlet temps; fix airflow with blanking
  7. Day 14Review: hardware checklist for rack-and-stack
Week 3

Operations

  1. Day 15Ticketing: write 5 remote-hands tickets with evidence standards
  2. Day 16NetBox: model your rack, devices, cables, IPs
  3. Day 17Fibre: inspect/clean, light-meter test (borrow tools if needed)
  4. Day 18Shutdown/startup procedure for a rack; sequence and verification
  5. Day 19Incident drills: hot rack, failed PDU, disk failure
  6. Day 20Vendor coordination: how to open HPE/Dell cases with logs
  7. Day 21Review: SOP document for a technician shift
Week 4

Growth & portfolio

  1. Day 22Monitoring: Zabbix for iLO/iDRAC and environmental sensors
  2. Day 23Capacity audit of your lab/room with recommendations
  3. Day 24Relocation plan for 5 racks on paper
  4. Day 25Certifications plan: CDCP/Schneider DC fundamentals, CompTIA Server+
  5. Day 26Learn virtualization basics (our Proxmox path) — the next step up
  6. Day 27Mock interview with our question bank
  7. Day 28Portfolio: photos (where allowed), diagrams, SOPs; update resume
After day 30

What you will have

  • A portfolio repoDiagrams, configs, scripts and runbooks a hiring manager can read in five minutes.
  • Interview storiesReal faults you fixed — the answers to “tell me about a time…”.
  • A certification targetSee the role path for which exam to book next.
  • A place in our networkFinish the plan, share the repo, and apply — we mentor and place engineers who complete it.

Finished the plan? Show us.

Share your repo and notes; completed plans get a technical conversation with our architects and first paid tasks through the engineer network.

Apply to the networkPractice interview questions