4 ms·

not trying to be a dick, but after seven years you must have some friends or former colleagues that work at other companies, right? if so, why are you applying

not trying to be a dick, but after seven years you must have some friends or former colleagues that work at other companies, right? if so, why are you applying through the jobs page instead of having them refer you internally? fwiw, I did take a look at your linkedin page. imo, you are listing way too many skills, languages, and tools. I don't doubt that you worked with all of those things. but when you list so many, it raises doubt about which ones you're truly proficient with.

wegfawefgawefg 3y ago
I have only worked for small companies. When you work for small companies you have to wear hats. When I worked at skylark I had to write cli tools to interact with their SoC in c and bash, but also do hardware test in python, but also make a yield assessment website (js/python/orm shit). At Cratus i wrote a microservices backend docker yaml gui with a react frontend with a team of ten-ish turkish guys, but also worked with their electrical engineer on some embedded flashing webserver, a fluidflow calculator, and some ml camera tech involving nvidia jetsons for a taiwanese company, and a bottle manufacturing company for flaw detection. I was tasked with reverse engineering some chinese blue tooth beacons, and implementing a multilateration algorithm. I personally went to the Olympus endoscope repair facility, interviewed the staff, mapped the facility, and wrote a simulator for it. I have taken the few jobs I have been able to get. I learn what is professionally required. It might sound crazy but this is genuinely what i worked on. Atleast I can say it has not been boring!
- leetcrew 3y ago
  I've worked at small companies too, I get it. the charitable read of your linkedin page is that you're a engineer with a broad skillset who can be dropped into any kind of project and get it done. the uncharitable read is that you haven't spent enough time with any specific tool/language/domain to truly master it. you're not appealing to recruiters who are looking for X+ years of specific skill, and you're not telling your story the right way for recruiters that are looking for a generalist. if I were you, I would actually remove most of the individual projects from each job. keep 2-3 examples of what you consider your most impressive work and sell the reader on why it was impressive. key points to hit are a) why was the project important b) how did you solve the problem, and c) what was the impact to the business. by the way, b) should not just be a description of the tech stack you used. if you're looking at senior roles, people/organizational problems are more interesting to the reader.
  - wegfawefgawefg 3y ago
    That is reasonable advice. Thank you. I had it reduced to all back end development for a few months. I got no responses. To be honest I've given up on it.
wegfawefgawefg 3y ago
As for my friend developers. One works at apple, one works at amazon, those are unlikely hires for me. One got laid off this year and now is getting certified to drive a city bus. A few of them work for the BP subcontractor, which is currently not hiring, layoffs. My other friend just got a new job, he was unemployed for about six months this year. My other friend has a degree and years of experience but is unemployed. I have one friend in bed with C# and medical industry. Have asked him about it. Lets say the average person has 10 professional acquaintances, id wager many of them are simply not in a position to make a referal.
- leetcrew 3y ago
  that's too bad. friends that can directly vouch for your skills are the easiest way into a job. still, don't forget a lot of companies give a bonus for any referral that results in a hire. unless you've specifically pissed them off, I bet most people who even vaguely recall that you've worked together would be willing to refer you. I got my current job through a second-degree connection. I didn't even know the guy that referred me.

wegfawefgawefg 3y ago

I have only worked for small companies. When you work for small companies you have to wear hats. When I worked at skylark I had to write cli tools to interact with their SoC in c and bash, but also do hardware test in python, but also make a yield assessment website (js/python/orm shit). At Cratus i wrote a microservices backend docker yaml gui with a react frontend with a team of ten-ish turkish guys, but also worked with their electrical engineer on some embedded flashing webserver, a fluidflow calculator, and some ml camera tech involving nvidia jetsons for a taiwanese company, and a bottle manufacturing company for flaw detection. I was tasked with reverse engineering some chinese blue tooth beacons, and implementing a multilateration algorithm. I personally went to the Olympus endoscope repair facility, interviewed the staff, mapped the facility, and wrote a simulator for it. I have taken the few jobs I have been able to get. I learn what is professionally required. It might sound crazy but this is genuinely what i worked on. Atleast I can say it has not been boring!

leetcrew 3y ago
I've worked at small companies too, I get it. the charitable read of your linkedin page is that you're a engineer with a broad skillset who can be dropped into any kind of project and get it done. the uncharitable read is that you haven't spent enough time with any specific tool/language/domain to truly master it. you're not appealing to recruiters who are looking for X+ years of specific skill, and you're not telling your story the right way for recruiters that are looking for a generalist. if I were you, I would actually remove most of the individual projects from each job. keep 2-3 examples of what you consider your most impressive work and sell the reader on why it was impressive. key points to hit are a) why was the project important b) how did you solve the problem, and c) what was the impact to the business. by the way, b) should not just be a description of the tech stack you used. if you're looking at senior roles, people/organizational problems are more interesting to the reader.
- wegfawefgawefg 3y ago
  That is reasonable advice. Thank you. I had it reduced to all back end development for a few months. I got no responses. To be honest I've given up on it.

wegfawefgawefg 3y ago

As for my friend developers. One works at apple, one works at amazon, those are unlikely hires for me. One got laid off this year and now is getting certified to drive a city bus. A few of them work for the BP subcontractor, which is currently not hiring, layoffs. My other friend just got a new job, he was unemployed for about six months this year. My other friend has a degree and years of experience but is unemployed. I have one friend in bed with C# and medical industry. Have asked him about it. Lets say the average person has 10 professional acquaintances, id wager many of them are simply not in a position to make a referal.

leetcrew 3y ago
that's too bad. friends that can directly vouch for your skills are the easiest way into a job. still, don't forget a lot of companies give a bonus for any referral that results in a hire. unless you've specifically pissed them off, I bet most people who even vaguely recall that you've worked together would be willing to refer you. I got my current job through a second-degree connection. I didn't even know the guy that referred me.