Monitoring Risk & Continuity Lead
MONITORING, RISK & CONTINUITY LEAD INTERN — WORKING LEADERSHIP ROLE
ABOUT MORSBY, GORMAN, MCCARTHY LLC
Morsby, Gorman, McCarthy LLC is developing Project Guardian as a multidisciplinary, project-based initiative focused on infrastructure planning, implementation readiness, policy research, partnership development, evidence management, risk analysis, and program coordination.
Project Guardian’s initial work centers on a proposed Kenya-focused infrastructure pilot. Participants will contribute to research, planning, analysis, documentation, and professional-quality project materials intended to help clarify the pilot’s feasibility, evidentiary foundation, funding requirements, implementation conditions, principal risks, and potential pathways toward responsible replication or expansion.
Participation does not represent employment by, appointment to, or endorsement from any government, university, funder, development institution, community, or prospective partner. Project Guardian is an independent initiative of Morsby, Gorman, McCarthy LLC unless a separate written agreement states otherwise.
PROGRAM TERMS
• Program dates: October 19, 2026–January 29, 2027
• Holiday pause: December 19, 2026–January 3, 2027, during which no routine work is expected
• Fully remote and asynchronous-first
• Normally 5–10 hours per week
• Work exceeding 10 hours in a week requires advance written approval
• Participants should not ordinarily exceed approximately 15 hours in any week
• Unpaid educational internship
• Academic credit may be available only when approved by the participant’s institution
• No promise or expectation of future employment
• Reasonable academic and accessibility accommodations will be considered
• Participation is subject to applicable confidentiality, data-handling, authorship, attribution, acceptable-use, and release requirements
EDUCATIONAL STRUCTURE
This is a structured, project-based learning experience. Participants receive defined learning objectives, supervised assignments, written or documented feedback, revision opportunities, and exposure to multidisciplinary infrastructure, public policy, research, monitoring, operational-risk, continuity-planning, and program-management work.
Assignments are designed to develop transferable professional competencies through applied work of educational value. Participants may produce portfolio-appropriate materials, excerpts, or descriptions subject to confidentiality, intellectual-property, attribution, data-protection, and release requirements. Inclusion of any project material, risk register, scenario, dashboard, process, screenshot, or deliverable in a portfolio requires prior written authorization.
Academic credit may be available only when approved by the participant’s institution. Participants are responsible for initiating and satisfying their institution’s credit-approval process. Morsby, Gorman, McCarthy LLC will reasonably cooperate with legitimate institutional documentation, learning-agreement, supervision, evaluation, and verification requirements when provided with sufficient notice.
Academic credit is not guaranteed and is not required for participation. The availability, amount, classification, and conditions of credit are determined solely by the participant’s institution.
The internship is intended to complement academic study and professional development. Participants will not displace regular employees or independently perform functions requiring licensed legal, engineering, medical, financial, cybersecurity, safety, emergency-management, or other regulated professional judgment.
ROLE PURPOSE
The Monitoring, Risk and Continuity Lead helps develop and maintain the systems used to monitor Project Guardian’s progress, identify emerging risks, support proportionate escalation, and preserve continuity when deadlines, staffing, evidence, approvals, information access, or external circumstances change.
The role will consider two related but distinct areas:
• Internal program-delivery risks affecting Project Guardian’s research, coordination, participation, documentation, review, and completion
• Preliminary risks and continuity considerations relevant to the proposed Kenya-focused infrastructure pilot
The Lead will help leadership distinguish routine variations from material threats, active risks from realized issues, and verified conditions from assumptions or unresolved uncertainty.
The role will emphasize practical early-warning indicators, documented ownership, proportionate responses, contingency planning, continuity arrangements, and decision support. Its purpose is not to eliminate all uncertainty or treat every concern as an emergency.
This is a working leadership internship. The selected participant will coordinate assigned contributors while personally performing substantive risk research, monitoring analysis, scenario development, register maintenance, status assessment, procedural drafting, and continuity-planning work.
The leadership component is educational and project-based. It does not confer authority to employ, discipline, investigate, contract with, or make commitments on behalf of other participants, the company, the project, or any prospective stakeholder.
LEARNING OBJECTIVES
By the conclusion of the internship, the participant should be able to:
• Explain the differences among risks, issues, assumptions, dependencies, controls, decisions, incidents, and opportunities
• Develop a proportionate monitoring and risk framework for a multidisciplinary project
• Translate project objectives and milestones into practical monitoring indicators
• Distinguish activity, output, outcome, quality, capacity, schedule, and readiness indicators
• Define proportionate thresholds for routine management, heightened attention, escalation, and leadership decisions
• Assess risk using clearly documented likelihood, impact, urgency, proximity, uncertainty, and control considerations
• Develop risk, issue, assumption, dependency, mitigation, corrective-action, and decision registers
• Identify single points of failure involving staffing, knowledge, approvals, systems, records, and decision authority
• Design practical contingency, cross-coverage, succession, recovery, and continuity measures
• Conduct supervised scenario reviews and tabletop exercises
• Evaluate whether mitigation and corrective actions were completed and whether they were effective
• Prepare concise exception reports and decision-support materials
• Recognize when legal, engineering, financial, safety, medical, cybersecurity, safeguarding, regulatory, or emergency-management questions require qualified review
• Incorporate context-specific information without overstating incomplete or unverified conditions
• Coordinate contributors through documented assignments, feedback, revision, escalation, and handoff practices
• Reflect on ethical monitoring, confidentiality, proportionality, cultural humility, and responsible use of risk information
PRIMARY RESPONSIBILITIES
Monitoring Framework and Indicator Design
• Help develop and maintain an integrated monitoring, risk, issue, dependency, decision, and continuity framework
• Translate approved objectives, milestones, deliverables, and dependencies into practical monitoring categories
• Define supervised indicators for schedule, capacity, participation, quality, evidence readiness, deliverable readiness, unresolved decisions, and continuity exposure
• Distinguish indicators that measure activity from those that provide meaningful evidence of progress or readiness
• Document each material indicator’s definition, purpose, source, owner, review frequency, limitations, and escalation threshold
• Avoid presenting imprecise, incomplete, or inconsistently collected information as exact
• Identify unavailable, unreliable, duplicative, intrusive, or unnecessarily burdensome data requests
• Recommend proportionate monitoring methods that can be maintained within the program’s time and resource constraints
• Coordinate with relevant teams to reconcile inconsistent status information
• Clearly label estimates, incomplete data, provisional assessments, and unresolved discrepancies
Risk and Issue Management
• Develop and maintain supervised risk and issue registers
• Record risk descriptions, causes, potential consequences, likelihood, impact, urgency, proximity, uncertainty, ownership, controls, mitigation measures, contingency actions, status, and review dates
• Distinguish potential future events from realized issues requiring active response
• Identify dependencies and assumptions that could materially affect delivery or pilot feasibility
• Avoid combining unrelated risks in ways that obscure ownership or response actions
• Identify correlated, cascading, cross-workstream, and cumulative risks
• Document risk movement, decisions, accepted exposure, corrective actions, and unresolved matters
• Close or downgrade risks only when supported by documented evidence and appropriate review
• Escalate material concerns rather than concealing, minimizing, or informally resolving them without authority
Early-Warning and Escalation Design
• Develop proportionate thresholds for routine management, heightened monitoring, formal escalation, and leadership decision-making
• Identify early-warning signals involving missed milestones, unavailable evidence, declining capacity, unresolved approvals, information-access problems, repeated quality failures, participant withdrawal, or external dependency changes
• Prepare concise exception reports focused on material deviations, required decisions, and recommended next steps
• Distinguish informational updates from matters requiring action or authority
• Identify the appropriate escalation recipient based on the issue’s subject, sensitivity, urgency, and required decision
• Avoid exaggerating routine uncertainty or using emergency terminology where it is not warranted
• Escalate immediate concerns involving safety, safeguarding, suspected misconduct, confidentiality, improper access, material misrepresentation, or other significant harm through designated channels
• Preserve relevant facts and records while avoiding unauthorized investigation or public disclosure
Milestone, Capacity, and Dependency Monitoring
• Monitor approved milestones, critical dependencies, delayed decisions, review bottlenecks, and deliverable-readiness indicators
• Help assess whether work is appropriately scoped for available time and participant capacity
• Identify assignments or functions dependent on a single person, source, system, approval, or access path
• Track absences, withdrawals, unassigned responsibilities, incomplete handoffs, and workload concentration at an operational level
• Coordinate with the Deputy Program and Operations Manager on capacity, cross-coverage, workload, and schedule risks
• Avoid collecting unnecessary personal, medical, academic, immigration, family, or other sensitive information
• Focus participant monitoring on authorized project requirements, agreed milestones, documented availability, and operational continuity
• Refer performance, conduct, accommodation, or welfare concerns to the appropriate supervisor rather than attempting independent disciplinary or clinical assessment
Continuity and Recovery Planning
• Identify critical functions, records, systems, approvals, roles, and dependencies that require continuity arrangements
• Develop supervised continuity plans for participant withdrawals, missed deadlines, unavailable leadership, inaccessible records, technology disruption, incomplete handoffs, or other plausible interruptions
• Establish practical cross-coverage, succession, handoff, recovery, and resumption procedures
• Coordinate with program operations on role transitions and temporary coverage arrangements
• Coordinate with the Knowledge and Data-Room Manager on records, access, backup, recovery, and information-continuity considerations
• Document minimum requirements for maintaining or safely pausing critical activities
• Identify recovery priorities, decision points, resource constraints, and unresolved dependencies
• Ensure that continuity recommendations remain proportionate to Project Guardian’s actual scope and resources
• Avoid representing internal continuity planning as certified emergency, disaster-recovery, cybersecurity, or business-continuity assurance
Scenario Analysis and Tabletop Exercises
• Develop realistic, proportionate scenarios for priority risks and continuity concerns
• Facilitate or support supervised tabletop discussions involving relevant participants
• Define each exercise’s purpose, assumptions, scope, participants, decisions, and limitations
• Record observations, gaps, dependencies, proposed actions, owners, and follow-up dates
• Distinguish hypothetical exercise findings from verified operational conditions
• Avoid using exercises to generate fear, assign blame, or simulate sensitive emergencies without appropriate approval
• Track whether agreed improvements are completed and tested where appropriate
• Incorporate lessons into updated procedures, registers, and continuity plans
Mitigation and Corrective-Action Tracking
• Maintain a tracker for approved mitigations, corrective actions, contingency preparations, and follow-up commitments
• Record action ownership, due dates, dependencies, evidence of completion, and review status
• Assess whether completed actions address the underlying risk or only the immediate symptom
• Identify overdue, ineffective, abandoned, or contradictory actions
• Recommend additional review when residual risk remains material
• Avoid certifying effectiveness beyond the available evidence or the participant’s qualifications
• Preserve a clear record of open questions and decisions still required
Pilot-Related Risk Research
• Support preliminary research concerning operational, institutional, stakeholder, infrastructure, implementation, funding, procurement, governance, environmental, social, and continuity considerations relevant to the proposed Kenya pilot
• Use reliable sources and preserve citation and retrieval information
• Distinguish country-level, sector-level, regional, local, site-specific, and project-specific information
• Avoid applying generalized national or regional claims to a specific community or site without adequate evidence
• Clearly identify gaps requiring local consultation, field validation, engineering review, legal analysis, financial review, safeguarding assessment, or other specialist input
• Treat local institutions, communities, stakeholders, and decision-making authority accurately and respectfully
• Avoid implying local endorsement, consent, participation, or agreement that has not been confirmed
• Present preliminary risk analysis as planning and research support rather than a substitute for locally grounded due diligence
Cross-Functional Coordination
• Coordinate with the Evidence and Quality Assurance Lead on evidence, methodology, verification, and quality risks
• Coordinate with the Knowledge and Data-Room Manager on records, access, backup, recovery, and information-continuity risks
• Coordinate with the Funding and PPP Integration Lead on eligibility, funding, partner, submission, and resource-dependency risks
• Coordinate with the Chief Research and Editorial Director on unsupported, overstated, inconsistent, or outdated claims
• Coordinate with the Communications and Design Integration Lead on accurate presentation of risk, uncertainty, status, and limitations
• Coordinate with analyst and specialty teams to identify risks affecting their workstreams
• Reconcile overlapping registers and avoid unnecessary duplication
• Escalate cross-workstream risks that cannot be resolved at the contributor level
Working Leadership and Team Coordination
• Translate approved monitoring, risk, and continuity priorities into appropriately scoped contributor assignments
• Provide clear objectives, source expectations, deadlines, templates, and review criteria
• Offer constructive first-level feedback subject to supervisory oversight
• Track dependencies, unresolved questions, mitigation actions, and completion status
• Encourage early communication of problems without creating a punitive reporting culture
• Promote accurate sourcing, proportionate analysis, confidentiality, and timely escalation
• Cross-train contributors and preserve usable handoff documentation
• Produce substantive individual research, analysis, and written work in addition to coordinating others
• Refer performance, conduct, accommodation, safeguarding, or participation concerns to the designated supervisor rather than acting independently
SUPERVISION, FEEDBACK, AND REVISION
The Monitoring, Risk and Continuity Lead will receive direction and supervision from the Program Director, with operational coordination through the Deputy Program and Operations Manager.
The educational workflow is expected to include:
• Initial orientation to Project Guardian’s scope, objectives, standards, information classes, and escalation pathways
• Defined assignments connected to the role’s learning objectives
• Access to approved templates, examples, registers, and source requirements
• Scheduled or milestone-based supervisory review
• Written, annotated, or otherwise documented feedback
• Opportunities to ask questions and clarify expectations
• Reasonable opportunities to revise substantive work
• Periodic reflection on professional development and learning progress
• A final review or evaluation where appropriate
Feedback may address analytical reasoning, proportionality, indicator design, source use, register quality, scenario design, mitigation logic, continuity planning, cultural awareness, ethical judgment, communication, escalation, documentation, collaboration, and the participant’s ability to incorporate revisions.
EXPECTED EDUCATIONAL OUTPUTS
Depending on project needs, participant readiness, source availability, and supervisory direction, outputs may include:
• Integrated monitoring, risk, issue, assumption, dependency, decision, and continuity framework
• Monitoring plan and indicator dictionary
• Risk, issue, assumption, dependency, mitigation, corrective-action, and decision registers
• Milestone, capacity, participation, quality, and deliverable-readiness indicators
• Early-warning thresholds and escalation matrix
• Single-point-of-failure assessment
• Critical-function and dependency map
• Cross-coverage, handoff, succession, and temporary-coverage plan
• Continuity, contingency, recovery, and resumption procedures
• Scenario analyses and tabletop-exercise materials
• Exercise observation and follow-up records
• Weekly or milestone-based exception reports
• Mitigation and corrective-action tracker
• Preliminary Kenya-pilot risk research
• Risk assumptions, evidence gaps, and specialist-review requirements
• End-of-program continuity and lessons-learned assessment
• Final handoff and unresolved-matters record
• Substantive original research, analysis, and writing
Outputs are educational and developmental materials. Their production does not guarantee that they will be adopted, externally distributed, certified, implemented, or used to make a final project decision.
PERFORMANCE AND LEARNING ASSESSMENT
Progress may be assessed according to:
• Accuracy and completeness of monitoring and risk records
• Quality, proportionality, and usability of indicators and thresholds
• Ability to distinguish risks, issues, assumptions, dependencies, controls, actions, and decisions
• Quality and reliability of sources
• Transparency concerning uncertainty, limitations, and data gaps
• Practicality of mitigation, contingency, and recovery recommendations
• Ability to identify single points of failure and critical dependencies
• Quality of scenario analysis and follow-up documentation
• Appropriate escalation of material concerns
• Respect for confidentiality, privacy, local knowledge, and stakeholder authority
• Ability to avoid unnecessary alarm, false precision, unsupported certainty, or inappropriate minimization
• Ability to receive, evaluate, and incorporate feedback
• Reliability in meeting agreed milestones or communicating constraints early
• Effectiveness in coordinating contributors without exceeding the role’s authority
• Growth against the stated learning objectives
Assessment is intended to support learning and program administration. It is not a licensed professional examination or certification in risk management, monitoring and evaluation, emergency management, safety, cybersecurity, auditing, or business continuity.
PREFERRED QUALIFICATIONS
Strong candidates may be advanced undergraduate students, graduate students, postdoctoral researchers, recent graduates, alumni, or early-career professionals. Exceptional earlier-stage students who can demonstrate substantial readiness may also be considered.
Relevant academic areas may include risk management, emergency management, business continuity, monitoring and evaluation, public policy, public administration, international development, project management, operations, auditing, economics, statistics, data analysis, infrastructure planning, engineering management, or related interdisciplinary fields.
Candidates should demonstrate:
• Strong analytical, organizational, research, and written-communication skills
• Ability to identify risks without overstating uncertainty or treating every concern as equally urgent
• Ability to distinguish risks, issues, assumptions, dependencies, controls, mitigations, actions, and decisions
• Interest or experience in project monitoring, risk registers, continuity planning, operations, auditing, evaluation, policy analysis, or related work
• Ability to develop practical indicators, thresholds, mitigation measures, contingency plans, and decision-support materials
• Sound judgment regarding escalation, confidentiality, proportionality, ethics, and reputational sensitivity
• Ability to follow corrective actions through completion and assess whether they addressed the underlying concern
• Respect for local knowledge, cultural context, and legitimate decision-making authority
• Reliability when coordinating distributed contributors across disciplines and time zones
• Willingness to document work, receive feedback, and revise substantive assignments
• Familiarity with shared documents, spreadsheets, dashboards, registers, trackers, or collaborative project tools
Experience relating to Kenya, Africa, international development, infrastructure, safeguarding, public-sector programs, organizational resilience, or distributed-team operations may be helpful but is not required.
Applicants are not expected to possess professional legal, engineering, financial, medical, cybersecurity, safety, emergency-management, or risk-certification credentials.
APPLICATION MATERIALS
Applicants should submit through Handshake:
• A current résumé
• A cover letter explaining their interest in Project Guardian and describing relevant risk, monitoring, continuity, evaluation, operations, research, or transferable experience
• One relevant work sample, such as a risk assessment, monitoring framework, evaluation plan, policy analysis, scenario analysis, continuity plan, audit-related exercise, decision memo, dashboard, research paper, or comparable academic, professional, volunteer, or independent work
Applicants should remove or redact confidential, proprietary, personally identifiable, restricted, privileged, or third-party information from submitted samples.
If the applicant’s strongest work was completed collaboratively, the applicant should briefly identify their individual contribution.
A prior professional work sample is not required. Applicants may submit an academic, volunteer, independent, simulated, or appropriately redacted example that demonstrates relevant analytical judgment.
SELECTION PROCESS
Initial screening will be asynchronous. Applications will be assessed based on demonstrated alignment, analytical readiness, communication quality, proportionality, judgment, transferable skills, and the relevance of submitted materials.
Finalists may be invited to complete a brief, time-limited educational evaluation exercise involving a hypothetical or publicly available scenario. The exercise may ask the applicant to distinguish risks from issues and assumptions, identify early-warning indicators, prioritize a small risk register, recommend continuity measures, or prepare a concise exception report.
Any selection exercise will be designed solely to evaluate the applicant’s reasoning and communication. It will not involve actual confidential project information, be used as uncompensated production work, or be incorporated into Project Guardian deliverables without separate written permission and appropriate arrangements.
Live conversations will be limited to finalists or circumstances requiring clarification. References may be requested selectively. Reasonable accommodations are available during the selection process.
Priority application deadline: October 2, 2026. The posting may close earlier or later based on application volume, institutional review timing, or program needs.
ELIGIBILITY AND INSTITUTIONAL CONDITIONS
Applicants must be able to participate remotely during the stated program period and communicate reliably in an asynchronous-first environment.
Students seeking academic credit must contact their institution and initiate any required approval, registration, learning-agreement, or internship-verification process. Institutional approval and academic credit are not guaranteed.
Where required, participation may be conditioned on completion of appropriate institutional documentation, confidentiality agreements, information-handling acknowledgments, intellectual-property terms, conflict disclosures, acceptable-use requirements, or other reasonable program documentation.
International students and other applicants are responsible for confirming with their institution or qualified adviser whether participation is consistent with applicable academic, immigration, authorization, funding, or institutional requirements. Morsby, Gorman, McCarthy LLC does not provide immigration, visa, tax, legal, or employment-authorization advice.
CONFIDENTIALITY, ATTRIBUTION, AND RESPONSIBLE TOOL USE
Participants may encounter confidential, preliminary, proprietary, sensitive, or access-controlled information. Such information may be used only for authorized program purposes and handled according to applicable instructions.
Participants must:
• Protect confidential, personal, proprietary, and restricted information
• Use only authorized systems, accounts, storage locations, and transfer methods
• Access only materials reasonably necessary for assigned work
• Avoid uploading confidential, personal, proprietary, or restricted materials to unapproved third-party platforms
• Preserve citations, source records, calculation notes, review history, and version information
• Distinguish original work from quoted, adapted, collaborative, or tool-assisted material
• Disclose material use of generative artificial intelligence or other automated tools when requested
• Independently verify factual claims, quotations, calculations, classifications, and source interpretations
• Avoid fabricating risks, incidents, data, sources, approvals, stakeholder views, actions, or findings
• Obtain approval before externally sharing project materials or including them in a portfolio
• Report suspected confidentiality, access, integrity, or information-handling incidents promptly
Automated tools may support learning, brainstorming, organization, analysis, or drafting only when permitted. They may not replace the participant’s judgment, source verification, confidentiality obligations, or responsibility for submitted work.
Risk scoring, summaries, forecasts, classifications, and automated alerts must receive appropriate human review. Restricted information may not be entered into public or unauthorized artificial-intelligence systems.
ETHICAL MONITORING AND PARTICIPANT INFORMATION
Monitoring should be limited to information reasonably necessary for authorized educational and program-management purposes.
The Lead must not independently:
• Conduct covert or invasive surveillance
• Request passwords or access private personal accounts
• Collect unnecessary medical, disability, immigration, family, financial, academic, or other sensitive personal information
• Diagnose a participant’s physical or mental health
• Investigate alleged misconduct without authorization
• Publish individual performance comparisons
• Retaliate against or penalize a participant for raising a good-faith concern
• Represent preliminary observations as formal findings
Concerns involving individual performance, conduct, accommodation, safeguarding, welfare, or sensitive personal circumstances must be referred through designated supervisory channels and handled with appropriate discretion.
PROFESSIONAL AND REGULATORY LIMITATIONS
This internship does not authorize the participant to provide or represent that they are providing legal, engineering, financial, medical, cybersecurity, safety, regulatory, emergency-management, auditing, or other licensed professional advice or certification.
Monitoring tools, risk registers, scenarios, continuity plans, and mitigation recommendations are educational planning and decision-support materials. They are not certified safety plans, engineering risk assessments, cybersecurity audits, emergency-response directives, legal opinions, insurance evaluations, or guarantees of continuity, compliance, feasibility, or performance.
Questions requiring specialized professional judgment must be identified and routed for qualified review.
REPORTING, ESCALATION, AND AUTHORITY
The Monitoring, Risk and Continuity Lead reports primarily to the Program Director and coordinates operational matters through the Deputy Program and Operations Manager.
The Lead collaborates closely with the Evidence and Quality Assurance Lead, Knowledge and Data-Room Manager, Funding and PPP Integration Lead, Chief Research and Editorial Director, Communications and Design Integration Lead, and relevant analyst and specialty teams.
The Lead may:
• Maintain approved monitoring, risk, issue, dependency, action, and continuity records
• Request authorized project-status information
• Coordinate approved internal assignments
• Recommend mitigation, corrective-action, contingency, and continuity measures
• Prepare internal exception and decision-support reports
• Facilitate approved scenario reviews and tabletop exercises
• Escalate material concerns through designated channels
• Provide supervised feedback to assigned contributors
The Lead may not independently:
• Accept risk on behalf of the company, project, or another participant
• Declare an emergency or activate external emergency procedures
• Direct government, emergency, institutional, community, contractor, partner, or other external parties
• Conduct unauthorized investigations
• Access private accounts or collect unnecessary sensitive personal information
• Make legal, financial, employment, procurement, safety, technical, or contractual commitments
• Authorize hiring, removal, discipline, or other personnel actions
• Contact external stakeholders without approval
• Represent the company, project, or any institution externally
• Issue public statements
• Release project materials
• Override approved confidentiality, access, retention, or disclosure requirements
• Promise funding, implementation, safety, continuity, academic credit, employment, or any project outcome
Final decisions concerning risk acceptance, major project changes, external disclosure, emergency action, resource commitments, personnel matters, and project continuation remain with authorized program leadership and, where necessary, qualified professionals.
All external outreach, representations, commitments, releases, and material response decisions require appropriate authorization.
EQUAL CONSIDERATION AND ACCOMMODATIONS
Morsby, Gorman, McCarthy LLC intends to consider applicants based on role-related qualifications, demonstrated readiness, learning potential, and program needs. Reasonable accommodations may be requested for the application process or internship experience.
Applicants are encouraged to describe relevant academic, professional, volunteer, military, emergency-response, community, entrepreneurial, caregiving, independent, or lived experience when it demonstrates transferable skills applicable to the role.