I love the mission. As a software developer, I've been able to work on projects that help doctors and nurses who care for my friends and family across the US. That feels good.
The work itself is mentally challenging. I've designed and coded projects on multiple platforms, each with different quirks and ways of doing things. Most of my work has been in Cache, SQL, and Python, but I also had exposure to lots of other areas. Some projects have been in completely new areas; others needed to integrate into a very established codebase. Never boring, always learning.
I like how Epic has developers also lead the design process. I lead the design process for projects that I'm also the lead developer for. That means I get to devote time to learning about a given domain and designing my project, and I know I'm personally on the hook for whatever I proposed in the design. There's a nice balance between heads-down coding and research/design.
The benefits are great, especially once you hit the 5-year mark.
Epic does a great job hiring fast thinkers. I'm a "boomerang" (I left Epic and later returned). I didn't fully appreciate the speed and efficiency of the "normal" Epic staff member until I left. It's a great place to work with really intelligent co-workers who positively challenge each other to continually grow.
My complaints would only be solved by going into business for myself and being my own boss. I have no intention of doing that.
No option to work from home for part of each week. I could be just as efficient (or more efficient) working from home, meeting-free, for 1 or 2 days each week.
Some of our processes can be tedious or annoying. Some individuals can be hard to work with. But those are normal at any profession, in any job, unless you work for yourself. For me, the Pros far outweigh the Cons.
Allow tenured, high-performing employees the option of working from home 1-2 days per week. Based on tenure and performance, you can likely count on them using the time well.
Started with a phone interview. Then an online skills assessment, which was made up of math questions, questions about a made-up programming language, and LeetCode-type programming questions. Lastly, a 3-hour Zoom session, which was mainly just lea
There was a 45-min introduction to the hiring process, and then I took a 2-hour behavioral assessment and a 5-hour technical/math assessment. The second assessment was absolute garbage. You could not run the code you write; you basically write it in
3 rounds: 1. 15-minute phone screen with a developer to check basic information and ask basic interview questions (explain a project you are proud of, explain a time you had to compromise with a teammate, etc.). 2. Asynchronous assessment testing m
Started with a phone interview. Then an online skills assessment, which was made up of math questions, questions about a made-up programming language, and LeetCode-type programming questions. Lastly, a 3-hour Zoom session, which was mainly just lea
There was a 45-min introduction to the hiring process, and then I took a 2-hour behavioral assessment and a 5-hour technical/math assessment. The second assessment was absolute garbage. You could not run the code you write; you basically write it in
3 rounds: 1. 15-minute phone screen with a developer to check basic information and ask basic interview questions (explain a project you are proud of, explain a time you had to compromise with a teammate, etc.). 2. Asynchronous assessment testing m