matisoffn

Depends on the operation. For most operations there are backwards compatible options that generally result in a 2-step process.

Soundcloud (I don't work there) developed something in Ruby for online database migrations that copies the table and uses triggers to handle everything. Note that this only works for MySQL. For PostgreSQL or others, the best option is taking a backwards compatible approach.

https://github.com/soundcloud/lhm

I worked multiple years in an organization led by the founding team. Just dropping a note to say that the team is top-notch, and they are maniacal about listening to customer feedback.

They advocated for and implemented a strikingly similar product within the organization, and it was used for all deployments: development, test, staging, production, etc. The system was a crucial aspect of everyday development and extraordinarily helpful for working with cross-functional partners.

Like Sidekiq but for Python. Neat.

The order of magnitude is important. In your example it's a windfall. But considering the dilution with exits at 1b or 10b it's a different story - the exit will surely be millions.

The strategy should differ based on the role and company, as well as your years of experience and accomplishments. I doubt there's a one size fits all approach.

Yeah, they have sessions for culture fit that they call the "Googley" or "Googleyness" interview. You can find content on Google itself, of course.

Algorithms and System Design on the technical side.

Location: Los Angeles

Remote: Yes, if it will work with the client.

Willing to relocate: No, only looking for local or remote part-time contract work

Technologies: Ruby, Ruby on Rails, React, Vue.js, ES6, Webpack, AWS, Heroku

CV: Experienced in building technology for the financial sector. Have built and maintained payments processing software that does $80mm in annual revenue. E-mail me for my CV.

Email: noah at matisoff dot me

Which side is behaving inappropriately? Hard to tell..

Riot is a good one! Awesome location and fun company to work for.

You got a user here, definitely need something like this.

Answering for @reiderrider, the bulk of life insurance is still sold face-to-face and purchased from an agent or agency local to the consumer.

Not only could big banks + financial institutions plug in our js to sell life insurance online (from quoting -> application -> signature & medical exam), but also smaller agents/agencies that do business locally could accept online apps. Currently, agents meet in person and/or have plenty of phone calls with a client to figure out what coverage they need and then they sell the policy.

With our product, agents can direct their clients to their website which will walk the consumer through the process.

The Stripe analogy makes sense because Stripe & PayPal make it so easy for companies to accept payments online via their HTML button/JS script, which is what we are trying to do here. They also (both cos) provide great dashboards to the consumer (an insurance agent/agency for us) to track their data (which is in the pipeline for us).