Position - Kafka DeveloperLocation - RemoteNotice Period - Availability to join below 30 DaysShifts - CST Time zone (6.30PM to 3.30 AM)
Job DescriptionFocus Area: KafkaThis is a role on the data engineering team, but the majority of the people on the team are quite software minded, commonly former software engineersThis person will monitor Kafka topic creation and respond to teams to advise them on best practices. There is a good bit of manual work, that includes the ability to context switch frequently.There is also some cleanup work around topics and partitions to be completed and cloud cost mitigation effortsWill work with Software, Cloud, and Data Engineering teamsThe person should have Kafka fundamentals down and ideally Confluent Kafka (not just someone who set up the platform as a service)The ideal person would have experience with Teraform for automationThere will be monitoring and provisioning workAzure is preferred, but we are open to other cloud platformsPerson should be self-driven and be able to work independently to identify areas that need improvement, and work to ensure environments are safe and optimizedMay need to write orchestration scripts in Node or .NET (DO NOT WANT JAVA as we need to maintain this code and we do not have that expertise at Mastery)Preference for PowerShell & C#/.Net, but will consider Bash & NodeJSWill use GithubMust understand REST APIs
Responsibilities Develop and implement solutions using Kafka in C#, PowerShell & Bash scripting.Work with multiple teams to ensure best use of Kafka and data-safe event streaming.Monitor Kafka Topic creation for best practicesIdentify needs for and develop reference architecture.Assist developers in choosing correct patterns, event modeling, and ensuring data integrity.Identify and implement metrics and alerting needs.Perform regular reviews of performance data to ensure efficiency and resiliency.Contribute regularly to event-driven patterns, best practices, and guidance.Work with manager to ensure all teams are aware of technology changes and impact.Troubleshoot issues in a microservices architecture.