Our Team Is Hiring: THREE New Positions Open – North America and Europe

As Gartner GTP client inquiry volumes grow, our team needs to expand again. We now have THREE positions open (one long-running replacement hire and two expansion hires). So … our team at Gartner for Technical Professionals (GTP) is HIRING!

If you already read my tips in the past, go and apply at the links below:

AWS Builder Community Hub
  1. US/North America – Network Security (apply here – code 00011882)
  2. US/North America – Application Security (apply here – code 00021384)
  3. Europe – Security Programs (apply link TBA later – code 00021383)

Generic job description for our team – with my highlights:

  • Conduct research and analysis in specific areas of expertise targeting client’s key initiatives.
  • Deliver high quality actionable advice through a variety of media.
  • Write high quality, clear, actionable, advisory research documents.
  • Remain ahead of the curve on developments and issues within these specified areas as well as applicable adjacent areas.
  • Respond to client questions, create materials for and deliver to clients in person, via teleconference, video conference or webinar and event presentations
  • Maintain the Gartner’s industry leadership reputation by responding to press inquiries
  • Proactively work with the wider sales organization and deliver outstanding sales support in order to retain and grow the business

In essence, your job would be to do research and write papers [1], advise clients (via phone inquiries / dialogs) [2] and speak at events [3]. Also, we do list a lot of qualifications, but you can look at my informal take on them in this post.

A few common questions that candidates have asked in the past:

  • Location? Any location in the region noted (e.g North America or Europe) would be acceptable, mostly due to the desired time zone for client call coverage. This is negotiable for these roles, to some extent. You will still work from home most of the time.
  • What does occasional travel really mean? In all honesty, there is not much travel, apart from 2-3 Gartner events per year, really. If you want to travel more, you can. Probably cannot travel less than 1-2 times a year.
  • Do we really need 10 years of experience? Well … we don’t really need TEN years, but we do need diverse and extensive experience in the real world (ideally, “vendor + enterprise/government + consultant”, but “pick any 2 of those” works as well, with enterprise/government security architect being the preferred background)
  • Do we really need a college degree (advanced or bachelor)? Frankly, no. We have people already working on the team without such, and they are great. Still, if you have a PhD, this is great as well. In any case, many people with advanced degrees working in security have them in areas other than security [like, say, me]
  • Is this a technical role? Well, it is a role for a technologist, a person who was recently hands-on and/or has a deep understanding of how security technologies work inside the box. However, Gartner does not really do lab product testing (you are welcome to have a home lab, of course, and some security analysts do) so there is a risk of losing some of the cutting edge technical hands-on skills. Ideally, you should be able to retain them (mostly) via ongoing conversations with “people who do stuff” (as opposed to “just talk about stuff”), but it may be challenging for some…

Now, let me share some Anton’s super-secret interview tips (learned by our team from the experiences interviewing many candidates in the last 6 years or so) – ignore them at your peril!

  • When preparing for a group interview [a second stage in our interview process], you will be asked to write a mini-paper and then defend it. By god, pick a topic you know really well. I feel stupid even saying this, but some candidates sunk since they picked the topic “they wanted to explore.” Hell no! Put your BEST foot forward!
  • When writing a mini-paper, re-read the text for clear and logical structure and potential value for the readers. If you need to rant, get a blog. Think of this as a mini-research paper, not a mini-vendor whitepaper – your point is to help, not to sell.
  • Now, an actual super-secret tip: the key to success at our group interview is to be firm-but-not-defensive-or-too-pushy, and let me tell you this is really hard for many. However, if you are TOO FIRM (“NO! You guys are just wrong!”) or TOO SOFT (“Yeah … perhaps this is also OK.”), you will not be hired. This is important!!
  • To expand further on this, pick a position and be ready to defend it with facts and materials in hand. As one of our freshly hired team members said “don’t get wishy-washy during the group interview
  • Finally, behave professionally during the interview! And… eh…one more tip: for fs sake, don’t ask “how many more twitter followers will get if I join?”

P.S. If you have questions, feel free to email / tweet me – I cannot promise a prompt response, but I sure can promise a response.

Related posts related to hiring:

*** This is a Security Bloggers Network syndicated blog from Anton Chuvakin authored by Anton Chuvakin. Read the original post at: