Julie Oseka

Page Assembly & Responsive Production

Once designs and copy were finalized, I led production across desktop, tablet, and mobile. I partnered with Design Technologists on complex interactions, and built the remaining site in CMS.

I handled all asset production — including localized imagery, video, and animation — and ensured everything was optimized, responsive, and performance-ready across breakpoints.

The page is still live. Visit Squareup.com if you'd like to see it in person. If you'd prefer to stay here, there's a full video walkthrough of the live site attached.

Figma PD working file, asset slices across breakpoints and locales

Production Figma File

A page is never just a page.

I built and maintained a highly structured production file to support asset generation at scale across breakpoints and locales.

Assets were modular, systematically named, and optimized for reuse across Contentful, Box, and Figma — making updates faster and enabling other teams to self-serve when needed.

One Page. Eight Markets. Eleven Languages.

Localization was one of the most complex parts of working for a global company. I owned it end-to-end, from coordinating translations and adapting assets, to running QA with native speakers to make sure each experience felt right for that market, not just translated.

One of the most time-intensive parts of my role was building and maintaining localized UI screen libraries for marketing — across multiple devices, languages, and product updates.

For the Restaurant POS product, I built a Figma-based component system designed to solve two problems: the initial build took too long, and as the product evolved, keeping every screen library updated was nearly impossible to do manually.

The system is built on main components. Enter content once per locale, and it flows through to every screen that inherits from that component — across all devices and screen types. When the product UI changes or a new feature launches, updates propagate automatically rather than requiring a manual rebuild of every screen.

I maintained a reusable template and module library in Contentful to support scalable web production. The system provided pre-built, on-brand components that allowed teams to create pages quickly and consistently, without starting from scratch.

I worked closely with the Design Systems team to test components and ensure alignment with the Figma library, then owned the library in Contentful — keeping it up to date, production-ready, and easy to use.

This reduced build times by 50% and lowered the barrier to entry for teams working in a complex CMS, enabling faster and more consistent output across the company.

Public Web Template & Module Library, an internal tool for all builders at Square

AI enabled us to automate the creation of 100 SEO programmatic landing pages, dramatically reducing production time and manual effort.

This freed up time for higher-impact work: handling ad hoc tickets, exploring new AI workflows, and spending more time on creative problem-solving.

I tested real scenarios, resolving edge cases, and helping define workflows the broader team could adopt.

Once it was in a stable place, I created onboarding documentation and trained other Production Designers so the team could effectively use the tool and scale its impact.

3 of 100 programmatic landing pages. Click to visit the live pages

Since we're on the topic...

AI is part of my daily workflow — improving speed, consistency, and output quality across production. I stay current with what's developing in this space, and yes, this portfolio was vibe-coded. I'm actively experimenting with Claude, Figma Make, and Sites. These tools are genuinely exciting, but working with them has only made it clearer: AI needs a talented designer's eye to do anything worth looking at.

AI in my day-to-day