← 回到文章列表Back to writing

,閱讀約 4 分鐘, 5 min read

從前後端到光譜:為混亂的AI人才市場,繪製一張清晰的地圖

AI時代來臨,但市場上對於職位的定義似乎是一片迷霧。A公司的「機器學習工程師」,做的是B公司的「AI工程師」的工作,而C公司的「資料科學家」,可能根本不碰模型。我們缺乏一套共同的語言,來描述AI時代下的不同專業職能,這讓企業招聘困難,也讓人才定位模糊。

本文的目的,並非要創造更多新名詞,而是試圖提供一個清晰的分析框架,幫助個人和企業,更好地理解和定位在AI浪潮中的價值。需要特別說明的是,這套分類並非業界標準,而是基於觀察與經驗的歸納,旨在幫助讀者快速找到自身與團隊的位置。

一個熟悉的比喻:用「前後端」理解AI職能

為了簡化這個複雜的問題,我們可以借用軟體開發中最經典的模型 — — 前後端分離 — — 來做一個類比。

這個簡單的二分法,幫助我們做出了第一次關鍵的區分,讓我們看到AI領域存在兩種截然不同的價值創造路徑。

模型的極限:當「前後端」的界線開始模糊

然而,這個簡潔的模型在面對真實世界的複雜任務時,便會暴露出它的局限性。例如,一個關鍵的、高價值的工作 — — 模型微調 (Fine-tuning) — — 究竟該屬於前端還是後端?

Fine-tuning 在光譜上的位置相對特殊,它既涉及模型參數調整,又需考量實際應用場景,因此在我看來,它是「模型端」與「系統端」之間的關鍵橋樑角色。

更精準的地圖:「AI職能光譜」模型

一個更準確的視角,是將AI職能視為一個連續的光譜。它清晰地描繪了從純粹的科學研究,到最終的商業應用,中間每一步的價值創造過程。為了讓這些角色在同一個脈絡下被比較,我將它們放在一條從「模型研究」到「系統實現」的光譜上。

AI 職能光譜表:從模型研究到系統實現,依序比較研究科學家、應用科學家、資料/機器學習科學家、機器學習工程師、AI 系統架構師、AI 工程師、AI 顧問/解決方案架構師的光譜位置、核心任務、價值衡量與 Tech Stack。
AI職能光譜

這個更精細的光譜,清晰地劃分了「應用科學家」和「資料科學家」的區別:前者是探索未知可能性的先鋒,後者則是利用成熟技術為企業創造穩定價值的工匠大師。

更重要的是,它解壓縮了從「模型」到「產品」之間,那個最關鍵的工程地帶。它不再是一個模糊的「中心點」,而是一個由三個關鍵角色組成的「工程三部曲」:

  1. 機器學習工程師(MLE) 將模型變成穩定、可被呼叫的服務。
  2. AI系統架構師(AI Systems Architect) 將這些服務與其他系統組件,設計成一張宏大的應用藍圖。
  3. AI工程師(AI Engineer) 根據這張藍圖,實現最終的產品功能。

一份典型的AI系統架構師的思維產出,並非只是一份技術規格文件,而更像是一份完整的商業與技術作戰藍圖。例如,它會清晰地定義出一個分階段的導入策略:

給後端工程師的福音:「90/10法則」

這個光譜模型,特別是從中心點到右端的職能,對廣大的Web後端工程師來說是個好消息。因為一個生產級AI應用,「90%是我們熟悉的後端工程」。

重疊的90%技能包括:

關鍵的10%差異則在於:

後端工程師距離成為市場最渴求的AI人才,只差那最後10%的關鍵認知。

結論:在這張新地圖上,找到你的位置

AI時代的職涯路徑,不再是單一的階梯。我們都需要成為一個懂得在地圖上定位、並規劃自己前進路線的「戰略家」。

在AI這個全新的大陸上,我們需要的,不僅是勇敢的探險家,更是能繪製地圖、指引方向的領航員。無論你身處光譜的哪一端,清楚自身定位並理解其他角色的價值,才是應對這個快速演化市場的長久之道。

From Frontend/Backend to a Spectrum: Drawing a Clear Map for the Chaotic AI Talent Market

The age of AI has arrived, but the job market seems to be lost in a fog. The “Machine Learning Engineer” at Company A does the work of the “AI Engineer” at Company B, while the “Data Scientist” at Company C might not touch models at all. We lack a common language to describe the different professional functions in the age of AI, making it difficult for companies to hire and for talent to position themselves.

The purpose of this article is not to invent more new titles, but to provide a clear analytical framework to help individuals and companies better understand and define their value in the AI wave. It is important to note that this classification is not an industry standard, but rather a summary based on observation and experience, aimed at helping readers quickly find their own position and that of their team.

A Familiar Analogy: Understanding AI Roles Through “Frontend” and “Backend”

To simplify this complex issue, we can borrow the most classic model from software development — the frontend/backend separation — to make an analogy.

This simple dichotomy helps us make the first crucial distinction, allowing us to see two vastly different value-creation paths in the AI domain.

The Model’s Limits: When the Frontend/Backend Line Blurs

However, this concise model reveals its limitations when faced with the complex tasks of the real world. For example, a critical, high-value job — model fine-tuning — where does it belong?

Fine-tuning holds a unique position on the spectrum. As it involves both adjusting model parameters and considering practical application scenarios, I see it as a key bridge role between the “model side” and the “system side.”

A More Precise Map: The “AI Job Spectrum” Model

A more accurate perspective is to view AI functions as a continuous spectrum. It clearly delineates the value-creation process at every step, from pure scientific research to the final business application. To compare these roles within the same context, I will place them on a spectrum that runs from “model research” to “system implementation.”

AI job spectrum table: from model research to system implementation, comparing Research Scientist, Applied Scientist, Data/ML Scientist, Machine Learning Engineer, AI Systems Architect, AI Engineer and AI Consultant/SA by spectrum position, core task, value measured and tech stack.
AI Job Spectrum

This more granular spectrum clearly delineates the difference between an “Applied Scientist” and a “Data Scientist”: the former is a pioneer exploring unknown possibilities, while the latter is a master craftsman who uses mature technologies to create stable value for businesses.

More importantly, it unpacks the most critical engineering zone between “model” and “product.” It is no longer a vague “center,” but an “engineering trilogy” composed of three key roles:

A typical output from an AI Systems Architect is not just a technical specification document, but a complete business and technical battle plan. For example, it would clearly define a phased implementation strategy:

Good News for Backend Engineers: The “90/10 Rule”

This spectrum model, especially the functions from the center to the right, is good news for the vast community of web backend engineers. Because for a production-grade AI application, “90% is the backend engineering we are already familiar with.”

The overlapping 90% of skills include:

The critical 10% difference lies in:

Backend engineers are only that final 10% of key knowledge away from becoming the most sought-after AI talent in the market.

Conclusion: Finding Your Place on This New Map

In the age of AI, career paths are no longer single ladders. We all need to become “strategists” who know how to find our position on the map and plan our path forward.

On this new continent of AI, we need not only brave explorers but also navigators who can draw the maps and guide the way. No matter where you are on the spectrum, clearly understanding your own position and the value of other roles is the sustainable way to navigate this rapidly evolving market.

Knas 的文章。想聊聊的話:Written by Knas. To get in touch: Email GitHub LinkedIn