Enterprise software, coding, testing, packaging, support, troubleshooting, and documentation.
ERIC NOLAN // BUILDER FIRST
Product judgment with dirt under its fingernails.
I came up through software development, performance engineering, release delivery, and product leadership. Today I spend a lot of that range building and governing AI systems—close enough to the code to know when the architecture story is lying.
Career arc
I did not arrive at AI from a slide deck.
More than two decades in technology gave me a useful bias: systems have to operate after the demo, people have to understand them, and someone eventually has to debug the consequences.
Release systems, capacity, performance analysis, launch readiness, architecture, vendors, and production realities.
Epics, requirements, prioritization, stakeholder alignment, roadmaps, risks, dependencies, and delivery.
AI product strategy, hands-on development, orchestration, APIs, governance, testing, developer enablement, and rollout.
What I optimize for
Useful. Explainable. Durable.
I like ambitious technology. I just don't confuse ambition with complexity.
Show the work.
Public implementations and case studies are more useful than stacking adjectives into a headline.
Know what the system may do.
Authority, privacy, approvals, and failure behavior should be designed—not discovered in production.
Do not automate the wrong thing faster.
Product sense still matters. Sometimes the best AI architecture is less AI.
Scouting is not a résumé footnote
Unyielding Claw has a history.
Unyielding Claw is my Mic-O-Say name. I am an Eagle Scout and a Sachem in the Heart of America Council's Tribe of Mic-O-Say. Scouting has been a major thread in my life through leadership, service, mentoring, Cub Scouting, Wood Badge, and helping people grow into responsibility.
The name became my public engineering identity because it already meant something to me long before GitHub did.
Learn about Mic-O-Say from the Heart of America Council →Off the clock, same brain
The hobbies look unrelated. The pattern isn't.
I like learning systems, adapting plans instead of worshiping them, and making something tangible. Sometimes that is code. Sometimes it is a jig, a photo, a brisket, a bowling adjustment, or a crochet hook.
Builder is the through-line
Software. Systems. Jigs. Teams.
The medium changes, but I keep coming back to the same thing: understand what has to work, build enough structure to make it dependable, and improve it with evidence from actual use.