"I'm starting to feel that perhaps the python/django market is overly flooded at the moment?"
Maybe it's just not as big as you think it is? I've heard for years about Django being some hotness, but I actually rarely come across it in the wild. I also don't see a lot of general purpose Python use - it's typically being used for a niche purpose - scientific number crunching, etc.
I just quit a relatively convenient and well paid job as a Java webapp backend consultant, just couldn't do it anymore.
The thing is, there are PLENTY of jobs right now, but most of them are so dumbed down and meaningless that any ignorant fool can perform them, and ignorant fools are cheap to hire and easy to take advantage of.
My current strategy is aiming further down the stack, closer to the hardware, embedded stuff; which hopefully means less ignorant fools to deal with and more interesting problems to solve.
> I'm starting to feel that perhaps the python/django market is overly flooded at the moment
Python is a super popular language for newbies and people converting from less currently in demand languages, and Django is the dominant web framework, so there's probably lots of moderately skilled people with low (for development) salary demands available for Python/Django jobs.
> I have noticed a high percentage of jobs seem to want you to have a bunch of AWS experience. I've messed around with EC2 instances but that is about it.
Yeah, I am guessing a lot want CloudFront/API Gateway/Lambda experience and others. You seem to be looking for a Sr. position where you need either real deep expertise in a component of the stack, or coverage of the whole stack (or a large subset) in use and a good story about ability to pick up the rest and guide architecture and implementation approach choices or somewhat less tech skill and deep experience of the problem domain. If you are going out of the area where you have that depth (Perl on the tech side, ERP on the domain side), you may have to temporarily aim lower until you can build the necessary breadth or domain/tech-specific depth.
That is strange, I have maybe written 10 applications in my whole life (embedded development, µC in C mainly).
I did a "sabbatical" for a year shorty after my first job and then switched to another company. So I guess I was unemployed for more than 6 month technically.
I guess it depends on locality a lot, I mostly wrote applications on my own initiative and didn't use channels like LinkedIn aside from researching contacts.
I wouldn't focus on what stacks you use, just tell them which problems you solve with it. Larger companies have non-tech people in HR and they might think you to be a freak or snake charmer if you mention Python.
Consider taking the initiative on applications and maybe target companies that don't primarily develop software (those offer far better condition in my experience. Maybe not money-wise, but overall).
Some companies are vulnerable to buzz words. If you know Python you could venture into ML. Has high value now, but I think companies might not be too healthy if they focus too much on buzz.
>60 interviews
60 interviews with no offers is a big issue. I know you're looking for reasons but maybe your skill level in Python is not where you think it is and overall you're not aligned with the general market of what a Sr. engineer. skill level should be.
I think you are facing problems that many other senior candidates are facing in this job market. The number of candidates on the market is at a high, and companies are being extremely picky about who they want to hire. Add to this the fact that expectations of senior candidates have risen, sometimes unrealistically high.
Perl is a dinosaur, and will not get you as many job opportunities as something more recent. But the programming language is hardly the stumbling block. Most shops know that experienced people pick up languages, frameworks etc. easily.
Here are some suggestions: - Building/operating software on AWS is really becoming a basic skill most people are expected to have nowadays. You could get an AWS certification that shows you are serious about building skills in the area.
- Apply to jobs on LinkedIn. You will get a better selection of jobs that are tailored to your needs, and I have found that recruiters respond to LinkedIn applicants a bit more.
- Consider a job with a nonprofit org, such as a university. These places have more legacy software, and are also unable to compete with the open market. You will face a reduction in pay perhaps, but you can get back into a job, where you will have a stronger negotiating position.
- Not having a job somehow makes you less attractive to recruiters and hiring managers. It's bizarre, but go figure. If you interview with the goal of getting hired anywhere and get yourself into a job, you will strengthen your hand considerably.
- Try not to reveal that you are unemployed when you initiate a conversation with a firm.