Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
vintprox4803353dDamn, these pesky brats with their demands - remember, they are the ones that *are* in the bin. Let those who are in need of competent AI specialist find you. Do you perhaps have website or GitHub profile?
Demolishun22110353dI have n years experience in these technologies (list). You are asking for x technology proficiency. It will take me n days to get up to speed. Much of my n years of experience will transfer as the concepts are the same. Are you willing to have me learn x technology on the job?
WalkingBed60352dIn my personal experience, you have to customize your CV (somewhat..) for each job opening to match with what they require and what you feel you know or what you can get a working knowledge in a matter of weeks.
Changing your stack is also quite a challenge and will need long hours of self-learning and practicing, but since you already have the logical thinking and algorithms etc, it wouldn’t take you long to earn new skills. Try new languages and see which clicks with you most and start digging deep into the stack related to that.
In both these cases, don’t ever give up and keep on trying until you feel like you have found what suits you.
MM831198352dIf I had a quid for every CV I’ve seen with a skill that the engineer figured they could blag enough knowledge of in an interview then learn on the job, I’d have:
£(most of the times I’ve ever been sent one) + (every time I’ve sent off my own).
Also, remember that 90% of recruiters are fuckwits who get a dopamine hit every time they write a technical term they don’t understand, a lot of job specs bear very little relation to what you’ll be doing daily. If I also had a quid for every irrelevant competency I’d seen under a job spec I’d be a thousandaire. You’re not alone.
I’d suggest making a small personal site, use a template so it doesn’t look like coder-design, link to a handful of varied projects and write a post about each (seriously, writing about code is fun, can demonstrate your knowledge and general aptitude more readily than asking someone to look through a codebase too). An engineer will see the talent there, if you have it.