I don't know about 'constantly' but I think once you're 8-10 months into a gig it doesn't hurt. For one, it gives you some real data about your market value in case you want to negotiate at the end of the year for a raise/bonus and second, it's just good to keep these skills in practice just in case of a layoff or you want something better. A bit time consuming but I've found it useful.
Interesting to reflect on how this plays out in the tech world. I know a lot of people who work in tech and outside, and my impression is that the interview process outside tech (and specifically data science or software engineering roles) involves more discussion and networking, whereas in tech (for tech roles), it shifts very rapidly to exam taking. For instance, a fundraiser might talk a bit about her experience as a fundraiser, whereas a programmer is likely to talk about how to find the shortest path in a graph using python, or the difference between logistic regression and a one-layer neural net. By "talk", I mean implement at a white board, preferably in julrythonava++script, but tight pseudo code is fine too.<p>There are such things as more casual job hunting in tech (giving presentations and having discussions can be great), but this sounds to me like living in a perpetual mid-term week during second year of a computer science curriculum. Which maybe is a good thing, at least you wouldn't ever forget how to implement merge sort or how to find all subsets of a superset of words that combine to make a different word that is also in the set.
> For decades, the prevailing narrative has been to stay in a role for as long as possible, build résumé clout and make a lasting contribution to an organisation.<p>I don't know in which world BBC lives.