Has Omar built design systems at scale?
Yes — four, and he treats them as infrastructure for a team rather than a personal artifact. Athena Design System 2.0 at Plastiq is the deepest. He co-led it, audited every product to find where nomenclature and patterns had diverged, then ran workshops to align product, design and engineering on principles and KPIs before producing a single asset. He partnered with engineering on the Storybook implementation, and it became the foundation for Plastiq's IPO-era brand. He built Wisdom's system from scratch as founding designer, rebuilt the one at Welcome Lend, and the fourth runs this portfolio and is published at /design-system. Earlier, at Disney, he and engineering started an ad-sales system — documentation and React components — and handed the foundation on.
What's Omar's fintech and payments experience?
Two years at Plastiq, 2021 to 2023, as Product Design Lead — 0→1 on a regulated product. Plastiq Connect is an embedded payments product: a partner puts card and bank payments inside their own platform, under their own brand, and Plastiq carries the compliance and the disbursement. Benchmarking against Stripe Connect settled what it competed on — not feature breadth, but letting a partner hand PCI scope and risk operations over rather than build and certify them. Compliance is visible in the design: masked stored cards, the encryption notice at the card-block boundary, beneficial-owner collection in the payer form, and a Texas step that fires on the payer's billing address. $20M+ monthly volume in month one, three pre-launch partnerships, eight weeks signed to live.
What AI or LLM work has Omar actually shipped?
Two products at Wisdom, both designed so the model assists rather than decides. Posting Assistant handles insurance payment posting. OCR and LLMs pull data out of scanned documents and surface it in a structured review interface, but specialists keep the judgment calls. He chose the assistive path over full automation deliberately, to preserve specialist trust. It cut manual posting time by about 40%. Management Portal includes an LLM-powered Office Watchlist that flags offices when A/R aging crosses thresholds — over-60 and over-90 balances, week-over-week spikes — and explains what changed rather than just reporting that a rule fired. Its outcome metrics are projected rather than measured.
Is Omar a design leader or an individual contributor?
Both, and the roles track it. He was the founding and sole design lead at Wisdom for two years, owning design across Management Portal, Reporting, Insurance Verification and Posting Assistant. At Plastiq he co-led the Athena design system and ran the cross-functional workshops that set its principles. On Disney's Unified Ad Platform he led two designers and mentored others on the wider design team. He has stayed hands-on throughout, describing his current engagements as equal parts consulting and building — as likely to be rebuilding a design system as shipping a feature to production.
Is Omar actually technical, or only a designer?
He writes production code, and this site is the evidence. It's a React and Vite build he wrote himself: a generated static route per case study, enforced security headers, consent-gated analytics, and an automated test suite that runs on every pull request. Not a template. Day to day he works in Figma, React, HTML, CSS and JavaScript, and uses Claude Code, ChatGPT and Codex inside the design workflow rather than beside it. On Athena he partnered with engineering on the Storybook implementation instead of handing off specs. His own framing: he'd rather put a rough prototype in a teammate's hands than spend another week polishing a deck.
What does Omar's research process look like?
He starts by watching people work rather than asking them what they want. On Posting Assistant he ran observational research using OBS Studio to capture the multiple monitors specialists actually worked across, alongside 40+ interviews for that product specifically. On Disney's Critical Communication Tool he interviewed the Support Center and found they were handling roughly 1,600 calls a month, producing about 1,300 tickets, with around 150 initial criticals. That number shaped what got built. The work ran through affinity mapping, journey maps, MoSCoW prioritisation and usability testing. Across his career he puts the interview count at 500+, including 200+ at Wisdom.
Where has Omar worked, and for how long?
Five roles, most recent first. **Designed by Omar** — Principal Product Designer and consultant, Feb 2026 to present. Independent practice, embedded with Welcome Lend plus a few companies he keeps private. **Wisdom** — Principal Product Designer, founding, Feb 2024 to Feb 2026. Sole design lead on an AI-powered dental operations platform. **Simplero** — Lead Product Designer, Apr to Dec 2023. Page Builder 2.0 and a checkout redesign. **Plastiq** — Product Design Lead, Apr 2021 to Apr 2023. Lead designer, 0→1, on Plastiq Connect. **Disney** — Senior UX Designer, Aug 2019 to Apr 2021. Enterprise ad-sales and communication tools. Earlier: GoNation. Full dates are on the resume.
What kind of role is Omar looking for?
He's open to Head of Design, Principal Product Designer, and senior, staff or fractional product design and design-engineering roles. The work he's drawn to is consistent: hard product problems with messy data, edge cases, operational constraints and users whose job depends on the thing working. Complex B2B, AI workflows, fintech, healthcare SaaS, enterprise platforms. He currently runs an independent practice and is embedded with Welcome Lend, so fractional and consulting engagements are live options alongside full-time. The fastest way to find out whether it's a fit is to ask him — there's a 20-minute intro call link in the contact section.
What are Omar's salary expectations?
Fair question, and it isn't published on the site. It genuinely depends on scope, level, and whether the engagement is full-time, fractional or consulting — those land in different places. The fastest path is to ask him directly. There's a 20-minute intro call link in the contact section, or email omar@designedbyomar.com. If you can say roughly what the role is and where the budget sits, he'll tell you straight away whether it's worth both your time.
Why did Omar leave his last role?
Not something the site covers — and not something worth relaying second-hand through a bot on his own portfolio. The history itself is public: five roles with dates, on the resume and in the work-history answer here. The reasoning behind any particular move is a conversation, not a FAQ entry. If you're doing reference work or weighing fit, ask him directly — booking link in the contact section, or omar@designedbyomar.com.
Tell me about the Wisdom Management Portal
Wisdom's ops team was running 260+ dental offices across 9 Team Leads on 200+ interconnected Google Sheets. Risk stayed invisible until it became a crisis — at-risk clients surfaced too late and capacity was opaque. He designed a centralised command centre around an LLM-powered Office Watchlist that evaluates A/R aging signals and ranks offices by urgency, plus workforce and capacity views. The watchlist explains what changed and why it tripped, rather than just firing a rule. Its headline numbers — 200+ spreadsheets retired, scale from 260 to 900+ offices, 90%+ weekly active usage — are projected targets the design was built for, not measured results.
Tell me about Posting Assistant
Insurance payment posting at Wisdom was chaotic: documents arrived in every format, specialists jumped between screens comparing EOBs, and every posting needed a judgment call. Rather than automate it outright, he designed an assistive workflow. OCR and LLMs extract the key data from scanned documents and present it in a structured review interface, with the specialist still deciding. He ran observational research with OBS Studio to capture how specialists actually worked across multiple monitors, plus 40+ interviews for this product specifically. Result: about 40% less manual posting time, and a foundation for fuller automation later.
Tell me about Plastiq Connect
Plastiq Connect let a company put card and bank payments inside its own product, under its own brand. A buyer could pay a vendor by card even where that vendor did not accept cards, and the vendor was paid the way it already got paid — wire, ACH or a posted check. Two products came out of it: the payer-facing widget a partner embedded, and the portal their developers used to integrate it. He led design 0→1 on both. Compliance shaped the screens rather than sitting beside them — stored cards shown masked, the encryption notice placed at the boundary of the card block, and a Texas step triggered by the payer's billing address. $20M+ monthly volume in month one, three partnerships secured pre-launch, and eight weeks from signed to live.
Tell me about the Athena Design System
Plastiq's products had drifted: inconsistent components, duplicate work, engineering unable to pick up what design produced, and no governing process. He co-led the design system effort. They audited every product holistically before building anything, then ran workshops to align product, design and engineering on principles and KPIs — deliberately doing the alignment work before producing assets. He partnered with engineering on a Storybook implementation and documented layout grid, dashboard components, the payment widget and feedback indicators. Engineering pickup time for global components dropped, 3+ products standardised on it, and it became the foundation for Plastiq's IPO-era brand.
Tell me about the Disney Critical Communication Tool
In 2019 a fire in Italy disrupted Disney network coverage and the right people were never notified. The existing tool either missed stakeholders entirely or flooded them. He led all UX solo across a large cross-functional team, designing a self-service subscription manager that was scalable — brands and tags addable without architecture changes. The work ran through interviews with the Support Center, affinity mapping, journey maps, MoSCoW prioritisation and usability testing, with two versions of the subscription manager scrapped and rebuilt. 1,600+ users, 200,000+ emails sent, 250 critical incidents covered. It's the deepest case study on the site.
Tell me about the Disney Unified Ad Platform
AdVisor was Disney's ad-sales platform, and when the project started it served ESPN and nobody else. ABC, Disney, Hulu, ABC News, Freeform, FX Networks and National Geographic each ran their own tooling, so booking across the portfolio meant working in unrelated systems. The job was bringing those seven brands onto AdVisor without regressing the workflow ESPN depended on daily. He started by mapping the decision flow rather than the screens — a current-state map tracing how a single decision moved through sales, traffic, promo, legal, operations, research and accounting. Eight brand perspectives aligned on a shared model, ESPN's baseline preserved, and reusable patterns that fed Disney's Adapt design system. He led two designers and mentored others on the wider team.
Tell me about Page Builder 2.0
Simplero's page builder was so limiting that users were writing custom CSS to work around it and threatening to move to competitors. It also blocked migration from other platforms, so it was actively driving churn. He led the full rebuild from scratch in two months — user and expert interviews, competitive analysis, and the product requirements, since there was no PM and he owned that role. He worked directly with the Lead Engineer to ship fast. Four core capabilities shipped, contributing to a 9% increase in sales.
Tell me about the Plastiq marketing site
Plastiq needed a full site overhaul in three to four weeks ahead of going public. The old site buried products in navigation and didn't communicate value to investors or target customers. He took the creative lead role without being formally assigned it — building the visual language, brand direction and content strategy, and running workshops to align an eight-person cross-functional team across design, copy, marketing and engineering. Delivered on the three-to-four week timeline and WCAG compliant at launch.
Does Omar have healthcare experience?
Two years of it, as founding designer at Wisdom — an AI-powered dental operations platform — from February 2024 to February 2026. He was the sole design lead across four products: Management Portal, Reporting, Insurance Verification and Posting Assistant. The work was revenue-cycle operations rather than clinical: insurance payment posting, A/R aging, claims, and the ops layer running hundreds of dental offices. That means real exposure to regulated healthcare workflows and the people doing them — 200+ interviews at Wisdom — rather than consumer health.
Has Omar worked at enterprise scale?
Yes — two years at Disney, 2019 to 2021. He led UX on the Critical Communication Tool, adopted by 1,600+ users and used to coordinate 250 critical incidents. On the Unified Ad Platform he brought seven Disney ad-sales brands onto AdVisor — the platform ESPN already ran on — without regressing the workflow ESPN depended on every day. Enterprise there meant the real version: eight brand perspectives to align, each with its own tooling and vocabulary, a single decision crossing seven business functions, and workflows where the product failing has consequences measured in bookings.
Does Omar have 0→1 experience?
Repeatedly, and at different kinds of zero. Plastiq Connect was 0→1 on a regulated product — two products defined from nothing with one PM, one business analyst and five to seven engineers, shipped to $20M+ monthly volume in its first month. Wisdom was 0→1 on the organisation as well as the product: he was the founding designer, so process, system and products all started empty. Page Builder 2.0 was a rebuild from scratch in two months with no PM, so he owned the product requirements too. He describes his draw as hard problems with messy data, edge cases and operational constraints — which is usually what 0→1 actually looks like.
Has Omar designed for developers or APIs?
Yes — Plastiq Connect's partner portal was a product in its own right, built for the engineers integrating the payments widget. Their questions are not a payer's: where the keys are, what is hitting the endpoint, which transaction broke. So API keys were capped and shown masked to their last four characters with the whole rotate-and-expire lifecycle designed, IP whitelisting accepted CIDR ranges and validated the offending row inline, and transaction search carried a per-transaction issue state distinct from an empty result. Sandbox and production were split in the navigation. Eight weeks from signed to live was a design target, not a sales number. He also writes React and HTML/CSS/JS, so handoff tends to be a conversation.
How does Omar handle accessibility?
He treats it as a design-system requirement rather than QA cleanup. The design system powering this site states that plainly: WCAG AA is the floor, and focus states, keyboard flows, contrast, touch targets and reduced motion are requirements rather than fixes. In practice: the Plastiq marketing site shipped WCAG compliant at launch on a three-to-four week timeline, and the Disney Critical Communication Tool carried accessibility as an explicit tag alongside mobile-first and scalable. On this site every moving treatment has a stable equivalent under reduced motion, and that behaviour is enforced by automated browser tests.
Does Omar do brand and visual design?
Yes, though it isn't the centre of the practice. On the Plastiq marketing site he took the creative lead role without being assigned it — building the visual language, brand direction and content strategy for a pre-IPO relaunch, and running workshops to align an eight-person cross-functional team. The Athena design system fed directly into Plastiq's IPO-era brand evolution. His background starts there: he grew up in Brooklyn as an artist and came to design through Photoshop, music covers and flyers before moving into product.
How does Omar work with engineers?
Close, and usually in the same artifacts rather than across a handoff. On Athena he partnered with engineering on the Storybook implementation instead of shipping specs. On Page Builder 2.0 he worked with the Lead Engineer to ship a full rebuild in two months. On Plastiq Connect the specification went past screens — spacing called out per breakpoint, the mobile button block annotated as pinned, and the fee popover specified separately for desktop hover and mobile tap, because a finger has no hover state. On the Unified Ad Platform he aligned the front-end to the backend architecture rather than designing around it. He writes React and HTML/CSS/JS, which changes the conversation.
How does Omar work with product managers?
As a partner in defining the product, and occasionally as the substitute for one. On Plastiq Connect he set the product vision with the PM from nothing, alongside one business analyst and five to seven engineers. On Page Builder 2.0 there was no PM, so he owned the product requirements himself next to the design. He also does the alignment work directly — co-leading workshops on Athena to set principles and KPIs, and running an eight-person cross-functional workshop on the Plastiq relaunch. His stated preference is starting in plain text: writing, mapping the problem and naming the tradeoffs before moving to screens.
How does Omar handle ambiguous problems?
He starts in writing, not in Figma. His own description: begin in plain text — writing, mapping the problem, naming the tradeoffs and cutting through ambiguity — then move quickly into flows, prototypes and working artifacts. The pattern shows up in the work. On Athena the audit and the alignment workshops came before any asset was produced. On Management Portal the problem arrived as 200+ interconnected spreadsheets across 260 offices, and the design work was largely deciding what risk looked like before building anything to display it. He describes the draw as hard problems with messy data, edge cases and operational constraints.
How does Omar measure whether design worked?
By what the product changed operationally, and he's careful about which numbers are earned. Measured: about 40% less manual posting time on Posting Assistant, a 9% sales increase on Page Builder 2.0, $20M+ monthly volume in month one on Plastiq Connect, 1,600+ users and 250 critical incidents covered on Disney's Critical Communication Tool. Projected: Management Portal's targets — 200+ spreadsheets retired, 260 to 900+ offices, 90%+ weekly active usage — are what the design was built for, and the site labels them as projections rather than results. On Athena the team set KPIs in workshops before building.
Does Omar prototype?
Constantly, and he'd rather prototype than present. His stated preference: put a rough prototype in a teammate's hands rather than spend another week polishing a deck. Plastiq Connect was worked out through iterative wireframing and interviews with the engineering and product teams who would integrate it, and Page Builder 2.0 went from nothing to shipped in two months. Because he works in React and HTML/CSS/JS, prototypes can go as far as real code when that is the faster way to answer the question — this site being one example. AI-assisted prototyping is listed among his core skills.
Does Omar run workshops or facilitate?
Yes, and usually to unblock alignment rather than as process theatre. On Athena he co-developed a series of workshops that established the design system's KPIs, then gathered research to evangelise the system across the organisation — deliberately doing the alignment work before producing assets. On the Plastiq marketing relaunch he ran workshops to align an eight-person cross-functional team spanning design, copy, marketing and engineering, on a three-to-four week timeline. His own caveat on process: not for process theatre — for speed, consistency and better product quality.
Does Omar write?
Yes — he publishes on Substack, linked from the contact section and the footer. Writing is also part of how he works rather than a side activity. He describes starting problems in plain text: writing, mapping the problem and naming the tradeoffs before moving into design. That shows up in the artifacts too. This repository is public and documents its own design system, deployment runbook and AI-assisted workflow in writing.
Where is Omar based?
Torrington, Connecticut, working remote. US Eastern time. His recent roles have all been remote — Wisdom was New York remote, Simplero Brooklyn remote, Plastiq San Francisco remote. The Disney role was on site in Bristol, Connecticut. So he's worked remote with teams across US timezones for several years, and it's the default rather than an accommodation.
Is Omar available, and how soon?
He currently runs an independent practice and is embedded with Welcome Lend plus a few companies he keeps private, so availability depends on what you're asking for. Fractional and consulting engagements are live options alongside full-time roles. Rather than guessing at timing here, the honest answer is to ask him — there's a 20-minute intro call link in the contact section, or omar@designedbyomar.com.
Does Omar do contract work or only full-time?
Both. He's open to Head of Design, Principal Product Designer, and senior, staff or fractional product design and design-engineering roles. His current practice is consulting and embedded work — at Welcome Lend he's an embedded senior design lead, rebuilding their design system and shipping work brokers use daily. So a fractional or contract engagement isn't a fallback for him; it's what he's doing now.
How do I get in touch with Omar?
Fastest is the 20-minute intro call link in the contact section of this site. Otherwise: omar@designedbyomar.com. He's also on LinkedIn, GitHub, Substack and Behance, all linked from the contact section and the footer. His resume is downloadable from the hero and the contact section if you need dates and titles before reaching out.
Can I see Omar's resume?
Yes — it's linked from the hero and the contact section of this site as a PDF. It covers the five most recent roles with dates and titles, a selected-impact summary, and the core expertise list. If you want the narrative version instead, the eight case studies go considerably deeper than a resume bullet can.
How was this site built?
He built it himself: React 19 and Vite, deployed on Vercel. A post-build step generates a real static route for every case study with its own metadata, structured data and sitemap entry — and injects the full case-study text into the HTML so crawlers, ATS scrapers and AI assistants can read it without running JavaScript. It ships enforced security headers, consent-gated analytics, a published design system, and an automated test suite that runs on every pull request. The repository is public, and it documents its own AI-assisted workflow in docs/ai-workflow.md.
Am I talking to Omar or to an AI?
Neither, exactly. Most of what you get back was drafted from the case studies published on this site and then reviewed by Omar before going live — so the words are pre-written rather than improvised. A model usually picks which of them answers you, because matching on shared words alone got it wrong too often. It chooses from the written set and cannot edit what it picks. When none of them fits, a model drafts a reply from the closest reviewed answers, and that reply is labelled “drafted, not reviewed” wherever it appears — reviewed and drafted are never presented as the same thing. On a hiring site, an assistant that quietly invents a detail is worse than one that flags what has not been checked. For anything that matters, email him.
What data does this assistant collect?
Clicking a suggested question, or typing one word for word, is answered in your browser from a static file — nothing is sent. Anything else goes to this site's own endpoint, because word overlap alone got it wrong too often. From there it is usually passed to Groq with the list of written questions, so a model can say which one you mean. If Groq cannot be reached, or the daily limit is spent, nothing leaves this site. A question none of them covers is sent again with excerpts of the published case studies, so a reply can be drafted from them and labelled unreviewed. If you accepted analytics, the wording of a question nothing covers is recorded, so Omar can see which answers are missing.
Will Omar do a design exercise or spec work?
Not something the site answers on his behalf, because it depends entirely on what's being asked and at what stage. What is worth saying: there are eight case studies here covering the real thing — the research, the tradeoffs, the versions that got scrapped — and the site itself is production work he wrote and shipped. That's usually a better read on how he thinks than a weekend exercise. If you need to see something specific, ask him directly. Booking link is in the contact section.
Can Omar guarantee similar results for us?
No, and anyone who says yes is selling something. The numbers on this site belong to specific products with specific constraints — a 40% posting-time reduction at Wisdom, $20M+ monthly volume at Plastiq, 1,600+ users at Disney. They describe what happened there, not what's promised elsewhere. Where a figure is a target rather than a result, the site labels it projected. What transfers is the approach, not the outcome. Whether it fits your situation is a conversation worth having directly.
Tell me about Omar's personal life
The site keeps that brief on purpose. What's public: he's an amateur boxer, a music producer and a dedicated father, and he grew up in Brooklyn. Beyond that it isn't covered here, and it isn't relevant to whether he's right for a role. If you're trying to get a sense of how he thinks or what he's like to work with, the About section and the case studies are the better read — or just talk to him.
What does Omar think about [a company or person]?
Not something this assistant will do — opinions about companies or people aren't published here, and relaying them second-hand through a bot on his own portfolio would be a bad idea regardless. What's documented is the work: where he was, what he built, what it changed. If you want his read on something, that's a conversation. Booking link is in the contact section.
Can I get references or contact his former colleagues?
Not through this site, and not through an assistant — references are his to offer, not a bot's to hand out. There are attributed quotes from stakeholders inside the case studies, which give some sense of how the work landed with the people it was built for. For actual references, ask him. He'll arrange them directly: booking link in the contact section, or omar@designedbyomar.com.
What kind of product designer is Omar?
A principal product designer working on complex B2B products — AI workflows, enterprise platforms, fintech, healthcare SaaS and design systems. The range is deliberate rather than scattered: he works across strategy, research, UX architecture, prototyping, UI systems and launch execution, because in the products he takes on those are rarely separable. A workflow tool with messy data cannot be researched and then handed off; the architecture and the interface decide each other. If a role expects someone to pick one of those and stop, it is probably not the right fit.
What types of companies is Omar best suited for?
Startups and growth-stage teams building workflow products, AI tools, fintech platforms, healthcare SaaS, enterprise software, API products or internal operational systems. The common thread is a product where the hard part is the domain rather than the surface — payment rails and compliance at Plastiq, dental operations at Wisdom, cross-brand ad sales at Disney. He was the founding designer at Wisdom and the lead on a 0→1 payments product at Plastiq, so a team without an established design practice is familiar ground rather than a risk.
What kinds of problems should a team bring Omar in to solve?
When the workflow is messy, the product needs clearer direction, adoption is being slowed by UX, or the business needs stronger product foundations. The work is most useful where a team needs senior design judgement and hands-on execution at the same time — someone who will map the decision flow before drawing screens, and then draw the screens. On the Disney Unified Ad Platform that meant tracing how one decision moved through seven business functions before any interface existed. It is a poor fit for work that is already well defined and only needs producing.
What business outcomes has Omar influenced?
The ones that are measured, with their scope attached. Posting Assistant cut manual posting time by about 40%. Connect API Payments cleared $20M+ in monthly payment volume in its first month, with three partnerships secured pre-launch. Disney's Critical Communication Tool reached 1,600+ users and carried 200,000+ communications across 250 critical incidents. He ran 200+ interviews and discovery sessions across the Wisdom products. Other numbers on the site are targets a design was built to hit rather than results, and are labelled that way.