Westpac NZ - Senior Automation Quality Engineer: Difference between revisions

Jump to navigation Jump to search
Line 34: Line 34:
* Provided insights from a tester's perspective and liaised with the Westpac Quality Engineering Chapter.
* Provided insights from a tester's perspective and liaised with the Westpac Quality Engineering Chapter.


==Observability Squad==
==Observability Squad - Platform Engineer and Splunk Champion==
With this team I switched to a more Platform Engineering role, and became the Westpac Splunk Champion. We were supporting and growing the Splunk platform for Westpac internal technology teams. I have had exposure to Splunk in previous companies and have truly loved it for analysing data. I really like to try and find the customers' experiences come through the data. I would always ask the teams we were supporting on their Splunk onboarding journey three things:
 
# Are you logging how well your product/service/feature is working? eg transactions per hour
As a member of the Observability Squad, a Platform Engineering team tasked with supporting [https://www.splunk.com/ Splunk] and other observability tools like [https://www.dynatrace.com/ Dynatrace], I had the opportunity to learn and grow in the role of "'''Splunk Champion'''". I was encouraged into this role by [https://dirksonline.net/CV/2023%20Isaac%20Carrington%20-%20LinkedIn%20Recommendation.jpg Isaac Carrington]''(Head of Platform Engineering)'' despite lacking prior platform engineering experience.  
# Are you catching all the errors and warnings to know when the product/service/feature is doing something bad
 
# When you observe an error/warning are you recording good quality information that truly helps devOps understand the issue, and expedites the remediation of the issue?
In my role, I:
The latter I find particularly important because in the end the objective is to minimise the risk of major issues by knowing about them quickly, [[and]] also being able to solve them quickly. Timely & good quality information is paramount.
* 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)''
* 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
 
 
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, '''timely and quality information remains paramount''' in achieving this objective.


==D365 KiwiSaver Squad==
==D365 KiwiSaver Squad==
Retrieved from ‘https://dirksonline.net/cvwiki/index.php/Westpac_NZ_-_Senior_Automation_Quality_Engineer’