← Back to Operations: In practice Case study

An internship program that hired 8 of its 11 interns full-time.

A pipeline for new designers, recruited nationally and tested on product ideas that never reached a roadmap.

The problem

The department was growing and had no pipeline for entry-level designers. Few local applicants met the bar for an entry-level UX and UI role.

The constraint

Recruiting was limited to a local zone. Hiring beyond it, with relocation, needed special approval.

The outcome

8 of 11 interns were hired full-time, all rated high performers, and product received roadmaps for ideas it had not been able to prioritize.

8 of 11interns hired full-timeinterns hired full-time: 8 of 11.
4annual cycles
12 weeksper cycle

The program was approved before anyone had designed it

Executive leadership encouraged the department to use internships to build a pipeline for new talent, and the program was approved as part of the department's growth plan before its shape was set. I built it with the company's internship recruiting team. Two recruiters went to college recruiting events, reached out to candidates on LinkedIn, and reviewed applicants who found the posting on job boards.

The portfolios made the case for recruiting nationally

Local programs focused on graphic design, or on computer science with more development than UX and UI design. Applicants from both were considered, and few met the needs of an entry-level role. I took the case to leadership with examples: local applicants who would not meet the bar, and portfolios the recruiters found at schools outside the zone that matched those of some full-time candidates.

The department hired only a few positions, so relocating an intern after a full summer of working together was a justifiable cost next to a full-time hire. The approval came through, and interns came from across the country.

Where interns came from
  • Most interns: university programs on the east and west coasts
  • Some: Texas
  • A few: tech schools in the Midwest
  • The original local recruiting zone
Most interns: university programs on the east and west coasts. Some: Texas. A few: tech schools in the Midwest. The original local recruiting zone.

Regions shown, not individual schools or states.

Intern projects came from the backlog product could not prioritize

Two months before each cycle, I opened a submission period for projects. The requirements were specific: a backlog item that was not being prioritized, needed a lot of concept work, and met a known need whose return was still unclear. These were the ideas product management wanted to explore but could not justify as features yet.

Projects were chosen to give product a delivery roadmap, and to be broad enough to evaluate each intern across the skills a designer on the team needed. By then the interns were already selected, so each project could be matched to what they had shown in interviews.

Setting up one cycle
8 weeks out

Submissions open

Product teams submit backlog ideas they cannot prioritize.

8 to 4 weeks out

Scope and prioritize

Each idea is scoped with its deliverables, then ranked with leadership.

Before day one

Match to interns

Projects are aligned to the skills each intern showed in interviews.

12 weeks

Run the cycle

Interns deliver a roadmap for product and are evaluated across the full skill set.

Twelve weeks doubled as the hiring evaluation

I set the calendar and pacing for every intern team, and served as their team lead and mentor, at times leading two teams of four at once. I reviewed all of their work and made or guided the UX and UI decisions. The evaluation used the same skills matrix and checkpoints as the department's onboarding, so each full-time offer came with a clear picture of the intern's skills and the team they fit best.

In practice

USF behind eight real operational initiatives.