Clojurians Log v2

It's worth to re-apply to the same companies, after 3+ months had passed. Everything changes, including your experience, CV and their demands - so you might get an answer this time. In fact, companies that complain about shortage of Clojure devs, specifically say that the 1st time you post about vacancies, there is a rush of CVs, you hire 1-3. Later, you need to hire again, but suddenly there's a lack of candidates. So, in this job market, have no pride. Apply and re-apply, even when ghosted.

Not everyone (myself included) use an applicant tracking system. Many hiring managers are just using email, LinkedIn, and Slack. It makes sense to apply and/or email them, ping them here, or on LinkedIn.

I sent an email to one recent remote-jobs poster and got no reply

I think people just want to pass time. They either do it by posing jobs and forgetting about it, or conduct interviews, and go to bed with a feel that they have done their job for today, and once again forgetting about it. Or both. Unless and until job posters maintain consistent communication with the applicants, offers proper closure, people are going to lose hope, and the community is going to face a loss. Just today I saw another post in #remote-jobs, and I am wondering if it would waste another month in my life.

If it helps at all it's worth pointing out that the Clojure community has many incredibly qualified applicants. All job postings are essentially a competition (on multiple dimensions other than raw technical competence). As in any competition, even if you are a great performer you can still lose by "fractions of a second", to make an analogy with sports. Sadly it doesn't help that both the economic downturn and the AI applications can make recruiters' life harder. In the meantime, keeping a positive attitude can only help - if it's not Clojure, other languages can also provide good job opportunities.

@mindaslab I don't think people are deliberately trying to upset candidates. There's just a lot of competition. And from what I know, in Clojure world there are almost always good candidates to choose from. It's tiring and unpleasant to write a rejection for everybody. Also, sometimes there are just honest mistakes - I had a case where my email was mistyped, and I didn't get the interview invite.

@shkertik I am not sure why people don't reply even when I ask: "Am I still in the race?". All one needs to do is to hit the reply button without changing my email. The last interview I was told that, their company respected devs, and they don't ghost anyone. I think statistics will help here. If we have a common place to record ghosters, applicants can check it before applying.

They wrote back. I'm not selected. But the time it took. But at least they did not ghost me forever. 🙂

yeah, that sucks, but as @darrell said, blessing in disguise.

I know that sometimes companies will wait on giving the “no” because their first pick might fall through and they might end up giving you the offer.

indeed. My condolences on being ghosted... And yes I agree that prompt feedback is best! Not just for you the candidate, but also for the company.

This offers little solace but, it’s probably a blessing in disguise. Any company that can’t have the professional decency to give you a clear answer may be a company you wouldn’t want to work for anyway. I’m sorry that happened to you, though.

Yep, unfortunately this becomes normal in the programming market