A number of clients we are working with at the moment have introduced a technical case study into the recruitment experience. Some as a first stage, others as a final stage (followed by a technical interview to discuss the case).
The case studies are generally designed to test technical Transfer Pricing knowledge required as a bare minimum for the job grade being applied for, as would be faced on a daily basis in the job. It often represents a "live" scenario being worked on by the team.
However, as the roles become more senior, there is an element of constructing draft client advice and an element of "sales" or opening up opportunities.
I have to say, feedback across the board has been fairly mixed.
From "overselling" to being too long winded, to not being detailed enough, it's becoming a bit like Goldilocks and the Three Bears (and you should be aiming for "just right"!)
Here are my simple rules for attaching case study sections of any interview experience you might find yourself involved in.
Remember the audience: This might seem plainly obvious but put yourself in the shoes of the recipient of your draft advice email. A CFO doesn't need the OECD Guidelines listed in detail but you are likely to get away with a bit more technical language with a Head of Tax or TP.
KISS: Keep it Simple, Stupid! None of us like long emails or letters. Get to the point and prioritise risk areas that need further information or exploration. It's not a proposal or engagement letter.
Call to Action: Suggest a call or meeting to discuss options based on the levels of risk and agree priorities. This is what you would do with your clients, so why treat your response like a theoretical exam question. Only once you've had this type of discussion can you begin to explore what a potential project or scope of works could look like.
Good luck to anyone out there interviewing at the moment!