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

    Salary, Responsibilities, or Title?

    IT Careers
    8
    41
    462
    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.
    • IRJ
      IRJ @RamblingBiped last edited by

      @RamblingBiped said in Salary, Responsibilities, or Title?:

      When it comes to disclosing previous salaries I've been pretty open when I am actively pursuing opportunities. I'm not going to devote hours of conversation and meetings with an organization just to find out the pay and benefits are not where they need to be. That's disrespectful of their time, and a waste of mine. I'll usually discuss that within the first couple of meetings with a recruiter or HR representative, and if appropriate I disclose it without prompting.

      I agree with you about time wasting which is why it's one of my first questions. As in salary is discussed on first contact about the position.

      I dont agree about disclosing my old salary. Why does it even matter? My requirements now are X which is obviously more than my old salary of Y. Only X is relevant in a conversation with a potential employer. They should already realize that money is a big motivating factor especially in Cloud architecture and DevOps. Many employers try to hire people for 6 months + for those positions so they know they have to open their pockets.

      Obsolesce RamblingBiped 2 Replies Last reply Reply Quote 0
      • Obsolesce
        Obsolesce @IRJ last edited by

        @IRJ said in Salary, Responsibilities, or Title?:

        @RamblingBiped said in Salary, Responsibilities, or Title?:

        When it comes to disclosing previous salaries I've been pretty open when I am actively pursuing opportunities. I'm not going to devote hours of conversation and meetings with an organization just to find out the pay and benefits are not where they need to be. That's disrespectful of their time, and a waste of mine. I'll usually discuss that within the first couple of meetings with a recruiter or HR representative, and if appropriate I disclose it without prompting.

        I agree with you about time wasting which is why it's one of my first questions. As in salary is discussed on first contact about the position.

        I dont agree about disclosing my old salary. Why does it even matter? My requirements now are X which is obviously more than my old salary of Y. Only X is relevant in a conversation with a potential employer. They should already realize that money is a big motivating factor especially in Cloud architecture and DevOps. Many employers try to hire people for 6 months + for those positions so they know they have to open their pockets.

        I always get the salary range even before I consider discussing the job with anyone in any real context.

        They know anyone worth a damn is going to ask straight away anyways.

        I never reveal my previous salary. I'm not saying I never will, but during recruitment in the past I haven't. When asked, I've redirected with stating something along the lines of the salary range I'm looking for and it was never more than that.

        I'll keep leaving it to my gut to decide after judging the situation, but so far it's been as mentioned.

        IRJ scottalanmiller 3 Replies Last reply Reply Quote 2
        • IRJ
          IRJ @Obsolesce last edited by

          @Obsolesce said in Salary, Responsibilities, or Title?:

          @IRJ said in Salary, Responsibilities, or Title?:

          @RamblingBiped said in Salary, Responsibilities, or Title?:

          When it comes to disclosing previous salaries I've been pretty open when I am actively pursuing opportunities. I'm not going to devote hours of conversation and meetings with an organization just to find out the pay and benefits are not where they need to be. That's disrespectful of their time, and a waste of mine. I'll usually discuss that within the first couple of meetings with a recruiter or HR representative, and if appropriate I disclose it without prompting.

          I agree with you about time wasting which is why it's one of my first questions. As in salary is discussed on first contact about the position.

          I dont agree about disclosing my old salary. Why does it even matter? My requirements now are X which is obviously more than my old salary of Y. Only X is relevant in a conversation with a potential employer. They should already realize that money is a big motivating factor especially in Cloud architecture and DevOps. Many employers try to hire people for 6 months + for those positions so they know they have to open their pockets.

          They know anyone worth a damn is going to ask straight away anyways.

          Yep lol

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

            @Obsolesce said in Salary, Responsibilities, or Title?:

            I always get the salary range even before I consider discussing the job with anyone in any real context.

            Oh yeah, at least a ballpark. Because that's the primary way that people/companies define the "level" of a job. A "Senior UNIX Admin" can mean $60K or $300K in the same market. Just one is a company that tops out at "entry level" and the other likely starts at "pretty darn senior." Only salary really clearly informs you what the real level and expectations are.

            And as salary is the primary reason that people work, knowing the expectation of compensation is kind of the foundation of even being willing to have a discussion about employment.

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

              @Obsolesce said in Salary, Responsibilities, or Title?:

              I never reveal my previous salary. I'm not saying I never will, but during recruitment in the past I haven't. When asked, I've redirected with stating something along the lines of the salary range I'm looking for and it was never more than that.

              I've walked out when requested before.

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

                @scottalanmiller said in Salary, Responsibilities, or Title?:

                @Obsolesce said in Salary, Responsibilities, or Title?:

                I always get the salary range even before I consider discussing the job with anyone in any real context.

                Only salary really clearly informs you what the real level and expectations are.

                I like that statement because job descriptions are so ridiculous, they virtually mean nothing.

                Obsolesce 1 Reply Last reply Reply Quote 1
                • Obsolesce
                  Obsolesce @IRJ last edited by

                  @IRJ said in Salary, Responsibilities, or Title?:

                  @scottalanmiller said in Salary, Responsibilities, or Title?:

                  @Obsolesce said in Salary, Responsibilities, or Title?:

                  I always get the salary range even before I consider discussing the job with anyone in any real context.

                  Only salary really clearly informs you what the real level and expectations are.

                  I like that statement because job descriptions are so ridiculous, they virtually mean nothing.

                  I've seen IT manager for $40k lol. But that's a fake title anyways.

                  IRJ scottalanmiller 2 Replies Last reply Reply Quote 0
                  • IRJ
                    IRJ @Obsolesce last edited by

                    @Obsolesce said in Salary, Responsibilities, or Title?:

                    @IRJ said in Salary, Responsibilities, or Title?:

                    @scottalanmiller said in Salary, Responsibilities, or Title?:

                    @Obsolesce said in Salary, Responsibilities, or Title?:

                    I always get the salary range even before I consider discussing the job with anyone in any real context.

                    Only salary really clearly informs you what the real level and expectations are.

                    I like that statement because job descriptions are so ridiculous, they virtually mean nothing.

                    I've seen IT manager for $40k lol. But that's a fake title anyways.

                    Probably one man IT guy for 100 employees lol

                    P scottalanmiller 2 Replies Last reply Reply Quote 0
                    • P
                      pmoncho @IRJ last edited by

                      @IRJ said in Salary, Responsibilities, or Title?:

                      @Obsolesce said in Salary, Responsibilities, or Title?:

                      @IRJ said in Salary, Responsibilities, or Title?:

                      @scottalanmiller said in Salary, Responsibilities, or Title?:

                      @Obsolesce said in Salary, Responsibilities, or Title?:

                      I always get the salary range even before I consider discussing the job with anyone in any real context.

                      Only salary really clearly informs you what the real level and expectations are.

                      I like that statement because job descriptions are so ridiculous, they virtually mean nothing.

                      I've seen IT manager for $40k lol. But that's a fake title anyways.

                      Probably one man IT guy for 100 employees lol

                      Most likely.

                      There are also situations where there are SME's that have 100 employees, with X remote business clients that have a 2-3 person IT department employees depending upon the services they provide. If that is the case, is the person managing the other 2+ techs considered to be a manager?

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

                        @IRJ It mattered in my most recent offer because I'm relocating from the Bay Area to the Midwest. I offered my salary up in the conversation because it was useful when discussing total compensation as it relates to what I'm currently making, and where I want to be with the position I was interviewing for. The cost of living in the area of the Midwest I'm moving to is drastically different than most larger Metropolitan areas, let alone the Bay Area / Silicon Valley. I think it helped them put together an acceptable offer quicker than if I had not volunteered the information.

                        I do agree with you though, your current salary shouldn't be a point of discussion or contention. If a recruiter or hiring manager were to make it a point to probe me on the topic it would be an immediate red flag.

                        Obsolesce Dashrender scottalanmiller 3 Replies Last reply Reply Quote 1
                        • Obsolesce
                          Obsolesce @RamblingBiped last edited by

                          @RamblingBiped said in Salary, Responsibilities, or Title?:

                          @IRJ It mattered in my most recent offer because I'm relocating from the Bay Area to the Midwest. I offered my salary up in the conversation because it was useful when discussing total compensation as it relates to what I'm currently making, and where I want to be with the position I was interviewing for. The cost of living in the area of the Midwest I'm moving to is drastically different than most larger Metropolitan areas, let alone the Bay Area / Silicon Valley. I think it helped them put together an acceptable offer quicker than if I had not volunteered the information.

                          I do agree with you though, your current salary shouldn't be a point of discussion or contention. If a recruiter or hiring manager were to make it a point to probe me on the topic it would be an immediate red flag.

                          What if you said you made $100k higher than you told them? Did they really not know the worth of the position they were hiring for? Did they know what they were hiring for?

                          1 Reply Last reply Reply Quote 0
                          • Dashrender
                            Dashrender @RamblingBiped last edited by

                            @RamblingBiped said in Salary, Responsibilities, or Title?:

                            @IRJ It mattered in my most recent offer because I'm relocating from the Bay Area to the Midwest. I offered my salary up in the conversation because it was useful when discussing total compensation as it relates to what I'm currently making, and where I want to be with the position I was interviewing for. The cost of living in the area of the Midwest I'm moving to is drastically different than most larger Metropolitan areas, let alone the Bay Area / Silicon Valley. I think it helped them put together an acceptable offer quicker than if I had not volunteered the information.

                            I do agree with you though, your current salary shouldn't be a point of discussion or contention. If a recruiter or hiring manager were to make it a point to probe me on the topic it would be an immediate red flag.

                            yeah, location is huge - the housing difference is a complete killer.

                            3,000 sqft home in Midwest (not Chicago or Minneapolis) is $250K for a nice place (or possibly less),
                            but Bay area - 2.5 Million. or maybe less.

                            JaredBusch 1 Reply Last reply Reply Quote 0
                            • JaredBusch
                              JaredBusch @Dashrender last edited by

                              @Dashrender said in Salary, Responsibilities, or Title?:

                              @RamblingBiped said in Salary, Responsibilities, or Title?:

                              @IRJ It mattered in my most recent offer because I'm relocating from the Bay Area to the Midwest. I offered my salary up in the conversation because it was useful when discussing total compensation as it relates to what I'm currently making, and where I want to be with the position I was interviewing for. The cost of living in the area of the Midwest I'm moving to is drastically different than most larger Metropolitan areas, let alone the Bay Area / Silicon Valley. I think it helped them put together an acceptable offer quicker than if I had not volunteered the information.

                              I do agree with you though, your current salary shouldn't be a point of discussion or contention. If a recruiter or hiring manager were to make it a point to probe me on the topic it would be an immediate red flag.

                              yeah, location is huge - the housing difference is a complete killer.

                              3,000 sqft home in Midwest (not Chicago or Minneapolis) is $250K for a nice place (or possibly less),
                              but Bay area - 2.5 Million. or maybe less.

                              Chicagoland suburb, Schaumburg, 1,500sqft house = $280k

                              Dashrender 1 Reply Last reply Reply Quote 0
                              • Dashrender
                                Dashrender @JaredBusch last edited by

                                @JaredBusch said in Salary, Responsibilities, or Title?:

                                @Dashrender said in Salary, Responsibilities, or Title?:

                                @RamblingBiped said in Salary, Responsibilities, or Title?:

                                @IRJ It mattered in my most recent offer because I'm relocating from the Bay Area to the Midwest. I offered my salary up in the conversation because it was useful when discussing total compensation as it relates to what I'm currently making, and where I want to be with the position I was interviewing for. The cost of living in the area of the Midwest I'm moving to is drastically different than most larger Metropolitan areas, let alone the Bay Area / Silicon Valley. I think it helped them put together an acceptable offer quicker than if I had not volunteered the information.

                                I do agree with you though, your current salary shouldn't be a point of discussion or contention. If a recruiter or hiring manager were to make it a point to probe me on the topic it would be an immediate red flag.

                                yeah, location is huge - the housing difference is a complete killer.

                                3,000 sqft home in Midwest (not Chicago or Minneapolis) is $250K for a nice place (or possibly less),
                                but Bay area - 2.5 Million. or maybe less.

                                Chicagoland suburb, Schaumburg, 1,500sqft house = $280k

                                that's why I excluded chicago and Minneapolis. I'm not sure about Kansas City - I'm sure there are places where 1500 sqft cost 300K+...

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

                                  @Dashrender said in Salary, Responsibilities, or Title?:

                                  @JaredBusch said in Salary, Responsibilities, or Title?:

                                  @Dashrender said in Salary, Responsibilities, or Title?:

                                  @RamblingBiped said in Salary, Responsibilities, or Title?:

                                  @IRJ It mattered in my most recent offer because I'm relocating from the Bay Area to the Midwest. I offered my salary up in the conversation because it was useful when discussing total compensation as it relates to what I'm currently making, and where I want to be with the position I was interviewing for. The cost of living in the area of the Midwest I'm moving to is drastically different than most larger Metropolitan areas, let alone the Bay Area / Silicon Valley. I think it helped them put together an acceptable offer quicker than if I had not volunteered the information.

                                  I do agree with you though, your current salary shouldn't be a point of discussion or contention. If a recruiter or hiring manager were to make it a point to probe me on the topic it would be an immediate red flag.

                                  yeah, location is huge - the housing difference is a complete killer.

                                  3,000 sqft home in Midwest (not Chicago or Minneapolis) is $250K for a nice place (or possibly less),
                                  but Bay area - 2.5 Million. or maybe less.

                                  Chicagoland suburb, Schaumburg, 1,500sqft house = $280k

                                  that's why I excluded chicago and Minneapolis. I'm not sure about Kansas City - I'm sure there are places where 1500 sqft cost 300K+...

                                  That must be nice.

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

                                    @Obsolesce said in Salary, Responsibilities, or Title?:

                                    @Dashrender said in Salary, Responsibilities, or Title?:

                                    @JaredBusch said in Salary, Responsibilities, or Title?:

                                    @Dashrender said in Salary, Responsibilities, or Title?:

                                    @RamblingBiped said in Salary, Responsibilities, or Title?:

                                    @IRJ It mattered in my most recent offer because I'm relocating from the Bay Area to the Midwest. I offered my salary up in the conversation because it was useful when discussing total compensation as it relates to what I'm currently making, and where I want to be with the position I was interviewing for. The cost of living in the area of the Midwest I'm moving to is drastically different than most larger Metropolitan areas, let alone the Bay Area / Silicon Valley. I think it helped them put together an acceptable offer quicker than if I had not volunteered the information.

                                    I do agree with you though, your current salary shouldn't be a point of discussion or contention. If a recruiter or hiring manager were to make it a point to probe me on the topic it would be an immediate red flag.

                                    yeah, location is huge - the housing difference is a complete killer.

                                    3,000 sqft home in Midwest (not Chicago or Minneapolis) is $250K for a nice place (or possibly less),
                                    but Bay area - 2.5 Million. or maybe less.

                                    Chicagoland suburb, Schaumburg, 1,500sqft house = $280k

                                    that's why I excluded chicago and Minneapolis. I'm not sure about Kansas City - I'm sure there are places where 1500 sqft cost 300K+...

                                    That must be nice.

                                    In Omaha 1500 sqft costs 90-150, pretty damned cheap.

                                    Can you get a 1500 sqft home for $300K+ sure, with marble everywhere, granite everything, etc.

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

                                      @Obsolesce said in Salary, Responsibilities, or Title?:

                                      @IRJ said in Salary, Responsibilities, or Title?:

                                      @scottalanmiller said in Salary, Responsibilities, or Title?:

                                      @Obsolesce said in Salary, Responsibilities, or Title?:

                                      I always get the salary range even before I consider discussing the job with anyone in any real context.

                                      Only salary really clearly informs you what the real level and expectations are.

                                      I like that statement because job descriptions are so ridiculous, they virtually mean nothing.

                                      I've seen IT manager for $40k lol. But that's a fake title anyways.

                                      I just (and I think most people do subconsciously) consider "IT Manager" to mean "Entry Level Generalist." It's a title almost universally used for one man shops where the person is on their very first rodeo and mostly just hiring out. I've pretty much never seen a shop of any size retain that title, mostly because the stigma is so strong. If I see that title, I just assume that they are in their first posting after having interned or graduated, and probably after a year or so of mid-$30Ks doing straight helpdesk in a slightly larger firm and have graduated to the lowest rank of one man shop.

                                      I had a friend, who we can't keep talking because she was so offensive to people in IT, who always bragged about her husband the "IT manager". The thing he did that was so brilliant and made him a tech god? He convinced the company to use email. He didn't implement the email or do anything IT, he just told them about email and got them to try it out. That was his laurels and his career had rested on it for twenty years!

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

                                        @IRJ said in Salary, Responsibilities, or Title?:

                                        @Obsolesce said in Salary, Responsibilities, or Title?:

                                        @IRJ said in Salary, Responsibilities, or Title?:

                                        @scottalanmiller said in Salary, Responsibilities, or Title?:

                                        @Obsolesce said in Salary, Responsibilities, or Title?:

                                        I always get the salary range even before I consider discussing the job with anyone in any real context.

                                        Only salary really clearly informs you what the real level and expectations are.

                                        I like that statement because job descriptions are so ridiculous, they virtually mean nothing.

                                        I've seen IT manager for $40k lol. But that's a fake title anyways.

                                        Probably one man IT guy for 100 employees lol

                                        Probably for more like 20-30.

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

                                          @pmoncho said in Salary, Responsibilities, or Title?:

                                          @IRJ said in Salary, Responsibilities, or Title?:

                                          @Obsolesce said in Salary, Responsibilities, or Title?:

                                          @IRJ said in Salary, Responsibilities, or Title?:

                                          @scottalanmiller said in Salary, Responsibilities, or Title?:

                                          @Obsolesce said in Salary, Responsibilities, or Title?:

                                          I always get the salary range even before I consider discussing the job with anyone in any real context.

                                          Only salary really clearly informs you what the real level and expectations are.

                                          I like that statement because job descriptions are so ridiculous, they virtually mean nothing.

                                          I've seen IT manager for $40k lol. But that's a fake title anyways.

                                          Probably one man IT guy for 100 employees lol

                                          Most likely.

                                          There are also situations where there are SME's that have 100 employees, with X remote business clients that have a 2-3 person IT department employees depending upon the services they provide. If that is the case, is the person managing the other 2+ techs considered to be a manager?

                                          SMEs are never managers, it would be crazy. A manager makes way, way less than an SME. An SME would never waste their time doing that, they'd lose too much money.

                                          If you have two people who each need 50% of a manager's time, those are some pretty worthless employees. Like completely useless. Fire everyone, hire one or two competent people with no manager.

                                          And SME with two more junior people who all work together would likely be a lead, but not a manager.

                                          1 Reply Last reply Reply Quote 1
                                          • scottalanmiller
                                            scottalanmiller @RamblingBiped last edited by

                                            @RamblingBiped said in Salary, Responsibilities, or Title?:

                                            @IRJ It mattered in my most recent offer because I'm relocating from the Bay Area to the Midwest. I offered my salary up in the conversation because it was useful when discussing total compensation as it relates to what I'm currently making, and where I want to be with the position I was interviewing for. The cost of living in the area of the Midwest I'm moving to is drastically different than most larger Metropolitan areas, let alone the Bay Area / Silicon Valley. I think it helped them put together an acceptable offer quicker than if I had not volunteered the information.

                                            I do agree with you though, your current salary shouldn't be a point of discussion or contention. If a recruiter or hiring manager were to make it a point to probe me on the topic it would be an immediate red flag.

                                            Talking current salary is a big tool when talking about relocation and parity needs.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post