72 karma · joined November 12, 2016
Follow-up question: how do you define if founders can do that? Is it how they talk (credibility is something hard to image without context)? Maybe they need talk about numbers & future plans?
I'm curious to understand, what is important to show in the job description and tell during the interview with the engineers.
Some side note: in our founding team we have both business and engineering expertise. We talk about this from the perspective "what we can teach you" but not from "look, we can deliver result".
and when we bought .io 2.5 years we spent several days looking for a cheaper option. For dev tool having some shitty website name or provider is suck
You can't find good free website names. So in our case, we took .io domain, which costs us $50/year. That's very expensive, but we have branded website name on .io
After the year it will cost $35, which is still a nice deal. Hope, it will be useful for someone.
But what I see, is that all candidates for our iOS job postings were around 20-27y.o. Honestly, I'm not sure if we would hire older developer to work in our team. Not being mean, just it's difficult to have a huge age difference in the team (we all around 22 -25 y.o., small startup team).
What do you think? Would you hire an "older" developer? Did you personally face such issue?
"when are planning to merry?" "when are planning to have children?" + long educational lecture on why it's so important. That's a disaster.