2. EMPLOYMENT HISTORY
Groupon Inc (Palo Alto, CA, USA) August 2014 Present (Full Time)
Role(s): Software Engineer in Test (Mobile)
Types of Testing: Feature Testing, Integration Testing, Regression Testing
Systems Tested: Groupon Core Mobile App (incl. Integration with Other Groupon and Third Party
Services/Systems)
I was recruited by Groupon in April 2014, and after working out my Visa began work with them in August,
2014. I am one of two fulltime Functional Testers in the Android team, and my responsibilities include:
● Managing and Coordinating Releases across the Android Functional Test Team, including:
○ Allocation and assignment of Features
○ Coordinating and reporting within Tiger Teams and Stakeholder meetings on Individal
Feature and Release Status
○ Creating and Executing Testcases for Individually Assigned Features
○ Managing the Integration and Regression Testing Phases
○ Coordinating Payment Testing with the INTL test teams
○ Bug/Defect Management and Triage throughout the Release period (and outside of the
Release period)
○ Coordinating/Managing the staged rollout of the Release to the Google Playstore
● Identifying and improving the existing Testing Process, including:
○ Reducing Regression timeframes from 10 days down to approximately 8 days
○ Improved quality of releases (on average we have 1 2 patches per release which is
down from an average of 4)
○ Creation of rampup documentation in order to be able to bring QA resources up to
speed quicker
● Involvement in the Groupon Recruiting Process and interviewing potential candidates for the
Test and Development Teams
Aussie Farmers Direct (Melbourne, VIC, Australia) October 2013 August 2014 (Full
Time)
Role(s): Software Quality Assurance Engineer
Types of Testing: User Acceptance Testing, System Testing, System Integration Testing, Regression
Testing
Systems Tested: Aussie Farmers Direct eCommerce Site (and satellite sites), The General Store
eCommerce Site (and satellite sites), SWAG Internal AFD Customer Service Representative Application
and their integration with backend SQL databases via the Service Bus.
Whilst it is a step down with respect to my actual jobtitle, the role at Aussie Farmers Direct was one that
I was unable to resist and is one that I have seized with both hands as it has enabled me to take on
more responsibility (despite the role not being titled – Test Lead) and have been able to expand my
skillset. My current responsibilities and achievements to date include:
● Day to day management of testing priorities and reporting to stakeholders. Due to the fast paced
and dynamic nature of the IT department at Aussie Farmers, this can prove to be a very difficult
(but satisfying) task as there can be any number of different projects running in parallel with
different stakeholders and priorities to manage.
● Day to day management of testing resources across different projects. Whilst I was not
assigned a ‘Test Lead’ role, this has been something I have taken upon myself to do as I
5. ZedMed Medical Software (Melbourne, VIC, Australia) December 2012 February 2013
(Contract)
Role(s): Test Lead, Business Analyst, Release Manager
Types of Testing: User Acceptance Testing, System Testing, System Integration Testing
Systems Tested: Windows Application – ZedMed Office G2 (Custom built windows application for all
facets of patient, doctor and practice management in the Medical Profession using an SQL Database);
ZedMed Clinical (Custom built windows application for all facets of patient management with respect to
patient clinical records).
I joined ZedMed under a 4 month contract to lead the existing testing team on the ZedMed Office Gen 2
Project. However, having identified gaps in some of the requirements, I expanded my role to include that
of a Business Analyst with respect to working with the other BAs to clean these issues up and help
develop screens/wireframes in order to speed up the process and help clear the backlog of
requirements/specs that the testing team was waiting on.
In addition to this, I also took on a role as a Release Manager and was responsible for developing and
managing a process for releasing defect fixes from the Development environment into the Testing
Environment.
Test Lead:
● Developing the overall testing strategy
● Selection of Testing and Defect Management Tools
● Creation of Testing and Defect Processes
● Coordinating/Managing the development of test cases and scenarios (a team of 5 including
myself)
● Identifying and mitigating risks and issues to test planning (eg. taking on a Business Analyst role
to help clear a backlog of specifications that were needed to progress with planning; along with
clarifying issues/gaps in existing specifications and fixing these).
● Planning the execution of test cases through liaising with the Development team on expected
delivery dates
● Identifying and mitigating risks and issues to test execution
● Managing the execution of test cases (a testing team of 5 including myself, along with additional
business resources who were utilised as testers – ranging from 3 to 6 at any one given time)
● Defect Management (both from a Test Lead perspective and following up with developers on
fixes/resolution)
● Status Reporting to Management and Business Stakeholders (both on Test Execution Progress
and Test Planning Progress)
Business Analyst:
● Clarifying requirements within existing documentation with the Business Stakeholders (and
Technology Stakeholders where applicable)
● Identifying gaps and liaising with the Business to elicit further requirements around these
● Writing missing requirements documents and functional specs
● Helping to develop screens and wireframes for various screens throughout the system
Release Manager:
● Developing a Release Schedule/Plan for the release of defect fixes into the Testing
Environment
● Managing/scheduling the release of defect fixes into the Testing Environment (including one off
exception circumstances where Sev 1 defects fixes were required)
6. Australian Pharmaceuticals Industries (Melbourne, VIC, Australia) December 2011
December 2012 (Contract)
Role(s): Senior Test Analyst, Test Lead, Business Analyst, Project CoOrdinator, Devloper
Types of Testing: User Acceptance Testing, System Testing, System Integration Testing
Systems Tested: Web Based – Store Portal (Custom Web Application built for store and team
members to use across the organisation), Online Store (eCommerce Site built upon Magento and
Concrete 5)
I joined API initially under a 3 month contract in December 2011, and due to a combination of being able
to prove myself in the position and further work being available I have been fortunate enough to have
this contract extended numerous times.
My roles/duties (often in parallel) have included:
Project CoOrdinator for Store Portal Project:
● Producing and maintaining the Project Plan
● Chairing Weekly Project Meetings discussing progress against the plan and identifying
additional tasks that needed to be put into the plan
● Working with the Business Stakeholders to give them an understanding of the tasks and
process required around Launch/GoLive
Test Lead on the Store Portal Project:
● Developing the overall testing strategy
● Coordinating the development of test cases and scenarios
● Planning the execution of test cases across the various test phases
● Managing defects/defect resolution with both Internal and External Vendors
● Reporting on Progress to the Business Stakeholders
Business Analyst on the Store Portal Project:
● Clarifying requirements within existing documentation with the Business Stakeholders (and
Technology Stakeholders where applicable)
● Identifying gaps and liasing with the Business to elicit further requirements around these
● Developing Functional Specifications for functional gaps and Change Requests based on
requirements
Senior Test Analyst on the eCommerce Project:
● Development of test cases and scenarios
● Planning the execution of my set of test cases
● Executing test cases and raising defects where applicable
● Working with both Internal and External Vendors to resolve those defects
● SME point of contact for all other testers within the project
Macro Developer (Ad Hoc Tasks for Business Performance Team):
● Writing and updating excel macros to assist in streamlining the current reporting process
(automating manual tasks), and add additional functionality/capabilities to existing reports
7. IBM Australia (Sydney, NSW, Australia) May 2005 October 2011 (Full Time)
Role(s): Graduate, Consultant (Test Analyst), Senior Consultant (Senior Test Analyst, Test
Lead/Manager)
During my time working for IBM I worked on several long term and complex projects for large clients that
have run for a number of years. The below projects are in order of Most Recent to Oldest.
IBM – National Australia Bank (NextGen Project)
Project Period: January 2011 October 2011
Role(s): Senior Test Analyst
Types of Testing: System Integration, System, User Acceptance
Systems Tested: Web Based/Interface – Oracle FlexCube Internet Banking, NAB Internet Banking,
NAB National Online (Business Customers), NAB Connect (Business Customers – DE Credit/Debit File
Uploads/Processing); Other – Oracle FlexCube (NAB Banking System), eBobs (NAB Banking System),
Mainframe (checking/processing transactions through Legacy Systems).
During my time at NAB I worked as a Senior Test Analyst where my responsibilities included:
● Test Case Preparation (Developing test cases and writing test steps for the test cases): this
involves a lot of coordination and liaising with a number of key stakeholders/groups, including:
Business Analysts, Legacy Asset SMEs, Oracle SMEs, Technology SMEs Environment and
Data teams, as well as to a degree the System Test team to gain an understanding of what is
required to be tested and how the system will work from a System Integration perspective
between the Legacy world and New world.
● Test Case Planning/Scheduling (scheduling and planning execution from a data and
environment availability perspective as well as a batch scheduling perspective)
● Test Case Execution (both execution of test cases and coordinating offshore execution of test
cases)
● Test Coordination/Management (due to the size of my area within the payments team,
eventually extra resources were brought on board with whom I would coordinate the test
execution effort from day to day. This included both offshore and onshore resources.)
IBM – Telstra BigPond (Telstra Transformation Project)
Project Period: June 2008 December 2010
Role(s): Test Analyst, Senior Test Analyst, Test Lead, Test Manager
Types of Testing: System Integration, System, User Acceptance, Regression, End to End
Systems Tested: Web Based – Online Registration, Online SelfCare; Billing & Customer Care – Siebel,
Kenan; Other – Oracle Database, AAA (Usage), Unix (running scripts for Order Processing)
Test Analyst (June 2008 – November 2008)
I started work at Telstra as a Test Analyst where my role involved the development and execution of test
cases with a high degree of independence, as well as to a lesser extent the maintenance of existing
automated test scripts using WinRunner.
Senior Test Analyst/Test Lead (November 2008 – June 2009)
In November 2008 I was promoted to a Test Lead role for the Non Functional Test Team (a small team
of 3 including myself). My role in this team centred more around planning and coordination as well as
reporting results to the Test Manager as well as relevant Business Analysts to ensure that the coverage
we had was sufficient to cover the Non Functional Requirements.
8. In February 2009 I was moved from the Non Functional Test Team to lead a small team within the
Functional Test Team (roughly 5 individuals). My role here was to coordinate both test case
preparation, as well as planning and coordinating execution whilst reporting into the overall Combined
SIT/UAT Functional Test Lead. Testing within the Functional Test Team required a great deal of
coordination across multiple vendors and systems, and our team focused on the BigPond aspects of the
testing. From an End to End perspective, my role was to coordinate with the other test leads to ensure
that there was adequate coverage and coordination amongst the vendors and that test cases and
scenarios were aligned and planned/scheduled accordingly.
Test Lead (June 2009 – March 2010)
In June 2009 I was promoted to the Overall Test Lead role for a small Release within the Project (around
10 – 15 testers below me and reporting directly into the Test Manager) where I was responsible for
coordinating the planning and execution of the test cases (via the test leads for the different areas), and
the reporting of progress to both the Test Manager and Project Management. The planning and
coordination effort also involved a significant amount of communication/liaising with the various other
vendors and stakeholders across the business (not just those within BigPond) to coordinate and piece
together an overall End to End picture of the testing to ensure that there was alignment amongst the
various stakeholders.
Senior Test Analyst/Test Lead (March 2010 – October 2010)
In March 2010, for personal reasons I took a step back from the Test Lead role and moved back into a
Senior Test Analyst/Test Lead Role with similar roles and responsibilities. The most significant difference
was that I was leading/coordinating the team remotely from Melbourne (where I was working more
closely with the other vendors on the project who were Melbourne based).
IBM – Qantas (eQ Production Support/eQ Replatforming Project)
Project Period: June 2005 June 2008
Role(s): Graduate Consultant, Test Analyst
Types of Testing: Regression, User Acceptance
Systems Tested: Oracle eBusiness Suite – Customer Care/CRM, iLearning, HR
Graduate Consultant/Test Analyst (June 2005 – June 2008)
I started at Qantas as a recent Graduate who had joined IBM and originally worked in a
Support/Maintenance role for 6 months which required me to liaise with the client (both with client team
leads and individual employees) to help diagnose issues with the system and then coordinate with
Offshore Oracle resources to resolve the problem. Once it was resolved, I was then required to
coordinate deployment and testing through the various preproduction environments prior to deployment
into production. My role then progressed to a purely Test Analyst Role in the transitioning of the system
to a new platform for the last 6 months of the project.
