Jobs
>
Independence

    241 - Senior BizOps Engineer - Missouri Township, United States - Triwave Solutions

    Triwave Solutions
    Triwave Solutions Missouri Township, United States

    1 week ago

    Default job background
    Description

    Job Description

    Job DescriptionPosition Title*Senior BizOps EngineerPosition ResponsibilitiesO'Fallon MO - Open to 100% REMOTE

    this is a tough role for sure
    we could even look at an SDET with some PM experience.
    must still have the chaos or quality assistance testing.
    • Position is a bit unique because our group sits within the command center
    • For all the modernizations going on across MasterCard, the command center oversees those projects
    • Looking for someone that has a background within chaos or quality assistance testing
    • Our team does not report to a single program or product or given applications, we oversee and facilitate the chaos of what we refer to as game day testing
    • Need to be driven
    • Need to understand how things tie together
    • Need to be able to lead these game day calls
    • Need to have good communication
    • The focus is on facilitating testing calls
    • It is not focused on their technical skills. They need to understand modernization across stacks.
    • Base knowledge of pivotal cloud foundry, AWS is highly beneficial, we need them to understand things end-to-end. How a product works. Break points. Understand if the other are resilient enough application wise to handle that. Need a base knowledge of everything. Not a master of anything but a jack of all trades. If they know Splunk. Dynatrace, Jira (a bunch of things in general is better than being an expert in one)
    • Modernization Zones: Availability Zone, End Zone, and Regional Network Transit Zone
    • Makes sense for them to come from a technical PM role to be able to run functional tests while we bring things down and understand how that plays out. Did the monitoring fire? Did we receive notifications for a TRT if that's the case? Things of that nature. It is more of understanding process, and integration. Knowing what connects to what
    • Their day to day responsibilities are more of leading meetings and calls. They are not going to be hands-on making changes. If they have this experience, they can speak up and bring it to the table when needed of course especially when someone who is doing the hands-on piece isn't getting it and needs assistance.
    • Lean towards the consulting side background in the sense that generally speaking, those roles are more focused on the problem solving aspect and that is a lot of what this role entails. Being able to have the conversation and ask the right type of questions. Want someone with similar background to one of the Managers: Technical background supporting test environment that leads up to production and to troubleshoot any failures and then evolves into a strategic thinker to understand how everything works- if they have a background in integration overall and then also have project management experience and are very driven that is really what we are looking for
    • What happened? How does that impact everybody? Now What are we Going to Do? (Remediate that). That is what the documentation that would look like based of a use case being used for a Game Day they will have the team to leverage so they won't be alone as they come up to speed
    • Our team and this individual are not going in and executing the test, it is just working with the teams to facilitate it
    • Some of the benefits of this role is that you are on the cutting edge of the modernization process. Along with the uniqueness of the team itself (you are not responsible for one given product or application so you continue to get that wide breadth of knowledge across everything and they are not solely responsible for having to go and fix any issues that may arise). Between the team, you have over 40 years of MasterCard knowledge so they wont be short of answers or help here.
    • From a resume perspective want to be able to see what they've done and how they've used their skillset in their projects rather than just putting managed a scrum call right? It is really saying managed scrum calls to ensure hitting their stories on time and so and so forth. Wants to see detail in bullet points- what they've done to contribute versus what the team accomplished