Seeing them before candidates do
Questions are generated when you prepare a stage, not improvised during an interview, so you can read every one before it is used. For a stage you will run fifty times this is twenty minutes well spent.
Editing
Any question can be edited in place, replaced with a different generated one, or removed. Removing one changes the stage's coverage, and you are told when a removal leaves a skill with too few questions to assess it properly.
Regenerating
Regenerating replaces a question with a new one for the same skill at the same level. Use it when a question is technically fine but not what you would ask — that is a judgement only you can make.
A regenerated question is generated with the position's subject in mind, so a "Debugging" question for a Python role stays about Python rather than drifting to whatever debugging most commonly means.
Building a bank
Questions you approve can be saved to your organisation's bank and reused on other positions. A bank is the natural home for the things specific to how you work — your domain, your architecture, your customers — which generation cannot know about.
Difficulty
Each question carries a difficulty, and a stage carries a mix. The mix matters more than any single question: an interview of only hard questions discriminates poorly, because almost everyone fails them and the ranking comes down to noise.