GenAI Architect
Design how a generative system is put together for a real operation: the model boundary, the tools it may call, the evaluation, and the point where a person stays in the loop.
The work
- Draw the boundary of the model: what it may read, which tools it may call, and what it must refuse.
- Decide where retrieval, rules, and a person sit, and write that so an engineer can build it.
- Set the evaluation before a release: the cases, the failure that matters, and the number that has to hold.
- Stay through the first production use, and change the design when the workflow disagrees with the diagram.
You will fit if
- You have shipped a generative system that called real tools, not only a chat window.
- You can explain a permission, an audit record, and a model limit to someone who does not write prompts.
- You are comfortable in Python or TypeScript, and you have worked with at least one model API and a retrieval store.
- You would rather delete a capability than ship one you cannot evaluate.