The Result
The Platform
Resilient Hires became a statement piece for what the Resilient Coders organization represents: bold aspiration, relentless pursuit, and a confidence not often seen in this industry. It's a platform that does not just list engineers; it advocates for them.
.jpg)
Phase 1 — Strategy
Discovery started with the Resilient Coders team completing a detailed intake form covering what worked on their existing presence, what was not landing, and where they wanted to be.
User Flows and Content Mapping
Three primary user types were mapped, each with a distinct entry point and funnel. Recruiters and hiring managers ready to act were routed to the talent directory.
Moodboard, Wireframes and Brand System
The moodboard took the longest to arrive at and produced the most decisive creative direction of the project. Early references from competitor research were not hitting the bar.
Phase 2
Phase 2 — Development and Implementation
The final build landed at 12 pages plus CMS templates, built on the MAST framework for class structure and variable management.
The main architectural lift was the CMS system: five collections in total, Fellows, Case Studies, Testimonials, Events (regular and upskill workshops), and Tech Stacks.
The Talent Directory
The talent directory is the core of the platform.
.png)
.png)
HubSpot Integration and Lead Capture
HubSpot handles all lead capture across the site through custom-styled forms that match the brand.
.png)
The Headline System
The most technically demanding element of the build is the headline system used throughout the site.
Phase 3
Phase 3 — Resilient Coders Annual Report
The Resilient Hires brand system did not stop at the platform.
Reflections
What I Learned
Playing it safe is the riskiest design decision you can make
Sites like this become bland because organizations default to conservative design out of fear. Resilient Hires needed to be the opposite: a platform that earns attention first, then earns trust.
Data-driven audiences need both efficiency and engagement
CTOs, engineering managers, and recruiters are optimizing for signal over noise. They need to know immediately what they are getting: skills, location, experience level.
Plan the build before the build
The CMS architecture, component system, and class structure were all mapped before a single page was built in Webflow. That front-loaded work made development feel like assembling pieces rather than solving problems under pressure.
Historic data should inform the intake, not just the outcome
Looking back, more of Resilient Coders' hiring history should have been built into the strategy phase: understanding exactly what has and has not worked in prior hiring conversations, what objections come up, what makes a partner commit.
