Epic’s User Group Meeting. For many recent years, UGM has been covered extensively by Madison local newspapers and trade press from around the United States and internationally. It’s quite a spectacle.

It wasn’t always that way. In fact, when I started it was nearly the polar opposite to what someone might experience today if they were to attend.

The first UGM I attended in 1993 was held in the The Madison Concourse Hotel conference center. I’d not been in a hotel conference center before, so I had zero specific expectations. My memories of the facility is that it was fine, very bland, very corporate, very practical. Epic had reserved most of the rooms for various events and sessions that would take place. There were a few broad general sessions with teams parading on stage to discuss upcoming application functionality. They were long sessions. In the era before mobile devices, wifi, laptops, this meant you were either captivated by the content, or lost in your thoughts (or an occasional napper).

The theme that year was…oh, this was before the annual theming became a thing. So, it was themed as Epic UGM 1993. The attendees were quite varied. Remember that this was before EpicCare was a thing with sales. A lot of content was focused on application functionality, but there was a healthy dose of technical content too. Many earlier Epic customers had IT and developers extending and modifying the core functionality at the time. There were courses on Epic’s database for example, Chronicles.

Leading up to the event, Epic employees set up a ton of terminals in the Concourse conference center so that “live training” could take place. I attended most of the “programmer” focused training sessions as a way for me to get up to speed on Epic’s technology stack. My only recollection really is that they were well done courses for the customers. I found them to be very slow paced for me, but I wasn’t the training target.

UGM was absolutely an all hands experience. I don’t recall what I did leading up to the event (I was quite overwhelmed by new employment, a conference, customers, MUMPS, etc.). The entire company was laser focused on UGM during the weeks leading up to the event. We had a number of all staff meetings and there were many many preparation meetings. Practically speaking, very little other work was done leading up to UGM in the month prior. If we weren’t doing UGM prep in some way, you’d likely get a stink eye or two. 🦨👁️

Modern UGM attendees are spoiled by the multimedia extravaganza and spectacle. Remember, this was before fancy digital projectors and before PowerPoint was nearly on every business computer. We had transparencies and overhead projectors and microphones. There was a video projector as far as I recall in the main session room where the Epic applications were shown in their Sunday Finest.

I’ve had to socialize/mingle over the years at many events, but nothing like UGM. I’m an introvert by default, so when my team leader said we’d all been assigned a specific person (a customer’s employee) to shadow and be sure that they were always “doing well” and was having a productive and useful experience, I was more than a bit terrified. This was a person I’d never met nor talked to and I was somehow supposed to stealthily monitor their happiness during UGM. 😬😳

One of Cohort’s customers was the state of Texas public health lab (Cohort = Epic’s Public Health Lab software). My assignment was one of their employees, Ron. I was assured they were all friendly. Not surprisingly, that doesn’t make this introvert feel any better. (“Are some of them not friendly?“)

In any case, when UGM started, my TL introduced me and I proceeded to rather poorly I think try to interact with Ron over the few days of UGM. What’s amusing I suppose is that they knew this was happening too and just played along.

If you wear a suit routinely because you have to, I am sorry. I thankfully donated my last suit when I left Epic. Back in 1993, Everyone had to wear Business Formal. Including customers. It was just the expectation that this was a formal event (the UGM invitations for many years said as much). It was in such stark contrast to Epic on a day to day where anything went, shorts, t-shirts, etc. (And in August in Southern Wisconsin can have some brutally hot and humid days). I didn’t have a suit, so I had to buy one for the “once a year” need. I had to relearn from my father on how to tie a tie the easy way. I’ve never learned anything but that basic knot.

Epic’s UGMs have for decades had a dinner event and in 1993 it was held at a local private event space in the Madison Club. I suppose it wasn’t held in the hotel just to give attendees a break from being in the hotel (but there may have been more to it than that). My recollection is that the dinner was held at this same location the following year. So, I may be confusing the two events, but all I remember was that the facility was essentially at capacity for attendance and some of us, well, less-important staff and products were relegated to an off-room of some sort. For those of you with big families who have attended an event where the kids were in a different room at a table, this had a similar feel. But, what I remember the most was that it was FREAKISHLY HOT. Like a sauna. In my suit.

It was awful. There were too many humans and an overcapacity cooling system that hadn’t paid attention during the UGM prep meetings to keep customers comfortable.

Epic has had a formal way of customers directing development directions over the years. One of course is money (and sales prospects). But, in absence of an extra spend on software functionality, customers have had the opportunity to vote on what was most important to their organization. In advance of UGM, current customers would receive a list of options with some details about the functionality. Each Epic product team would hold a special session going through more details of future development directions and then would step through the suggested options for functionality that could be scheduled. Each customer would then be able to cast a certain number of votes (or rank) helping Epic decide what was most important during the next long development cycle for a product. What was interesting about the process is that it appeared to be a transparent democracy in many ways as these items were discussed. Customers would be able to see what was important for other customers in addition to their own requests. The votes/ranks were completed by the end of the session. The full results however were not given back to customers and were generally only a team guide/influence. Unfortunately, there wasn’t a level of accountability during this process, but very often the ranked/voted functionality was scheduled and worked on. Most importantly, large customers had no more votes than a small customer.

As customers were often suggesting features during a development cycle, this process helped them focus their interests on functionality that was most important to them. There were definitely healthy discussions during the voting sessions too. When Epic was smaller, these meetings had fewer attendees too and I know that one customer’s enthusiasm and need for a feature could transfer to another customer who would end up deciding that they too would benefit from a feature. That type of immediacy and interaction is missing in many software planning discussions unfortunately. A forum post or a thumbs-up 👍 on a feature request isn’t the same. Of course, even then there would be some vocal and opinionated attendees that could derail an otherwise positive discussion (not unlike in a online forum today).

I’ll leave you with this …, downtown Madison not being on a North-South / East-West and having the Capital be in the center with roads wrapping around …, has never never clicked with me. I’ve not had a useful mental model of the streets or layout. It’s broken in my head. I’d not been in the downtown more than a few times ever in my entire life, so nothing was familiar.

So, one day when I left the parking ramp on the way back to my apartment, I was attempting to navigate the streets, discovering more and more places that I didn’t recognize. I didn’t have a map of downtown, only a general map of Wisconsin. With a weird mix of extreme unhappiness and delight, it wasn’t until I drove by the street that eventually goes to the Dane County Airport that I could find my location on the map (the street is called International Lane, which is funny as Dane County Regional airport doesn’t have international flights ✈️).

I was 45 minutes from my apartment. I’d been lost for about 30 minutes. So, what should have been a 15 minute trip turned into more than an hour. Ugh.

My first day at Epic was August 23, 1993. A Monday. I don’t know why I’ve remembered that date so well over the years — it was my first full time job and I suppose that’s locked the date in my brain. Do others remember their start dates too?

It was a remarkable Monday at Epic. And not because I was starting. 😎 Never before had more than 2 people started on the same day. If you’ve seen Epic hiring days during the busy hiring years when 100+ would start on a single day, then 2 probably sounds ridiculous, downright impossible. But, in a company that had fewer than 40 people at the time, hiring 4 people was worthy of a big Note. I remember the names of the others that started still to this day even though I’ve not seen them in decades (I stayed a lot longer). Now that I think about it, the staff hired back in the 90s was quite different from a more modern Epic, and it wasn’t just because of the grunge style popular then.

On that day, I was the only new employee that had no full-time job experience prior to Epic. I was fresh out of college and still had that new-college smell. One of the new hires was placed into a customer facing support role, one was software development, and the other had a few roles that crossed areas. Epic hired software developers often fresh out of college, but not nearly as frequent in the 1990s. New college grads became more common at Epic as the number of job openings increased. In fact, it became rare to encounter someone with prior working experience in software development joining Epic. I do have a topic queued up to talk about the pros and cons of that hiring practice.

The first few hours of Day 1 are a bit hazy but I know there was some paperwork to sign, but not too much: healthcare, confidentiality agreements, employment agreements, etc. We didn’t have ID cards or anything of the sort. Weirdly, I was hoping for a badge as that was going to be a “right of passage” for me. I can’t recall whether we had actual keys to get in … I think we were given keys. The basement of the building had a dentist’s office and a secondary door which was locked, preventing patients of the dentist from making an unexpected visit. The front door was always open during business hours.

Donuts 🍩

Even back in 1993, Epic had the concept of a team mentor that would provide some guidance during the orientation period of employment. I’m sure I met my mentor early in the day — and then we went to gather a donut. One of the long traditions at Epic through the early 2010s or so was on an official hiring day that donuts would be supplied for all employees. The idea was that the donut feeding area would be a gathering place for the new hires to meet existing existing staff and start the day off with some sugared goodness. We hung around in the kitchen for 15-20 minutes and met some staff that way while I enjoyed my (probably) fruit or chocolate cake donut (my first choice when available).

Admittedly in practice, even back then, there wasn’t much donut eating & mingling going on, but the idea was sound. Usually people headed to the kitchen and grabbed a donut and ran back to their offices. No one complained loudly about free donuts. Seriously. (I think there were occasionally bagels too for the non-donut lovers).

Meet My Team

I started on Cohort. Cohort is one of the few Epic applications that was officially put out to the Midwest pasture (AKA sunset or retired). Some portion of its code base lived on in Epic Lab, later to become known as Epic Beaker. Cohort however had an unusually limited market, as it was specifically designed and built for (USA/Canada) public health laboratory systems (of which there was one in each state of the USA and provinces of Canada). So, maximum number of customers: 60 +/-. At the time I joined, there were 4 customers. And, now there were 4 employees on Cohort. There had recently been two departures from the team, so I and a customer facing employee were the shiny replacements.

My TL by the way was the same Epic employee that I’d told: “I just want a job.”

I do wish I had a screen shot of a workflow of Cohort, but given the era it was created and the privacy controls Epic has around it’s software and screenshots for decades, I’m not surprised I cannot dig one up. You’ll need to use your imagination — 80 characters wide x 25 characters tall. Lots of text, some ASCII art lines, and a square blinking cursor. It was a terminal based application. For those of you that occasionally dabble using modern terminal based applications, you should have a good sense of what it was.

Not Much for Day 1

Epic did have a basic training plan for new employees and it shared some content with customer facing technical training. My training would start later due to scheduling issues with the upcoming Epic User Group Meeting that was going to be held in about 2 weeks from my start date. I’ll talk more about that later.

Epic employees that started before the Verona campus did not have a cafeteria available. So, what had been tradition even back in the early nineties was that each day someone would pick a restaurant from a folder of places that could deliver and employees would write down what they wanted and leave the money. Someone would call it in later and announce when the food arrived. Epic paid for my first day’s meal — I have no recollection of what it was that we ate that day. Regardless, it was a smart way to keep staff in the building working more and offer a variety of food options during the week.

The Afternoon

My TL gave me the ABCs of MUMPS programming that I mentioned in a prior post and said: “read and learn this.” My mentor and TL would review some coding exercises (named appropriately: A, B, and C). Additionally, she scheduled some time to start to teach some of what a ‘public health lab system’ was and how the software worked both from a programming perspective, but also from the end user perspective.

My Terminal

Few Epic employees started BEFORE everyone had a personal computer or laptop. My first “Epic” computer was a dumb character-oriented terminal (I don’t remember the models, maybe an ex-Epic from that era remembers and could provide that detail). It wasn’t actually a green screen as far as I recall, it was amber. But, you get the idea. Glowing CRT text on a dark screen. Although, it was one of the fancier terminals as it had TWO connections it could maintain to distinct server connections. Two! The licenses and the server resources were limited though, so if you weren’t using a connection to a server, you’d release it.

I realize that many of you have never experienced first-hand a CRT terminal. While you may have used a LCD terminal, or even a CRT monitor displaying a terminal, it’s just not quite the same as low resolution CRT computer terminal and its glowing text (and the ). I sit here typing this on a 4K monitor display — and I don’t miss the glowing text. 😉

This Introvert’s Nightmare: The Overhead Page

If you needed a server resource and didn’t want to wait … ugh. An introvert’s nightmare…all-building paging system and say, I kid you not:: You’d grab your desk phone’s handset, tap a few keys to activate the

“Paging a COMPUTER_NAME line, paging a COMPUTER_NAME line.”

For example, one of the early servers that Cohort developers would use was called Quark. So, I’d need to announce: “Paging a Quark line.” Everyone’s phone would make the announcement immediately. It was so nerve wracking and I hated doing it. I did not grow more comfortable with that task and was very thankful for the era where that became uncommon and unnecessary.

The Simple Script

While there was a basic new employee orientation script for teams to follow, it wasn’t complicated or lengthy:

• Learn MUMPS/M
• Learn Chronicles (Epic database system)
• Learn your application
• Learn other responsibilities needed by your team (I’ll talk more about how broad this was back then)
• Learn “Epic” through a few courses taught by various staff. Judy taught one called “Philosophy of Epic”

I’ll talk more about these though in later posts as this was just Day 1 with Donuts.

Donut Science

Oh my the Science section of Wikipedia’s article on Donuts is thorough.

Questions for you

What was your first day like at your first full time job in your current career? What’s your favorite donut / doughnut? Write me! I want to know! 🍩💖

I’d accepted the Epic job! Now, the “adulting” stage of my life would begin. The first panic wasn’t about moving my stuff. Moving I’d perfected over the last 4 years of college: stuff absolutely everything I could into my car and on-my-way! This would be a bit more “permanent” ideally and would involve a few more trips to get things that I hadn’t normally taken to college with me (like a bed!). Thankfully, the trip from my childhood home to Madison was shorter too, so the move wasn’t a U-Haul like experience yet.

No, the first real panic was: “where was I going to live!?”

On Moving to Madison

I’d either lived at home or in a college dormitory since birth. I’d never needed to navigate any self-arranged rental housing. As with the job hunt, back in 1993, there was no Internet with dozens of ways to look for apartments. I had to … well, I wasn’t exactly sure. There were some apartments listed in the back of the same newspapers I’d found Epic’s job advertisement in, but the majority were people renting rooms. That wasn’t at all something this small town boy wanted to do. I’d had enough of sharing space with hundreds of other people in the dorms and didn’t want anything like that for the forseeable future. Those that were multi-units that seemed like possibilities I plotted on a PAPER MAP. What this young first-time-renter, first full-time-employment guy needed was a bit of help.

Need Help!

I’m confident that I’m one of the ONLY people to ever have done this after getting a job at Epic as it relates to finding housing:

I called Judy to ask advice.

Yes, I called Judy asking if she or anyone else at Epic knew of apartments or even areas of Madison they’d recommend. Seriously. I called her. She never acted like it was a problem (as I don’t think it was), but if you recall from my previous post, I didn’t know she was also the President and Owner of Epic. I called a few times about several topics, but I no longer remember what the others were. I hadn’t been introduced to my mentor yet, that call was much too late for things like this. I’m not even sure if my team assignment had been completed yet.

I don’t honestly know if she followed up with my request for help or not as I didn’t hear anything back (but I left it in such a way that I didn’t expect a “no answers” call). I’ll talk later about Epic’s early internal communication system. Just a hint — there was no “e-mail” or Microsoft Teams like you know today when I started.

Eventually, I drove up to Madison around areas I was interested in one day and stopped in at some of the larger apartment complexes that had availability, looked decent, and were easy drives to Epic. I looked at least 4 or 5 (it was time consuming!). I narrowed it to 2 and then selected a place called “Harbor House” which wasn’t the best choice in hindsight. Apparently, Harbor House also wasn’t a good business model for the owners, as they eventually owed bags of money in back-taxes to the city of Madison and later sold the complex off as condos.

Next up is Day 1 at Epic.

I don’t know if Epic started to provide any general listings to new hires of apartment complexes that had treated employees well (maybe with some discounts?). I know eventually there were some Epic discounts available around town.

If you haven’t read parts 1 and 2, start there instead.

An Interview with Jake

Shortly after my second interview with Epic, I received a phone call from State Farm Insurance, at the time headquartered in Bloomington, Illinois. Having attended my university in that same city, I knew where their corporate campus was and the influence they had on the local community. They had a lot of employees — doing whatever insurance companies do (heck, I know generally, but I don’t know why they have so many employees).

The position was in Data Processing. They didn’t call it software development for Legacy Corporate Executive Decision Reasons. I hated the name, but again, it was a job. I didn’t really want to work there or live in Bloomington. I wasn’t getting job offers left and right, the choice was made.

It was a three and a half hour drive one way. Unlike Epic which encouraged even then a business casual dress code for interviewees, State Farm was a Suit and Tie Wearing Culture. Ugh. Suit culture added to the list of reasons I didn’t want this job. But, as my mother said, I wouldn’t need to work there forever. I could look for other jobs. Sure. That was Mom-speak: “Just try something honey.”

I remember only one interview. I imagine there must have been more, but one struck me and haunts me to this day.

Don’t Interview Like State Farm and Don’t Interview “Corporate-Style”

Someone from State Farm (his name could have been Jake, I don’t remember) explained to me across from their glorious giant wooden desk in a characterless office with a required arrangement of potted plants and photo of a potentially stock-photo family:

“Data Processing is a wonderfully planned career option at State Farm. Blah Blah. You start at Level One and in 5 years, you may be promoted to Level Two, Blah Blah.”

He might have said 3 years, but he may have as well said 20 years. The forced waiting period to be able to advance a career based on time served rather than skill and achievements sent a chill down my spine that I can still feel today. The lack of career growth wasn’t enough though:

“Tell me 5 things that you’re not good at.”

I had mentally prepared for these stupid questions.

The Career Center at my university had nearly covered it. I had only prepared 3! No one had asked for more than 3 before. Here’s the State Farm interviewer, needing 5 to prove that I would be worthy of being a State Farm Data Processor.

I expect that you’re thinking I would be super honest.

I was. I said I didn’t have more, but I didn’t add what I wanted to say: “you gotta freaking be kidding me. How is this providing any value to you?!” I recall stumbling my way through a fourth on the fly, but didn’t make it to his five.

If I hadn’t heard in my head my mother saying, “don’t give up,” I would have walked out of the interview right there and then. The rest of the interview process took place in that room. No helpful tours, nothing. There may have been some sort of test that I took, but I’ve blocked it all but this one key incident.

I imagined what it would be like: a sea of endless cubicles, stretched as far as the horizon, everyone wearing dark suits while quietly pecking away at corporate issued keyboards staring at glowing green-screen terminals. An occasional festive necktie, probably celebrating they’d decided to quit. It was like a movie scene from a secret government storage facility, with endless rows of crates stacked …, but in this case, with cubicles with bright fluorescent lighting that was thoroughly bright yet extraordinarily exhausting at the same time.

I didn’t meet a manager that day to find out what torture I would have endured experienced day to day. I think I may have met a few Data Processors but I don’t remember any specifics. They certainly didn’t provide a lasting impression. I knew I didn’t want a job, and they weren’t offering any meaningful interaction that could have served as “interview practice.” I’m sure they thought I was quiet; I’d already mentally put in my resignation papers. Sincerely, I didn’t care. I might have looked for hints that they were telling me to RUN RUN RUN.

I could not work there.

I also knew that day that I never ever ever wanted to interview someone else using that technique in the future. If a company I worked for asked me to do that, I wouldn’t.

If I had been asked about projects in college and how I’d handled adversity and overcome programming challenges, not only would the interviewer likely gotten less canned responses, but I would have left feeling far better about the interview and State Farm. (Except it still wasn’t a job that I would have wanted).

I drove home with a healthy mixture of anger, relief, and disappointment. It was an absolute waste of a day after driving 7 hours, but my mother and father were happy that I’d tried.

The Epic Call

That night, I’d guess around 8pm, I received a call from a woman at Epic that I hadn’t met during my interviews. She gave me her name, but not her role at Epic. She said her name was Judy and she wanted to offer me a job!

She told me the salary and me, oversharing honest Aaron, said I was very excited, and that I was also disappointed because I’d just driven 7 hours for a job interview that day. I’m sure she thought it was odd I mentioned that, but, that is me. I accepted the offer on the phone (which in hindsight wasn’t an effective negotiation tactic for a small salary increase). At the time, I assumed she was in HR. (In fact, she was in many ways, as Epic had no formal HR department for a few more years.)

So, good timing: one day earlier and I wouldn’t have had the experience of learning how to not interview a candidate.

Don’t Give Up, Keep Practicing

I wasn’t in a position to give up. I know when to stop working on something (plenty of stories about that to come and how to weigh those decisions). Getting my first job was a necessary step.

But, what I did do was keep learning and tinkering while looking for a job. While I didn’t have access to the Internet to explore new technology and such, I did have access to my trusty Borland C/C++ compiler (legally obtained thank-you very much education discount), so I kept coding. Nothing groundbreaking or patent worthy by any means, but I kept my skills active and practiced, in spite of not having a particular target. I knew software development was my future, so I had to keep doing it as often as possible.

I know that some readers are actively looking for a job. Maybe because you were let go, maybe because you’re itching to try something new, or maybe because you’re looking to get your first job (or many other reasons). To you I say, keep at it. You don’t need to spend 8 hours a day pounding at a keyboard to keep sharp. I strongly recommend not doing that unless you have a specific tangible goal in mind. Instead of aimlessly coding, try to broaden your knowledge. Read about technology, business, history, stories of success, failures, interviews with creators, and anything else. Keep your mind active. Get away from the glowing screen for a while, play a board game, go for a walk, talk with your kids, your friends, or even your pets, whatever!

There’s an opportunity out there for you. It just may take some time for them to realize you’re the one.

Questions

If you were job-hunting before the internet, how did you find your first employment?

If you got a job at Epic before they had an Internet presence, how did you hear about them?

If you haven’t read part 1, start there instead.

An Interview with Epic

It was about a week later that I spotted a job in a Madison, Wisconsin newspaper from a company: EPIC SYSTEMS CORPORATION.

The advertisement was very Epic like and left out a lot of details, but they were searching for software developers. Given this was the pre-Internet-answers-all-your-questions days, I couldn’t find anything meaningful about them at my local library (yes, I tried!). But, it was a software development job so I sent my resume in. The job advertisement wasn’t so bad that the opportunity sounded terrible in any way, it just lacked detail.

I got a call about a week later from an Epic employee and went through some basic phone-screening type questions (I honestly don’t remember who phone screened me which I feel bad about!). That phone screen proceeded into an in-person interview (I think there was a follow-up call for this). I was told that my interview afternoon would be a mix of in-person and some test taking. Nervous, but job-needy, I agreed on a time and date.

Anyone who’s worked at Epic or who has applied to Epic knows the drill. While the specifics have changed over the years, the core hasn’t. You’re paraded around, meet some people who mostly just talk about their day and what they do, you’re asked some questions (full well knowing that you’ve only been to college, so the questions aren’t very deep), and then you TAKE A TEST (or two or three).

As I mentioned, the specific tests have of course changed many times but the spirit hasn’t. Back then, the first test was basically a programming language comprehension test for what seemed like it must be a made up programming language; this programming language had some peculiar traits and definitely wasn’t familiar.

It wasn’t till I was hired and started learning the programming language MUMPS (also known as M, AKA Caché Object Script, etc.) that it was clear that one of the tests covered a “must be a made-up programming language” was in fact heavily inspired by MUMPS (and a spiritual predecessor MIIS that Epic had used). The second test was more traditional, presenting a series of questions that needed to be hand-coded in a programming language of my choice. I know I chose C as it was something I was familiar with at the time. The other programming languages I knew at the time would have hardly impressed the Epic test-graders.

One often-forgotten aspect regarding the Epic programming tests is that there’s a mix of speed and accuracy that plays into the final evaluation. Fast and highly accurate is most desirable of course. They don’t tell you this and even if you know it, how it affects your behavior may not change. Being fast with poor code isn’t a great way to land a job generally speaking.

I know that I spent an extraordinary amount of time reviewing my code since I was told I had something like 3 hours to complete the work. I’m sure on pass number three through my code that it wasn’t time well spent. But, I didn’t know that I was being measured on time as well. In hindsight, I should have considered it and only made one or two passes.

A week later, a second call! I’d done OK on the tests. They’d like me to come back in and do another round of interviews with some team leaders and managers. I was excited. As my schedule was wide open, I scheduled it for as soon as they could make it work.

Upon arriving at the then HQ of Epic on Medical Circle Drive in Madison, I was told that it was customary to do an interview with the founder of Epic, but she was traveling on a sales trip that day. I can’t say that I was disappointed by that as the very idea had made me nervous.

I met with 5 team leaders from around Epic on that second interview day. They only had about 8 at the time, so I met most of them that were in R&D. Everyone was pleasant and didn’t ask any tough questions.

Except for one.

She’d gotten her playbook straight from the interviewing books I think. (You’ll find out more about her later and why this became funnier over the years).

“Why do you want this job?”

I’m usually open and direct with others. I suppose I could have come up with a line of crap. But, that’s not me. I’d rather be honest. I took a risk.

Be Thoughtfully Honest

I just want a job.

Aaron, July 1993

That was honest. My internal warning systems flashed for a moment, but dimmed. But, it was the truth. Through all the interviews and testing, I really didn’t have a good picture of what I’d be doing at Epic if I got the job and it wasn’t clear what software they needed help with. All these years later and I still remember sitting there in the small Rosewood conference room saying that.

Epic commonly places employees on teams after interviewing successfully unless a specific request for a team or work is approved. I’m not faulting them for not telling me, but the actual things that they were doing didn’t make much sense to me as I’d had zero experience with “healthcare software.” I couldn’t get excited about a particular application or piece of functionality.

“My gosh, insurance billing software challenges sounds like keen fun.”

That’s just not something you’d hear me say without a giggle. (While there are definitely some technical and algorithmic challenges dealing with mass amounts of data in a timely fashion—billing software is just not my normal cup of tea).

Now, I’m generally “fast on my feet” and added something jokingly about how my parents wanted me to start working soon anyplace, and yadda yadda. I did think to add “I don’t care as long as it’s a programming job–that’s what I’m interested in.”

She wrote down my response. I could tell that she wasn’t prepared for my honesty by her reaction. My final interview was with the TL of the Resolute billing team. The interview was fine, but again, she failed to convey what the team needed and was doing to this recent college graduate. (Again, I don’t fault any of them for failing to do this well, the products are complex and difficult to discuss with an outsider in 30 minutes and have time for back and forth questions). Remember, these were green-screen style terminal applications that Epic was selling at the time, so showing working software wasn’t particularly compelling either.

Sometimes Dumb Timing Happens

Shortly after my second interview with Epic, I received a phone call from State Farm Insurance, at the time headquartered in Bloomington, Illinois. Having attended my university in that same city, I knew where their corporate campus was and the influence they had on the local community. They had a lot of employees — doing whatever insurance companies do (heck, I know generally, but I don’t know why they have so many employees).

I’ll talk more about this in my next post.

Question

If you took an Epic programming test, what programming language did you use? Was it hand-written or online? Did you ever learn your score?