Our mission is to transform education by democratizing learning and empowering anyone to become a teacher.
There are some people who like a challenge, and then there's someone who joins Skillshare.
Think about all the moments in history when people said "it couldn't be done". Being an engineer at Skillshare is for the people who defy these remarks, lead the charge and as a result change the world.
As an Engineer, you'll be joining a fast-paced engineering team that identify and solve problems from conception to deployment daily. The product we build supports the fast-growing Skillshare community at large, at scale and you'll be leading its evolution into the world.
Skillshare is a small yet fast-growing NYC-based web startup that is working on creating a platform to learn anything, from anyone. Our mission is to flip the traditional notion of education on its head and revolutionize learning.
We're looking for Engineers / Developers to add to our Tech team.
You will have the opportunity to work directly with our co-founders, both of whom have worked at successful companies in the past, including: OMGPOP, Hot Potato (acq by Facebook), Behance, and Razorfish.
It's hard to give a "right answer" because "it depends."
But in general, IMO, it's best to keep things as simple as possible to get a user from point A-to-B. ie. ask yourself why you want the user to sign up, and what do you want them to do after?
With this in mind, I prefer email+pw (and maybe a few other fields depending on your needs). No pw repeat. No email confirmation.
Just my 2 cents.
And to add to the mix.. curious what others think once Facebook / Twitter / etc SSO are added to the mix?
