 |
IT Mentor Program
Purpose:
Due to the Rutgers' unique computing environment, even the most experienced IT professional faces a considerable learning
curve when coming to Rutgers. Although there are on-line resources available to them, it is still very helpful to have a person to turn to when questions arise. The mentor will act as the "human face" of the
UCS Toolkit website.
The mentor is there to smooth the transition to the Rutgers environment.
Program Details:
- Maintain a pool of qualified volunteers from varying backgrounds.
- Within their first week on the job, new IT employees (hereafter referred to as a UCS, though mentoring will be
available for any new IT professional) will be assigned a mentor.
- Preferably, the mentor will come from a department similar to the new UCS' department, e.g., if the new UCS'
department is an academic or research department, the mentor should come from one also. Similarly, if the new UCS'
department is a multi-site, multiple service, large user base department, the mentor should have experience in the
same type of environment.
- The official mentoring period will last no longer than three months.
- Following the mentoring period, feedback will be requested from both parties.
Exceptions:
- When there is already a higher level, or very experienced (at Rutgers) IT worker in the new employee's department,
mentoring will be waived. For example, an individual hired as a UCS in a department that already has a UCM will not
need a mentor assigned. It is expected the UCM will handle the necessary training and mentoring.
MSSG:
- Will periodically solicit mentor volunteers via the various IT related mailing lists.
- Selects mentors from pool of volunteers.
- Works with UHR to identify start dates and coordinates mentor assignments.
Mentors:
- Have a minimum of two years experience working in IT at Rutgers.
- Pool of mentors should include some from research/academic departments and administrative units.
- Mentors should have a varied range of technical experience, some combination of:
- Running web and/or mail servers
- Unix/Linux system administration
- Windows system administration
- Active Directory administration
- Mac administration
- Demonstrated knowledge of RUNet and TD services
- Managing lab environments
- Working under special security requirements (HIPAA, GLBA, etc.)
- Accesses data/services managed by ESS/ACS
- The mentor should also have a comparable level of responsibility, e.g., a UCS would not be an appropriate mentor for a UCM.
- Mentors should come from departments that operate in accordance with University and OIT guidelines.
What is expected of the mentor:
- Give the new UCS someone to call to keep from getting overwhelmed.
- Meetings should be kept short, meet with the new UCS once a week, perhaps over lunch. The initial meeting may be
slightly longer.
- Mentor shouldn't be negative or express biases concerning departments, services, software, etc.
- Expose the new UCS to appropriate mailing lists and training opportunities.
What is not expected of the mentor:
- The mentor is not expected to provide technical training. It is expected the new UCS has sufficient technical
knowledge for their position.
- Mentor should not get involved in providing any direct support to the new UCS' department, though they should
certainly offer advice on matters, if asked.
- Mentors should ideally only have one mentoring assignment per year.
|