An inevitable part of a career into consulting involves additional interviews. You will be submitted to multiple hospitals, clinics, and Epic hiring managers. While it seems scary, the whole process is intended just to get you on the phone for an interview. Of course I have also been at a client where they wanted to hire an additional consultant, instead of calling each of them separately the PMO simply dropped a stack of resumes on my desk and asked which one sounded the best. No interview, they were just brought in. The resume is just important in this scenario as well.
Take Stock of Your Skills
While obvious, I always end up with writers block when I start writing or updating my resume. So instead of listing employers, I begin with a full list of my skills. You best friend here is either a pencil and paper or a word processing system. Since you probably refer to this for the rest of your professional career, you can also maintain this list in a cloud or easily accessible program like Dropbox or Evernote.
So with your pad of paper out, just start listing every skill you can think of. Not just ones that are Epic consulting related. The thing to remember is that if your Epic Resolute Professional Billing resume was being compared with another Epic PB consultant, what exactly are the differences between you? You both can create workqueues, rules, and created new EAF records. Do you submit a smiling picture of yourself along with your resume? No soft skills are what will separate you from another candidate.
So take stock of everything you know. Did you study Java in college? Maybe the client is needing someone to actually help the team lead with their project management skills but they did not include it in the job description. You might not be a report writer, but you can still be a whiz at Excel. Take stock of all these items.
List of Professional Clients and Experiences
Similar to your list of soft skills, for every health system you have worked, list every project you performed. If you were to build a Project List Resume, it would be similar to this process. For every client, in chronological order, create a full list of projects you worked on. Similar to this:
- Created new department for Durable Medical Equipment office
- Implemented collections process for entire professional billing health system
- Updated charge review workqueues based on new organizational structure
- Worked with several Epic teams to install Global Billing Package
For each client, you need to maintain a list like this. Your job in this step is not to try and fit everything on to one or two pages. Create a full list of every project worked through and keep it separate from your resume.
Power Trick For Project Lists
More than likely, you will not be able to remember every single project for every single project you have been a member. Remember how I mentioned Evernote? As you are working with your clients or even in your current Epic Application Coordinator job, keep a separate list. Use Evernote to maintain your list, then you can also just pull it out for your resume.
Another tool I really like is Microsoft OneNote. This works like a document management system where you can maintain lists, projects, videos, and screenshots of builds and Epic implementations you are working through. While working on your project list, you can peruse your projects and pull them into your resume.
Largely a Numbers Game
As an Epic consultant, the PMO receiving your resume is concerned largely about their return on investment. You can say some of your projects were effective, but how do you prove this? Probably the same you way you proved it to your client. You didn’t just resolve a problem, you probably reduced provider workflow by X number of keystrokes, released X amount of AR, reduced denials by how many dollars.
All of these numbers show you are not only an expert in your field, but you can produce with results this is also called quantifiable successes. You may only need one or two examples per client to really show your knowledge in this category. The more examples the better though, this is still a brainstorming category and you want as large a list of Epic build or projects as possible. Remember you want scenarios showing how much, how many, how often, how frequently.
For example which of the two statements look better to you if you were hiring a new Epic analyst?
- Updated rules to reduce volume of claims in claim edit workqueues.
- Modified several claim edit checks to reduce volume of claims incorrectly held by $250,000 over a two month period.
The second one is the obvious choice. Why? There are quantifiable results showing what happened when analyst two modified the claim edits. There is a dollar volume and time period measurement present. Whereas for the first analyst, all we know is they were modifying rules, and we do not know how effective they were in that case. So make sure to accumulate your examples and keep them on hand.
Defining the Customer and Building Experiences
Before walking into an interview, interview experts will recommend you scout the business prior to entering the interview. My recommendation is to scout the business before you even start creating your resume. Even the minimal reviewing of the consultant requirements will glean some information in how to craft your resume.
As you move forward in your career as an Epic consultant, you gain access to a variety of soft skills and new Epic certifications. (Yes consultants can gain about one new certification a year.) So at each client you will inevitably practice different skill sets that apply to some clients but not all. The key is identifying the job you are applying for. Within each job there are a variety of keys in the position that will allow you to craft your resume.
Some key questions to ask yourself
- Do they want community connect experience?
- Does the position allow you to utilize all of your certifications or just a single one?
- Would any of your soft skills apply?
- Would any of the projects you have completed in the past mesh with the requirements of the position?
Attempt to match your project experience and soft skills with what they are asking. By pulling this data directly from your list of soft skills, quantifiable successes, and successfully projects, there is not much left you need to do to complete your resume.
Do You Need a Summary In your Resume?
Some people leave a summary in their resume and others leave them out. The inclusion of exclusion of this summary really depends on your list of experiences.
- Do you have enough project experiences to flesh out your history?
- Are you having trouble filling a single page of professional Epic Experiences?
- Can you explain what you hope to accomplish in your next position better than what is listed under your experiences?
- Are there any strong skills you possess that should be highlighted at the top of your resume that are not considered a certification or degree?
Keep the summary at four lines and do not become personal. Just keep it to professional experiences and what you can bring to the table when entering this new engagement.
Unlike the Summary, the Employment History Important
Now that you have what you want to write and have studied your new prospect, you just need to pick a format. Insert your summary if you feel it is relevant and will flesh out your resume. Typically you will then have a list of clients and how long you worked at each. Under each position, you need to include your list of quantifiable projects that you feel are most relevant. You can do this in any order but I would list them in the following.
- Most relevant quantifiable successes
- Most relevant project successes
- Projects completed that could mesh with the client
Anything else listed would just be to fill space on your resume if you cannot come to a full page.
This was really all you needed to complete your resume. Recruiters and IT managers want to see if you are certified and if you have any experiences that can be immediately applied to their current situation. If they see at least one or two items on your resume that meshes, you will more than likely be queued for an interview. This is an entirely different set of skills that we will breach for another day.
Of course I have only interviewed so many times and there are probably some things I could be missing out on when building a resume. If you have any tips, please leave them in the comments below.