3 ms·
Pre-revenue businesses with no product fit "I learned a lot so your startup won't fail trust me lol" and no references But yeah they won't care about the crapp
by vmception 5y ago
Pre-revenue businesses with no product fit "I learned a lot so your startup won't fail trust me lol" and no references
But yeah they won't care about the crappy products since all the companies you interview with are doing the same, honestly the real followup question would be what do you do about references
- developer93 5y agoEmployers like a github link, should go some way towards what you need?
- vmception 5y agoEmployers don’t really care If you have enough experience for a recruiter to respond at all, none of that extracurricular stuff matters
- codetrotter 5y ago> none of that extracurricular stuff matters But that “extracurricular stuff” is exactly what op has been spending their time doing for the past years.
- TomVDB 5y agoWhen I’m given a resume with GitHub links, I jump at the opportunity to check them out. (It almost never happens.) You don’t?
- mewpmewp2 5y agoI really don't and I am not aware of anyone at work who would. I rarely even read resumes and that if I am very mixed after the 1 hour coding/design/arch whatever round. I never send my GitHub links either. If I am coding a side project and I think it has business potential I am unlikely to start with open source and if it doesn't have business potential, I wouldn't bother. Also if I am building something on the side, code is likely to be rushed and seemingly horrible. I have no idea what in GitHub was written by the owner itself, what was copied, how long it took them etc.
- moksly 5y agoI don’t. I’m Danish and almost everyone here has some kind of higher education, so our hiring practices are a little different from other countries. Anyway, there is no reason to spend the time looking at what people have done on GitHub. Once you make the final five or ten candidates, we could honestly use sheer chance to decide and end up just fine. The only reason we don’t do that, is because it would be disrespectful to the applicants, but the interviews are as much an opportunity for them to figure out if they want to work with us once they’ve met us, as it is for us to do the same. Hiring people once you move past a certain skill level is much more about finding a common fit, so that you can continue having the good culture that you have already established. It’s not that I think you are wrong to look at github though. It’s just that I don’t feel it’s really ever worth the resources you need to allocate to get a proper picture. I feel the same way about the coding interview, it’s just a waste or everyone’s time. I mean, how can you tell if their GitHub profiles aren’t doctored? If it was too clean or too good, I’d personally be suspicious why they’d work for us.
- mewpmewp2 5y agoOne thing I'd like to mention about being "fine", you'd be fine, but you could be extremely well off if you are able to find the engineers that go way beyond. I find the multiplying effect of engineers within top 1% can be more than 5x. These folks will take responsibility for everything, innovate and work intelligently, tirelessly and passionately to solve any problems thrown at them as opposed to someone who will just pick up Jira tickets blindly. It's just a little attitude thing that makes so much difference. The way salaries work, they probably don't get 5x salary so they are extremely valuable for the company and to find in general. If you just look at general performance, resumes and things like that you might just get "rest and vest" types.
- gkilmain 5y agoSame, but I don't get too much from it. If its not there I really don't care anymore and never ask for it. Whats the point of showcasing your github profile today? Little to no experience (entry level / jr) makes sense but for anyone else - don't fret.
- mratsim 5y agoPeople without a Github/Gitlab start with a huge disadvantage in the hiring process at my company since they don't have code to support their claims and that they can walk us through together. Now I get some people don't have time for open-source after work but it's way way easier to ace an interview when it can be based on something you build yourself, can show and can talk about the ins, the outs and the design constraints and your architecture choices.
- wreath 5y agoSo few previous employers who bet on you and paid you hundreds of thousands on a yearly basis is not enough cred to prove that you can deliver software that solves business problems?
- sokoloff 5y agoIf you were at a place for five years, got two promotions, and shipped three products while you were there? Strong evidence. If you were at five places for 9-18 months at a time with several six month gaps interspersed? Not evidence of absence, but that’s absence of evidence to me. (Immediately, I’m assuming several of those gaps might be flameouts.)
- deleted 5y ago[deleted]
- KptMarchewa 5y ago>If you were at five places for 9-18 months at a time with several six month gaps interspersed? I'm curious, what about this situation but no gaps?
- sokoloff 5y agoThat’s better, because it suggests four times out of four, the decision to leave and timing was yours rather than “seven times out of nine [four listed], the change was employer-initiated”. None of these are signals that I rely on as binary go/no-go gates; the main point was “just because you got other employers to pay you for a short while, that’s not standalone evidence that you can deliver business value through working software”. I don’t believe in jobs-for-life, “putting in your time”, “paying your dues”, “never quit before 2 years”, or other nonsense advice, but if you’ve never had a long stint at a place, at minimum you’ve never seen the pain from your decisions 24 months prior play out and the maximum negative case is far worse.
- risyachka 5y ago>> Pre-revenue businesses with no product fit This is true about a majority of small/medium (and sometimes even big) startups.
- vmception 5y agoMy comment says that.