Custom recruitment web experiences
Recruitment-Focused Landing Pages
I owned routing, components, frontend implementation, and deployment for audience-specific recruitment sites, often built in Next.js.
- Campaign goal
- Route + components
- Responsive experience
- Deployment
Problem
What needed to change
Admissions and enrollment teams needed campaign-specific sites for prospective and admitted students instead of one generic landing-page template.
Users
Who the system serves
Prospective students, admitted students, families, admissions stakeholders, and campaign teams.
Team context
Where I fit
Technical lead (frontend product engineering) · University of Arizona
Worked with admissions and enrollment stakeholders around short-lived, high-priority campaigns; owned routing, components, frontend implementation, and deployment.
Important technical decision
The implementation choice
I used focused Next.js builds and reusable components for campaign-specific messaging and routes.
Tradeoff or limitation
Where the boundary sits
The campaign sites had short deadlines and still needed responsive behavior, performance, and support for late content changes.
Implementation
What I personally owned
- Owned routing, landing pages, tech stack choices, components, and deployment for custom campaign experiences.
- Built the campaign sites, often in Next.js, alongside larger university platform work.
Result
Result and limitations
- Custom Next.js recruitment and campaign experiences.
- Campaign-specific landing pages, components, routes, and deployment flows.
- Audience-specific pages focused on helping students choose Arizona and Tucson.
- Shipped public recruitment experiences for admissions and enrollment campaigns.
- Reused frontend patterns across campaign-specific routes and components.
Technical scope