Are you still using the same job engineering description from three years ago?

The AI wave has split software development into two speeds. On one side are developers running multiple Claude Code instances in parallel, experimenting with voice interfaces, and figuring things out as they go. Their workflows might be held together with duct tape, but they're building a lead that will be hard to catch. On the other side are developers who dismiss AI entirely because an auto-generated pull request didn't follow their coding standards. They resist change, insist their standards are higher, and in doing so, drag the people around them backwards.

This dynamic reminds me of when Google first emerged. Some people embraced search engines early, not because they knew where it would lead, but because they were curious. They learned the quirks and built a skill that took years to develop. AI is heading the same way. Developers who are curious about AI tooling and actively integrate it into their workflow are becoming more productive and more adaptable.

If you haven't revisited your engineering job descriptions in the last six months, now is the time. Too many vacancies still read like a copy-paste from two years ago, with zero mention of AI. Hiring someone who is actively hostile toward AI will do more harm than not hiring anyone. At a minimum, you need people who are open to trying the technology. If your job descriptions don't reflect this shift, you're either attracting the wrong candidates or signalling that your company hasn't caught up.