TL;DR: Company ghosted on me far into the interview process. They don't respect candidates' time and effort. After submitting my resume, Jarrod Simpson, operations manager, contacted me via e-mail. We had 30 minute phone call which was focused on soft skills. I was then invited to speak with the software lead, Bryce Blanton. We had a 1 hour phone call which covered a mixture of soft skills and technical skills. I received an invitation to participate in a coding challenge which involved creating a simple Twitter clone. Bryce and Jarrod understood my level of experience and that I had never worked with PHP or the microframework they recommended using, but asked I try it anyway. I spent a weekend diving into the challenge and produced a fully functioning app that met the user story requirements, complete with bootstrap styling. About a week after submitting the app, I received a boilerplate rejection email (the sort of email you would expect upon initial review of your resume, not further down the interview process). It was completely inappropriate for the amount of time I spent speaking with individuals at Koddi and developing a successful coding challenge. A follow-up email requesting feedback or suggestions for improvement went unanswered. The silver lining is that I am not working at a company that has so little value of its potential and current employees' time. Thanks for sparing me the heartache Koddi! I have some suggestions for Koddi if you're looking to turn the corner: 1. Provide personalized feedback in all cases, no matter how far a candidate went in the interview process or what position they applied for. Explain to candidates what is and isn't a good fit, and give feedback on how they can improve for future interviews. 2. Be very careful handing out coding challenges. You're asking someone to dedicate a lot of time and energy to a project. If you don't want someone with little experience, don't hand them a coding challenge just to see how they'll do. Spend the time upfront to determine if they have the skills/knowledge/experience you're searching for before presenting a coding challenge. 3. Answer all communications. Don't ignore anything or let something slip through the cracks. And a suggestion for developers: 1. Be very careful accepting coding challenges. Make sure a company isn't being lazy and handing them out to everyone before doing their homework. They need to put in some effort upfront to determine if it's in everyone's best interest to proceed with a challenge.