Skip to main content

Developer interviews out of step with reality

Disclaimer 

I am in the process of trying to get back into the workforce, after taking a few months out to be more available for family while dealing with a medical situation.

After some time away from coding my muscle memory for solving little software problems is a bit slower than normal, so I fear that I may not be coming across as being a relatively intelligent and capable professional software developer with over two decades of industry experience.

I'm feeling a bit glum, as shortly after each interview I established some aspect that I had not covered off with my implementation - which can be a showstopper for progressing to the next round of the interview process.

The coding interview process is out-dated

Disable default editor functionality

I have attended a couple of online coding interviews in the last couple of weeks, and found myself having to disable some of the default features in my integrated development environment to enable myself to show my own capabilities separated from the auto-completion suggestions.

On the positive side, at least by coding in my own editor I was able to choose some familiar and relatively up to date test libraries as dependencies - unlike an in browser development environment for another interview, where I found myself stuck with JUnit 4 that has been "in maintenance" for about half a decade.

Meanwhile, in the real world

Day to day software development within the types of company that I am interested in joining now generally involves making the most of the suggestions offered up by editing tools. Additionally, there is an increasingly common expectation that developers will lean on AI systems where their employer has paid for a subscription to have access to those coding assistants.

Turn on AI and let her rip?

No. I don't have a solution to offer, as I still believe that the assessment is meant to be of the developer's capability.

My underlying gripe is quite tangential to this particular aspect of the state of the approach to coding interviews. From having been on both sides of the current interview process, I am of the opinion that there is too much time pressure on candidates and interviewers to squeeze in a coding. implementation and try to gain a realistic impression of the candidate's ability to do the job.

Labels:

Comments

Post a Comment

Popular posts from this blog

2022 - A year in review

Just a look back over the last 12 months. January I moved back to Christchurch to live, after having spent a few months further south since moving back from London. Work was mainly around balancing other peoples' understanding and expectations around our use of Kafka. February I decided that it would be worthwhile to have a year's subscription for streaming Sky Sports, as some rugby matches that I would want to watch would be on at time when venues wouldn't be open. Having moved to Christchurch to be close to an office, now found myself working from home as Covid restrictions came back into effect across New Zealand. March Got back into some actual coding at work - as opposed to mainly reviewing pull requests for configuration changes for Kafka topics.  This became urgent, as the command line interface tool that our provisioning system was dependent on had been marked for deprecation. April   Had my first direct experience with Covid-19.  I only went for a test because ...
Post a Comment
Read more

Speeding up Software Builds for Continuous Integration

Downloading the Internet Can you remember the last time you started out on a clean development environment and ran the build of some software using Maven or Gradle for dependency management? It takes ages to download all of the necessary third party libraries from one or more remote repositories, leading to expressions like, "Just waiting for Maven to download the Internet". Once your development environment has been used for building a few projects the range of dependencies that will need to be downloaded for other builds reduces down as the previously referenced ones will now be cached and found locally on your computer's hard drive. What happens on the Continuous Integration environment? Now consider what goes on when Jenkins or your other preferred Continuous Integration server comes to build your software. If it doesn't have a local copy of the libraries that have been referenced then it is going to pay the cost of that slow " download the Internet" p...
3 comments
Read more

Designing systems - The "ity"s That Limit or Enable Profitability

Introduction This started off as a little aide-mémoire to get my head into the right space for preparing for an interview. It's not an exhaustive list, and twists terminology that has been used to represent other things (see:  to Velocity), so don't treat it as a text book reference to work from. Most of the listed points can be associated back to so called "non-functional requirements" - NFRs. I don't like that particular terminology, so alternatively we might consider them as dimensions of the quality of the sytem. Usability "If you build it, they will come" should come with a provisor, "... but if it's awkward to use they'll soon go away, and might not come back." Security All of the aspects that combine to protect data from being seen or manipulated by anyone other than the intended recipient or sender, and also assuring users that the data has originated from the intended source. Velocity Here I'm cheating a bit by trying t...
Post a Comment
Read more