12 ms·

Flip (https://flip.lease https://flip.lease) | Backend Engineer | New York | REMOTE, SALARY:100k-140k Flip is the easiest way to sublet or get out of your leas

Flip (https://flip.lease https://flip.lease) | Backend Engineer | New York | REMOTE, SALARY:100k-140k Flip is the easiest way to sublet or get out of your lease. We're growing quickly, just raised new funding from Union Square Ventures and are hiring a small team (5-7) of talented product engineers. We care a lot about how our product looks and feels. We're looking for people that love to work on consumer facing products and care a lot about the details. We're a team of 90% engineers, so you'll have a lot of freedom to execute and flexibility in hours. We pride ourselves on few meetings. We're focused on creating an amazing experience for renting any space, and we're building out every tool core to that experience. We're hiring for: * Backend data engineer (we use microservices, so we're open to many languages but Node experience is necessary for working with our API) Apply here: https://angel.co/flipyourlease https://angel.co/flipyourlease or reach out directly to roger@flip.lease with a portfolio (we don't care about resumes as much as pure output). Cultures we look to emulate are Stripe and Airbnb, so if you like and respect those companies give us a shout :) Some of our current team: https://dribbble.com/BurakAslan https://dribbble.com/BurakAslan https://dribbble.com/jon-hargreaves https://dribbble.com/jon-hargreaves https://dribbble.com/owensbla https://dribbble.com/owensbla (Our head of API eng!) and me! https://dribbble.com/RDGthree https://dribbble.com/RDGthree

pedrohidalgo 9y ago
Do you know that most Backend Engineers doesn't have portfolio because almost all the work is not accessible to the public via internet? what do you think about this? am I missing something?
- rdgthree 9y ago
  Usually backend engineers have some OSS work or side projects they can share. Even if that isn't the case, there is usually something they've done at work they can discuss, if it isn't the pure code. We're not looking for engineers that purely do work for their employer and then turn it off when they head home. Since this will be our ~8th employee, they need to be ready to really dive into the work, and those people tend to have a portfolio. Of course, I'm open to people without one - there needs to be a stronger pitch than just a resume. Hopefully that makes sense!
  - pedrohidalgo 9y ago
    Thanks for the reply. In my case I worked on several side projects, i.e: https://itkdb.com https://itkdb.com and https://github.com/pedrohidalgo/pleasure https://github.com/pedrohidalgo/pleasure But the quality of my open source and side projects can't be compared to the quality of my daily job because of time and resources issues. So I still think that my portfolio as a backend developer won't be good enough because the awesome work is closed source and webapps are not accessible to the outside world. When you say: "there is usually something they've done at work they can discuss" then you're not talking about portfolio. Thanks again!

pedrohidalgo 9y ago

Do you know that most Backend Engineers doesn't have portfolio because almost all the work is not accessible to the public via internet? what do you think about this? am I missing something?

rdgthree 9y ago
Usually backend engineers have some OSS work or side projects they can share. Even if that isn't the case, there is usually something they've done at work they can discuss, if it isn't the pure code. We're not looking for engineers that purely do work for their employer and then turn it off when they head home. Since this will be our ~8th employee, they need to be ready to really dive into the work, and those people tend to have a portfolio. Of course, I'm open to people without one - there needs to be a stronger pitch than just a resume. Hopefully that makes sense!
- pedrohidalgo 9y ago
  Thanks for the reply. In my case I worked on several side projects, i.e: https://itkdb.com https://itkdb.com and https://github.com/pedrohidalgo/pleasure https://github.com/pedrohidalgo/pleasure But the quality of my open source and side projects can't be compared to the quality of my daily job because of time and resources issues. So I still think that my portfolio as a backend developer won't be good enough because the awesome work is closed source and webapps are not accessible to the outside world. When you say: "there is usually something they've done at work they can discuss" then you're not talking about portfolio. Thanks again!