1. Quit! #40: Getting Through the Door →

    One thing irritated me, though: it sounds like his assumption is that job postings need not list the position’s salary or a salary range, which should instead be negotiated in the interview. When I was job-hunting, this always drove me nuts.

    I’m sure that’s the case, but as an employer it’s not feasible unless you have a very narrowly defined position. At Crowd Favorite we hire the best people (for our team) we can find. It’s not uncommon for this to result in a change the original definition of the position to fit an awesome candidate (knowing that we need to make another adjustment elsewhere).

    Since the position is flexible, the compensation is as well. I fear that putting out a tight salary range would cause us to lose out on a great potential teammate. Likewise, we don’t post many hard requirements in our job postings; instead we focus on outlining the skills people need to be successful in our environment.

    (Apologies for the meta nature of posting on someone else’s link post – I have not listened to the originanating podcast episode yet.)

  2. I wouldn’t be shocked to see MacBook Pros in “space gray” in the not so distant future.

  3. Institutional Knowledge

    Don’t underestimate the value of your team’s (collective) experience. When new folks come on board you can tell them how you do things and why you do things certain ways. You can share historical anecdotes about the reasons things are done these ways, but there is no way for those new hires to actually have…

  4. Define the Problem Instead of Suggesting a Solution

    Life lesson from running a digital agency: When asking for help, focus your efforts on defining the problem instead of suggesting a solution. The person you’re asking for help from may have solutions you’ve never considered. If my recent experience is any measure, it works equally well when asking a hotel concierge for help getting…