I just failed my dream job

There is no ideal solution. I don’t mind the 30 minute multiple choice basic competency tests (much), but they are usually just theoretical enough and outside the scope of the “muscles” I exercise daily, that I tend to return mediocre “acceptable” scores that, taken without nuance or used in actually ranking me with others, doesn’t accurately measure my real-world abilities relative to anyone else or to any sort of standard. Beyond a certain point one intuits the path forward, whether it comes from raw experience or practical application of “book learning”. Unless you have done a lot of teaching or blogging on a topic, it’s probably hard for a lot of perfectly excellent developers to break down and explain their process than to write and demonstrate working code and survive a code review.

If a company is sincerely interested in me as a finalist I don’t mind spending an hour or so meeting the team and, in a small company, executive leadership so that my potential colleagues have some input into the process and so that leadership is comfortable that I am a “team player” by their particular definition.

Beyond that though I find it a waste of my time if they aren’t sure what they want or are looking for post-hoc rationalizations for decisions I can tell they’ve already come to.

In a hypothetical situation where I found myself without current employment I could get by fine for months without an income (indeed at this point I’d file early social security), but paradoxically I would also have a lot more time and energy for the interview process and might put up with more nonsense to get at least a bridge position to conserve my resources. However I’d also have the option to invest that life force in a deep-dive into an area of interest or participation in an open source project or something. Guess which i think would be more helpful to me in the long run?

As to the question of years of service counting for something, I think that it actually counts for a great deal. It could conceal that I can’t program my way out of a paper bag, but if I have had interesting assignments and good references and am clearly not an asshole it is far more likely that I have some super valuable mature skills to add to any team. At this point in my career, asking me to dance for my dinner like a trained seal is leading with disrespect that I will not abide, sorry.

There’s also the whole question of education. If I had gotten a CS degree I’d have gotten my BS in about 1979 and it probably would have involved keypunching and COBOL and other things of absolutely no relevance today. As it was, I was an autodidact at a time of low-hanging fruit and was too busy making money to get a degree.

Thankfully, this is ONE area where the industry is generally in good shape. Job listings generally say, “BS or equivalent work experience” and I daresay that unless i were in my 20s or perhaps 30s no one would even inquire about my degree or grades because there’s a general understanding that things are moving so fast that you’re no good if you aren’t constantly learning anyway. In 38 years I have been asked exactly twice by a client or employer where I matriculated and by then the answer (“nowhere”) was even more impressive because I had already done months of excellent work for them. It’s not quite the same as my early days when the general ethos was “if you’re not as terrified of computers as me you must be a genius, here is a wheelbarrow full of money, please write software for me.” But it is quite reasonable.

3 Likes

I think it’s worth it to try and sharpen these skills even if you have no plans to teach or write a blog.

It feels like diminishing returns hit you pretty hard once you get to a certain technical skill level. There’s always something new to learn but if this were a video game and you have 16 out of 20 in tech skills but 10 out of 20 in communication skills, you’ll probably end up in a much better spot (more job position options, better pay, more flexibility, more interesting opportunities coming your way, etc.) by bumping up your communication skills to 15 from 10 vs taking your tech skills to a 17.

3 Likes

^^^ This, a thousand times this! Soft skills, particularly communication skills – especially writing – is a HUGE differentiator.

Actually, blogging or teaching is one of the best ways to learn. I think it was Gerald Weinberg who said, “when I want to master a subject, I always arrange to teach it to others”.

3 Likes

A very interesting and educative topic!

I will share some of my personal experience as someone who has only about 5 years of experience.

I started my career in a small company from Moldova. The interview process was just a 15 minute talk, where mostly the owner would tell me about his ideas of a new project that I would participate in developing, after that he accepted to hire me with the salary I wanted. I asked him later why he would not make a proper technical interview, he responded that the interview would not show anything he needed, for him it was easier to ask one of the teachers from university for feedback.

It was one of the most interesting experience from my career. That project idea he had, I was assigned to lead and make it happen, it taught me a lot of hard lessons and mistakes that I think even people working tens of years could not anticipate. After working for about 3 years I had quite an impressive technological stack and development experience with very limited resources, however my soft skills did not improve that much, because we worked with a small team.

A while later sadly the company almost went under because one of the clients bailed out on a project where we used elixir, it’s the same thing mentioned on this thread about the fear of client that he will not be able to find new developers who will maintain the elixir solution if we were to quit.

After that the lack of soft skills bit me very hard, after about 3 months of interviews for an elixir position, I had to give up and ended up being hired at a small company in my country to work in golang. The sad thing is that the interview process was easy because I was recommended by a former colleague, however the mentor I was assigned was just pressuring me constantly, even though I made it clear before that I had no production experience in golang.

Almost a month passed and I received an elixir offer at a startup and I accepted it because I couldn’t take being watched every hour by the mentor. Sadly that job would not last, once again because of my bad soft skills. The CEO came from VS ecosystem, having worked in slow moving industries, had no prior experience with either elixir or CI/CD practices. I was tasked to design and build their backend in elixir. It was all going smoothly until he was insisting on using some questionable practices, that I would start to argue and give him arguments on why it was wrong, and the mistake I did was to not let go and let him see the result for himself. I made an enemy out of him, so I had to leave the company shortly after.

Now the biggest thing that bite me in the ass was the period after that, I had a very rich resume for my years of experience and I thought that would help me land a job easier, that was not the case.

In my country recruiters get intimidated if they see more than 2 technologies in resume, especially when they see elixir, that they and their engineers never heard about. After a lot of painful interviews and tasks, I was able to realize that the resume should be more or less tailored to the position they require, because I would always fail at the interview with the recruiter or never get contacted, because they needed someone with X years of experience in their stack, most of them don’t care about other things. The other realization I made was that soft skills are much more important, as the technical interview is mediocre usually (at least for positions I applied for).

Now after about 6 months without a job, I was hired, however I will either focus more on soft skills from this point on or try to move slowly to a different industry.

7 Likes