A DevOps Engineer is responsible for supporting and maintaining the infrastructure behind the leading health sciences education web platform. When it comes to making sure that everything is running as smooth as possible, DevOps Engineers come to the rescue. We make no pretenses – our system is complex in many ways, and the backend provides a challenge that can only be solved by the most skilled of individuals.
-Design, build and improve tools and processes for monitoring, managing, and deploying application servers, databases, and code
-Proactively review and integrate new technologies for better efficiency, reliability, scalability
Work closely with other developers to troubleshoot and make improvements
-Document infrastructure, tools, and best practices
- BS degree in Computer Science or equivalent in experience
- Strong fluency with one or more of the following programming languages: High level of experience with deployment technologies like Git, Nginx, Redis, etc.
- Expertise with Linux servers and Bash
- Ability to learn and apply new programming languages extremely quickly
- Adapts quickly to AllofE’s development methodology and component infrastructure
- Strong analytical and problem-solving skills
- Ability to work both independently and in small, dedicated teams
- Must be a US Permanent Resident or Citizen
- Computer Science, Engineering, or other technical field experience or degree (Master’s, Ph.D. degree, further education)
- Experience with cloud computing platforms such as Amazon Web Services, Google Cloud Platform, Microsoft Azure
- Strong interpersonal, written communication, and presentation skills
- Knowledge in the areas of database management, machine learning, natural language processing, server architecture, source control, software security, distributed and parallel systems
- UI/UX design experience
Day In The Life
9:00 AM | Arrive at the office, clock in, and check your taskboard
9:30 AM | Check that all databases and server infrastructure is functioning smoothly.
10:30 AM | You find a bottleneck that could be resolved with automation. Log a bug to yourself and get to work on fixing it.
12:30 PM | Head out for lunch.
1:30 PM | There’s been a ticket about some loading issues. Find the source, communicate the problem back to the Client Support Team, and get to work resolving it.
2:00 PM | Along the way, you encounter something that could potentially become an issue. Log it to someone else on your team, and get back to work.
3:30 PM | Time for your Standup. Head to the infamous UnderHall in order to hear about what others have been working on.
4:15 PM | After grabbing a snack from the snack bar, get back to the coding grind.
5:30 PM | Once again, run system diagnostics to make sure everything is running smoothly before you leave.
6:00 PM | Clock out, say goodbyes, and head home for the night. The night is yours.