+ Reply to Thread
Results 1 to 21 of 21
  1. Senior Member Infosec85's Avatar
    Join Date
    Jan 2016
    Location
    Ireland
    Posts
    185

    Certifications
    Just a few...
    #1

    Default How long typically to adopt to I.T in an enterprise

    So I recently got my first I.T job in a security role. The product etc is huge. Wondering how long it typically takes someone to adapt whether new or coming from a support role etc?
    Reply With Quote Quote  

  2. SS
  3. Senior Member
    Join Date
    May 2013
    Posts
    1,445

    Certifications
    CISSP, CISA, GWAPT, GSEC
    #2
    Most jobs...especially if the tasks or environment is new will take something like 6 months to become comfortable.
    Reply With Quote Quote  

  4. Are we having fun yet? UnixGuy's Avatar
    Join Date
    Mar 2008
    Posts
    3,558

    Certifications
    GPEN, GCFA, eJPT, RHCE, Solaris 10, SNIA SCSP, Security+, Server+, ITILv3, CCNA (Expired)
    #3
    6 months is the honeymoon period....
    Goal: MBA, March 2020
    Reply With Quote Quote  

  5. Member
    Join Date
    Mar 2016
    Location
    North America
    Posts
    87
    #4
    For most jobs, it's about 3-6 months. I recall my first three jobs took me about 4-5 months to get comfy in each of those positions...
    Reply With Quote Quote  

  6. Senior Member
    Join Date
    May 2014
    Location
    NJ
    Posts
    908

    Certifications
    CCNP: R&S, CCDA, CCNA: Security, CCNA: R&S, MTA: Networking Fundamentals, Security+, Network+, Linux+, A+, Project+
    #5
    I'd normally agree but I stepped into the fire immediately and there was no time to adjust. If you're not the only guy doing your job though, you won't have that issue
    Reply With Quote Quote  

  7. Senior Member greg9891's Avatar
    Join Date
    Mar 2014
    Location
    Bahamas
    Posts
    1,088

    Certifications
    Network +, MTA: 98-366, 367,MCP, MCTS Win 7, VCP-DCV, MCSA SERVER 2012, MCTS Hyper-V
    #6
    I would say about 5 to 7 months!
    Certs Gained 2017: 70-410, 70-411,74-409, MCSA Server 2012r2
    Upcoming: Security +, ITIL FOUNDATIONS, 70-345 Exchange Server 2016, Ccent

    “Therefore encourage one another and build each other up, just as in fact you are doing.” - 1 Thessalonians 5:11
    Reply With Quote Quote  

  8. Senior Member Queue's Avatar
    Join Date
    Oct 2015
    Posts
    170

    Certifications
    A+, Network +, Security +, Project +, Linux +, LPIC1, CCENT, CCNA
    #7
    I agree you start to contribute around 6 months. After realizing this it baffles me how people can switch jobs so quickly.
    Reply With Quote Quote  

  9. Completely Clueless TechGromit's Avatar
    Join Date
    Oct 2015
    Location
    Ontario, NY
    Posts
    1,604

    Certifications
    A+, Network +, Sanity+ (Revoked), GSEC, GCIH, GREM
    #8
    Anywhere from 3 to 9 months, depending on the position, Higher level jobs like a Network engineer take longer to become proficient in there positions than say someone joining the deskside support team.
    Still searching for the corner in a round room.
    Reply With Quote Quote  

  10. Senior Member
    Join Date
    Mar 2011
    Location
    Chicago
    Posts
    1,382

    Certifications
    CISSP-ISSAP, HCISPP GPEN, GSEC, GSNA, GCIH, E|CH, ECSA, Security+
    #9
    I was clueless till about five months into the position. At six months I was accurate. Within the year I became both feared and respected. Its normal for most IT positions save development where we assume it takes three months before you start to get useful, production code out of a dev or DevOps type.

    - b/eads
    Reply With Quote Quote  

  11. Senior Member
    Join Date
    May 2014
    Location
    NJ
    Posts
    908

    Certifications
    CCNP: R&S, CCDA, CCNA: Security, CCNA: R&S, MTA: Networking Fundamentals, Security+, Network+, Linux+, A+, Project+
    #10
    Quote Originally Posted by Queue View Post
    I agree you start to contribute around 6 months. After realizing this it baffles me how people can switch jobs so quickly.
    LOL well if you are clueless, you probably have to switch jobs every 6 months so you do not get caught.

    I remember the second day at my current job. Internet connectivity at HQ lost. BGP relationships everywhere still up. My answer for how long it takes to contribute is now two days as a result!!!
    Reply With Quote Quote  

  12. Senior Member
    Join Date
    Sep 2016
    Location
    VA
    Posts
    719

    Certifications
    CISSP, PMP, CCNP, FITSP-M
    #11
    Depends on the job. For helpdesk or desk-side, 2-3 months is usually sufficient but six months is pretty accurate otherwise. I won't even look at a resume where the person has two of their last three jobs under 18 months if they're interviewing for a tier-2 or 3 job. I have no intention of training someone up for six months then having them leave three months later.
    2018: CCIE Written (R/S) (done - Jan), CCIE R/S
    After that: MBA, OSCP
    Reply With Quote Quote  

  13. They are watching you NetworkNewb's Avatar
    Join Date
    Feb 2015
    Location
    Off the grid
    Posts
    2,894

    Certifications
    A+/Net+/Sec+, CCENT, CCNA:Sec, CCSK, GCIH
    #12
    Quote Originally Posted by EANx View Post
    Depends on the job. For helpdesk or desk-side, 2-3 months is usually sufficient but six months is pretty accurate otherwise. I won't even look at a resume where the person has two of their last three jobs under 18 months if they're interviewing for a tier-2 or 3 job. I have no intention of training someone up for six months then having them leave three months later.
    I applied to a job like awhile back (forget the exact position, something like Security Analyst or Engineer) and someone from HR called me back about it and was asking me about 2 year stints at jobs. My last 3 jobs I've only been there less than 2 years on average. She just kept questioning them and nothing else. They all were small moves up and one was actually cause I moved to another part of the city. But she just couldn't get passed it and I didn't get an in person interview. Was surprised she even called me the way she kept asking about them.

    Been at my current position for a little over 2 years now though...
    Last edited by NetworkNewb; 02-19-2018 at 06:35 PM.
    Reply With Quote Quote  

  14. Are we having fun yet? UnixGuy's Avatar
    Join Date
    Mar 2008
    Posts
    3,558

    Certifications
    GPEN, GCFA, eJPT, RHCE, Solaris 10, SNIA SCSP, Security+, Server+, ITILv3, CCNA (Expired)
    #13
    Quote Originally Posted by EANx View Post
    ... I won't even look at a resume where the person has two of their last three jobs under 18 months if they're interviewing for a tier-2 or 3 job. I have no intention of training someone up for six months then having them leave three months later.

    You will overlook my resume
    Goal: MBA, March 2020
    Reply With Quote Quote  

  15. Senior Member
    Join Date
    Sep 2016
    Location
    VA
    Posts
    719

    Certifications
    CISSP, PMP, CCNP, FITSP-M
    #14
    Sure would. Different organizations value different thing. Mine values stability and I mean that both ways.
    2018: CCIE Written (R/S) (done - Jan), CCIE R/S
    After that: MBA, OSCP
    Reply With Quote Quote  

  16. Senior Member
    Join Date
    Feb 2018
    Location
    Boston, MA
    Posts
    166

    Certifications
    ITIL v3, Security+, Network+, Project+, A+
    #15
    Quote Originally Posted by EANx View Post
    Depends on the job. For helpdesk or desk-side, 2-3 months is usually sufficient but six months is pretty accurate otherwise. I won't even look at a resume where the person has two of their last three jobs under 18 months if they're interviewing for a tier-2 or 3 job. I have no intention of training someone up for six months then having them leave three months later.
    How do you argue with the statistic that people age 22-35 leave jobs every 18 months as the "standard" in the work force now. At least that's what I keep getting told anyway. I personally think it's BS.
    Reply With Quote Quote  

  17. Senior Member
    Join Date
    Apr 2017
    Posts
    385
    #16
    My first IT job in a company of around 250 employees and 300 endpoints took about 2-3 months to get comfortable and 6 months to become fully productive. I started my current job in security engineering ~4 months ago and I'm still ramping up in many areas. We are a global company with 50,000+ employee's and 110,000 endpoints which my group manages. I fully expect it will take another 3-4 months before I can be considered to be fully productive and even then there is always still more to learn.
    Last edited by ITSec14; 02-21-2018 at 12:03 PM.
    Reply With Quote Quote  

  18. Completely Clueless TechGromit's Avatar
    Join Date
    Oct 2015
    Location
    Ontario, NY
    Posts
    1,604

    Certifications
    A+, Network +, Sanity+ (Revoked), GSEC, GCIH, GREM
    #17
    Quote Originally Posted by Squished View Post
    How do you argue with the statistic that people age 22-35 leave jobs every 18 months as the "standard" in the work force now. At least that's what I keep getting told anyway. I personally think it's BS.
    That may work fine when your just starting out in your career, but most managers I talk to want to see stability before hiring someone for a higher level position, such as a Network engineer. Hiring, training and getting someone up to speed on their business is expensive, it's far more cost effective to hire someone who is good at what they do and stick around for 5+ years, then hire some great hotshot that is going to jump ship at the next higher offer in 6, 12 or 18 months.
    Last edited by TechGromit; 02-21-2018 at 01:52 PM.
    Still searching for the corner in a round room.
    Reply With Quote Quote  

  19. Senior Member
    Join Date
    Sep 2016
    Location
    VA
    Posts
    719

    Certifications
    CISSP, PMP, CCNP, FITSP-M
    #18
    Quote Originally Posted by Squished View Post
    How do you argue with the statistic that people age 22-35 leave jobs every 18 months as the "standard" in the work force now. At least that's what I keep getting told anyway. I personally think it's BS.
    I don't argue with it but I do say that it's incomplete data.The age range of 22-35 is HUGE when you consider the working life of people. That covers everything from people who are just starting out (assuming college) to people that are almost retiring from the military (the earliest I am aware you can retire with pension is 37). Never mind people who are married, single, kids, no kids, etc. Most people go through at least two life transitions during that period (graduate from school, get married, have a kid, etc.)

    Quote Originally Posted by TechGromit View Post
    That may work fine when your just starting out in your career, but most managers I talk to want to see stability before hiring someone for a higher level position, such as a Network engineer. Hiring, training and getting someone up to speed on their business is expensive, it's far more cost effective to hire someone who is good at what they do and stick around for 5+ years, then hire some great hotshot that is going to jump ship at the next higher offer in 6, 12 or 18 months.
    Absolutely. Job candidates forget that the key isn't how long people are sitting in the role, it's also about the quality of the work. Even if I found a person to fill a position the day it came open, the work they do isn't the same quality as the person who just left. Every company will have a different tolerance for job hopping based on the job in question. If I ran a call center, I probably wouldn't care if your average job history was 9 months. But if I have a position for a Cisco network designer or VMware architect, you aren't getting in front of me unless you've averaged 2+ years over the last few jobs. I'll cut someone some slack for ONE recent job because things happen, the job wasn't as advertised, the applicant is a chick and she was harassed, etc. but if you have a pattern of hopping, I don't care how good you are. I value stability, my boss values stability and I want employees that value stability. Another exception is contracting but that's a different topic.
    Last edited by EANx; 02-21-2018 at 03:45 PM.
    2018: CCIE Written (R/S) (done - Jan), CCIE R/S
    After that: MBA, OSCP
    Reply With Quote Quote  

  20. Senior Member
    Join Date
    Feb 2018
    Location
    Boston, MA
    Posts
    166

    Certifications
    ITIL v3, Security+, Network+, Project+, A+
    #19
    Quote Originally Posted by TechGromit View Post
    That may work fine when your just starting out in your career, but most managers I talk to want to see stability before hiring someone for a higher level position, such as a Network engineer. Hiring, training and getting someone up to speed on their business is expensive, it's far more cost effective to hire someone who is good at what they do and stick around for 5+ years, then hire some great hotshot that is going to jump ship at the next higher offer in 6, 12 or 18 months.
    Thanks, I guess I have some hope! Hah!
    Reply With Quote Quote  

  21. Are we having fun yet? UnixGuy's Avatar
    Join Date
    Mar 2008
    Posts
    3,558

    Certifications
    GPEN, GCFA, eJPT, RHCE, Solaris 10, SNIA SCSP, Security+, Server+, ITILv3, CCNA (Expired)
    #20
    Stability is a great thing, until the company runs out of budget, or your manager leave and someone else replace them, or you realise that you haven't learned a thing in 2 years.. then the company will replace you


    Nothing against stability and staying in the same employer (I stayed for 7 yrs in one place), just keeping things in perspective. Things change quickly in our field and a change of job is sometimes necessary to get more exposure/money....but staying in the same company can give you a leg up for promotions..who knows.
    Goal: MBA, March 2020
    Reply With Quote Quote  

  22. Senior Member
    Join Date
    Feb 2018
    Location
    Boston, MA
    Posts
    166

    Certifications
    ITIL v3, Security+, Network+, Project+, A+
    #21
    Quote Originally Posted by UnixGuy View Post
    Stability is a great thing, until the company runs out of budget, or your manager leave and someone else replace them, or you realise that you haven't learned a thing in 2 years.. then the company will replace you


    Nothing against stability and staying in the same employer (I stayed for 7 yrs in one place), just keeping things in perspective. Things change quickly in our field and a change of job is sometimes necessary to get more exposure/money....but staying in the same company can give you a leg up for promotions..who knows.
    I'm at 8 years. We're out of budget(have been for 3+ years) and haven't done a new thing in 5+ years. I'm burnt.
    Reply With Quote Quote  

+ Reply to Thread

Social Networking & Bookmarks