[124388] in North American Network Operators' Group
RE: Finding content in your job title
daemon@ATHENA.MIT.EDU (Olsen, Jason)
Wed Mar 31 10:08:26 2010
Date: Wed, 31 Mar 2010 09:05:10 -0500
In-Reply-To: <4BB2BE2C.9000901@ibctech.ca>
From: "Olsen, Jason" <jolsen@devry.com>
To: <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
> From: Steve Bertrand [mailto:steve@ibctech.ca]
> Sent: Tuesday, March 30, 2010 10:15 PM
> Subject: Finding content in your job title
>=20
> For instance, I like to present myself as a 'network engineer'. I have
> never taken formal education, don't hold any certifications (well,
> since 2001), and can't necessarily prove my worth.
>=20
> How does the ops community feel about using this designation? Is it
> intrusive or offensive to those who hold real engineering degrees? I'm
>=20
> Instead of acting like I'm trying to sell myself out, I'll leave out
> what I actually do and ask those who sig themselves with 'network
> engineer' what they do day-to-day to acquire that title, and if they
> feel comfortable with having it.
I have "Senior Network Engineer" as my title. I have an undergraduate
degree in networked communications and management. When working some
days or on some projects, like when I'm laying out a whole new
datacenter for $EMPLOYER, I feel that I'm filling the role admirably.
Other days, when I'm simply pushing paper or "stamping license plates"
(small, repetitive tasks of little import) I don't feel that I really
deserve the title.
But then, if I had my druthers, I'd put "Chief Bit-mover" on my business
card (the CIO's secretary put the kabash on when I tried it, citing
something about executives not much liking it when non-officers put
"Chief" anything on their cards... ;) )
-JFO
