ProfitWell (https://www.profitwell.com) | Backend (Python), Frontend (TypeScript/React), DevOps (Kubernetes) | Mid + Senior level | Boston, MA | Full Time | ONSITE
ProfitWell provides free subscription metrics to help you identify opportunities and then tools to help you reduce churn, optimize pricing, and grow your subscription business end-to-end.
We care a lot about building great products, but also about writing great software. We have high standards for our code, and everything to push goes through a rigorous code review. We're ok if it takes a little longer to get things right because we believe it leads to better products, better software, and happier engineers in the long term. There's obviously a tradeoff between speed and quality, and while we're always trying to find the sweet spot, we tend to err on the side of shipping well designed software.
Related to this, engineers are expected to give input on the product. It's not "here's a spec, go build exactly what it says." We think building great products is a "contact sport," meaning there's typically a lot of (respectful!) debate and refinement over the things we build before they reach their final form. This means pointing out the UI inconsistencies and UX awkwardness when starting to build out the frontend or coming up with novel ways to leverage the immense dataset we have on the backend to drive better outcomes for our customers.
We also do a lot of team activities here. Whether it's trivia or game nights, or lunch with the team, or our bi-weekly lunch & learn where we rotate presenting to the rest of the engineering team on technical topics that are interesting to us. There's always something going on.
Even though you can remove SMS as a 2FA, it looks like Google still asks for an email and phone for "Account recovery options". Probably should remove that as well?
Yes, you should. They demand phones because normal users who aren't being guided through the setup would be likely to lock themselves out of their account without it, but if you know what you're doing you can eliminate the phone dependency.
Or create an email account. It's impossible to sign up to any web email service to be able to send email not just receive if you don't have a phone.
I needed an untraceable email to send from for reasons I won't go into but couldn't create one.
If you're poor but need a webmail account you need a phone. You can't even put in a fake number since you need to reply to the approval link setup email. Gmail, Outlook, Yahoo, everyone one I tried all require a phone.
They may allow you to do that. If you are on an IP that they deem not trustable enough, like if you are on a dynamic IP or come from the wrong country, they'll refuse to create the account without some phone verification (to hinder spammers)
It would be a device that plugs into your car's onboard computer. There are dozens of devices out there that do things on the hardware side that are very similar to what I'm looking for, but just not exactly. I don't think I'm going to get very far asking them to change their products either, since the changes I'd be asking for are too specific to what I want to do.
Does that help you point me in the right direction? It doesn't seem like an overwhelming project for anyone, but none the less, someone would need to dedicate themselves to getting it built, and I just don't know how to find that person.
I also have the chicken/egg scenario here where I'd love to get funding for it, but need to partner up with someone on the hardware side to at least get it to the prototype stage.
By "plugs into your car's onboard computer" do you mean through the OBD port? If so, there are a few open source projects out there. Searching the usual OSS repositories may turn up a hardware engineer who's startup minded. There must be lots in Boston!
ProfitWell provides free subscription metrics to help you identify opportunities and then tools to help you reduce churn, optimize pricing, and grow your subscription business end-to-end.
We care a lot about building great products, but also about writing great software. We have high standards for our code, and everything to push goes through a rigorous code review. We're ok if it takes a little longer to get things right because we believe it leads to better products, better software, and happier engineers in the long term. There's obviously a tradeoff between speed and quality, and while we're always trying to find the sweet spot, we tend to err on the side of shipping well designed software.
Related to this, engineers are expected to give input on the product. It's not "here's a spec, go build exactly what it says." We think building great products is a "contact sport," meaning there's typically a lot of (respectful!) debate and refinement over the things we build before they reach their final form. This means pointing out the UI inconsistencies and UX awkwardness when starting to build out the frontend or coming up with novel ways to leverage the immense dataset we have on the backend to drive better outcomes for our customers.
We also do a lot of team activities here. Whether it's trivia or game nights, or lunch with the team, or our bi-weekly lunch & learn where we rotate presenting to the rest of the engineering team on technical topics that are interesting to us. There's always something going on.
Additional detail on our Built-In-Boston site: https://www.builtinboston.com/job/engineer/midsenior-full-st...
Contact me at michael@profitwell.com