3 ms·

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

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!