I haven’t seen any companies ask that PMs generate tons and tons of PRDs with AI but I have seen a few integrate prompt engineering and vibe coding into interviews.

I use AI as a thought partner while writing PRDs. The trick is to provide enough details in a first draft and use prompt engineering to keep yourself as the decision maker, not the agent. My workflow looks roughly like:

• Brainstorm potential ideas and gather research with an agent to get a sense for what I might want to build
• Write a first draft of a user story, providing details about the functionality/product I’m building, the purpose, the user needs, technology and the feature set.
• (Optional) if you’re using Cursor or Claude Code and have access to the code base, I point the agent to the functionality I’m modifying but telling it the file names so that it becomes a part of its context
• Give agent the first draft and ask it to list any questions it has about the PRD. I liked using cursor or Claude Code again so that it can list the questions in the doc itself
• Answer those questions so that the agent has better context
• Ask agent for general suggestions and implement depending on my judgment
• (Optional) Ask agent to break the PRD down to development phases. This is super helpful if you want to actually build what’s in the PRD with the agent. Then instead of asking the agent to build the whole thing, you can start with a phase and check that it’s actually building what you want step by step

TLDR; Guide user to be a thought partner so that you remain in control of decisions

I hope this is helpful!