[not a job offer] network engineers vacancies
Roman Mashak
Often skimming through recruiting agencies, I find the vacancies named
"Network protocol engineer", "Protocols stack developer" etc.("...The
candidates should have a good understanding
of network and routing protocols, in particular IP, MPLS, VPLS, ATM, Frame
Relay, Ethernet, routing protocols such as BGP, OSPF...")
I'm just wondering what sort of jobs are done on such vacancies -- as all
such protocols and stacks had been already invented and designed, what else
to do? Ot it's rather related with optimization, profiling, porting on new
platforms/network processors etc. ?
PS. no grumbling, just curious :-)
Best regards, Roman Mashak
Jim Logajan
> Often skimming through recruiting agencies, I find the vacancies named
> "Network protocol engineer", "Protocols stack developer" etc.("...The
> candidates should have a good understanding
> of network and routing protocols, in particular IP, MPLS, VPLS, ATM,
> Frame Relay, Ethernet, routing protocols such as BGP, OSPF...")
It is possible that some of the requirements are listed because the work
involves new protocols or algorithms that share some aspects in common with
the ones mentioned. Or the hiring manager thinks that if you know your way
around those, you would be way ahead of other candidates in stack-smarts.
> I'm just wondering what sort of jobs are done on such vacancies -- as
> all such protocols and stacks had been already invented and designed,
I believe that part of your premise is wrong. I've already run into a
several "new" stack development projects. Consider this scenario - what if
a chip company wanted to reduce to silicon a TCP/IP stack - or some subset?
> what else to do? Ot it's rather related with optimization, profiling,
> porting on new platforms/network processors etc. ?
That's probably what some of the jobs involve too.
Also keep in mind that many of those "invented and designed" stacks still
exhibit bugs and other nasty critters. Somebody has to go in there and
exterminate them.