What does "extensive TCP/IP knowledge" means?

cw3k

I don't have a networking background, and have been only studying the subject for a few months. I see quite a few job descriptions with something like "extensive TCP/IP knowledge" as a requirement, but what exactly does it means?

Thanks

SecurityThroughObscurity

basic networking knowledge.
icnd1 level.

Chitownjedi

SecurityThroughObscurity wrote: »

basic networking knowledge.
icnd1 level.

I Concur, CCENT Level knowledge.

dmoore44

I've always kind of wondered what employers mean when they say "extensive knowledge of..." in a job description. To my mind, if someone says "extensive knowledge", I'm thinking that the ideal candidate is almost a SME, so this is good to know.

pert

It doesn't mean anything. It's a vague, undefinable quality. Written by a manager or HR person that is unable to quantify what qualities their ideal candidate would actually have. It has about the same meaning as "Ideal candidate would be good with computers".

jibbajabba

pert wrote: »

It doesn't mean anything. It's a vague, undefinable quality.

Yepp ... best job specs I got recently

"Extensive knowledge of Active Directory, Group Policy Objects and GPOs - Also requires DNS"

or

"Extensive knowledge about ESX 5 , HyperV and Citrix - virtualization knowledge advantageous"

Had that one last week ...

I HATE when either HR or recruiter post adverts like that without knowing what they are talking about.

DoubleNNs

I would think it is CCENT/CCNA level knowledge. Or Net+ mixed w/ some Server networking knowledge. But it all depends on the rest of the job ad.

Danielm7

DoubleNNs wrote: »

I would think it is CCENT/CCNA level knowledge. Or Net+ mixed w/ some Server networking knowledge. But it all depends on the rest of the job ad.

Right, if the job is to install home networks and wifi routers for people "extensive" might mean make sure DHCP is setup and they are pulling an address and how to ping.

NetworkVeteran

pert wrote: »

It doesn't mean anything. It's a vague, undefinable quality. Written by a manager or HR person that is unable to quantify what qualities their ideal candidate would actually have.

This best translates the meaning.

An entry-level candidate who grasps the basics of TCP/IP would have a fighting chance, because if the employer doesn't know what they need, there's a fair chance they'll start with the cheapest person who might meet their needs.

paul78

I think largely depends on the author of the job description and the company. It can do either way. In companies where I have worked, HR and recruiters do not write job descriptions - the hiring manger writes them. So - if that was my description, I would expect "extensive" knowledge which means being able to decode a TCP stream and understand it's interaction with other IP protocols and how TCP is used by applications.

Of course, that siad - I would never say "extensive knowledge of TCP/IP" but say "extensive knowledge of IP based protocols" instead - since I care about UDP and application level protocols.

vanquish23

I was going to say the ability to troubleshoot network data transfer, either real time or analyzing packet captures. I know I use these skills everyday in the data center because its "always the network's fault."

powmia

If the person requesting extensive knowledge of tcp/ip is some IT company's SME:

tcp/ip doesn't mean tcp over ip. Technically TCP/IP refers to the DoD model that is the IETF equivalent of the OSI model. In other words... the TCP/IP stack encompases the entire suite of protocols that are network communication. I'm a CCIE and I learn something new about TCP/IP on a daily basis. So, I completely disagree that extensive knowledge equates to ICND level knowledge.

If the person asking is a head hunter/corporate recruiter/HR:

You know more about it than they do, so you have extensive knowledge. That's probably the same post that says the ideal candidate will either have a CCNA, CCIE, network+, or a PMP

powmia

Also, every once in a while you do see that legitimately placed on a job listing. Some use a reference to TCP/IP, because there is a big difference between a network engineer that focuses on TCP/IP and one that primarily does something in the area of optical networking. More often than not, that isn't the case, though.