My take is that Lever's features are well-optimized for companies doing outbound sourcing for roles like engineering (e.g. the extension, snooze features, pipeline structure) and where most hiring is owned by managers who don't have time to devote to mastering recruiting best practices (multi-touch sourcing with Nurture, easy scheduling, pipeline management, email sync, reporting).
Ultimately, you save a lot of money by not having to hire dedicated recruiters and recruiting coordinators, and you actually get a much better candidate experience and hiring effectiveness by having hiring managers and interviewers more closely involved in the process instead of trying to translate them through a separate recruiting team.
You know far more about your needs and are able to evaluate how well software would solve them, and the salespeople you've talked to haven't been worth the time....and that's not normal.
You'd be shocked how bad most people are at evaluating software, especially when it's highly technical. Most people don't even know what a reasonable budget is, what their biggest problems are, what would fix them, and what software is actually doing -- so they rely on cheap self-service products or just take marketing speak at face-value and hope for the best.
And a good salesperson is worth their weight in gold. If you're one of those buyers, salespeople should be much closer to an interviewer or consultant for them: approaching sales calls like research to uncover needs you didn't know you had, introducing you to best practices, and tailoring advice to your specific situation. Their goal is to find a mutual fit and stand by the quality of their solution (and should recommend competitors' products if you wouldn't be happy with it)
Male engineer at Lever here, and I can confirm that we don't make hiring decisions based on gender or gender presentation. It's not only highly illegal, but totally not the point of tracking diversity metrics.
The ultimate goal here is not to build a company with perfect representation of the general population, but to build a company which honestly evaluates and rewards the contributions of all its employees (because we believe that those kinds of companies do build better products, businesses, etc.) and you can't do that unless you're inclusive and consistently fair with everyone in the company.
A number like 50-50 gender balance doesn't mean that we've finished building that company (and no company is ever finished). However, an imbalance of gender or any demographic such as age, race, prior work experience (such as government, enterprise, startup), academic background, parental status, etc. at a company usually indicates that there's a blindspot or bug in a company's hiring or culture and it deserves a closer look.
I'm pretty understanding of occasional bugs, but Zenefits' site has been one of the most consistently buggy pieces of software I've ever used. Every flow has had broken pieces of UI, incorrect form validation, totally wrong calculations, or some other frustrating flaw.
It's an incredibly useful product (and leagues better than the competition) but when they can't even calculate your 401(k) contribution correctly, imagine what's going on behind the scenes...I'm trusting them with a lot of financial and personal information and it erodes a lot of the trust & confidence I would have in them to see such shoddy work.
I've been hit with this too and it's not pretty at all.
If anyone else is concerned about this, you should talk with your CEO/legal team about early exercise options which can remove a lot of the risk of massive tax liabilities. From my understanding, some companies offer an early exercise option where you pre-purchase the shares and then instead of being able to buy the shares after they've vested, the company instead gradually loses the right to buy them back at the original strike price.
I'm not a tax lawyer, but Google "section 83(b) election" and you'll find more information.
Magoosh ~ Berkeley, CA ~ Software Engineer (Rails + more)
###
We’re looking for our third full-stack developer to contribute to building the future of test prep.
Our engineering team is small (two developers + you), but we have a huge impact! We already help millions of students around the world study and prepare for their standardized tests with our popular web and mobile apps, and more are signing up every minute.
From day one, you’ll own projects and contribute directly to code running in production and we highly value collaboration, positive feedback, and mentorship.
Our projects usually involve close collaboration with other departments, which means you’ll learn far more than just engineering. The whole company is around 25 people, so you’ll know everyone in the office and have a real say in Magoosh’s goals and business decisions.
If you're an engineer excited about building edTech products, I'd love to talk :)
We’re looking for our third full-stack developer to help build the future of test prep.
Magoosh’s Engineering team is small, but we have a huge impact! We already help millions of students around the world study and prepare for their standardized tests with our popular web and mobile apps, and more are signing up every minute.
From day one, you’ll own projects and contribute directly to code running in production and we highly value collaboration, positive feedback, and mentorship.
Hey aboodman, I was wondering if you've got some other recommended reading for designing offline applications. I'd love to read more about common design patterns.
Junior Developer at Magoosh (http://magoosh.com) -- Berkeley, CA (interns welcome too)
=-=-=-=-==-=
We’re looking for another full-stack developer to join our team building the future of test prep.
Our product helps tens of thousands of students around the world study for their GRE, GMAT, SAT and TOEFL exams and since we're such a small engineering team (in a company of almost 20), you'll be contributing to production from the first day. We ship early and iterate with feedback. We have fun all the time and meetings only when absolutely necessary.
You’ll work with Zach (https://github.com/zmillman) and Zack (https://github.com/zackm) to release new features and keep everything running smoothly. We use Ruby on Rails, CoffeeScript, AngularJS and PhoneGap, code reviews on GitHub, continuous integration with Semaphore, and deploy several times per day to AWS with Capistrano. There's a healthy mix of front-end and back-end work and we're constantly learning new tools and techniques to make us more productive.
I knew I recognized you from somewhere! For those who don't know, nirvdrum's one of the primary contributors to rubber https://github.com/rubber/rubber (it's a pretty critical part of our current infrastructure)
In my book at least, you've already contributed a huge amount to open source and I wouldn't worry about needing to do more :)
Ultimately, you save a lot of money by not having to hire dedicated recruiters and recruiting coordinators, and you actually get a much better candidate experience and hiring effectiveness by having hiring managers and interviewers more closely involved in the process instead of trying to translate them through a separate recruiting team.