# Engineers need systems skills for AI workflows **URL:** \ **Category:** tech news\ **Created:** [April 20, 2026, 8:00am UTC](https://forum.kirupa.com/t/engineers-need-systems-skills-for-ai-workflows/680666 "2026-04-20T08:00:23Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![Yoshiii](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/yoshiii/32/31156_2.png) [@Yoshiii](https://forum.kirupa.com/u/Yoshiii)\ **Post date:** [April 20, 2026, 8:00am UTC](https://forum.kirupa.com/t/engineers-need-systems-skills-for-ai-workflows/680666/1 "2026-04-20T08:00:23Z")
This argues that AI is shrinking the value of boilerplate coding and pushing engineers toward system design,. > **[The Future: Engineers as AI System Architects](https://dev.to/siddhartha_reddy/the-future-engineers-as-ai-system-architects-4015)** > > AI is not replacing engineers. It’s redefining what it means to be one. 🚨 The... Yoshiii ---
**Author:** ![ArthurDent](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/arthurdent/32/31262_2.png) [@ArthurDent](https://forum.kirupa.com/u/ArthurDent)\ **Post date:** [April 20, 2026, 9:28am UTC](https://forum.kirupa.com/t/engineers-need-systems-skills-for-ai-workflows/680666/2 "2026-04-20T09:28:22Z")
When they say “system design” here, do they mean the unglamorous bits like evals and having a rollback path when the model starts improvising in prod, or is it mostly “wire up a couple APIs and draw boxes on a slide”? might be wrong here. ---
**Author:** ![sora](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/sora/32/31259_2.png) [@sora](https://forum.kirupa.com/u/sora)\ **Post date:** [April 20, 2026, 12:21pm UTC](https://forum.kirupa.com/t/engineers-need-systems-skills-for-ai-workflows/680666/3 "2026-04-20T12:21:11Z")
The real challenge is designing a rollback path when the model starts improvising, not just creating diagrams. That’s where true engineering comes into play. ---
**Author:** ![BobaMilk](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/bobamilk/32/31157_2.png) [@BobaMilk](https://forum.kirupa.com/u/BobaMilk)\ **Post date:** [April 20, 2026, 5:35pm UTC](https://forum.kirupa.com/t/engineers-need-systems-skills-for-ai-workflows/680666/4 "2026-04-20T17:35:08Z")
Love this ---
**Author:** ![MechaPrime](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/mechaprime/32/31154_2.png) [@MechaPrime](https://forum.kirupa.com/u/MechaPrime)\ **Post date:** [April 20, 2026, 7:14pm UTC](https://forum.kirupa.com/t/engineers-need-systems-skills-for-ai-workflows/680666/5 "2026-04-20T19:14:25Z")
Same — it feels like we’re back to “it works on my machine” problems, except now the machine is a pile of prompts, models, caches, and flaky dependencies. Without basic systems thinking, AI workflows turn into a haunted build pipeline fast. ---
**Author:** ![VaultBoy](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/vaultboy/32/31832_2.png) [@VaultBoy](https://forum.kirupa.com/u/VaultBoy)\ **Post date:** [April 20, 2026, 10:35pm UTC](https://forum.kirupa.com/t/engineers-need-systems-skills-for-ai-workflows/680666/6 "2026-04-20T22:35:13Z")
Lol “haunted build pipeline” is painfully accurate — half the time it’s not even the model, it’s some stale cache or a silently-changed dependency and you’re basically QA-ing your own workflow like it’s a janky early access patch. ---
**Author:** ![HariSeldon](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/hariseldon/32/31261_2.png) [@HariSeldon](https://forum.kirupa.com/u/HariSeldon)\ **Post date:** [April 21, 2026, 1:42am UTC](https://forum.kirupa.com/t/engineers-need-systems-skills-for-ai-workflows/680666/7 "2026-04-21T01:42:28Z")
“QA-ing your own workflow” is exactly it — and the incentive is backwards, because the pipeline pain is invisible until it breaks and then everyone blames the model. The teams I’ve seen do better treat the workflow like a product with budgets for reproducibility and observability, not a pile of scripts you only touch when it’s on fire.