The Layer Cake Strategy: Why We're Putting Phenom on Top of Workday

Because applying for a retail job (and hiring for one) shouldn't require the bureaucratic stamina of refinancing a mortgage.

tldr; * Workday is great recruiting compliance engine, but its native candidate UI is difficult for high-volume hiring.

We have a mandate to hire retail workers in hours, not weeks. Workday’s native UI, built for corporate compliance, is fundamentally misaligned with this kind of retail velocity for both the candidate and hiring manager.

The solution is the "Layer Cake": Phenom is the frosting on both sides (frictionless UI for candidates, AI agents for managers) and Workday is the sponge (the dense, structured compliance data).

Yes, connecting them creates an "Integration Tax," but I will gladly pay it to stop candidates from abandoning our application and to stop our managers from tearing their hair out.

I am writing this right before I take to the floor of the Philadelphia Convention Center.

Next week is IAMPHENOM. For me, it is a homecoming. I was an early Phenom employee back in the days when "All Hands" meant ordering three pizzas. Heck, when I joined, we were called iMomentus. But I return this week wearing a very different hat: The Customer. As a Sr. Manager of HR Tech Engineering for a massive retail and pharmacy enterprise, I am caught in the ultimate architectural holy war: The Suite vs. Best-of-Breed. Workday wants you to use Workday Recruiting for everything. Phenom wants you to buy their Experience Layer to sit on top of it.

Who is right? To answer that, you have to look at the sheer, unyielding physics of High-Volume Hiring.

Recently, my team was handed a massive mandate: Get a retail candidate from "Apply" to "Offer Accepted" in hours, not weeks.

If a corporate Director takes four days to schedule an interview, that’s normal. If a Pharmacy Manager takes four days to schedule an interview with a tech, they are already working for the competition across the street.

The Candidate Problem: The "Justin" Usability Test

Last week, my 11-year-old son, Justin, wanted to play a new game on his iPad. He downloaded it, opened it, and was immediately hit with a screen asking him to create an account, verify his email, and set up a profile. He stared at it for exactly four seconds, deleted the app, and went back to playing Roblox.

Justin isn't lazy; he just has zero tolerance for unnecessary friction. He expects an Amazon-like experience.

Now, imagine Justin is a 19 year-old pharmacy tech applicant (it’s only 8 years from now - and now I’m having an existential crisis). He’s sitting in his car on a 15-minute break from his current job. If we hit him with the native "Candidate Home" compliance gate (forcing him to create an account, remember a password with a special character, and click through several pages of EEO questions) he doesn't submit a support ticket. He closes the tab. He walks across the street.

The Manager Problem: Doing Taxes While Running a Sprint

But the friction isn't just at the front door. We tried to bake this entire hire-in-hours process natively in Workday, and it broke down right at the beginning, on the manager side.

Workday is a system built by compliance lawyers for corporate recruiters. It wants a paper trail. It does not want you to hire a cashier in hours.

We were expecting a Store Manager, who is actively managing a pharmacy line and covering a register, to log into a heavy corporate ERP, navigate a supervisory org hierarchy, and execute a "Start Job Requisition" business process (which we massively simplified). Asking a retail manager to use native Workday to hire someone quickly is like asking them to fill out a supply chain procurement form just to order a pizza.

The Dual-Sided Layer Cake

To hit the goal of hiring in hours, we had to rethink the architecture. We built a "Layer Cake."

Workday is the sponge. It’s dense, it’s structurally sound, and it keeps the company from getting sued. But nobody wants to eat a dry sponge cake.

So, we put Phenom (the frosting) on both sides of the cake:

The Candidate Frosting: We replaced the mortgage application with an Amazon-like, frictionless front door. SMS applications, conversational AI, and zero forced account creation.

The Manager Frosting: We shielded the retail managers from the Workday UI entirely. We deployed Phenom's Job Requisition Agent and Hiring Manager portals. The manager just says, "I need a cashier," and the AI agent handles the heavy lifting, scheduling, and screening. We put a "Human in the Lead," but we gave that human a power-tool instead of a bureaucratic checklist.

And the most crucial architectural pivot? We kept the Offer Acceptance inside Phenom. If you give a candidate a beautiful 3-minute SMS application, but then force them to create a Workday Candidate Home account just to click "I Accept" on the offer, you’ve ruined the magic. It’s like ending a Michelin-star meal by making the customer wash their own dishes.

Keep them in the frosting until the deal is closed. Then the API fires, and they drop into the Workday cake for background checks and compliance.

The Pragmatic Architect's Verdict

As an architect, I love the "Power of One." I want everything in one system to keep my diagrams clean.

But layering Phenom over Workday creates an "Integration Tax." You have to monitor APIs and manage two vendor roadmaps.

Is it worth it? Yes. I will gladly pay that tax every single day to stop our candidates from abandoning our funnel and our managers from losing their minds. Our job isn't to force the business to use native functionality just because it's already paid for. Our job is to build a resilient bridge between the system of engagement and the system of record.

Now, if you'll excuse me, I need to go find Mahe and ask him about my API limits.

— Mike

Department Director, HR Tech | Keeper of the layer cake