Skip to main content

On interview annoyances

There are a couple of pet peeves I've acquired while interviewing for a while, the first is about advice given to job seekers while the second is about tools used by recruiters. 

Many boards, influencers and head hunters recommend customizing CVs for each application and to do background checks on the prospect companies. This would be good if it wasn't really time consuming and the probability of landing the job was high. On current state of affairs a job seeker will be doing hundredths of applications, I've done this, to even get to a human is probably around 1 in every 50 applications, to pass to the second round it is 1 on every 20 most likely and then depending on role and organization there might be two or three rounds of interviews which means a very low probability per submission. Each tweak to CV or org review will take at minimum 20 minutes and probably longer if done thoroughly. So imagine that a candidate is doing the updates for 100 positions, which is a very low number from my own experience, it would mean an investment of 33 hours. That is almost a full week of non stop work, anybody would be left exhausted and burnt out not to mention that looking out for a job is inherently stressful. It is economics of scale, unless you know you are a really good fit you do this updates and checks; unfortunately this is only true if you are being referred or you have prior knowledge of the organization. For me it is simply not doable.

The other one has to do with applicant tracking software or ATS for short. These tools are designed to help only the hiring part, from the joob seeker it is a real nightmare.  I've seen simple ones that only ask for contact info and CV or ones that are already connected to linkedin or other work social networks, those are the best, but there are others that make me want to scream from the bottom of my lungs.

 The most painful are the ones that require to re create the cv within the tool itself, others that are SaaS but make you create yet another account that you’ll never use again unless you get to the human interview, or worse it is the same application but for a different organization hence yet another user/password to confuse yourself as the only difference is a subdomain that is very easy to miss or worse a different path.

Popular Posts

Logffillingitis

I'm not against of leaving a trace log of everything that happens on a project what I'm completely against is filling documents for the sake of filling documents. Some software houses that are on the CMMI trail insist that in order to keep or to re validate their current level they need all their artifacts in order but what is missing from that picture is that sometimes it becomes quite a time waster just filling a 5 page word document or an spreadsheet which is just not adequate for the task needed. Perhaps those artifacts cover required aspects at a high degree but they stop being usable after a while either by being hard to fill on a quick and easy manner by someone with required skills and knowledge or they completely miss the target audience of the artifact. Other possibility is that each artifact needs to be reworked every few days apart to get some kind of report or to get current project status and those tasks are currently done by a human instead of being automated.

Are we truly engineers? or just a bunch of hacks...

I've found some things that I simply refuse to work without. Public, Centralized requirements visible to all parties involved. I is ridiculous that we still don't have such repository of information available,  there is not a sane way to assign an identifier to the requirements. Then we go with the 'it is all on Microsoft Office documents' hell which are not kept up to date and which prompts my next entry. Version control. When we arrived here quite a lot of groups were working on windows shared folders... now it is a combination of tools but heck at least there is now version control. Controlled environments and infrastructure. Boy... did I tell you that we are using APIs and tools that are out of support? Continuous deployment. First time here, to assemble a deliverable artifact took 1-2 human days... when it should have been 20 minutes of machine time. And it took 1 week to install said artifact on a previously working environment. And some other things that

Qualifications on IT projects. Random thoughts

Projects exceed their estimates both in cost and time. Why? Bad estimation would be an initial thought. If you know your estimates will be off by a wide margin is it possible to minimize the range? Common practice dictates to get better estimates which means get the problem broken down to smaller measurable units, estimate each of them, aggregate results and add a magic number to the total estimate. What if instead of trying to get more accurate estimates we focused on getting more predictable work outcomes? What are the common causes of estimation failure: Difficult problem to solve / Too big problem to solve Problems in comunication Late detection of inconsistencies Underqualified staff Unknown. I'd wager that having underqualified staff is perhaps the most underestimated cause of projects going the way of the dodo. If a problem is too complicated why tackle it with 30 interns and just one senior developer? If it is not complicated but big enough why try to dumb it down a

Job interviews

So after my sabatic period I started to go to different job interviews (most of them thanks to my fellow colleages whom I can't thank enough) and after most of them I feel a little weird. Everyone tries to get the best people by every means possible but then somethin is quite not right. Maybe they ask wrong questions, ask for too much and are willing to give to little in return or just plain don't know what they want or what they need. Our field is filled with lots of buzzwords and it is obvious that some people manage to get jobs only by putting them on their résumé. Then there are some places where there is a bigger filter and filters out some of the boasters. But still it is a question of what do they really need and what questions are needed to weed out those that do not cover minimal aspects required by the job. Don't get me wrong, it is really hard to identify good developers on an interview. It seems that almost no one knows what to ask in order to get insights abo