Thank you, Charlie Brown. Now try to kick the goddamn football again.As I no longer have my beloved with whom to share my work frustrations, I am putting this here:
AAAAAAAAAAAAAAAAAAAAAGGGGGHHHHH!
thank you.
I see you post and I am reminded that my problems are meaninglessAs I no longer have my beloved with whom to share my work frustrations, I am putting this here:
AAAAAAAAAAAAAAAAAAAAAGGGGGHHHHH!
thank you.
Care to elaborate? We can give you a whole string of semi-serious slapsticky advice, some of which is designed to help, some of which is designed to make you smile, some of which might come from tanoomba. You should ignore at least one of these.I can fix it so "that sucks"is perfect as is the agggh chorus, Charlie Brown reference and empathy.....again, I know why G liked it "here" so much.
This is more common than you think. Simply cite accomplishments or projects that demonstrate that both your skills and work went beyond what your title would imply.Not looking for a new job for a long while, but a question popped into my head, and I'm curious of the response.
How does someone put into their resume that they did way more than the job title would imply, without coming off as a show off? As it applies to me, I'm a network tech. I load up Cisco IOS configs onto devices. So many times that shit is wrong, and it's our job to make it right, not the fucking designer who gets paid triple what I do. Makes total sense, right? Well, much of the troubleshooting and fixing I feel is CCNP level shit, but I don't have a CCNP. It's great experience, but would a simple bullet point about trouble shooting, with examples ready, if asked be sufficient?
Money. Dollar signs. Explain what you did and how much money you saved the company because you were there to "make it work right". Quantify it. Don't ever, in my opinion at least, be afraid to show off on a resume as long as you can back it up.How does someone put into their resume that they did way more than the job title would imply, without coming off as a show off?
As someone who has gotten lots of resumes in the past and done hiring, just list what duties you performed and such. Lot oif variation in titles from company to company. Also I have a hunch that a fair number of companies give out titles instead of a raise so they accumulate titles without actually doing anything different than they did with the last title. The company I worked out at for 5 years before my last nobody had a title outside of the owner. Everyone got a business card with nothing more than the company and your name. On our website it listed what department you were in "kind of". Either management, engineering, or sales. That was it, and that went for the boss who was lsited under engineering and his son who was just listed under sales.Not looking for a new job for a long while, but a question popped into my head, and I'm curious of the response.
How does someone put into their resume that they did way more than the job title would imply, without coming off as a show off? As it applies to me, I'm a network tech. I load up Cisco IOS configs onto devices. So many times that shit is wrong, and it's our job to make it right, not the fucking designer who gets paid triple what I do. Makes total sense, right? Well, much of the troubleshooting and fixing I feel is CCNP level shit, but I don't have a CCNP. It's great experience, but would a simple bullet point about trouble shooting, with examples ready, if asked be sufficient?
Oh yeah, titles are a crap shoot. Never know what they mean. For me... network tech, network admin, network engineer... who the hell knows which sounds better these days. Leaning towards slapping the engineer title on my LinkedIn just for shits and giggles!As someone who has gotten lots of resumes in the past and done hiring, just list what duties you performed and such. Lot oif variation in titles from company to company. Also I have a hunch that a fair number of companies give out titles instead of a raise so they accumulate titles without actually doing anything different than they did with the last title. The company I worked out at for 5 years before my last nobody had a title outside of the owner. Everyone got a business card with nothing more than the company and your name. On our website it listed what department you were in "kind of". Either management, engineering, or sales. That was it, and that went for the boss who was lsited under engineering and his son who was just listed under sales.
"I do get a little salty when people slap the engineer title on. I'm a douche though
IT isn't really like that, much to Noodlebro's chagrin. Crone has his CCNA, he's a network engineer. Pretty much if you build systems, you're an engineer. In security they refer to people who analyze log data and shit as engineers.In our industry if they use the term engineer they better have a stamp and the ability to use it. Otherwise they just say you work in the engineering department which is pretty common, which is actually what you do.