ParachuteHome | Venice, Los Angeles - ONSITE | Full Stack Engineer
Parachute is looking for a Sr Software Engineer to lead the development of the platform which powers the operation of the business. The engineer will be joining a small and growing digital team. This role will require general software development skills which will improve supply chain, commerce, and back-office functions.
The Sr Software Engineer will partner with Digital Product Management, Customer Experience, Supply Chain, Fulfillment, and Marketing team to build the foundation of Parachute's business. The Sr Software Engineer will be responsible for technical leadership of software platform, from gathering requirement, technical design, implementation, and maintenance with a strong emphasis on usability.
The Sr Software Engineer understands direct to consumer business and will turn complex requests into scalable software solutions. Sr Software Engineer needs to show initiative solving important business problems.
The stack needs to be build from the ground up, so this is the perfect opportunity to make big/important decisions on technology adoption at a startup.
Microsoft Antitrust nightmare that probably set them back 5 years.
Google for invading our privacy, they are still fighting big important battles in Europe.
Facebook for similar privacy invasion, the whole beacon debacle.
There are a lot of things that they probably did wrong, but not to the extend that the press is picturing it.
Craigslist: That lawsuit came well over a decade after it launched, so that's not an example of something startups are forced to do to succeed.
Github: The point I'm arguing against is the idea that startups have to use exploitative and legally questionably business practices to succeed. This Github thing sucks, but it doesn't really have anything to do with business practices, and obviously nobody is arguing that startup leaders have to to be sexist to succeed.
PayPal: That scandal looks like it's related to PayPal Credit, which they acquired a decade after PayPal was founded. Not an example of something startups have to do to succeed.
Twitter: This is somewhat debatable, but it's a reasonable point. Maybe Twitter wouldn't have succeeded if it tried to stamp out harassment early on.
Square: Similar to Github. This sucks, but it's not really relevant to the point I'm trying to make. It is possible and relatively common for a startup to find massive success without relying on exploitation and potentially illegal business practices.
I would like to add that Square internally has a very oft-repeated (and somewhat tongue-in-cheek) mantra of "break the rules, not the law", and IMO a pretty strong moral compass in general.
Absolutely aggreed with this. We still have to pay a 5 to 10% task to get the conference call going.
Chime is the absolute good step in the right direction, however we will need need a layer on top to solve for all conference call systems.
There are three pieces that needs to be figured out to make this work well:
1. How do you deal with (non?) presence? Are you joining from the AV hardware?
2. How do you deal with PSTN?
3. How do you deal with other VoIP solutions out there.
Finishing things impossible. When do you know it's finished? When it's dead? It's not bad to start something and table it. The amount of time "that thing" comes back to you is probably the best filter for you get it moving. If it does not come back to you, it probably means it's not important to you, or not important to anyone else.
Just use pattern recognition to spend the right amount of time on the right idea.
love the idea, but logins are not dead, you just piggy backed on device/passcode combination instead of email/password combination.
PS: I have always wondered why PINS from debit card are 4 digits, and some random consumer product will ask you for a crazy complex password with at least 8 characters.
As the story goes, when John Shepherd-Barron[1] was working on the original ATM system, he originally planned 6 digits, but reduced it to 4 because his wife wasn't able to consistently recall a 6 digit random number.
If true (and it sounds at least plausible), then the sheer number of legacy devices that expect a 4 digit PIN (including hardware crypto modules, which cost an absolute fortune to design and verify)
And, of course, a numeric keypad is much smaller and easier to design around than a full qwerty (and probably internationalises better as well)
The Cambridge Uni security group have a nice paper on PIN security in more detail, if you're interested[2].
I think 4 digit pins are so prevalent because they're easy to remember. As they get longer and harder to remember, people are more likely to write them down etc.
Parachute is looking for a Sr Software Engineer to lead the development of the platform which powers the operation of the business. The engineer will be joining a small and growing digital team. This role will require general software development skills which will improve supply chain, commerce, and back-office functions.
The Sr Software Engineer will partner with Digital Product Management, Customer Experience, Supply Chain, Fulfillment, and Marketing team to build the foundation of Parachute's business. The Sr Software Engineer will be responsible for technical leadership of software platform, from gathering requirement, technical design, implementation, and maintenance with a strong emphasis on usability.
The Sr Software Engineer understands direct to consumer business and will turn complex requests into scalable software solutions. Sr Software Engineer needs to show initiative solving important business problems.
The stack needs to be build from the ground up, so this is the perfect opportunity to make big/important decisions on technology adoption at a startup.
Send a note to careers@parachutehome.com