RPeres | 1 year ago | on: Ask HN: Former employees' RSUs at risk after startup's IPO
RPeres's comments
RPeres | 2 years ago | on: Ask HN: What apps have you created for your own use?
RPeres | 3 years ago | on: Ask HN: Who is hiring? (November 2022)
Vital provides a single API for all your wearables data. We standardise your healthcare data across various wearables sources and give you a cleaned and compliant API to use.
Apply here: https://vital-api.notion.site/Senior-Backend-Engineer-97c197...
RPeres | 3 years ago | on: Automate pull requests in 1 minute with Reviewpad
RPeres | 3 years ago | on: Ask HN: Example of a good dev standards document?
RPeres | 4 years ago | on: Hopin Has Round of Layoffs
RPeres | 4 years ago | on: Dropbox Engineering Career Framework
Different people want different things. A lot of people want to code and to be left alone. A lot of other people don't. They want to feel they are progressing towards something. Good frameworks usually state: we consider you as a senior if you are doing X & Y consistently. This helps people aligning their actions/work with a level. The group of people that usually don't care about this things, might start doing so, when their title (e.g. "Software Engineer") lacks the "senior" keyword and they are applying for a senior role elsewhere. This might seem nitpicking, but you would be surprised how many people don't even pass the first screening because they don't have the "senior" prefix. In bigger companies monetary compensation is assigned according to the person's level. In smaller companies, not so much. Everyone has the same title, and people can have significantly different salaries. A good career framework makes it very clear to everyone that if you want to earn between X and Y you need to be at a particular level.
As for the framework itself, I am big fan of giving examples. Say for instance on IC3: "I’m able to navigate ambiguity and remain resilient through ups and downs". I would love if they assigned a somewhat real example: "I am able to complete tasks, even when the acceptance criteria is not 100% clear.". They did well with the separation of the different functions: QA, Software Eng, Security Eng & Reliability Eng. A lot of places bundle some of these together and leave people scratching their head.
RPeres | 4 years ago | on: Show HN: I wrote the book Building Mobile Apps at Scale
RPeres | 6 years ago | on: Running Tips
RPeres | 8 years ago | on: On being an Engineering Manager
RPeres | 11 years ago | on: Paasifier – Find the best PaaS for your app
RPeres | 12 years ago | on: KirKos: App Development Under 24h