Job Shadowing

Shadowing Experience Overview

  • As students are preparing to enter the "real-world" and the next chapter of their lives, we want them to learn about the careers they are interested in.

  • The skills of computer programming are applicable in many fields. The shadowing experience does not need to be in computer programming or information technology. If there is a genuine connection between the career goals of the student and the experience, it will be valuable.

  • Each student will find a professional mentor that they can shadow. It is the responsibility of the student to find their mentor, communicate with the mentor, and set up meetings.

  • Since this is a shadowing experience, the student will be mostly observing, asking questions, and making connections with professionals. Students will probably not complete work tasks as in an internship, during the shadowing time.

    • Experiences in the software development field still count as Work-Based Learning hours as they are aligned with Career Technical Content Standards for Information Technology.

    • The shadowing mentor may also serve as a simulated workplace mentor by completing code reviews with the students. The time students spend working on projects during the simulated workplace experience (see Simulated Workplace Experience below) in the classroom will involve work tasks as in an internship.

  • As part of the experience, mentors may arrange for the student to shadow other employees/positions at the company.

  • Students will choose one of the "plans" below as the timeline for their experience. I expect that most students will choose Plan A which is a 3-hour experience, but students can arrange longer experiences if their mentor allows.

Guidelines & Procedures

  • It is recommended that mentors not be parents or close family members. This way, the student will have a chance to see new opportunities and expand their professional network. However, it is permitted if this choice always a student to shadow in their desired career field.

  • Students will submit documentation in class to approve their experience and plan choice. Students will first complete a general proposal digitally, and will then be given the official approval paperwork to complete. No hours can begin until all documentation has been completed, physically signed by all stakeholders, and submitted to the classroom teacher.

  • With prior approval, students can drive themselves, be driven by other students, or driven by parents. Please talk to the classroom teacher if the student needs district assistance with transportation.

  • The stakeholders that need to sign experience agreements are:

    • Student

    • Parent/Guardian (even if student is 18)

    • Mentor

    • Classroom teacher

    • (Physical signatures are required, but can be transmitted by printing, scanning, and emailing documents.)

  • Students will submit a time log that is verified by the mentor along with reflections about the experience. The classroom teacher will be in close contact with all mentors to discuss how the experience is going and to verify hours completed.

Students can make arrangements that are slightly different than the following. These are listed as suggestions.

Plan A (3 hours)

Shadowing

  • Student shadows their mentor for a total of 3 hours.

  • Student is excused from class during 8th & 9th period (12:53 - 2:25 PM) for two days:

    • Tuesday, April 19th

    • Thursday, April 28th

  • Shadowing does not necessarily have to be completed during these times. As long as the student logs a total of 3 hours, they have made up the time excused from class.

  • Student is in class all other days to work on programming projects as part of the simulated workplace experience.

Plan B (6 hours)

Shadowing

  • Student shadows their mentor for a total of 6 hours.

  • Student is excused from class during 8th & 9th period (12:53 - 2:25 PM) for four days:

    • Tuesday, April 19th

    • Thursday, April 21st

    • Tuesday, April 26th

    • Thursday, April 28th

  • Shadowing does not necessarily have to be completed during these times. As long as the student logs a total of 6 hours, they have made up the time excused from class.

  • Student is in class all other days to work on programming projects as part of the simulated workplace experience.

Plan C (15 hours)

Shadowing

  • Student shadows their mentor for a total of 15 hours.

  • Student is excused from class during 8th & 9th period (12:53 - 2:25 PM) for ten days:

    • Monday, April 18th through Friday, April 29th

  • Shadowing does not necessarily have to be completed during these times. As long as the student logs a total of 15 hours, they have made up the time excused from class.

  • Student resumes attending computer programming on May 4th.

Simulated Workplace Experience

Overview

  • All students are also working on authentic software development projects that are closely aligned with Career Technical Content Standards for Information Technology. The time students work on these projects counts as Work-Based Learning hours similar to an internship experience. These projects allow students to have a simulated experience of what it is like to work as a software developer. They are developing products for a real company or organization in the Sylvania area.

  • Students work on these projects in the classroom with supervision and guidance from the classroom teacher and industry mentors. Industry mentors review student work and provide support via virtual code review sessions. The mentors will also evaluate their work as they work and on at "delivery" of the product.

  • Students will also receive feedback from their "clients" who are the real people for whom the projects are designed.

  • Students will present these and other projects as part of their Senior Portfolio during the Senior Showcase in mid-May (date TBD). Industry mentors (not necessarily the shadowing mentors) will attend the event and evaluate projects according to industry standards.