Back to UX Portfolio

UX Internship · Playcast

Internship at Playcast

Design work across internal configuration tools, an operations admin dashboard, and the customer-facing Host Rewards experience—documented here at a level that respects what is public versus confidential.

Role
UX Intern
Company
Playcast
Focus
Internal tools, admin UX, host-facing product
Tools
Figma, cross-functional review

How this page shares Playcast work

Playcast asked interns to treat internal systems carefully on public portfolios. This case study follows that standard:

  • Publicly visible work — okay to show when the UI is released and screens use no test data, unreleased features, internal views, or customer information.
  • Internal work — okay to describe the problem and my design role; original screenshots, Figma files, workflows, and implementation detail stay off the portfolio unless explicitly approved.
  • Confidential / admin work — default to no real dashboard captures; use reconstructed, simplified screens with fake data (as on this page) to show design thinking without exposing business rules, fraud controls, or operations.
Internal tool

Macro Recorder

I designed an internal macro-recording tool used by product and operations teams to configure automated interaction sequences—reducing repeated manual setup when the same flows needed to run across environments or host scenarios.

At a high level, the problem was repeatable configuration without engineering each one-off: teams needed a structured way to define steps, validate inputs, and hand off a sequence others could run safely. My work focused on layout, step hierarchy, empty and error states, and how non-engineers scan a long macro at a glance.

Shared on this pageProblem framing, my role, and a sanitized reconstruction of the interaction model (fake steps, no real configuration).
Not sharedProduction screenshots, Figma source files, internal workflows, configuration fields, or implementation logic.

Illustrative layout only—not the production tool, names, or rules.

Internal admin

Rewards Manager dashboard

I contributed UX for an internal admin surface used to manage host rewards operations—reviewing accounts, monitoring activity signals, and supporting moderation workflows. Admin dashboards like this often embed fraud controls, reward economics, and customer-identifying data, so they need the strictest portfolio treatment.

My design work emphasized scannable tables, clear status language, and separation between “review” and “act” so operators could move quickly without mis-clicks on high-impact actions. I did not publish the real dashboard; the mock below is a simplified, fictional admin view approved for portfolio use.

Shared on this pageHigh-level problem, design principles, and a redacted reconstruction with placeholder metrics and host IDs.
Not sharedActual dashboard screenshots, real KPIs, fraud rules, payout logic, or host/customer records.

All numbers and identities are fabricated for portfolio display.

Customer-facing

Host Rewards app

The Host Rewards experience is what PC owners see when they participate in the Playcast network—progress, status, and incentives for keeping machines online and performant. Because this product ispublic-facing, it is the most straightforward to discuss on a portfolio: released UI patterns, progression, and clarity of rewards—as long as captures avoid test accounts, unreleased features, or internal analytics.

I supported flows that explain what earns credit, how rank maps to rewards, and what “ready” means for a host machine—reducing confusion between progress metrics and redeemable value. Where I show UI here, it follows the reconstructed / public-safe approach rather than dumping raw internal builds.

Shared on this pagePublic-style patterns, fictional host state, and narrative about host-facing clarity—not live customer data.
Not sharedStaging builds with test data, unreleased tabs, admin-only views, or analytics tied to real users.

Representative layout; replace with approved public screenshots when available.

Takeaways

This internship stretched across three visibility levels—internal tooling, privileged admin surfaces, and shipped host UX. The through-line was making complex incentive systems legible: structured steps for internal users, cautious affordances for operators, and plain language for hosts.

Publishing Playcast work also meant negotiating what storytelling is worth without leaking how the system works. Reconstructed mocks turned out to be a useful compromise: they preserve design decisions and IA without becoming documentation of production rules.