In my cases there were 2 practical stages. The first one was to fix some issues in a real project like you would do in a real scenario, interacting with Slack, GitHub comments etc The second one was more of a planning and high level architecture for a feature

Approached by an internal recruiter about interest generally in a position, without specifics. Had a chat, which went well and felt we had a good rapport. Assigned a code test, accessible via a cloud environment and provided access to a Slack channel to talk things over with the recruiters. Although this wasn't hard, there was a lot of small granular tasks to complete which took longer than expected, due to full time employment. Completed all requested challenges - wrote out my thought process for each approach, however was not successful. Feedback was prompt, however in my opinion some of the points raised felt quite subjective and would easily be rectified with discussion - as in a work environment. One of the points raised was that a specific submitted file on PR had formatted differently to their standards, meaning it was hard to spot the changes. This is valid, however I think it's reasonable given the circumstances when not provided the expected formatting standards / configs. It did feel like there was some hidden rules / hoops to jump through that weren't explained all that clearly.