Work-Integrated Learning for Interdisciplinarians: IT & Security Focus

Open Closing on December 1, 2025 / 3 spots left
Main contact
The University of Virginia
Charlottesville, Virginia, United States
Jennifer Wallace
She / Her / They / Them
Administrator
Timeline
  • January 13, 2026
    Experience start
  • January 28, 2026
    Milestone 1: Project Orientation & Assignment (Weeks 1–2)
  • February 11, 2026
    Milestone 2: Project Scoping & Planning (Weeks 3–4)
  • April 8, 2026
    Milestone 3: Project Development & Interim Deliverables (Weeks 5–12)
  • April 22, 2026
    Milestone 4: Final Delivery & Partner Feedback (Weeks 13–14)
  • April 29, 2026
    Milestone 5: Reflection & Evaluation (Week 15)
  • April 29, 2026
    Experience end
Experience
3 projects wanted
Dates set by experience
Agreements required
Preferred companies
Anywhere
Any company type
Any industries

Experience scope

Categories
Security (cybersecurity and IT security) Information technology Cloud technologies
Skills
gap analysis key performance indicators (kpis) threat modeling data dictionary executive presentations incident response
Learner goals and capabilities

Engage interdisciplinary technology teams to improve reliability, security, and business value, without heavy lift.

The UVA School of Continuing & Professional Studies (SCPS), in partnership with Riipen, is launching an interdisciplinary, project-based learning program connecting industry partners with motivated students in Cloud Solutions & Operations, Cybersecurity Analysis, and Information Technology. Teams turn real problems into clear analysis, practical recommendations, and ready-to-use assets, delivering immediate value while building your future talent pipeline.


About the Learners 

Learners come from Cloud Solutions & Operations, Cybersecurity Analysis, and Information Technology and are developing as business-aware technologists and ethical problem-solvers who connect architecture, security, and IT service management to measurable business outcomes. Skills will include:

  • Systems & cloud thinking: Understand how apps, networks, storage, and data fit together; weigh trade-offs in cost, reliability, performance, and scalability.
  • Cyber risk & resilience: Identify common threats and control gaps; recommend practical protections (identity and access, encryption, segmentation, logging) and recovery approaches.
  • Integration & automation: Map data flows and interfaces, assess vendor/SaaS fit, and automate routine tasks with templates/runbooks to improve speed and consistency.
  • Data & monitoring literacy: Define simple, useful KPIs; plan basic instrumentation; draft dashboard wireframes to track availability, latency, errors, cost, and risk.
  • Change enablement & communication: Produce executive-ready briefs, diagrams, and rollout plans that translate technical options into clear business impact and next steps.
  • Ethics, privacy & compliance: Work with de-identified/sandbox data; consider privacy and legal context when proposing designs and processes.
  • Professional habits: Scope clearly, manage milestones, document assumptions, respond to feedback, and deliver polished, adoption-ready artifacts.


Project Details: 

  • Entry-level scope, designed to match beginner project complexity. 
  • Runs January to April 2026
  • Approximately 300 total hours per team over a 12 week period. 
  • Teams of 3 students will be pre-assembled by the program to ensure balanced skills and collaboration. 
  • Structured to build practical skills, strengthen workplace readiness, and deliver tangible value to employers. 


Employer Role

As a partner and mentor, you’ll help shape a focused problem, share context the team can’t Google, and guide students toward professional, audience-ready work. Expect to join a brief kickoff, provide concise feedback at one or two check-ins, and attend the final readout, offering practical input on what’s working, what to refine, and how recommendations map to real constraints. Your domain expertise, examples, and quick clarifications keep the project on track; your coaching builds students’ professional judgment. The total time commitment is light, but your timely guidance is the difference between a good student project and deliverables your organization can use.


What Employers Provide 

  • A focused project brief (problem, goals, audience, constraints)
  • Relevant materials/data (brand voice guides, prior reports, sample content)
  • A single point of contact for timely feedback during check-ins
  • Access (as needed) to users/stakeholders for interviews or guidance

Learners

Learners
Undergraduate
Beginner, Intermediate levels
10 learners
Project
80-120 hours per learner
Educators assign learners to projects
Individual projects
Up to 3 team(s) or 3 learner(s) per project.
Each learner can join up to one team
Expected outcomes and deliverables

Expected Outcomes 

Think of this as a focused tech consulting sprint. With light guidance, students deliver a grounded view of your cloud/IT environment, clear security and operations options with rationale, and adoption-ready assets, helping you reduce risk, improve performance/cost, and move faster on what matters.


Potential Deliverables

  • Architecture & service blueprint: current→target diagrams, option trade-offs (cost/reliability/performance), assumptions, and decision log.
  • Security posture snapshot: threat model, control gap analysis, prioritized mitigations, risk register, and residual-risk notes.
  • KPI & monitoring framework: definitions and baselines, data dictionary (non-sensitive), dashboard wireframes, alert thresholds, and reporting cadence.
  • Runbooks & playbooks: incident response, backup/disaster recovery, change/rollback procedures, and escalation paths.
  • Sandbox proof-of-concept: deployable reference pattern (e.g., logging/alerting pipeline or API hardening), setup guide, and acceptance criteria.
  • Integration & vendor toolkit: SaaS evaluation scorecard, data/classification checklist, SSO/integration pattern, and onboarding/offboarding steps.
  • Implementation roadmap: phased plan with roles, milestones, dependencies, success measures, and risk/mitigation plan.
  • Executive presentation package: final deck and one-pager summarizing findings, recommendations, costs/timelines, and next steps.
Project timeline
  • January 13, 2026
    Experience start
  • January 28, 2026
    Milestone 1: Project Orientation & Assignment (Weeks 1–2)
  • February 11, 2026
    Milestone 2: Project Scoping & Planning (Weeks 3–4)
  • April 8, 2026
    Milestone 3: Project Development & Interim Deliverables (Weeks 5–12)
  • April 22, 2026
    Milestone 4: Final Delivery & Partner Feedback (Weeks 13–14)
  • April 29, 2026
    Milestone 5: Reflection & Evaluation (Week 15)
  • April 29, 2026
    Experience end

Project examples

1) Cloud Reliability, Cost & Security Optimization


Objective: Improve service reliability and cost while reducing risk in a cloud-hosted workload.

Scope & Workstreams: current-state mapping; SLO/KPI definition; cost and rightsizing analysis; basic threat model; logging/alerting in sandbox.

Deliverables: current→target architecture; option analysis (trade-offs, TCO); KPI & dashboard wireframes; prioritized mitigation list; implementation roadmap.


2) Zero-Trust Access Pilot for a Hybrid Workforce


Objective: Strengthen identity and access for remote/hybrid users without hurting usability.

Scope & Workstreams: user journeys and risk points; policy & control options (MFA, least privilege, network segmentation—tool-agnostic); change & comms plan.

Deliverables: access policy pack; rollout playbook; training micro-modules; success metrics (adoption, auth failures, help-desk load).


3) Incident Response & Business Continuity Kit


Objective: Build a reusable IR + DR framework that shortens detection and recovery times.

Scope & Workstreams: tabletop scenarios; role and escalation mapping; backup/restore procedures in sandbox; communication templates.

Deliverables: IR playbook; DR runbook and test plan; drill checklist and after-action template; leadership brief on residual risks.


4) Data Pipeline Hardening & Observability


Objective: Increase reliability and trust in a data pipeline feeding analytics or customer features.

Scope & Workstreams: data flow diagram; failure mode review; logging/metrics design; alert thresholds; data quality checks.

Deliverables: instrumented pipeline plan (sandbox); monitoring/KPI framework; incident runbook; implementation roadmap.


5) Customer-Facing App Security & Performance Review


Objective: Reduce common web/API risks and improve page/API responsiveness.

Scope & Workstreams: threat model referencing common categories (e.g., injection, auth, exposure); perf baseline; caching/DB query improvements (conceptual).

Deliverables: risk register with fixes; perf improvement plan; acceptance criteria; developer-ready brief and test plan.


6) SaaS Integration & Vendor Risk Framework


Objective: Standardize how new SaaS tools are evaluated and integrated.

Scope & Workstreams: requirements and data classification; security/privacy checklist; integration/SSO patterns; de-provisioning process.

Deliverables: vendor scorecard; integration cookbook; governance calendar; onboarding/offboarding checklist; KPI set.


7) Backup, Recovery & Ransomware Readiness


Objective: Validate that critical data and services can be restored quickly and safely.

Scope & Workstreams: asset prioritization; RPO/RTO targets; immutable backups in sandbox; recovery testing plan; user comms.

Deliverables: DR architecture options; test/runbook package; metrics dashboard wireframes; executive decision memo.


8) Telemetry to Insight: Security & Ops Dashboard


Objective: Turn logs/metrics into an actionable dashboard for leaders and operators.

Scope & Workstreams: KPI design (availability, latency, cost, risk); source mapping; wireframing; data quality plan.

Deliverables: dashboard prototype (tool-agnostic); data dictionary; alert rules; usage guide for stakeholders.

Additional company criteria

Companies must answer the following questions to submit a match request to this experience:

  • Q1 - Checkbox
    I confirm that I have read and understand the Agreements of this program.  *
  • Q2 - Checkbox
    I understand that students are not responsible for sourcing the data needed for their project and that the organization must provide access to relevant datasets.  *
  • Q3 - Checkbox
    I understand that I must provide ongoing mentorship and guidance to the student(s) working on my project(s), be responsive to questions, check in on progress, and provide any tools or resources needed to complete the project.  *
  • Q4 - Checkbox
    I understand that I must provide a point of contact who is available for questions that arise and ongoing feedback and who will reply to student queries within 24-48 hours.  *
  • Q5 - Checkbox
    I will evaluate the students' final project submissions within 5 business days, offering feedback on the platform that can be utilized by the students to strengthen their resumes, LinkedIn profiles, and overall professional development.  *
  • Q6 - Multiple choice
    My project requires an NDA to be signed by learners.  *
    • Yes
    • No
  • Q7 - Multiple choice
    Will learners need access to any internal systems, software, or programs to complete your project (e.g., company tools, platforms, secure environments)?  *
    • Yes
    • No
  • Q8 - Text long
    If yes, please specify which systems, tools, or programs learners will be granted access to.