Dynamic programming questions scare candidates because they seem to need a flash of insight. In practice, a steady four-step process gets you most of the way, and narrating it earns credit even if you run out of time.
"dp[i] is the minimum cost to reach step i." If you cannot say the state in one sentence, you are not ready to code. Interviewers often stop candidates here to check understanding.
Ask: what was the last decision? For climbing stairs it was one step or two, so dp[i] = min(dp[i-1], dp[i-2]) + cost[i]. For knapsack it was take or skip the item.
Fill the smallest subproblems first. Mention whether you go top-down with memoisation (often faster to write) or bottom-up (easier to optimise space).
Once the table is correct, point out that row i only depends on row i-1, so you can keep two rows. Offering this as a follow-up shows depth without risking a broken solution.
Record yourself explaining state, transition and base case for each pattern. If you want structured feedback, Linkjob offers AI mock coding interviews that comment on your explanation as well as your code.
Disclosure: I'm part of the Linkjob AI team.