Lead Consultant

Position Description

Title Lead Consultant

Location Sydney/Brisbane/Melbourne/Philippines/Global Remote

Issued December, 2021

Position Purpose

The purpose of this role is to actively contribute to a project teams’ cadence in

collaboration with Project Managers, Technical Leads, QA and Developers, while

liaising with customers to ensure deliverables meet or exceed expectations.

This role includes implementing features, producing technical documentation,

coordinating feature releases, providing technical support, resolving software faults

and working with external clients and stakeholders within the company.

All Consultants are expected to be self-motivated, needing little guidance on completing

tasks on time and capable of meeting expectations in terms of requirements.

Key Relationships

Business internal:

- Project Managers
- Software Engineers
- Business Analysts
- Quality Assurance

Business external:

- Clients
- Design partners
- Strategic business partners

Performance Areas

1. Application Development & Support - 50%

Tasks
- Work closely with the Project Managers, Technical Leads, QA, and other

Developers to propose and implement technical solutions that fulfil functional

and non-functional requirements, as stipulated by user stories
- Ensure the quality of technical solutions via unit tests and peer-to-peer

code reviews; verify extensibility, reusability and maintainability with strong

emphasis on compliance to architecture
- Develop efficient and high-quality code while meeting product release

deadlines. Ensure development standards are met and high-quality software is

delivered on a consistent basis
- Review the requirements specifications and raise any clarifications

required. Gather stakeholder feedback at various phases of the project
- Demonstrate a willingness and ability to collaborate and work within a multi

skilled team including external suppliers.
- Constructively challenge and discuss opportunities, alternatives and

and subsequently raise user stories to address incurred code debt

increase throughput, availability, scalability, redundancy, superior performance

and quick recoverability as applicable
- Adhere to good development practices: documentation, code standards,

code/design reviews, optimisation and maintainability.

Indicators
- Applications and features built in accordance with criteria of satisfaction

stipulated in user stories and signed off by project managers/client
- Executing development on time as per timeline, data design, activity

diagrams.
- Issues, delays, and schedules to project team communicated in a timely

manner
- Continuous implementation of recommendations resulting in increased

by statistical data gathered and analysed through logs and monitoring tools

(e.g.: New Relic)
- Assuming additional responsibility without being asked
- Encouraging fellow team members to make innovative contributions and

embrace new ideas.
- Overall code debt remains below an acceptable level as agreed with

Technical Leads
- Achieve acceptable levels of code coverage via unit tests as agreed with

Technical Leads

2. Sprint Planning, Retrospectives & Collaboration - 15%

Tasks
- Collaborate with key stakeholders on user stories, define requirements and

agree on the conditions of satisfaction. Clarify any ambiguity with the project

managers
- Prepare time estimates, schedules for projects and software design plans

based on technology & resource availability
- Participate in sprint planning, estimations, daily stand-ups and

retrospectives as and when required
- Gather requirements, write acceptance criteria and user stories

collaboratively as part of a team for ongoing maintenance of code debt and

technical objectives
- Conduct retrospectives periodically, identify and implement improvements,

measure success and/or failure of outcome
- Work closely with Project Managers, Technical Leads and others in the

project teams to prioritise and plan sprints/backlogs
- Collaborate closely with project managers and technical leads to

understand the requirements so that you have a good understanding of the

problems you are trying to solve, and we do not waste time on rework and more

importantly are able to suggest appropriate solutions to their needs

Indicators
- As a team deliver potentially shippable increments of product at the end of

each Sprint
- Improved and consistent effort estimations on user stories based on

previous experience
- Identify risks early to ensure impact to delivery of committed stories per

sprint is minimised
- As a team self-organise user stories such that QA are not bottlenecked, and

throughput is maximised
- Collaborate with each other to ensure no one person is solely responsible

for any task or activity so that we are able to continue working effectively when

any of our team is away
- As a team, be self-organising and be capable of prioritising tasks according

to business priorities with mínimal supervision

3. Perso