Ask HN: Should I put my startup on my resume? Hey guys I recently launched my company’s first product last month. It’s a ML driven comic collection manager app. We have 1200 users so it’s been a great success for a bootstrapped company. Unfortunately I’m also trying to find a job. I’ve been stuck at as a mid level engineer with a 5 YOE. I’m debating whether or not I should put it on my resume. |
When I was in college I created a tiny ISP for my friends in my apartment. I got a DSL (which was $350/mo in 1999, about $1200/mo in today's dollars). Then I ran ethernet cables to all the apartments, and set up the router and collected payment from everyone.
I put this on my resume as running a small ISP.
When I was interviewing at Google, everything was great, I was on the last interview, and he asked me about it. So I told him honestly about how I had 10 customers. And he said "oh, so not a real business, why would you put this on here?". And then he rejected me and I didn't get into Google pre-IPO (I had an insider tell me it was his rejection that did me in and it was the only reason he didn't like me).
So my point is, if it's there it invites questions. If you have a good story it can only be a good thing (and you honestly have a good story). Just be aware people might ask questions and be ready to answer.
Tailor your resume for the role you're applying for.
If the role is purely engineering, then show relevant tech skills. Instead of I built a startup, you could say I built a a platform X that does this using this.
When you're applying for a job you're basically submitting an answer to a question, so you need to understand what they need from you. Putting `I made a startup with X number of users` signals that you've your own thing and would leave in a heartbeat. It only make sense if you're looking for an advisor position related to product/business.
On the positive side, it gives the hiring manager, if they care for that, a signal that you can build and ship stuff. You have tried building your own company and has more experience around the challenges that most devs do not have. I love to interview people who built stuff.
On the negative side, it also signals that you might not be as committed to the new company since you are pursuing something on the side, or has demonstrated that you want to pursue something other than the engagement you are applying for. I’m not saying that you can’t do both things at once, or that X is better than Z. Just stating how it might come across and can negatively affect your job search.
As long as you consider these two sides and come up with a “solution” to this, you are in the path to make an informed decision and can “defend” your position.
Good luck!
B) your resume should be tailored to the particular job. So you’d want to gauge whether it’s valuable on a case by case basis.
If not putting it on your resume will help filter them out.
Essentially put yourself in the hiring managers shoes and say 'what's in it for him/his company/the role being done well'.
I generally assume someone has 0 users unless they express otherwise.
It can become a hiring story or an example in your cover letter.
I love seeing our candidates having outside projects/etc but we make sure that there is a clear delineation between what our company offers vs what is done by the employee.