ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Resume Update

    Scheduled Pinned Locked Moved IT Careers
    resume reviewresume
    95 Posts 6 Posters 5.7k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • EddieJenningsE
      EddieJennings
      last edited by EddieJennings

      It's been a couple of years since I've done a resume update, so I figured it was time. I want to avoid what I did during my teaching career and do zero updates over a course of eight years.

      For a bit of scope, I'm still looking to transition from a Windows administration role toward a Linux administration role. Since all of my 9-5 experience has been in the Windows world, the resume reflective of that.

      Just like a couple of years ago, I welcome your folks' opinions. 🙂

      Draft 1
      Draft 2
      Draft 3
      Draft 4
      Draft 5

      1 Reply Last reply Reply Quote 0
      • IRJI
        IRJ
        last edited by

        Always tailor your resume for the job you want, not the jobs you've had. Highlight experience Linux experience in your previous roles and make that your focus on your resume. Obviously include important accomplishments you've done with Windows, but make it at least 60-70% about Linux even if that has only been 25% of your role.

        EddieJenningsE scottalanmillerS 2 Replies Last reply Reply Quote 3
        • IRJI
          IRJ
          last edited by

          Also I'd remove the top area and put each skull under relevant role. It will give your employer a better idea of how long and in what jobs you utilized the role.

          1 Reply Last reply Reply Quote 3
          • EddieJenningsE
            EddieJennings @IRJ
            last edited by

            @IRJ said in Resume Update:

            Always tailor your resume for the job you want, not the jobs you've had. Highlight experience Linux experience in your previous roles and make that your focus on your resume. Obviously include important accomplishments you've done with Windows, but make it at least 60-70% about Linux even if that has only been 25% of your role.

            True. I’ll see how I can frame some things differently. It’ll be difficult for the current environment since, from the systems side of things, it’s a 100% Microsoft shop.

            1 Reply Last reply Reply Quote 0
            • scottalanmillerS
              scottalanmiller
              last edited by

              I feel it is weird that you list Windows versions, but not other versions.

              EddieJenningsE 1 Reply Last reply Reply Quote 0
              • scottalanmillerS
                scottalanmiller
                last edited by

                Make sure technology names are correct.

                PowerShell is PowerShell, not Windows PowerShell. "Windows PowerShell" isn't a thing.

                ObsolesceO 1 Reply Last reply Reply Quote 0
                • scottalanmillerS
                  scottalanmiller
                  last edited by

                  What is the difference between these two roles? Since IT uses "System" to mean "Server" instance, these two titles make no sense....

                  IT System Administrator (September 2019 – Present)
                  IT Server Administrator (February 2018 – September 2019)

                  The only thing that as a hiring manager I can guess from seeing this is that you are confused as to terms and don't know what you were doing or you moved from being a bench tech doing rack and stack and literally managing server hardware (bench work, not IT) and got promoted into an IT role in systems.

                  Also, using "IT" in front of it makes no sense. Server/System are IT tasks. Are you saying that you only worked for servers that weren't used by the business and only by the IT department internally? So like an intern role? I don't think that that is how you want to portray that. And that's what that implies and/or it makes you sound like someone's grandparent calling it "The Facebook" or something. It just doesn't sound natural or make logical sense to refer to IT roles with "IT" in the front of them unless you truly intend to imply that IT is part of the role. It implies that finance system admin, operations systems admin, etc. are out there and are the far more senior departments because they make the money.

                  EddieJenningsE 1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller
                    last edited by

                    Provided ad hoc remote hands support for NTG (ntg.co)

                    You can punch this up a bit. And I often drop the verbs, the can be awkward in bullet points.

                    Something like...

                    Regional Premises Technician for Global IT Outsourcer ntg.co

                    EddieJenningsE 1 Reply Last reply Reply Quote 0
                    • scottalanmillerS
                      scottalanmiller
                      last edited by

                      This is pretty good, but I'd keep iterating and tightening it up. Some thoughts...

                      *Designed a FreePBX VoIP system using Vultr VPS and Twilio SIP trunking
                      •Consolidated physical servers into a Hyper-V 2016 virtual environment
                      •Migrated E-mail system from on-premises MDaemon to Exchange Online
                      •Developed PowerShell scripts to automate Exchange mailbox management
                      •Implemented centralized user authentication using Active Directory
                      •Configured user workstations using group policy
                      •Deployed user support request management system using Spiceworks
                      •Managed software license compliance
                      •Created IT documentation using DokuWiki
                      •Trained and supported end-users


                      Same list but tighter...

                      • Implemented FreePBX telephony platform
                      • Consolidated & Virtualized to Hyper-V
                      • MDaemon On-Premises to Microsoft 365 migration
                      • Exchange automation via PowerShell
                      • Implemented Active Directory & Group Policy
                      • Managed software licensing and compliance
                      • Created documentation processes & platform

                      I dropped a few things, the lists are too long. Notice I didn't mention who your cloud vendor or SIP vendor are. I don't add versions of things. I take out the unnecessary stuff that no one will care about. A SIP trunk is a SIP trunk, no need to name drop. No one is going to hire you because it was Twilio. Keep it short and sweet so that it gets read.

                      And like AD, you don't need to explain it. This feels awkward and you want to be in a position where you are being interviewed by people who know what AD is. If you have to explain what AD is, there is a problem and you want to avoid that situation.

                      I dropped some things like installing spiceworks because at some point, you don't want to be listing things like "I double clicked on a exe to install it" because it implies to the reader that you feel that that's notable, and it implies that you are listing every task you did and that this is all that there was.

                      IRJI EddieJenningsE 2 Replies Last reply Reply Quote 1
                      • IRJI
                        IRJ @scottalanmiller
                        last edited by

                        @scottalanmiller said in Resume Update:

                        This is pretty good, but I'd keep iterating and tightening it up. Some thoughts...

                        *Designed a FreePBX VoIP system using Vultr VPS and Twilio SIP trunking
                        •Consolidated physical servers into a Hyper-V 2016 virtual environment
                        •Migrated E-mail system from on-premises MDaemon to Exchange Online
                        •Developed PowerShell scripts to automate Exchange mailbox management
                        •Implemented centralized user authentication using Active Directory
                        •Configured user workstations using group policy
                        •Deployed user support request management system using Spiceworks
                        •Managed software license compliance
                        •Created IT documentation using DokuWiki
                        •Trained and supported end-users


                        Same list but tighter...

                        • Implemented FreePBX telephony platform
                        • Consolidated & Virtualized to Hyper-V
                        • MDaemon On-Premises to Microsoft 365 migration
                        • Exchange automation via PowerShell
                        • Implemented Active Directory & Group Policy
                        • Managed software licensing and compliance
                        • Created documentation processes & platform

                        I dropped a few things, the lists are too long. Notice I didn't mention who your cloud vendor or SIP vendor are. I don't add versions of things. I take out the unnecessary stuff that no one will care about. A SIP trunk is a SIP trunk, no need to name drop. No one is going to hire you because it was Twilio. Keep it short and sweet so that it gets read.

                        And like AD, you don't need to explain it. This feels awkward and you want to be in a position where you are being interviewed by people who know what AD is. If you have to explain what AD is, there is a problem and you want to avoid that situation.

                        I dropped some things like installing spiceworks because at some point, you don't want to be listing things like "I double clicked on a exe to install it" because it implies to the reader that you feel that that's notable, and it implies that you are listing every task you did and that this is all that there was.

                        If you have done any AD upgrades or migrations those are worth noting, however, but overall I agree with @scottalanmiller

                        Talking about supporting end users is a waste of space and using specific platforms for documentation is a turn off, because its unlikely the new employer would use the same platform. So yeah his list is pretty good.

                        EddieJenningsE 1 Reply Last reply Reply Quote 1
                        • scottalanmillerS
                          scottalanmiller
                          last edited by

                          So this isn't wrong, per se, but it's weird. Legally, your personal company is a company and you can list it as a place of work. But as an LLC, it's also "just you" and counts generally as self employed unless you have many owners and you have a salary and file a W2 and even then, "it depends".

                          But in this context, your LLC is a personal one and it's just you. And it's clear from the bullet points that this is true. And it's not like you are hiding that. It's not dishonest or anything, it's just odd.

                          The work you have listed under it doesn't go together or really make sense. Some of the world is IT and for another vendor, so that should be listed under that vendor (ntg) not your LLC, because you are a payroll handling entity in that case. You always list for whom you work, not who writes the checks (same rules the IRS uses.)

                          Everything listed on there is side projects, but it's listed much like it is full time employment. I have overlapping dates on my resume, but this is because each entity can claim me as a full timer, because I actually work double gigs.

                          So for a resume, this stuff normally goes in a "side projects" or "other" area, not as a full time job in the chronological career history listing.

                          Also, listing your personal lab under a corporate entity is very odd. Because we assume you weren't paid on a W2 and filed income taxes against the time used for your lab, and if you did, why?

                          EddieJenningsE 1 Reply Last reply Reply Quote 0
                          • scottalanmillerS
                            scottalanmiller @IRJ
                            last edited by

                            @IRJ said in Resume Update:

                            Always tailor your resume for the job you want, not the jobs you've had.

                            This is a big deal. Remember this is a marketing tool, not a documentation one. You want to be honest, but also concise, meaningful and intentional.

                            1 Reply Last reply Reply Quote 0
                            • EddieJenningsE
                              EddieJennings
                              last edited by

                              Good stuff to absorb :). I'll be making a second edit after work today (and responding to a few points). Thanks for the suggestions!

                              1 Reply Last reply Reply Quote 0
                              • ObsolesceO
                                Obsolesce @scottalanmiller
                                last edited by Obsolesce

                                @scottalanmiller said in Resume Update:

                                Make sure technology names are correct.

                                PowerShell is PowerShell, not Windows PowerShell. "Windows PowerShell" isn't a thing.

                                No, PowerShell is PowerShell, AKA PowerShell (6+) based on .NET Core.

                                Windows PowerShell is exactly that, Windows PowerShell up to 5.1.

                                1 EddieJenningsE 2 Replies Last reply Reply Quote 0
                                • 1
                                  1337 @Obsolesce
                                  last edited by

                                  @Obsolesce said in Resume Update:

                                  @scottalanmiller said in Resume Update:

                                  Make sure technology names are correct.

                                  PowerShell is PowerShell, not Windows PowerShell. "Windows PowerShell" isn't a thing.

                                  No, PowerShell is PowerShell, AKA PowerShell (6+) based on .NET Core.

                                  Windows PowerShell is exactly that, Windows PowerShell up to 5.1.

                                  So what's the difference actually? I thought it was the same thing.

                                  ObsolesceO 1 Reply Last reply Reply Quote 0
                                  • 1
                                    1337
                                    last edited by

                                    @EddieJennings

                                    Nobody mentioned it afaik but I would consider removing everything music related. That could be covered elsewhere. It's not relevant to IT unless the company is involved in it somehow.

                                    scottalanmillerS EddieJenningsE 2 Replies Last reply Reply Quote 2
                                    • ObsolesceO
                                      Obsolesce @1337
                                      last edited by

                                      @Pete-S said in Resume Update:

                                      @Obsolesce said in Resume Update:

                                      @scottalanmiller said in Resume Update:

                                      Make sure technology names are correct.

                                      PowerShell is PowerShell, not Windows PowerShell. "Windows PowerShell" isn't a thing.

                                      No, PowerShell is PowerShell, AKA PowerShell (6+) based on .NET Core.

                                      Windows PowerShell is exactly that, Windows PowerShell up to 5.1.

                                      So what's the difference actually? I thought it was the same thing.

                                      They are totally different softwares.

                                      PowerShell starts at version 6 (currently 7.x) and is based on .NET CORE.

                                      Windows PowerShell is up to 5.1 and is based on the standard .NET (non-core version), has all the standard Windows management frameworks (5.1) and all that. I don't know all the technical jargon.

                                      But PowerShell and Windows PowerShell are two separate and different products and very much a thing.

                                      scottalanmillerS 1 Reply Last reply Reply Quote 0
                                      • scottalanmillerS
                                        scottalanmiller @1337
                                        last edited by

                                        @Pete-S said in Resume Update:

                                        @EddieJennings

                                        Nobody mentioned it afaik but I would consider removing everything music related. That could be covered elsewhere. It's not relevant to IT unless the company is involved in it somehow.

                                        I agree. If you feel compelled to mention it, list it under hobbies or other interests. Don't actual like it's part of your IT career path.

                                        1 Reply Last reply Reply Quote 0
                                        • scottalanmillerS
                                          scottalanmiller @Obsolesce
                                          last edited by

                                          @Obsolesce said in Resume Update:

                                          @Pete-S said in Resume Update:

                                          @Obsolesce said in Resume Update:

                                          @scottalanmiller said in Resume Update:

                                          Make sure technology names are correct.

                                          PowerShell is PowerShell, not Windows PowerShell. "Windows PowerShell" isn't a thing.

                                          No, PowerShell is PowerShell, AKA PowerShell (6+) based on .NET Core.

                                          Windows PowerShell is exactly that, Windows PowerShell up to 5.1.

                                          So what's the difference actually? I thought it was the same thing.

                                          They are totally different softwares.

                                          PowerShell starts at version 6 (currently 7.x) and is based on .NET CORE.

                                          Windows PowerShell is up to 5.1 and is based on the standard .NET (non-core version), has all the standard Windows management frameworks (5.1) and all that. I don't know all the technical jargon.

                                          But PowerShell and Windows PowerShell are two separate and different products and very much a thing.

                                          Oh, my bad, it really was its name. What a horrible name, lol.

                                          ObsolesceO 1 Reply Last reply Reply Quote 0
                                          • ObsolesceO
                                            Obsolesce @scottalanmiller
                                            last edited by

                                            @scottalanmiller said in Resume Update:

                                            @Obsolesce said in Resume Update:

                                            @Pete-S said in Resume Update:

                                            @Obsolesce said in Resume Update:

                                            @scottalanmiller said in Resume Update:

                                            Make sure technology names are correct.

                                            PowerShell is PowerShell, not Windows PowerShell. "Windows PowerShell" isn't a thing.

                                            No, PowerShell is PowerShell, AKA PowerShell (6+) based on .NET Core.

                                            Windows PowerShell is exactly that, Windows PowerShell up to 5.1.

                                            So what's the difference actually? I thought it was the same thing.

                                            They are totally different softwares.

                                            PowerShell starts at version 6 (currently 7.x) and is based on .NET CORE.

                                            Windows PowerShell is up to 5.1 and is based on the standard .NET (non-core version), has all the standard Windows management frameworks (5.1) and all that. I don't know all the technical jargon.

                                            But PowerShell and Windows PowerShell are two separate and different products and very much a thing.

                                            Oh, my bad, it really was its name. What a horrible name, lol.

                                            Haha, that made me lol.

                                            scottalanmillerS 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 3
                                            • 4
                                            • 5
                                            • 1 / 5
                                            • First post
                                              Last post