Custom recruitment web experiences
Recruitment-Focused Landing Pages
Krystian owned routing, components, frontend implementation, and deployment for audience-specific recruitment sites, often built in Next.js.

- Campaign goal
- Route + components
- Responsive experience
- Deployment
Exact role
Senior Web Developer (frontend product engineering)
University of Arizona
Current status
Shipped
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
Worked with admissions and enrollment stakeholders around short-lived, high-priority campaigns; owned routing, components, frontend implementation, and deployment.
Important technical decision
Krystian used focused Next.js builds and reusable components for campaign-specific messaging and routes.
Tradeoff or limitation
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.
Constraints
Hard parts that shaped the work
- Campaign work arrived between larger platform commitments and carried short deadlines.
- Each site needed audience-specific content and behavior rather than a generic information page.
- The implementation had to support quick content changes while remaining responsive and performant.
Shipped result
What exists now
- 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.
Result
Verified result and current state
- Shipped public recruitment experiences for admissions and enrollment campaigns.
- Reused frontend patterns across campaign-specific routes and components.
Technical scope