denverpilot
Tied Down
A recruiter is bugging me to see if I want this job. See how many red flags YOU can spot...
I'll let you see the thoughts that run through any senior engineer's head while reading this, in italics...
I'll censor out some stuff but you can probably figure out who this is if you try. Won't take much.
I'm not going to worry too much about it, but who knows... maybe it'll be the last job on earth and I'll be turned down for it someday because I snarked at their job posting... I guess I'll starve.
Here we go...!
-----
Site Reliability Engineering (SRE) Engineer - Telephony
Job Type: Full-Time
Location: Denver, CO
Department: SRE NOC
[Just knowing it's based in a NOC already had me saying "no"... I didn't even have to read the rest, but let's, because it's FUN!]
The [Company Name Censored] environment is dynamic, success-driven, team-oriented and committed to providing world class service for its customers. Do you have the ability to thrive in a fast-paced environment? We are looking for candidates with an entrepreneurial spark!
[Awww... they forgot the whole "we're a family" thing... which says something, probably. Could they have crammed more standard buzzwords into this opening paragraph? Anyone with an entrepreneurial spark isn't going to go to work for this place, they're going to start a competitor and kick their ass. Duh. But we all know "We are looking for candidates who are dutiful little employees" doesn't really attract anyone.]
We’re not a phone company; we’re a cloud business-solutions provider. We've thrown out the old PBX along with its rigid rules and eliminated the complexity and unnecessary expense of managing business communications the old way.
[I bet you ARE a phone company. And I bet you don't get paid if the phones don't work. Thrown out the old... you mean like by configuring the system with phone numbers and a bunch of phones, and then they have to do stuff like ring and carry audio or all the other crap they might do, doesn't mean anything and you're out of business in telecom? "He who dies with the most Erlangs wins." We'll see further down just how "un-complex" your systems are...]
[Company Name Censored] is a leading Unified Communications as a Service (UCaaS) provider, offering an innovating suite of telephony, contact center, video conferencing, and collaboration products for enterprise, mid-size companies, and small businesses.
[Jack of all trades, and master of none? Like every other telecom company these days? Awesome! That'll help you focus. Yay decade old buzzwords and acronyms, too! UCaaS!! LOL. Hey just a thought, don't limit yourself to mid and small in your job postings either, don't you want a large customer? Or did you give up on doing that a long time ago and it just leaked into this posting? Just sayin'...]
Job Description:
The SRE Engineer contributes to the strategic objectives of the System Operations Division by providing telecommunication services and support. In this role you will perform the day to-day tasks for running of cloud-based environment consisting of telephony servers, media servers, fax servers, SIP proxies, etc. The SRE Engineer also investigates problems with applications and researches cloud-based VoIP telecom solutions. The SRE Engineer performs statistical analysis of data and participates in deployment procedures.
[So you're saying you haven't figured out how to create departments yet? How long have you been in business? I see Support, Operations, you listed off four separate platforms there, Troubleshooting/Systems Administration, Research & Marketing. While I appreciate that you think one engineer can do all of those things, and some can... I see a major organizational structure problems here.]
Responsibilities:
Qualifications:
I'll let you see the thoughts that run through any senior engineer's head while reading this, in italics...
I'll censor out some stuff but you can probably figure out who this is if you try. Won't take much.
I'm not going to worry too much about it, but who knows... maybe it'll be the last job on earth and I'll be turned down for it someday because I snarked at their job posting... I guess I'll starve.
Here we go...!
-----
Site Reliability Engineering (SRE) Engineer - Telephony
Job Type: Full-Time
Location: Denver, CO
Department: SRE NOC
[Just knowing it's based in a NOC already had me saying "no"... I didn't even have to read the rest, but let's, because it's FUN!]
The [Company Name Censored] environment is dynamic, success-driven, team-oriented and committed to providing world class service for its customers. Do you have the ability to thrive in a fast-paced environment? We are looking for candidates with an entrepreneurial spark!
[Awww... they forgot the whole "we're a family" thing... which says something, probably. Could they have crammed more standard buzzwords into this opening paragraph? Anyone with an entrepreneurial spark isn't going to go to work for this place, they're going to start a competitor and kick their ass. Duh. But we all know "We are looking for candidates who are dutiful little employees" doesn't really attract anyone.]
We’re not a phone company; we’re a cloud business-solutions provider. We've thrown out the old PBX along with its rigid rules and eliminated the complexity and unnecessary expense of managing business communications the old way.
[I bet you ARE a phone company. And I bet you don't get paid if the phones don't work. Thrown out the old... you mean like by configuring the system with phone numbers and a bunch of phones, and then they have to do stuff like ring and carry audio or all the other crap they might do, doesn't mean anything and you're out of business in telecom? "He who dies with the most Erlangs wins." We'll see further down just how "un-complex" your systems are...]
[Company Name Censored] is a leading Unified Communications as a Service (UCaaS) provider, offering an innovating suite of telephony, contact center, video conferencing, and collaboration products for enterprise, mid-size companies, and small businesses.
[Jack of all trades, and master of none? Like every other telecom company these days? Awesome! That'll help you focus. Yay decade old buzzwords and acronyms, too! UCaaS!! LOL. Hey just a thought, don't limit yourself to mid and small in your job postings either, don't you want a large customer? Or did you give up on doing that a long time ago and it just leaked into this posting? Just sayin'...]
Job Description:
The SRE Engineer contributes to the strategic objectives of the System Operations Division by providing telecommunication services and support. In this role you will perform the day to-day tasks for running of cloud-based environment consisting of telephony servers, media servers, fax servers, SIP proxies, etc. The SRE Engineer also investigates problems with applications and researches cloud-based VoIP telecom solutions. The SRE Engineer performs statistical analysis of data and participates in deployment procedures.
[So you're saying you haven't figured out how to create departments yet? How long have you been in business? I see Support, Operations, you listed off four separate platforms there, Troubleshooting/Systems Administration, Research & Marketing. While I appreciate that you think one engineer can do all of those things, and some can... I see a major organizational structure problems here.]
Responsibilities:
- Administer, update and support unique components of our platform based on Linux and Windows OS, oriented on voice and fax telecommunication services for customers [Translation: We haven't decided on a technology or a platform yet. We can't commit to anything.]
- Participate in projects intended to improve infrastructure, including the integration of new systems and software [Why the HELL would you add more things to this environment? You're hiring a RELIABILITY engineer, which indicates the above mess isn't reliable at all! You don't keep ADDING CRAP and expect reliability.]
- Perform pre-production tests in Staging environments [Hey look, another department! QA! Holy hell.]
- Deploying, configuring, and maintaining of voice and fax services, equipment and devices [You deploy through new product team, you configure ONCE and leave the bastard alone to do the defined job, if you're configuring things for customers you AUTOMATE that crap, you don't use mixed platforms for voice and fax, and you sure as hell don't pay an expensive engineer to do rack & stack.]
- Responsibility for software and hardware capacity expansion [Another department, Executive Management.]
- Keeps a keen eye on all [Company Name Censored] monitoring systems [The guy responsible for designing, testing, deploying, configuring, installing, and capacity... also handles monitoring. Riiiiiight. What exactly are you smoking? I know this is Denver and all, but seriously... leave it at home.]
- Solves any problems that arise in services [Because while you're doing all that other stuff, forest fires are definitely on the menu with four platforms, and multiple services, while you're installing even more new things. You people really are high.]
Qualifications:
- Bachelor’s Degree in Computer Science, Information Technology or similar [Yay, my "out'! I've been doing telephony for pushing 20 years and don't have a degree, so kiss my ass...]
- 3+ years of experience in the position of VoIP engineer [You just said you wanted this person 100% responsible for all of your future business growth, design, installation, operations, and monitoring... and you think 3 years of experience is going to cut it. Wow. Translation: We aren't planning on paying very well.]
- Strong grasp of Computer Science, Math and Science [We hired some guy the last time around who couldn't count his toes and was a Boulder hippie who thought "making a profit" was something someone else worried about when he designed this mess. Just a guess here.]
- Remote administration of servers, network devices [This is a thing? Like firing up a VPN, ssh, or RDP is not something you would expect of ANY IT ENGINEER these days?]
- Systems: Windows, Linux [Make up your mind. Seriously. I do both, but definitely have a preference for the one that can actually run for two years without a reboot. Just sayin'.]
- Networking: Switches, Routers, Hubs, Servers, Cables, Racks, Firewalls, VLAN, TCP/IP, VoIP, BGP, SIP, RTP, RTCP, T.38 [Another department Network Engineering! I think we're up to seven departments now, right... not just a single job. And come on... who lists "TCP/IP" anymore? Seriously? For an engineer who's going to plan and build and test your ENTIRE telephony environment? EFFFFF me...]
- Scripting skills: One of more of: Shell, Perl, Python, vbs, cmd [Ooh. "cmd"! I'll just whip out my "Learn 'cmd' in 24 Hours" book from Amazon... hey, wait a minute... isn't this department number eight, Software Engineering?]
- Willingness to learn cloud telephony technologies. [THIS IS WHERE I LOST IT AND HAD TO POST THIS. You're hiring an engineer who's going to run well more than half of your company, as described above, and they should be "willing to learn"... HOLY ****! Are you retarded? READ WHAT YOU WROTE. OMG.]
- 24х7 systems support [Nothing says "I have a great job running half the company" like being on call to fix it 24/7!]
- Good communication skills [I probably won't e-mail this to you, so I guess I fail this one.]
- Good team player [TEAM?! This job description is eight departments and twelve jobs! I think I could probably work with myself and not have too many arguments, but seriously?! What TEAM? You don't appear to have one, by this job description.]