What if you interview in the middle of a important project?

When you do a behavioral interview in the middle of a project you're owning or mentoring someone through, there isn't realized impact but small nuggets that give confidence that it could land. This is assuming full impact of the work takes months to accumulate in practice.

This leads to Results from STAR feeling like it will almost get there, but it won't quite land the same as getting it done before the interview date.

Take this example: I give a junior (and the rest of my team for that matter) scripts to abstract away common daily debugging and maintenance. I showed this junior engineer how to problem solve (what questions to ask themself: how to check kafka lag to debug performance bottlenecks). He works on a complex project and asks me for nuanced help now instead of basic questions. But he is 3/4 of the way there to get it to production.

Am I in a disadvantage of sharing stories like this where the actions in a vacuum seem reasonable and high signal, but aren't backed by a result now, but 3 months later?

My guess is just show projected impact and intermediate impact in R section of results.