Westpac NZ - Senior Automation Quality Engineer: Difference between revisions

Jump to navigation Jump to search
m
Line 39: Line 39:


In my role, I:
In my role, I:
* Acquired skills in '''Platform Engineering''' ''(Docker, Linux VM's, Terraform, Bash, HashiCorp Vault)''
* Acquired skills in Platform Engineering ('''Docker''', '''Linux VM's''', '''Terraform''', '''Bash''', '''HashiCorp Vault''')
* Provided '''support''' to internal users to leverage '''Splunk''' ''(Searching, analysis, dashboard creation, PagerDuty integration)''
* '''Supported''' internal '''Splunk users''' for ''(Searching, analysis, dashboard creation, PagerDuty integration)''
* Managed a distributed instance of Splunk Enterprise ''(Indexers, search heads, forwarders, event collectors, role-based access controls)''
* '''Managed''' a distributed instance of '''Splunk Enterprise''' ''(Indexers, search heads, forwarders, event collectors, role-based access controls)''
* Introduced the Quality Engineering Chapter to use Splunk for reporting of results from automation suites
* Introduced the Quality Engineering Chapter to use Splunk for '''Reporting and Dashboarding''' results from automation suites


Moreover, as the "Splunk Champion", I really strived to help people see the customer's experience through the data being collected. When onboarding new systems, I guided users through a series of questions aimed at maximizing the value extracted from Splunk data, focusing on monitoring '''solution's performance''', '''error detection''', and '''information quality''' being recording for '''efficient issue resolution'''.


Moreover, as the Splunk Champion, I really wanted to help people see the customer's experience through the data being collected. When onboarding new systems, I guided users through a series of questions aimed at maximizing the value extracted from Splunk data, focusing on monitoring '''product performance''', '''error detection''', and '''quality information''' being recording for '''efficient issue resolution'''.
Ultimately, the goal of observability is to swiftly remediate critical issues by detecting them, understanding their impact, and resolving them promptly. Therefore, its paramount that '''system monitoring information is timely and good''' in order to achieve this objective.
 
Ultimately, the goal of observability is to swiftly remediate critical issues by detecting them, understanding their impact, and resolving them promptly. Therefore, '''timely and quality information remains paramount''' in achieving this objective.


==D365 KiwiSaver Squad - Java API and UI Automation==
==D365 KiwiSaver Squad - Java API and UI Automation==

Navigation menu