TechWolf

🎙️ Our CEO Andreas De Neve 🐺 on the The Josh Bersin Company WhatWorks podcast. No "someday" disruption here. Software engineering, support, digital marketing: all rewritten in under a year, and Andreas isn't shy about what's coming next. He gets into what it means for skills strategy, workforce planning, and which tasks AI can genuinely take off your plate. 27 minutes, not one wasted 🎧👇

New from our engineering team: Silas Deblanc on a prototype that went from idea to working dashboard in under a week. The team lit up. Then we paused it. Not because it was broken, but because the honest answer to "should we ship this?" was "not yet." That's the whole point. AI made the building cheap. The judgment around it got expensive: which problem actually matters, what to test, when to pause the shiny thing. It's why we're leaning hard into one role, the Product Engineer. One person owning the track from customer problem to adopted product. If that's your kind of work, good news: we're hiring for exactly this. Full blogpost and the open role, both in the comments 👇

"Where we failed in the past was doing skills, grades and career development piecemeal. TechWolf brings it all together." 💬 That's Jonathan Jacobsen, VP Reward at Colt Technology Services, on what finally clicked. Colt Technologies is a global network and connectivity provider, right in the thick of a major workforce transformation. They had all the pieces, skills, grades, career paths, but each was built on its own. Every project made sense alone, yet nothing tied them together. So they stopped patching and started with the work itself. Instead of mapping who has what and forcing it onto old job titles, they began from the real roles and tasks. That's where we came in: our Redesign Agent drafted a new architecture from Colt Technologies's own work, with their team reviewing and validating every step. One layer, finally holding it all in place. This is exactly the kind of work we'll be demoing next week at SAP Connect, Las Vegas, October 5 to 7. Booth 6111, come say hi. Read the full story in the comments 👇

Give your AI a name, a spot on the team, maybe a Slack handle, and surely people will trust it more. That's the idea, and about a third of companies are trying it. Julie Bedard and her team at Boston Consulting Group (BCG) decided to test if it actually works. The setup was simple. Around 1,200 managers checked the same document for mistakes. The only thing that changed was who they were told wrote it: a person, an "AI employee," or an AI tool. The result is worth a pause. When people thought an "AI employee" wrote it, they trusted it too much. They spotted fewer mistakes, let more slip through, and started treating the AI as the one responsible. In short: people just got less careful. Moral of the story: name the AI whatever you like, a person still has to fully own the outcome. Full chat on our podcast, with her Harvard Business Review research behind it. Listen in the comments 👇

What does a skills partnership actually change? Two months on from announcing TechWolf x WTW, we asked three leaders who'd have no doubt: Renée E. Smith and Catherine Hartmann from WTW, and our own Daniel Torrens. The thread running through all three: getting from skills and workforce data to real, AI-driven business impact. Because skills only pay off when demand and supply stay connected, and stay that way. Favourite moment? Renée calling WTW part of the wolf pack. Daniel and Renée go deeper on the demand-and-supply idea in the piece in the comments 👇

One month out: what AI truly changed about how we build. 📌 Three talks and a proper night out, 28 October in Brussels. Block the date. Here's who's on stage at the AI-First Engineering Community event: → Niels Lowie (TechWolf) on what Specto builds overnight, and what still breaks. → Georges Lorré (ML6) on Unum, the execution layer that carries enterprise workflows through to done. → Christophe Geudens (Prismos) on two years of agentic coding, and what it did to code review. Co-hosted by TechWolf and ML6, with Wintercircus Ghent as ecosystem partner. Come compare notes 👇 details in the comments.

📍The pack is crossing the Channel. We'll be at the Gartner HR Symposium/Xpo™ 2026 conference in London. 6 to 8 October, ExCeL London, one of the biggest rooms in HR this year. 🎤 Come see Cedric Vandamme, our VP Professional Services & Customer Success, on stage Thursday 8th of October at 11:30. You'll also find the rest of the pack on the ground all week: Colin Tierney, Reinhard De Milt, Tom Reid, Hugo Marshall, Dan Fernée, Sam Pope (Taylor), Fee De Vos, Giulia La Volpe, Max Kelsey, Wolf Goderis, David Fitzpatrick. 🇬🇧 In London too? Come by booth 504, or get in touch to grab time with the team. All details in the comments 👇

Exactly what the picture below says 👇 Come cheers with us and TalenTeam at SAP Success Connect Happy Hour on October 6. See you there 🕺

TechWolf 🤝 Oracle Every HR leader knows the pattern: skills data gets entered once, then quietly goes stale. Oracle Cloud HCM's Dynamic Skills gives you the framework: Job Profiles, Talent Profiles, and the Skills Library. Keeping all of it fresh by hand is where it falls apart. That's where TechWolf steps in. We read real work signals across the tools your teams already use and keep Oracle fed with current, evidence-backed skills. It's live now, and documented in Oracle's own release notes as a supported skills provider. More on that in the comments. We put the whole thing in a two-minute watch 👀

A failing request used to cost one of our engineers 15 to 30 minutes of lining up logs and charts, only to end with a hypothesis. So our platform team rebuilt observability from scratch. First blogpost in our Platform series, by Ruben Hias. The goal: any engineer should be able to pick up a failing request, follow it across every service, and see what actually happened. It now runs on OpenTelemetry, ClickHouse and HyperDX. Ruben leaves the wrong turns in too, which is the best part. What worked, what didn't, and the setup we run today across 34 services and around 149 million records a day. Worth a read, especially if you've ever stared at a green dashboard during an outage. Full blog in the comments 👇