That is another thing: have personal equipment. If you don't have a non-employer-owned computer where you can nearly-instantly spin up a new project in your pr

That is another thing: have personal equipment. If you don't have a non-employer-owned computer where you can nearly-instantly spin up a new project in your preferred language with unit testing in place, it is going to make any take-homes you encounter harder. Make sure all your personal content isn't on the work computer, and if you want to keep your collection of reaction gifs have those on a hard drive you own. Similarly, make sure you are connected with any coworkers you may want to stay in touch with, whether that's on LinkedIn or exchanging phone numbers. And finally, if there are any useful generalizable utilities you've written for your current job, consider taking those through whatever your company's process is to open source them. Not only are those great things to have in a portfolio & passive networking with anyone who uses them, it means you won't have to write a similar tool from scratch and slightly differently at the next place. Just make sure they are something you would want potential employers looking at: legible code, automated tests, useful documentation, etc, and that your company's lawyers sign off before you expose any of the code.