StartupNorth

Category: Recruiting

  • 9 Tips to Network Your Way into a VC Job

    [Editor’s Note: This is a guest post by Jared Gordon . Jared is an Investment Manager at IAF and is a lawyer by training (though we don’t hold that against him). The post summarizes Jared’s experience in both finding a gig at a Canadian VC fund and his conversations with others about these elusive positions. ]

    CC-BY-20 Some Rights Reserved Photo by Robert Couse-Baker

    It is that time of year again, when my inbox fills with requests for coffee from graduating students asking for two things: “How do I get a job in venture capital?” and “How do I get a “biz dev” job at a startup?” I always appreciate the initiative of people reaching out to me, but I thought I would share some tips to maximize everyone’s time.

    Getting a job in venture capital is hard.

    It is not impossible. But it is very hard. If you are the kind of person who is interested in venture capital, you will probably ignore anyone who says the problem you are trying to solve is hard. If you are the kind who is committed you will also realize it is not about the money. We do it because we love working with startups.

    There are not many funds out there, but at least that narrows the focus of your search. To give you a better idea, there are maybe 10 non partner venture capital roles in all of Canada. Everyone I know in venture capital has worked many years to get here. It requires drive, energy, time and a lot of networking. In truth, the only way to get a job in venture capital is networking.

    The Difference between PE, IB and VC

    The journey prepares you for the job once you get here. People I met with along the way are people I now do business with on a daily basis. Also, the job hunt is a chance to demonstrate to the community what kind of person you are and what kind of value you add.

    Before we jump into the tips, there is a difference between PE (Private Equity) and VC (Venture Capital). Beyond the huge difference in compensation, VCs spend a lot more time understanding the dynamics of specific markets and verticals than they do on financial analysis. In PE you spend your time building and reviewing financial models. When working with startups, you spend some your time crafting financial models, however, the calculations and models are very different.

    There is no template for working in VC

    Some basic tips on how to network your way into venture capital are listed below. These tips are about how to get in front of the people you need to get in front of and how to make the most out of that meeting. There is no template for working in venture capital. Some of us have advanced degrees some don’t. Increasingly, having spent time at a startup is becoming more common. Having strong technical talent is a rare but desired commodity. If you can identify how technically hard a problem is, that will set you apart.

    9 Tips to Getting a VC Job

    1. Don’t send a message over LinkedIn – This one is my primary pet peeve. A lot of the job of being a VC is being able to find information. Every investor’s email is available somewhere.
    2. Warm intros work best – Did I come to speak to your class? Did I come speak to your friend’s class? Do we know anyone in common? Anything you can do to create a connection between us will make me want to spend more time helping you.
    3. Don’t be scared to cold email – Cold emailing is a great skill to learn and have. You never know whose interest you might catch unless you try. Why not reach out to Fred Wilson? A partner at Kleiner who went to the same school/has the same interests as you? I find the cold emails that work best have great subject lines and can bring attention to something I, and the person I am emailing, have in common.
    4. NO FORM LETTERS – These are just insulting. You should be spending at least twenty minutes crafting each email. The person you are trying to get in front of has a linked-in profile/about.me page/bio somewhere. Use that information to show them that you value their time and advice enough to put some work into getting the meeting.
    5. Be persistent but not annoying – When I do not get a response from a warm intro, I follow up after a couple days. Some people have poor inbox management skills and stuff falls to the bottom. It is nothing personal. The person definitely saw your email and it shows persistence and that you value someone’s time when you follow up. With cold emails, if I do not hear back I will wait a couple days and send a quick second try. If I hear nothing, I leave it be.
    6. Be clear in your ask – The clearer and more direct you are about your ask, the easier it is for someone to know if they can help. Nothing is less appealing than a note asking to “learn more about venture capital.” The internet has cast the profession wide open, with more information available online now than was available to VC associates five years ago. You can learn about everything from VC funnel management, what the average day for a VC is like to the difference between European and American style waterfalls. Examples of good asks would be: “You are an early stage VC. While doing my MBA, I mentored startups and participated in Startup Weekend. Can I get half an hour of your time to talk about how I can transfer what I learned in school to a job or what else I can do to make myself a competitive candidate?” or “I want your job because I like working with early stage startups. Are you hiring? Can we make some time to chat so when you are, or when you know someone who is, you think of me?”
    7. Once you get the meeting, don’t blow it – You have only one chance to make a first impression.I spent the first months of my networking journey wasting a ton of important people’s time. I would sit across from them in boardrooms, coffee shops, and their offices and talk about myself for an hour.It took a meeting with Jeff Rosenthal of Imperial Capital to set me straight. He would not remember if you ask him, because the meeting was so bland. Jeff ended our meeting with some advice. He told me that everyone who got a second meeting walked into his office with a list of companies they would look to invest in. They proved they were capable of doing the job they were seeking. You can do that too.Look at the person you are meeting with and what spaces interest them. Use Crunchbase and Angelist to identify some promising startups and why you like them. Be prepared to defend your thoughts. This discussion is more interesting (and fun) then hearing about your involvement in the investment club or student government. One person I met with had a presentation he had put together on three trends in technology that he found interesting and why. They showed they were capable of hitting the ground running on day one.
    8. Follow up is key – Always make sure to send a thank you and take care of any action items you might have left the meeting with. If the person you are meeting with did not follow up on theirs, no harm in waiting a couple of days and sending a polite reminder.Following up does not end with the thank you note. It is always great to hear from people you have helped along the way about where they landed or how their search is going. This becomes especially important when it comes to the last tip…
    9. Coming close to something? BRING IN THE BIG GUNS!! – When you know there is a position and you have met with someone at the firm or submitted an application, now is when the networking pays off. You can make up for a lot of flaws in your resume by having someone you trust recommend you for a gig. If you treat your network right and maintain good relationships, they will have no problem making a call to get your application moved to the top of the pile.

    This is where hard work pays off

    Mark Suster summed it up in a comment on a blog post by Chris Dixon:

    “The people who “sneaked into” the process were:

    1. great networkers
    2. great networkers and
    3. had other people contact me on their behalf (great networkers).

    But if you don’t have GREAT street cred already don’t hassle the VCs. Just accept that it isn’t likely you’ll get in without doing great things at a start-up first.”

    Chris Dixon agreed “Yeah, when I got my job in VC it was like a political campaign. I had one partner tell me ‘I’ve heard you[’re] a great guy from 6 people’ – which wasn’t an accident. I had done so many free projects, favors etc for VCs and startup and then I asked them to make calls on my behalf. It’s brutal.”

    The venture capital community is a very small tight knit community. And the number of potential gigs is very small. It is a lot of effort to build the relationships and connections to get a job working at a venture fund. (Before you even consider this, you might want to brush up on Venture Math 101 and figure out why you really want to do this).

    Additional Reading

    Here are some great posts from people with more experience and authority on the same topic:

    Still want some of my time? I am not going to tell you how to find me, but if you can figure it out, I look forward to chatting.

    Photo Credit: Photo by Robert Couse-Baker  – CC-BY-20 Some Rights Reserved

  • Mission Accomplished – StartupVisa Canada

    CC-BY-SA-20 Some rights reserved by Marion Doss
    AttributionShare Alike Some rights reserved by Marion Doss

    Remember back in 2011 when I was xenophobic and wasn’t supporting Startup Visa? To the credit fo the incredible StartupVisa Canada Initiativea team, which I was lucky enough to join and support, the Federal Government is launching a new class of immigration visa with the participation of CVCA and NACO. Check out Christine Dobby’s summary from the press conference (it’s where all my statistics and data are from). Go read Boris Wertz’s story about Summify founders and the impetus for Startup Visa Canada.

    “We believe startups to be the driving force behind job creation and prosperity,” says executive director Richard Rémillard. “We need to be pro-active in attracting foreign entrepreneurs.”

    The new visa is replacing the old “entrepreneur class” visa, which required the applicant/immigrant to hire one person for one year. In 2011, the federal government issued approximately 700 of the old entrepreneur class visa. The government is making 2,750 visas, issued to immigrants based on selection and funding by venture capital investors. Immigrants receive immediate permanent resident status. Looks like a pilot program with a 5 year lifespan, with the opportunity to make permanent depending on uptake.

    Thinking by Zach Aysan (zachaysan)) on 500px.com
    Thinking by Zach Aysan

    My issues back in 2011 and previously, were not with the intent of the program. But in the proposed implementation details. One of the biggest assets, in my not so humble opinion, is the population diversity, with 46% of Toronto’s pouplation being foreign born. It is the creative tension between differing viewpoints that makes Canada an amazing place. The implementation of startup visa makes Canada an even more attractive place to recruit foreign born scientists, engineers and now entrepreneurs. I love it!

  • Firing People

    I hate firing people. It’s the worst part of my job. Even after all these years I still spend days or even weeks agonizing over a decision to let someone go. I feel absurd complaining about this, given that of course it’s a hundred times worse for the person being fired than it is for me. Still, I hate firing people.

    My first firing at Top Hat was our VP Sales. He was employee number two, he joined right after we raised our angel round. In retrospect it was doomed from the start, and it was entirely my fault. I had no idea what I was doing when it came to building a sales organization and brought him into a role that didn’t make sense (read about the lessons learned in building a sales team). It took me 6 months before I finally pulled the trigger. In the end, it was undoubtedly the right decision and set the company back on track. But at the time it was an extremely tough call. It was admitting failure – to myself and to our investors – that this first major hire was a mistake. I felt  ashamed about it for months and kept convincing and re-convincing myself that we could still make it work.

    As a general rule once you’ve lost faith in an employee, things rarely get better. You can sometimes fix a skill-level problem by giving someone time to grow, but you can never fix a personality problem. If you’ve identified that someone isn’t a fit you need to move on it quickly and decisively. The longer you wait the worse it will be for both parties.

    Firing is an essential part of running a successful company.

    In a narrow way, it’s actually more important than hiring. You could, in theory, use a shit-against-the-wall style hiring strategy and as long as you filter out the bad apples quickly enough you’ll be able to build up a functional team over time. Of course that’s probably not the best approach.

    The reality is that even the most effective interviewers are rarely more than 70% or 80% accurate. The average interviewer is quite a bit worse than that and isn’t much better than chance – often even worse, because the naive approach just selects people who are great in interviews, which disproportionately selects for bullshitters. However, even if you’re some kind of super-human talent screening machine with a 95% success rate, that 5% will accumulate and degrade the culture until you’re surrounded by bozos.

    The Best Firing Process is a Better Hiring Process

    Of course the best “firing process” is not to have to fire people, which can only be done through effective hiring. That being said, not having an effective firing process is like not having an immune system – the first cold will eventually kill you.

    It’s fairly common knowledge these days that A players only like to work with other A players. A slightly more subtle observation is that someone’s status as an A player isn’t fixed. Bringing a weak player onto a team has a tendency to poison the culture and downgrade the rest of the team (especially if that weak player has a shitty attitude.) This bad apple syndrome has been observed to happen fairly reliably in studies on organizational dynamics.

    CC-BY_SA-20 Some rights reserved by MrB-MMX
    AttributionShare Alike Some rights reserved by MrB-MMX

    The Bad Apple Syndrome

    We’ve experience this at Top Hat a couple of times. One of the most instructive was with our inside sales team. Early on when we were in a pinch to fill the team we lowered our standards and brought on a few people that we should have passed on. The results were disastrous. The quality of the team degraded and eventually hurt not only the inside team but also other parts of the company that came into contact with it. It took nearly a year of solid effort to rebuild the team. For a time it seemed hopeless. No matter what changes we put in place, no matter how much talent we threw at the team, the cancer of negativity and poor morale just wouldn’t go away. The most profound mistake we made in the process of trying to fix the team was to keep those who were performing well but had a negative attitude.

    There was a pattern we observed a few times: we’d put a new person into the team, their performance would be great and they’d be super enthusiastic. Then like clockwork after a week or two their numbers would slowly drop, and they’d become engrossed in the culture of negativity and gossip. It was only after the cleared out the ringleaders who were perpetuating the negativity (who happened to have decent performance numbers!) and put in strong positive management that things finally began to change. The most amazing thing is that many of the people who were B or even C players when the team was dominated by negativity shot up to solid A player status. The overall output of the team per person went up by nearly 300%. In addition it seems as though life was trying to setup a lab experiment for us to prove just how much things had improved – we had a person who had left the company a few months prior re-join the team. His feedback was that he was blow away, he couldn’t believe it was the same team.

    Lessons Learned

    The first lesson we learned was that no matter how strapped for manpower you are, no matter how much it seems like the world will end if you don’t fill a position, compromising on the quality of talent will surely be more damaging. Second, we learned that in fixing a damaged team the key is to identify the cultural sources of the underlying problem and focus on those. Finally, we learned to use a divide and conquer approach – we would pull all the top talent into a separate team while rehabilitating the broken remaining team separately – it really helped prevent the “negativity cancer” from spreading while we were fixing things. These are simple things in retrospect, but it took a while to pull it off.

    One of the most revealing questions I tend to ask when interviewing potential managers is whether they’ve ever had to make the decision to fire someone. The answer and subsequent discussion usually tells you two things: first, it tells you if the person has ever had to deal with the most difficult problems in management, second it tells you if they know how to handle those problems through the process they followed. Assuming the person has ever had to hire and manage a team of a decent size for any length of time, it’s almost certain they’ve made hiring mistakes, and their answer tells you that they know how to detect and correct these mistakes. If the person simply walked into a mature team, or has had HR handle all the hiring/firing decisions for them, then they’ve been living on easy street.

    The process of firing someone is always somewhat unique to each situation. That being said there are some basic principles that you should always follow:

    1. Give people plenty of notice and regular feedback. Give people several chances to improve. The actual firing should never be a surprise – if it is then you almost certainly did something wrong in setting expectations. Depending on the role the whole process should take 1-2 months (longer for senior roles.)
    2. Try to be generous with severance and leave the person in a good spot to find their next employment. I know it’s not always possible in a startup, but do what you can. It’s the decent thing to do.
    3. Take time to reassure the rest of the team and explain (with discretion) the process that was followed and why the decision was made. Letting someone go is always a huge morale hit (even if the person wasn’t well liked, it still scares people.) You need to make people understand that their job is not in danger.

    Firing someone is always a brutal experience. Anyone who says otherwise is either lying or is a psychopath. That being said, it’s unfortunately a necessary evil and understanding when and why it needs to be done is essential to the success of any business.

  • Hiring your first sales rep: 10 tips and common mistakes

    CC-BY-NC-ND-20 Some rights reserved by redwolfb14
    AttributionNoncommercialNo Derivative Works Some rights reserved by redwolfb14

    How many times have you been at an event and met someone who gave you the pitch “I have this great idea, I just need someone to build it for me” or some variation of that?

    This has become such a cliche in startup circles that it’s almost cringe-worthy. If all someone has is an idea then they’ve basically got nothing. As the old Edison quote goes “genius is one percent inspiration and ninety-nine percent perspiration.”

    That being said, the other side of this pitch doesn’t get a ton of attention even though the problem is just as common.

    There are lots of startups that build pretty solid products but never end up getting traction because they don’t figure out the sales and marketing side of things.

    You don’t see a lot of technical founders searching for business development help, mostly because many engineers don’t even know they have a problem. They spend a year in their basement building the most amazing solution to a problem nobody has. When they do finally surface they discover that 6 of the 10 assumptions they made were wrong, and usually give up soon thereafter.

    I’m an engineer, and I’ve seen this problem come up first hand. One of the most basic ways to avoid it is to start focusing early on customer validation. What that means in the most basic terms is to not write a single line of code before you talk to a few dozen customers who tell you unequivocally that they will buy the thing you’re thinking of building.

    As you talk to customers tweak the pitch until you have 9 out of 10 potential customers telling you that they will pay money for what you’re planning to build (hint: 8 of them are lying.) This is your first step towards developing a sales process.

    You (or your co-founder) need to learn to sell. Frankly, it’s not that hard and it’s mostly about persistence when it comes to getting a few pilot customers – they’re going to be early adopters, they won’t expect a polished sales pitch. It’s essential that this basic sales and marketing expertise lie within the core team. Which brings me to the first tip about hiring your first sales reps:

    1. Learn how to sell and develop a basic process.

    The most common mistake technical startup founders seem to make is to try and cop out on the sales part of the business. They feel they don’t know how to sell and are worried that people won’t take them seriously because they don’t have grey hair. So they hire an experienced sales guy (a friend of a friend,) give him ownership of all sales and just sit back and wait for the deals to flow in. It seems like such a plausible idea (it’s exactly what I did with Top Hat Monocle) and yet I’ve never once seen it work out. You need to learn to sell. It’s actually a skill very similar to raising money, so it’s something you’ll need to do anyway. Learn to sell just well enough to close the first few customers and develop a basic process that you can plug someone into.

    2. Find reps who have experience with the same deal size and sales cycle as your product.

    If your product costs $200 per month and has a 1-2 week sales cycle, don’t hire some with enterprise experience who’s used to closing three $500k deals a year, it won’t work out. A match on deal size and sales cycle is probably the best predictor of whether the rep will be a good fit.

    3. Experience within your industry is useful but not essential if your product isn’t too complex.

    Focus on item 2 above. Unless you’re selling a very complex product with a long (6 month+) sales cycle, don’t worry about industry experience.

    4. If it’s a technical sale, tech savvy matters.

    Don’t hire someone who barely knows how to use a computer to sell a software product. Frankly in general you should only hire people with basic technical literacy because otherwise you will be explaining to them how to use the CRM and your webinar software 5 times a day.

    5. Sales reps are great bullshitters – ignore their words.

    Only look at verifiable track record to assess the rep. This means getting a printed record of their quota attainment at every sales job they’ve had, then verifying that record with their supervisor. Anyone who hasn’t consistently blown away their quota at every job is a risk.

    6. Place minimal value on prior contacts and rolodex.

    The rolodex runs out after about two weeks. After that it’s all about prospecting and hard work. Don’t ever overlook a lack of experience or cultural fit because you feel the rep has a rolodex of clients they claim they’ll bring with them (they’re probably exaggerating anyway, see #5 above.)

    7. With personality, focus on work ethic and motivation.

    Sales is repetitive hard work. When hiring reps look for work ethic and drive. Look for people who need to earn a certain amount of money to maintain their lifestyle due to financial obligations – a big mortgage is the best motivator to hit quota.

    8. Over time start to specialize your sales team.

    Lead generation and research. Appointment setting. Follow ups and closing. Each is a separate role. You should segment by task and eventually by customer size or market. It may not even take that long for it to make sense to do this – we started specializing at Top Hat Monocle when we had just 3 reps.

    9. Sales reps will maximize their paycheque above all else.

    At least the good ones will. You need to ensure your compensation plan incentivizes sales and has relatively short term rewards. This typically means at least 50% of overall earnings should be from commission and there should be a monthly performance based commission payout. Don’t try to hire people on 100% commission, because you will likely only attract flakes who waste your time and never deliver.

    10. Metric everything. Obsessively.

    How many calls per day does each rep make. How many emails. What is the conversion rate on email responses. How many meetings does each rep go on per day. How many inbound leads are being generated. What is the time from inbound lead to follow-up. How many foliow-ups does each rep do per day. What is the mean time between follow ups. Everything. Metric everything.

  • Hiring a Growth Hacker on StartupNorth.ca

    CC-BY-20 Some rights reserved by Eva Blue
    Attribution Some rights reserved by Eva Blue

    Did you know that we run a job board for startups? It does allow companies to reach an audience that is interested in startups.

    “Amar joined us 3 weeks ago after a long trial of hunting down and applying for the “Growth Hacker” position we posted on StartupNorth. We couldn’t be happier with his progress, hunger and efficiency. Over to you Amar!” – Michael Litt, Vidyard

    There are great stories of people find companies and roles like Amar Chahal (LinkedIn) and the Growth Hacker role at Vidyard. If your a looking for a new gig, go read about how Amar was hired at Vidyard. It will blow your mind how much he committed to the process. I’m actually shocked that no one has socially hacked our job board as a candidate, i.e., it’s not that expensive but you could pay to highlight your resume or portfolio, because it will only work once.

    Post Your Job

    Postings are only $25 for 60 days. Postings are embedded on StartupNorth.ca and all postings are shared on our Twitter account. For example:

    It’s a quick, relatively inexpensive way to post jobs to a targeted audience. Get a little bit of distribution and hopefully find candidates like Amar.

    We are open to discussion about how we can improve the Jobs Board for both candidates and companies. Got a suggestion for how we improve things? We are all ears.

  • Looking to get hired by a startup? 10 ways to stand out

    Editor’s Note: This is a guest post by Bruce Dorland (LinkedIn, @brucedorland). Bruce is the Managing Director & Recruiter at Grossman Dorland Recruiting. gdR recruits for permanent and contract positions at all levels, from roles for talented young professionals to accomplished executives. Prior to founding gdR, Bruce spent time at Brightspark, Tucows shipping products that have been used by over 3MM users.

    CC-BY-NC-ND-20 Some rights reserved by Candid-Moments
    AttributionNoncommercialNo Derivative Works Some rights reserved by Candid-Moments

    Occasionally I interview a developer that really impresses me with their ability to make their profile come to life beyond their resume.

    Want to know what makes these developers stand out? Here are my top ten tips for making a big impression. Many of these tips work for both a resume and, once that stellar resume gets you in the door, a job interview.

    I think developers looking for a new job can have it tough. Many, if not most, job descriptions aren’t great at describing the actual nature of the role. Traditional resume formats can be flat. Interviewers don’t always ask effective questions, and HR departments that rely heavily on keyword matching can’t differentiate you qualitatively from other candidates.

    The result: unless you do something different, the odds of standing out are stacked against you. But if you’re trying to get into a startup or midsize tech company that is truly looking to build a top-notch team, it’s essential that you learn to make your mark. Here’s how:

    Tip #1: Show me your side projects

    Small and midsize companies increasingly value a well-rounded candidate with a passion for technology and a dedication to growing their technical skillset. For confidentially reasons it can be hard to show people the code you’ve been working on at your job, but side projects are a great way to show how you design and implement code. In my opinion, side projects are also a surefire sign of your passion for the craft.

    A great tool for this is a code sharing and publishing platform like GitHub. The site gives you a place to contribute to open source projects and build a public reputation for your work since the community is quite transparent. For instance, if a patch you submit is accepted, you get credit for it and it shows up in your profile. The site acts like a resume that helps the maintainer of a project determine your reputation.

    Tip #2: Have a relevant and up-to-date portfolio site

    While it’s common for certain types of developers to have a portfolio site, UI developers in particular, I’ve found that many create a site early on in their career but don’t keep it up to date.

    Most employers who refer to your portfolio site won’t necessarily have the time or patience to fill in any blanks or realize is something is out of date. It’s up to you to make sure that your site accurately reflects where your skill level is today, that sites that aren’t live anymore are removed, that screenshots are illustrative and relevant, and that you give the context of why your work was original or important at that time.

    Tip #3: Form your own opinions on technology

    What are the topics of the day within your company? What technologies have they chosen to use and why? Form an opinion about your current company’s choices of tools and have an opinion about where things might be going in the future (of course, you’ll want to make sure you’re observing confidentiality requirements if you intend to share this information in an interview).

    In addition, know the big discussions happening in tech today. What are the latest thoughts on Continuous Integration and Deployment options? Javascript MVC frameworks? Big data? Be knowledgeable and you’ll always be ready if asked for your thoughts on the trends shaping your field.

    Tip #4: Understand the users and business behind your product

    Many developers are used to only describing their products from a tech perspective out, rather than a user perspective in.

    To make yourself stand out from the crowd, be able to articulate who the users of your product are and the solution it provides for them, and more generally, the business side of the product.

    Go into an interview from this angle in mind and a company will be confident that you always do your work with the user in mind.

    Tip #5: Whiteboard your work

    Many developers aren’t used to talking about themselves, their product architecture, what they’ve accomplished, or how to best articulate the technical challenges they faced. This is why whiteboarding your work is so important.

    When I say whiteboarding, I mean mapping out the architecture of your product, the modules your were responsible for and the technological challenges you faced. It’s about taking all this information and putting it into words so that you can talk about it during an interview.

    This might also literally mean drawing this all out on a whiteboard, as I often ask candidates to do during an interview. You can’t lie to yourself or anyone else in front of that whiteboard – either you can map out and explain your work, or you can’t.

    If you can bring sample documents to reinforce your whiteboard map without breaking confidentiality agreements, that helps too.

    Tip #6: Make it interactive – demo your work!

    In an interview, I’m always much more engaged if a developer can demo their product for me. This might seem obvious, but you’d be surprised how seldom I’m asked if I want a live tour of the product they’ve been working on.

    If you worked for a SaaS company, for example, and you still have an account, offer to log in and show me around. Tell me which modules you were responsible for. This is always much more visual and stimulating than a written summary of your work.

    Tip #7: Be articulate, simple & concise.

    Once you’ve prepared your whiteboard, be prepared to articulate all this information (your skills, your current responsibilities and your product) in a simple, concise manner. Start with less detail and drill down where appropriate. If you don’t know how deep to go, just ask the interviewer if they want to know more.

    Be prepared to guide some of the questioning so you know the interviewer is getting all the information that makes you an appealing candidate. An interview is an interactive process, after all.

    Tip #8: Tell me what you find exciting in tech today.

    Even if you haven’t been working for the sexiest company, products or applications, always be prepared to talk about what you DO admire and why.

    Please do me a favour – don’t say Apple or Google (and definitely don’t say Microsoft!). Come up with unique ideas that reflect your professional opinions on what makes a product or service shine.

    Tip #9: Get to know the company you’re interviewing for.

    Obvious, right? But it can speak volumes if a candidate isn’t informed, which happens a lot.

    Find out what technology stack the company uses and review their FAQs, support forums, training guides and blog. If they have a free trial account of their product, sign up for an account and give it a test drive. The more you know, the more enthusiastic you’ll appear and the better and more useful your own questions will be.

    Tip #10: Come to the interview with great questions.

    Hopefully after having done all the research I’ve suggested, you’ll have some original questions to ask that not only show that you’ve come prepared, but that will also help you make a decision about how the company, product, technology and team fit your overall career goals.

  • Waterloo’s Next Five Years

    Following on with Jevon’s original post of Canada’s Next Five Years, I want to discuss Waterloo.

    Five years ago, I organized the first StartupCampWaterloo. It built on the great community and open space tools from BarCampWaterloo and focused participants around startups. Simon Woodside, Ali Asaria, Mic Berman, and myself felt like we needed to something a little different to get the grass roots high tech startup community moving in Waterloo. It was a year after the Accelerator Centre opened and the community was just finding its feet. Waterloo felt bold and creative with a strong core of startups but it was small.

    With the aggressive growth of RIM and Open Text, the Waterloo community has spent the last five years building a strong and diverse tech community. In addition to the homegrown companies, the community was fuelled by a few California based companies making some big purchases in Waterloo Region. These three purchases resulted in the parent companies building a larger presence in the Waterloo Region:

    In the last couple of years Communitech grew beyond simply being a promoter and connector for local tech companies. Communitech has established a home base for startups in downtown Kitchener. They took the bold move to put a vibrant space for startups in an old Tannery complex, which has also attracted the likes of Google and Desire2Learn, each with hundreds of employees based in the building. The Communtech Hub is a strong message to entrepreneurs that the community is there to support you.

    However, the next five years are where all the attention the Waterloo region has drawn to itself is going to have to transition to results and further momentum growth. This will depend a lot on the companies that have been founded in the last five years and includes some that are now YC-backed.

    Looking at what Canada needs to do, what role does Waterloo play in that?

    Education

    Waterloo is home to arguably the top Engineering School in the country, the University of Waterloo. With programs like REAP, CBET, and living environments like VeloCity it is committed to educating and supporting students with regards to entrepreneurship. It is also focused on having them experience it through the Co-op program that allows students to work anywhere in the world with many choosing to work at Facebook, Google, Twitter, Apple, and a ton of different startups in the valley. This results in students that have a big head start in terms of building a network as well as learning about problems that could turn into great product ideas. That experience and opportunity is a big win for Canada’s startup community. We can see the rise of Waterloo alum lead startups like Vidyard, Kik, Upverter, Well.ca, TribeHR, LearnHub, Thinking Ape, Pair, and others.

    And it’s not just UWaterloo, Wilfrid Laurier University and Conestoga college are also doing their part. The MBA program at WLU has a focus on entrepreneurship and they are leveraging the Communitech Hub environment. Conestoga College is educating the work force in the region making it a very important partner in ensuring there is a workforce for growing companies.

    Community as the Framework

    The Waterloo Region has a ton of tech oriented events. A lot of folks assume the trick is to find time to attend all the events you want to attend. The real trick is figuring out which events you should attend, and how to make the most of your attendance. Are you attending for education? recruiting? to find funding? to be part of the startup scene?  More entrepreneurs need to clearly identify their desired outcomes from each event, and they participate accordingly.

    What there needs to be, is a greater focus on founders and information sharing.  Peer mentorship, breakfasts with friends at Angie’s, or just chatting at the end of the day. We should avoid gossip, we don’t want or need a ValleyWag for Waterloo Region. Building a company is difficult enough that we don’t need to be hindering each other. Entrepreneurs need to be able to establish trusting relationships with each other, to build I see it happening more and more but there isn’t enough peer mentorship going on.There are a large number of entrepreneurs that have been through the ups and downs of a startup. It includes fundraising, business development, channel partner discussions, contract gotchas, etc. We need to help entrepreneurs build connections with each other.  There is a huge opportunity for entrepreneurs to build trustworthy relationships and share their experiences.

    Tighter connections to elsewhere

    Jevon calls for tighter ties to Silicon Valley. But it’s more broad than that. Canadians need to get out of Canada. We need to build stronger connections in New York, Boston, Los Angeles, Buenos Ares, London, Mumbai, Shanghai, Eastern Europe.

    We are doing a pretty good job at getting exposure in Silicon Valley. We have companies going to YCombinator (Vidyard, Allerta, Upverter, Pair and others). The C100 has done an amazing job identifying Canadian expatriates and connecting them across the country. The C100 has expanded to NYC and to the UK. Entrepreneurs need to expand to.  We have startups raising money from NYC (Kik raised from USV), Boston (TribeHR raised from Matrix Partners). We need to get out of the local ecosystem and build products for global customers.

    I would be remiss to ignore the need for tighter connections to Toronto as well. Whenever anyone says “Toronto is better than Waterloo for…” or “Waterloo is better than Toronto for…” a kitten dies. Stop it. No one really cares and outside of Ontario people think it is just one big region. Lets build stronger ties and use both cities for everything they have to offer.

    Policy

    Beyond establishing the Hub, Communitech has done a lot of work on building connections with all levels of government. They have a big role to play with influencing policy as does Canada’s Technology Triangle Association.

    Grow Like Hell and Don’t Stop

    Hootsuite is mentioned but Waterloo is home to tech companies that have taken the long path to growth. RIM, Open Text, and Desire2Learn are examples of rapid growth (over a 10 year period) tech companies. What Waterloo needs is more of that. The challenge is going to be getting the talent that knows how to work sales funnels, marketing, etc to live in the Region in sufficient numbers.

    What I would guess is going to happen initially is that US VC-backed companies that started in Waterloo will have to find a way to balance having their product teams in Waterloo and marketing/sales teams in major US startup hub cities. That means an office in Waterloo and one of Palo Alto, Mountain View, San Francisco, New York, or Boston. This allows them to hire developer talent outside of the higher salaries zones that is on par (or better) but feed on the energy in those cities. The US market and understanding it quickly is key to many of the current fast moving startups in Waterloo.

    For the Region of Waterloo to live up to the expectations, in the next five years these companies will need to attract that marketing/sales talent to move here for work or be able to use Toronto for that.

     

  • Hiring for Lean Startups: The First Few Hires

    Editor’s note: This is a cross post from Flow Ventures written by Raymond Luk (LinkedIn, @rayluk). Follow him on Twitter @rayluk. This post was originally published in January 12, 2012 on Flow Ventures.

    CC-BY Some rights reserved by Maximus_W
    Attribution Some rights reserved by Maximus_W

    I was having coffee with a founder the other day and we started talking about his hiring plans. Since he’s a non-technical founder (which Ben Yoskovitz claims is a dead-end to begin with) he had several top coders in mind, all of whom were earning big bucks with larger companies.

    “I’m paying them a little bit of money but they’ll join full time once I can raise money,” said the founder. It’s something I hear a lot, especially from non-techie founders.

    I went back to review some blog posts on Lean hiring, and I came across Eric’s post “Lean Hiring Tips” and Mark MacLeod’s “Fat Hiring for Lean Startups“. Both are worth your time. But I think they’re also written for startups that are already up and running and need to expand. I’m interested in very early stage hiring, e.g. when you’re one person looking for a co-founder or you’re two people looking for your core team.

    Companies always take on the characteristics of their founders and in the rush to scale, I find many startups don’t stop to consider how they’re establishing the DNA of their company. The first few hires are the most important ones you’ll make.

    • Hire for an experimental mindset – Look for people who enjoy encountering problems, designing ways to solve them, and finding proof of success or failure. Skill at building, whether it’s software or a marketing plan or a sales funnel, is irrelevant at this point. You need people who will volunteer to scrap their plans, not fight you when you want to change course.

    How? Join a hackathon, Lean Machine or just create your own (laptop + Starbucks = hackathon). Give your (potential) team a crazy challenge and see who exhibits the right behaviours.

    • Hire generalists – A lot of people will disagree with this advice. If you can find the best Python developer in the country go for it. But only if she’s also willing to cold call customers, crank out some Web site copy and help you whiteboard the business model. Your #1 focus is to find a business model that works. The latent technical talent on your bench won’t help you unless you graduate from this first phase

    How? Again, hackathons are great practical tests. No matter what their skillset, look for passion about your business model and solving customer problems.

    • Prioritize UX over development – This is easier said than done since there’s a shortage of UX talent. But it’s better to have a kick-ass UX person and a mediocre developer than the other way around. UX will help you find your business model and most (good) UX people already have an experimental mindset and generalist attitude

    How? Actively seek out UX people, not just developers. You may need to work at a distance if you can’t find local talent. Consider working with less experienced people if they can prove themselves through testing.

    • Get skin in the game – Leaving a six figure job to join your startup for a paycut is not skin in the game, or not enough in my books. Hire those people later when you’ve found your business model, have money in the bank, and need to scale. Skin in the game means working full time, just like you are. It means putting their reputation on the line, raising Ramen funding from friends/family/spouses and saying “I’m going to see this through until we fail.”

    How? Stop feeling like you’re a poor startup that can’t afford to pay top salaries. Those aren’t the droids you’re looking for. Think of finding your co-founders like raising your first round. You need to get them excited to invest in your business.

    I know this advice seems to apply better to “Web” startups than general technology startups, which is a common criticism of Lean startups in general. But I think it applies more broadly. If you hire for the right attitude, you not only solve the critical product-market fit problem, but you set the DNA of your business right from the start. I guess I haven’t seen too many examples of startups failing because they lacked a specific technical skill. They probably think they failed because of it though.

    In the end, I guess “hiring” is the wrong word to begin with. You’re looking for people to co-found a business with you. You aren’t buying their skills, you’re asking them to invest in helping you shape the course of your business from the very beginning. Maybe not all of them (including yourself) will be able to scale up with the business. That’s a problem for another day.

    Editor’s note: This is a cross post from Flow Ventures written by Raymond Luk (LinkedIn, @rayluk). Follow him on Twitter @rayluk. This post was originally published in January 12, 2012 on Flow Ventures.

  • It’s people, people!

    Soylent Green - Tastes just like Chicken - CC-BY-NC-SA Some rights reserved by vj_pdx
     AttributionNoncommercialShare Alike Some rights reserved by vj_pdx

    How do I know that emerging technology is still booming? It is incredibly difficult and competitive to recruit, hire and retain people with startup experience across Canada. Just look at the number of jobs posted on the StartupNorth Job postings:

    The number one budget item for startups is headcount. For most companies, the people costs far exceed the costs associated with hosting, etc. I don’t know about you but we’re not designing our own servers or opening data centers near the Arctic to reduce the cost of computing and power consumption. It means that the people are the biggest cost for a startup as they grow.

    This is different during the initial creation of many of the startups in the bootstrapping phase. We’ve seen a lot of startups get to Minimum Viable Product and start the process of finding a scaleable business model keeping their headcount costs low or close to zero. You might infer that the experience at YCombinator or TechStars or 500Startups is designed to give entrepreneurs the bare minimum of capital and put them in a focused, competitive environment with a deadline (Demo Day) to do the customer development and build the connections necessary for the next stage. Upon exit, many of these companies raise a significant amount of capital. Have you asked yourself why?

    Soylent Green is People - CC-BY-NC-SA Some rights reserved by tjdewey
    AttributionNoncommercialShare Alike Some rights reserved by tjdewey

    It’s to hire the best people. And it turns out that hiring the best people is not something that can be easily solved with a job posting, or a tweet, or free iPad. Recruiting is Hard! And at startups, it can be difficult to step away from fund raising, product development and customer engagement to focus on the thing that can make or break your business. Ben Yoskovitz wrote a great summary post of his efforts to Recruit and Hire Top People for a Startup that every founder should read:

    The war for talent across Canada is just beginning. During my time at VeloCity at UWaterloo, I was impressed at the number of US companies and startups that were actively recruiting on campus. And the established companies aren’t alone, we have seen an increase in the amount of US investments (looking at you GoInstant, Vidyard, TribeHR, Kik, Playerize, Enflick, Shopify, Hootsuite, A Thinking Ape, and others). This will undoubtedly lead to increasing salaries (see @byosko’s # 4 prediction for 2012 in Montreal). It doesn’t even take into consider the continuing recruiting efforts that companies like Rypple, Radian6, Dayforce. For startups, we are going to need to improve our culture and game to keep talent. And getting your startup to a point to raise enough money to pay competitive salaries is going to be the baseline to play in 2012.

    If you are designer, marketer or developer and you are curious at who is hiring or if you want an introduction, drop me a note with a resume (david at davidcrow dot ca) and I’ll do my best to match you with companies I know are looking.

     

  • How to Hire Me, A Technical Co-Founder

    There has been a lot of buzz the past 6-8 months about hiring great technical co-founders. The implication seems to be that being a non-technical co-founder is a handicap of sorts and that CEOs buy sandwiches before the product is finished. Apparently coding & building great products is hard, but running the business is easy. Here are some articles:

    Why You Can’t Recruit a Technical Cofounder
    Quora – Technical Co-Founders
    Please, please, please Stop Asking How To Find a Technical Co-Founder
    Thoughts On Hiring a Technical Co-Founder

    I am a “technical co-founder” at Peek – I code, keep big scale systems up, hire & fire, set dev processes, and all that other technical stuff. So let me tell you about how I got recruited into Peek by Amol Sarva, @amolsarva.

    Sell Vaporware

    Amol had one VC committed to Peek in our A, and had a letter of intent from Target (yes – www.target.com – that Target) to sell Peeks nation-wide, in-store in the US. The status of the “product” – he had a carved out a wooden model of the Peek (ala Palm)!! And these deals were huge – a $15mm A round with half committed. Target – nation-wide for Christmas 2008!! These days I hear too much crap from “deal guy” founders about finishing product before doing deals. Lame. Be a stud – go sell vaporware. Go get real customers who pay you real money. Go find partners and distributors. I have seen countless, great sales guys in my life sell smoke and mirrors. Why can’t you?

    This guy hired me

    Hire Other Studs

    Amol had recruited John Tantum, former President of Virgin Mobile USA, as our chairman. He had an all-star marketing & retail guru lined up. Our advisory team was the president of BlackBoard, SVP strategy at Intuit, and the former head of the FCC. No matter what, I knew I was going to learn and have an awesome experience working with some great folks.

    Be Generally Awesome

    Amol was an interesting guy in general. He had a PhD in Philosophy from Stanford. He was/is building a new property in Queens. He took a photo that hangs in MoMA. The blog I write on is startupnorth, the “blogs” he writes on are Salon & Business Insider. Being generally impressive is important. The important question here is the Peter Thiel question, why is employee #20 going to come work for you? The weight of the CEO’s personality and accomplishments matter here. Senior guys will want to know the accomplishments of your business as well as the accomplishments of your management team. You have to be generally awesome enough to bring people in if you aren’t one of those super red hot, Twitter-esque companies.

    Be Top Amongst Your Peers

    Amol, while starting Peek, was mentoring other founders. He was one of the original members of Founders Roundtable. His peers looked to him for advice on starting a company.

    Now, I know this is a bit of a love-in of Amol. And it also probably feels like a pretty high bar. All you have to do is go get a PhD, raise $15mm and get a distro deal done with the second largest retailer in the US before you can hire great technical co-founders.

    Not quite. The main lesson is this. Forget your technical co-founder and realize that the “product” is one aspect of your business. Potentially an important one (also potentially a complete waste of time you need to pivot off of). You need to start consistently proving that you can make this business successful without having a “heroic engineering, product only” mindset. Can you on a day-in, day-out basis creatively solve the problems of the business such as acquiring customers faster/cheaper, reducing churn, recruiting great folks, financing the company’s goals, having great customer service, delivering everything on-time, getting great advice, navigating treacherous competitive waters, and so on and so forth. Can you relentlessly out-execute with or without the crutch of great product and fabulous engineering? The way you have built the business pre-launch tells me a lot about how you will run the business post-launch.

    If you can do stuff like Amol did, you’ll be fine. If you are buying sandwiches… sorry, go find someone else.

    I’d love to hear from other founders (technical or not) on how they both built their company pre-launch and how they found their technical co-founder.