Six Healthcare IT Analyst Resumé Tips for Success

In the healthcare IT consulting world, your resumé is the first impression for recruiters or hiring managers. Since hiring firms and health systems look at piles of resumés each day, the first impression is vital. To stand out, check out six tips for healthcare IT analyst resumés.

  1. Put your certifications first. Don’t bury them by putting them after your work experience or with your education information at the end of the document. This is especially important when verified vendor certification is a specific employment requirement.
  2. Highlight the skills most relevant to the position you are applying for within the professional summary. Customize this section each time you submit your resumé for consideration. Focus on your skills, qualifications and past achievements in similar positions. This section also gives you an opportunity to bring any relevant experience that may be buried further down (and possibly missed) in your resumé to the front page. For example, perhaps you are Epic certified in multiple modules and are applying for an Epic Grand Central analyst position. With certifications in Cadence and Prelude, as well as Grand Central, your last engagement was as an Epic Cadence analyst. Use your professional summary to highlight the Grand Central experience, so the recruiter (or hiring manager) does not need to get halfway through the second page before they see the applicable information.
  3. Stay consistent with formatting and verb tense throughout past roles details. While it is okay to use the present tense for bulleted statements under your current employer and then switch to past tense for the rest, that is the only time there should be a difference. Also, it is up to you to end bullet statements with a period or not. Whatever you decide, stick with it throughout the document. Consistency conveys an overall cohesive document to positively reflect your contributions.
  4. Start your support statements with action. The most effective bullet statements start with a verb– managed, designed or built. Avoid the phrase “responsible for” and get straight to the action. Instead of “Responsible for collecting, analyzing and documenting business operations and workflows,” try, “Collected, analyzed and documented business operations and workflows.”
  5. Check spelling with each resumé version change. Be especially attentive to the acronym “EHR,” since Microsoft Word automatically changes it into “HER.” Double check the spelling of various applications and programs you work with, since Word’s dictionary may not have those saved. When you run a spell check and the program stops on an unknown word, take the time to look it over.
  6. Capitalize the first word in a sentence or proper nouns. Avoid using capitalization for anything else. Don’t be fooled by job titles or department names, like project manager, business analyst, director or operating room. Generally, these are not considered proper nouns. Keeping capital letters to a minimum to ease readability. Notice how much more difficult it is to read the first version compared to the second in the example below:
  • Met with Process Owners, Directors, Department Administrator and Access Managers to prep their facility for implementation and Go-Live
  • Met with process owners, directors, department administrators and access managers to prep their facility for implementation and go-live

Apply these six tips and avoid fluff that falsely plumps up resumés. Doing so saves recruiters and hiring managers time, while increasing the likelihood of interviews and potential placement.

Stay tuned for additional HIT consulting tips, and check out Stoltenberg’s current job openings.

Do’s and Don’ts for Common Health IT Interview Questions

Regardless of your specific HIT software or application specialty, the questions interviewers ask and the topics they touch on are often similar across the industry. The following three interview conversation tips are useful for any health IT systems consultant, whether you work with Epic, Cerner, Allscripts or another major EHR vendor.

  1. Implementation deadlines

Don’t: Bring up blown deadlines and blame them on user resistance.

Example: “There were some issues in the build phase, and the implementation took longer than expected because of physician push-back.”

Do: Highlight the methods you used to help user buy-in for the system changes. Discuss your communication skills, specific contributions to past projects and how your work impacted overall project success or end-user adoption. Clients want to hear how well you perform under challenging conditions, not excuses for failures.

Example: “There was some pushback at first, but I was able to show users how the new product would make their lives easier. I did this by talking directly with end users to understand their concerns, educating them on how the new product works and how it will improve their workflow. Once they realized it wasn’t just change for the sake of change, we could push through the typical resistance and complete the implementation on time.”

 

Campus Interview Icon

  1. Past challenges

Don’t: Throw your previous client or consulting firm under the bus when asked about past challenges.

Example: “The last project I worked on was with a hospital that had a lot of issues. They were disorganized, their processes were confusing and the whole thing was a mess.”

Do: Focus on how you overcame the challenge instead.

Example: “When I first arrived, lines of communication were not optimal, and it was hurting the ability to accomplish project goals. I made sure everyone was on the same page by acting as liaison for my team. I worked with other departments to ensure responsibilities and timelines were clearly mutually defined. This pushed analysts in other departments to talk to each other about their needs and issues. That way, we could make sure everyone on the team, organization-wide, worked cohesively.”

  1. Rating your team performance 

Don’t: Tell the interviewer how much better or harder you worked compared to other analysts. This can make you seem like you’re not a team player.

Example: “There were six of us on the team, but I was the one who the client liked best and the only one who had a contract extension. I did almost all the job myself because the other analysts were inexperienced and didn’t know what they were doing.”

Do: Focus on describing how your work contributed to positive outcomes for the team. If you found yourself taking on extra work, say it in a way that doesn’t put the rest of the team down.

Example: “There were six of us working together on my last implementation, and I put in extra time to mentor less-experienced members of the team and ensure their work was of the best quality. When we ran into snags, I had no problem stepping up to help resolve the problem, so the implementation could be a success.”

By approaching these three topics from a positive angle, you can greatly increase your chances of interview success, showing that you are an experienced team player. Stay tuned for additional HIT career insight from the HITStoltenblog, and email us at stoltenberg@stoltenberg.com for any new topic requests.

-Melanie Streeter, Health IT Systems Recruiter