Aly
Fluckey

Context

Pocket's core save-and-read loop was strong, but user organization features had stagnated. Lists represented a meaningful step toward helping readers manage large collections, a high-visibility, high-complexity initiative that required coordination across frontend, backend, product, design, QA, and data.

Goals

• Ship a production-quality Lists feature on schedule
• Establish cross-functional rituals that could scale beyond this project
• Improve content engagement metrics by giving users better organizational tools

Who I Worked With

Frontend engineers, backend engineers, a product manager, UX designer, QA engineers, and the data team. Stakeholder alignment across multiple time zones.

What I Led

• Owned planning, sequencing, and delivery tracking
• Ran cross-functional syncs and unblocked dependencies
• Partnered with product on scope decisions and tradeoff conversations
• Coached engineers through architectural decisions on the feature

My Technical Contribution

Personally implemented core feature surfaces in React, TypeScript, and GraphQL, including the data model integration and UI components that shipped to users. Drove frontend architectural decisions that kept the feature extensible post-launch.

Results

• 17.6K lists created and 4.8% active engagement within the first month
• Feature shipped on target timeline
• Planning framework adopted for subsequent feature work

Context

Pocket's card components - the core UI unit across the product - had accumulated significant inconsistency and technical debt. Each team was solving presentation problems independently, creating divergence that slowed down feature work and made design changes expensive.

Goals

• Establish a consistent, composable card anatomy
• Reduce time-to-ship for UI changes across teams
• Improve design-to-engineering handoff quality

Who I Worked With

Frontend engineers across multiple teams, the design system team, and UX designers. Required alignment with product managers on prioritization of "invisible" infrastructure work.

What I Led

• Built the case for prioritizing design system work alongside feature delivery
• Partnered with designers to define canonical card variants
• Oversaw the implementation and migration strategy
• Created documentation standards for component consumers

My Technical Contribution

Owned the frontend architecture for Pocket's core UI component library in React, TypeScript, and Storybook. Translated design tokens and component specs directly into composable production components, reducing design-to-dev handoff time and enabling consistent theming across product surfaces.

Results

• Significantly reduced UI inconsistency across the product
• Improved velocity on subsequent feature work touching card layouts
• Stronger design–engineering shared language established

Context

Product teams wanted to test more, but the experimentation infrastructure was inconsistent and the process for running rigorous A/B tests wasn't well established. Decisions were being made on instinct rather than evidence.

Goals

• Establish a reliable, repeatable experimentation process
• Give product and engineering teams confidence in test results
• Increase the rate of data-informed decisions

Who I Worked With

Data engineers, product managers, frontend engineers, and QA. Close collaboration with analytics to ensure instrumentation was accurate and consistent.

What I Led

• Defined experiment design and review standards
• Oversaw analytics integration across feature surfaces
• Partnered with data team on instrumentation quality
• Ran retrospectives on experiment outcomes to capture learnings

Results

• Teams moved from ad hoc testing to structured experimentation
• Improved confidence in ship decisions based on experiment results
• Analytics instrumentation coverage increased meaningfully

Context

Mozilla launched a Mastodon-based social instance during the broader Fediverse growth period. As a new product with a small team and high public visibility, it required careful onboarding design and meaningful instrumentation from day one.

Goals

• Build a controlled, trust-based invite and onboarding flow
• Establish analytics that could guide early product decisions
• Ensure privacy-respecting instrumentation aligned with Mozilla's values

Who I Worked With

Small, cross-functional team including product, engineering, and trust & safety. Close alignment with Mozilla's privacy and data governance teams.

What I Led

• Designed and owned the invite flow architecture
• Built out analytics instrumentation from scratch
• Ran stakeholder alignment on privacy-first data decisions
• Coordinated rollout sequencing during public launch

Results

• Invite system launched with controlled onboarding that matched server capacity
• Analytics baseline established for ongoing product decisions
• Zero major instrumentation or privacy incidents at launch

Context

A client needed to expand their Webflow-based site to support multiple language markets, without rebuilding from scratch or introducing a content management burden that the team couldn't sustain. Existing i18n tooling in the platform was immature.

Goals

• Enable multilingual content delivery within platform constraints
• Build something maintainable by a non-technical content team
• Avoid full platform migration

Who I Worked With

Client stakeholders, content editors, and a small development team. Required close collaboration with non-technical team members to ensure the solution fit their actual workflows.

What I Led

• Designed the content architecture and routing strategy
• Built and tested the multilingual implementation
• Created documentation and training materials for the content team
• Managed client expectations through technical constraints

Results

• Multilingual content delivery live across target markets
• Content team able to publish independently without dev involvement
• No platform migration required