parkerconrad
I tried interviewing for jobs -- but from the perspective of employers, it was unclear what specific skills / experience I had - (most ppl would not have heard of the company I started, so it felt a lot like a 7-year gap on my resume). I was 32, but mostly was only able to interview for entry-level positions. I got very close to a job as a PM at Quora (thank you Marc Bodnick, @ccheever, Adam and Sandra)
We'd pitched 70 different VCs over the course of the co -- I emailed all of them to let them know I was leaving hte company, and asked to meet with them to get advice about my future plans. I only heard back from one person -- Brian Ascher at Venrock, who ultimately b/c an investor in my next co.
I ended up starting another company in part b/c it just didn't seem like there were many other good options.
This has changed a lot -- many cos, from growth-stage startups to stereotypical BigCos really want to hire former founders into positions that have meaningful scope and ownership and impact. At Rippling, we have some crazy ratios here -- around 40 ppl out of 350 are former founders, it's a candidate profile we actively seek out and view it as a badge of honor.
The way this works is that you, as an ADP client, call them up and says "hey, I've asked my HR firm, XYZ-HR, to manage my payroll. Can you create an account for them to access my payroll system?" ADP creates this account, and XYZ-HR then handles all the payroll admin work going forward -- adding employee, terming them, inputting hours worked, managing deductions, etc.
This is how this has worked for years, and it's how thousands of companies do this via ADP. Even today, as an ADP RUN client, you can call in and add any third-party person you want as an admin to your payroll system -- as long as it's not Zenefits. ADP has marketing materials that describe this feature, both for companies and HR / bookkeeping / accounting firms. This is how Zenefits was accessing client's payroll, and doing so in order to take on all the administrative work related to payroll that you don't want to handle. We weren't "hacking" anything. We were doing this at our customers' request, with their full knowledge of what we were doing, and ADP set up these accounts with @zenefits.com email addresses, knowing it was Zenefits.
There is nothing improper about how we were doing this.
This is particularly relevant in your case (an installation error on Aetna's end). One of the biggest problems with health insurance for companies < 1,000 employees is that everything is done via paper / pdf / fax machine. This is of course a pain in the ass, but more importantly it's a source of large and irreducible error. Insurance companies average about 10% to 20% error rates on the stuff that we send them even if Zenefits is 100% correct. These errors aren't unique to Zenefits -- any broker or other company doing this stuff would have them -- and we spend a lot of time following up with carriers to verify, etc....
Here's the important thing -- our growth means we can make insurance companies build APIs for us, some of which are live right now, and many more of which will be live in the coming months. Only with this full electronic integration can these processing errors go away, for us and for everyone else. APIs == zero errors. Existing paper / pdf method can never fully eliminate errors b/c we (zenefits) don't control the guy on Aetna's end who is keying information into their system.
It's small-group right now, each company is its own group. Right now we are CA only but plan to expand rapidly in other states -- although it might take quite some time before we're everywhere.
We don't get paid by 401K companies, so we don't have an incentive to recommend anything other than what we think is awesome for you.
Also, one thing we've promised our early 401K clients -- if they want to work with a 401K company that isn't on our list, we'll build an integration specially for them.
If you need sexual harassment training, & other liability-reducing stuff, TriNet makes a lot of sense.