From what I have learned from hiring others to join high profile and high performance teams these coding tests are very valuable and helps the team get a good l

From what I have learned from hiring others to join high profile and high performance teams these coding tests are very valuable and helps the team get a good look at what you do rather than what you say. A good benefit to this is, that it fairly helps include all personality types (quiet, outgoing, shy, etc.) and focuses on if they can perform an actual development project from theory, design, and finally to production. Once we started adding tests to our interview process the quality of people on our team and time to adjust dropped dramatically along with a decrease in the time between a hire and the individual leaving the company. Normally they only left if they were moving to another location or had a big family change. The task at hand is very simple, and helps weed out those that copy and paste everything along with those with an engineering title that have not actually been doing development for as along as their resume says they have. For those with actual experience developing projects, launching to production and maintaining them on a regular basis have a large capability to shine for these types of easy entry tests. I am guessing you are applying for a Senior or Principal level .NET Web Developer role? If so this test, tests your knowledge of taking customer requirements and turning them into a working prototype for review. It also tests your database and web development skills with C#, MSSQL and many of the various methods of developing web apps using standard web technology. The big test will be the way the final product is packaged up along with it's unit tests. If done correctly it proves you know how to conduct good deployments to production and actually tested your work instead of just copying the code to the server without packaging it up the .NET way. You are basically being asked to use the regular full cycle of developing and deploying a .NET web application. Many web developers do not know how to do this and just copy their code to a web server without packaging, changing the release types, unit tests, etc. I would recommend using this as a good way to actually set yourself above other candidates that want the job by going through the entire SDLC with a high quality MVP. When you get to the good jobs (higher quality engineering standards in place) normally the interview process is longer than your first job back when you first started as they just needed programmers not people that could conduct all parts of the SDLC and maintain large applications. Sounds like they want you to be able to do the latter and not just a small piece of applications. For my opinion on what to do, I always recommend doing these code challenges, as they are normally a pretty good mental engineering stimulant and honestly they have all been pretty easy and did not take 4 hours to complete unless I was trying to add extra shine awww to it. Normal outcome was a call back a few hours after they reviewed it with a really nice job offer wondering when the earliest I could start with a signing bonus to seal the deal.