William Roush

I started writing software professionally in 2003. I was 16. Self-taught, then somebody paid me to do it, and I've been doing some version of that ever since. Languages were never the hard part: I've shipped production code in more than fifteen of them. People, teams, and operational reality? That's where the work actually lives.

How RoushTech started

I founded RoushTech, LLC in June 2017, and it was honestly more market force than master plan. I was looking for a new role, picked up a few contracts to fill the gap, and then ex-employers started reaching back out because they wanted me on something specific. One of those calls turned into our first multi-year contract, which ran until that client eventually sold the business many years later. That set the pattern. Reputation and word-of-mouth have carried the firm ever since: I've never had to run real outbound, and I'd rather keep it that way.

Why we run the team this way

The honest answer: I got tired of being dropped onto teams where everyone was rowing in a different direction. Most teams I'd been on, the ceiling on what the work could be was set by whoever wasn't doing their job, not by whoever was. I started RoushTech to stop signing up for that. I'd rather hire small, hire well, and keep people for years. Some of these folks I've worked with since long before RoushTech existed, and that's not an accident.

That's also why I won't pitch staff augmentation. Handing engineers over to somebody else's org chart is exactly the dynamic I left. We work as a team, on a project, against an outcome. If a prospect needs bodies on a Jira board, that's a fine model. It's just not ours.

I'm pretty no-BS about how we operate.

What I actually do

Full-stack, networking, security, automation, infrastructure: the stuff that doesn't fit cleanly into one job title. I wear a lot of hats. I build strategy for products, for teams, for our SDLC, and I'm hands-on with the work while I'm doing it. I'm not an owner sitting at the top of an org chart.

The goal, every time: long-term, lasting relationships. Stability over squeezing the next quarter. Software that's still working in five years because somebody actually cared what they were doing.

Find me

• GitHub: StrangeWill
• LinkedIn: williamroush