Watch me as I navigate…

...our career site. I know this is one of the biggest hassles for the active job seeker. Sometimes it seems so complicated that you are looking for the quick out ("can't I just send you my I have to do all this?"). Because us recruiting folk know the back-end and how the selections you make on the jobs search page can impact the results returned, I guess I can offer a little help. Plus most of us, if not search gurus, are power users of search so let me help out a little here with some tips. These tips are about our site, but I suspect that some of the things I am going tell you apply to many, if not most, corporate websites.

Can't I just submit a resume?

Oftentimes, you can submit off the main jobs page without serching jobs. But you may have to look for that option. Windows users, control+F and enter "submit" or "apply" to find this link. But before you do that, decide if you might want to tweak your resume with company specific verbiage first. Also depends on how much time you want to spend looking at each company and how high the company is on your wish list. For your top few companies, I'd invest the time on the career site (and off by the way) doing some research before submitting (incidentally, I encourage this for people applying to Microsoft via other channels...there's alot ot be learned from the career site). Also, if you are going to cut and paste your resume, paste it into a notepad (.txt) file first to remove the formatting...this gives you some control over how it looks in it's inevitable format. Otherwise, it gets converted to .txt anyway. Better for you to see how it looks in that format first before sending it, don't ya think?

Pull-down menus

They're everywhere. You don't have to use them all. For the ones that you are going to use, I would recommend scrolling through the whole list to see what else is there. For example, if you scrolled down to Product Manager (under title), you might not think to continue down to Technical Product Manager, but it's there. Whatever the menu, see if multi-selection is an option. But don't feel like you have to use a menu if it doesn't make sense. I like to do a broad initial search and then look at my search results to gather info to narrow the search. For people who aren't as familiar with titling and categories at a specific company, I think this is the way to go.


Speaking of titles, what the deal with them anyway? They aren't the greatest search criteria. Microsoft's Marketing Manager might be a Product Marketing Manager elsewhere. Even within the company, a Product Manager for one team could have very similar responsibilities to a Marketing Manager in another. Titles are standardized here but there will always be roles that straddle the line.  I wouldn't start with title as a search criteria. You can use it later to narrow down if you need to (once you get some initial search results).

Job Categories

I think this menu is meant to go broader than title, but I think about it similarly. Try to search without it, if you need it, scroll the whole list and try multi-selecting. Again, there are fine lines. Someone who manages relationships and marketing strategy with an ISV could be "Channel Marketing" or "Business Development". What you think of as product management, might be considered program management here. Again, go broad, collect info from your search results, then narrow.


It is what it is.  If you are open to relocation, leave it blank. If you do use it, notice for example, there are listings for Palo Alto, Mountain View and San Francisco. Scroll the whole list if you need to select something, then decide. If you know something about the company, you can use this to focus in on a division if you want. For example, if you wanted to work on the Passport team, searching Mountain View might help. Of course, I encourage you to search WA-Redmond.


You have a couple options here. First, if your dream job is in a particular product space, you can search it. Doesn't fit my recommendation around starting broad and then narrowing, but I realize that some people are looking for that one dream job (keep in mind, there could be jobs that you don't even know exist...never dared to dream of...OK, I'm being dorky but you get my point...who knew there was a thing called "Technical Evangelist" until there was). You could use this menu  if you have technical experience (or tech marketing experience, or product management experience) in a certain domain and (important part:) only want to work in that space. Here again, scroll through the whole list because there could be some cross over or our naming convention could surprise you. Also consider that many jobs don't align with a product (mine for example, unless you consider happy employees, recruiters and hiring managers a product). Many marketing roles are aligned with a market segment but not a product. So go broad if you can bear it.


The Rosetta Stone of the career site. This field is your friend and can often cause frustration (or a challenge) as you search for the "just right" words. Use Boolean logic to select 'this OR this, but NOT that' (trust me, it's an art not a science).  I wouldn't use titles as keywords (it will just get you the same thing as using title as a search criteria or you may pick up jobs that describe working with someone with that title, which isn't very helpful). Also, think about how things could be explained or abbreviated; PR versus public relations (which is a tough one anyway, you'll have to use other PR related keywords to get the right results). For example, if you are an Accountant, you might try: ("GL" OR "ledger") AND (reconcil* OR "balance sheet"). If you only use "Accountant", you won't get "Accounting Manager", "Accounting Analyst", etc. Here's how I like to think about keywords: they are clues that get you to the result, they don't define the result. It's directions to someone's house with a description of the exterior, not their street address. Get it?

What to do with your results

Now you've gotten back a list of jobs. If you look through the first few and they seem like the right ones, that's great. If you want to go back and tweak your search, there are a few things that I would do. First, look at any jobs that ARE a fit. Review the title, job category, etc. Also browse the descriptions and make note of any keywords (do works...use the words in the job descriptions as keywords to find more similar roles). If you feel like you want to narrow your search results, you can use these common elements to find more of the same. On the flip side of that, if you are looking at the jobs you don't want, you'll find which of your search criteria need tweaking...maybe you need to not use one of the pull-downs or select a different value. Maybe your use of the word "program" pulled up a bunch of programmer roles and you want program management. This second method requires more experimentation because you are making assumptions based on what you don't want versus describing what you do.

How do I communicate with recruiters about the job then?

Let's say that you are e-mailing a recruiter about a specific position you found on the career site. Easiest and fastest way to get the recruiter to the specific opening is to provide the job code; which on our site is a six digit number in the upper right corner. Because these codes are unique, the recruiter will be able to find the exact opening to which you refer (take that grammar police). Also, if you have ongoing communications with a recruiter about jobs, I encourage you to always include your resume in the communication. Think about it: a recruiter may have hundreds or thousands of resumes on their hard drive (or even inbox) and you likely just have one (yours). Also, it makes that mail immediately forward-able (this is a good thing), with a resume in a pretty document versus the text version stored in our database.

Why broad then narrow?

I know there are people that start with a very narrow search first and then broaden it. The reason that I don't do it that way is that it doesn't give you much info to decide how to broaden your search. Let's say you filled in the drop downs, added some keywords and got nada. How do you know what to tweak to get better results? Whereas, if you do a broad search, you can look at the results you get and use the category, title, product listings to eliminate what you don't want or focus in on what you do. I always go for the informed approach ; )

Hopefully, I've made career site job searching easier for you. Sometimes you just have to try stuff, see how it works and then go back and make changes. The mistake many people make is trying to use too many or too few search criteria and not knowing how to find that middle place that gets them what they are looking for. Of course, all of my advice above is generic. I'm sure there are highly specialized roles where you *could* search by title and get them, I just wouldn't assume that it's the role you are looking for. And I'm just not sure of what those roles could be. So I guess the biggest pointer is to think about what will work best for you based on what you want to find and the tips above. Helpful?

PS: bonus points to you if you know what song I was listening to on my way into work based on the title of this post.

Comments (12)

  1. Tim says:

    Excellent topic, Heather! I may just steal this idea for walking applicants through our site (don’t worry, I’ll site you). We’ve made ours <u>tons</u> easier, but still many people don’t want to walk through the simple sign up procedure and would rather just "shoot a resume over". I understand sending to an e-mail address may be quicker and seem a lot more human, but we’ve developed this whole system to make sure every applicant who puts their information up gets the most eyes on them they can, plus they can access a whole online database of open jobs.

    But, still, I’ll take any resume we get and forward it on, no problem – I just don’t think it might be the <u>best</u> and brightest way.

    And, by the way, you used "The Rosetta Stone" in a post!

  2. HeatherLeigh says:

    I know…check me out, I’m cultured, huh? I forget which museum I saw it in..the V&A, the Tate…darn English beer, I don’t remember!

  3. Mark Tookey says:


    Now don’t you go blaming our beer, it’s only a lack of practice…


  4. Jonathan says:

    Great overview Heather on the process that I’ve been trying to wade through over the past two months. You mentioned that one should send a resume along with the email to the recruiter, but should the resume be sent everytime? (ie, I have five jobs I want to submit for, therefore should I send five separate emails with my resume attached OR one email with all five job codes and my resume attached or ???)

    Also, is it better to directly email a recruiter or use the "apply for this job" link from the job description area?

    Thanks for your help.

    BTW, I think you were listening to "Feel Good,Inc" by the Gorillaz. Specifically, your post title was from the lyric "Steady, watch me navigate"

    ~ Jonathan

  5. HeatherLeigh says:

    Nice work Jonathan. You got it. I love that song. Guess I could have done a better job of quoting the lyrics ; )

    Your question about e-mails and resumes: I think just one mail. It depends on who the recruiter is and what they are doing with the resume. If a mail were sent to me with a resume attached and 5 job codes, I’d forward it to all the recruiters associated with those jobs. I wouldn’t need separate mails. In fact, I like the idea of having multiple recruiters on the mails because it creates some gentle competition (candidates can be considered for more than one position, but recruiters generally like to be the first one in touch with the candidate).

    So if you know a recruiter that will indeed route your resume to the other recruiters (like me, for example), that is better than using the apply button because your resume goes to someone’s inbox. When you use the apply button, it goes into our system where the recruiter has to retrieve it and at that point it’s been converted into a .txt format, so it’s less pretty.

    Great questions.

    Mark, I could practice more with the English beer but not sure my liver could take it. ; )

  6. Nathan says:

    The Rosetta Stone is in the British Museum. I don’t think it helps with navigating huge websites, though.

  7. HeatherLeigh says:

    One of my co-workers filled me in on that. She has a higher alcohol tolerance than I do. I must have ODed on the museums when I was there.

    I’m pretty sure it pre-dates the internet (is everyone being literal today , or what?), but maybe we should ask Al Gore just to check. Did he discover the Rosetta Stone before or after he invented the internet (sorry, cen’t help it).

  8. Jonathan says:

    Heather, one of the career search issues I’m confused about is job titles. To point, on my resume should I list the actual job title I had at my previous companies or do I try to form fit them to the job/company I’m applying at? If I was a "Product Marketing Manager" in title at a previous company should I list that, even though at Microsoft the responsibilities in most of the job listings might fall under Product Manager too?

    How much weight do the job titles on my resume carry in regard to the MS internal career search engine? Is that the first thing that pops up when you’re looking to fill a req or do you keyword search throughout the resume?

    Thanks for your insights.

  9. Nathan says:

    The other interesting wildcard is the difference between my official–HR assigned–title and the ones I actually used. According to HR, I was a SR PLM MANAGER II at my last job (it was always all caps, musta been off an old software package), but I didn’t work in PLM (product line management). So, I had cards and email sigs that said Senior Manager, Advanced Planning, and later, Senior Marketing Manager, which more accurately reflected my role in the company.

    My resume has the descriptive titles; I usually assume a recruiter checking my background would understand.

  10. HeatherLeigh says:

    OK, guys, here’s the deal with titles. Good recruiters don’t look at them all that much. We know that titles differ, so the text of the resume is important to me, mostly of your most recent experience entry. Keep in mind that a reference check could yield your current title. So I wouldn’t go too far away from your "actual" title…at least the title that someone at your company would confirm. Don’t worry about matching to the title of the company you are applying to. That is the recruiter’s job and if they aren’t doing it, you might think twice about working there. Job titles aren’t weighted within the database search… they are all just keywords; unles syou use the resume builder on our career site AND the recruiter searches on the title field, which they don’t (I only know this because I was a trainer for our Candidate Tracking System).

    As far as official, internal titles with designations (II versus III), they are meaningless unless the recruiter is extremely familiar with your internal structure. For example, if you are in the bay area and your company makes server software, I bet the recruiters at another bay area competitor know the diff between II and III, but since there’s no consistency between companies, it ultimately doens’t matter. The recruiter will liekly lok at the skills and then, during the interview process, determine where they think you should come in within their company’s structure.

    What I would do is this:

    1) Stick with the most basic version of your title that you feel is a good descriptor, sans numerals, etc

    2)If your title isn’t a good descriptor, do something like this: "Software Development Manager (Product Management position)"

    3) Take advantage of the text space to get those keywords in that will attract the recruiter.

    End of the day, it doesn’t matter as much as people think.

    Hope that helps!

  11. Heather Hamilton made a recent post about &quot;How to navigate the MS career site&quot;. You can find the link…

  12. smith says:

    nice and tramandus job u have done for the markitting seekeers that make me to appricitate your skills

Skip to main content