Job Description :
ANY messaging system experience is a plus for them
If you have the Messaging Que/ Message Bus experience and DO NOT have Terraform, he would consider them!!
If you do NOT have Terreform, he’ll ask the question of how well you adopt to other products
If someone has recently got into the messaging que/ message bus world, is very driven and eager to learn, he would consider them as well.
Apache Product line of any sort would take
Skill set order preference:
Pulsar/Kafka/Storm/ Spark (any apache product)
RabbitMQ/any messaging
Work with messaging systems on an app/dev side vs. infrastructure
If they have adaptability, they can be trained. POC skill set would be seriously considered – they are in the early stages on this project, so they may be able to grow along with the team. They are in the design stage of this project.
In the past they used oracle which could scale vertically but not horizantally (upgrade Developing a distributed messaging bus – they are supporting the system by creating new applications, integrations and providing operation support.
Example: When a client is onboarded, if there are load balancing issues, this team manages that. Stand up and transfigure nodes in message bus.
This role falls on the infrastructure side – focused on configuration.
Skills:
Pulsar/Kafka batching experience – storm experience is helpful as it is similar
Any distributed database is helpful.
Any experience with distribution messaging systems is helpful
Publishing and subscribing for messaging systems – streaming
Kafka – used for streaming, but can be used for pubsub
Streaming messages on any capacity is helpful. Pubsub model experience
Operations and support of a distributed system is different than a monolithic system support
They will be partnering with other people to build instances for this message infrastructure
Monitoring, operations, management would be huge
Troubleshooting and monitoring for any messaging system would be a huge plus
Preferred experience on newer messaging platforms that are more scalable is a huge plus, rather than legacy systems
Questions Gunna would ask:
How do you set up queues?
How are you balancing and supporting those queues?
What is the use of the queues?
The DevOps Engineer is responsible for maturing the DevOps mindset within the agile teams using techniques such Continuous Integration and Continuous Delivery to provide quality products with seamless integration across Development, Quality Assurance, Infrastructure, Operations, and Release Management roles. The focus of this role will be helping design, implement and operationalize our Enterprise Message Bus offering within Azure across our portfolio.
The successful candidate will be a servant leader who develops and supports a learning organization model through coaching, training, and mentorship. The successful candidate will be one that can adapt as necessary for unintended consequences of this change initiative and one that understands the value of commitments to delivery made by a development team. Cross training of the team is a part of this role.
Candidates will work in a DevOps team environment and are expected to work on both tactical and strategic assignments. This candidate will be primarily responsible for helping teams prepare for the move into the public cloud (Azure) while helping maintain and automate legacy on-prem applications. Candidates are expected to handle the manual work while figuring out how to automate it.
Required Qualifications:
Azure Exposure - 10+ months, please reference highlighted portion above the job description for Azure experience and what they39;re looking for!
6 years of IT experience on web-based products
2+ years of Message Queuing/Enterprise Service Bus experience
2 years of experience with Agile methodologies
2 years of experience with at least 1 scripting language such as Perl, Python or PowerShell.
1 years of experience with programmatic interaction with a relational database
Preferred:
message queuing experience (Preferably Apache Pulsar, Kafka acceptable)
Previous design and architectural experience with messaging systems
Git (contributions on Github++)
Monitoring tools experience (Splunk, Dynatrace, SignalFx, VictorOps)
Scripted environments experience
Configuration as code experience
Infrastructure as Code (IAC) experience (i.e. Terraform)
Operations experience
Service Oriented Architecture (SOA) experience
Database change automation experience
Real-time automated metrics and reporting experience
PowerBI experience
Microsoft Azure IoT Developer certification and/or Microsoft Certified: Azure DevOps Engineer Expert