BigPanda Consultant

Purpose of the role

The BigPanda Consultant exists to help dotslash build a market-leading BigPanda practice. The role balances three things in roughly equal measure: delivering BigPanda engagements for clients, supporting the sales pipeline that feeds them, and building the practice assets that let us scale beyond any one person. It also carries day-to-day responsibility for dotslash's BigPanda-adjacent products and subscriptions. This document describes what that means in practice and is the basis for day-to-day accountability between the consultant and the Head of BigPanda Practice.

Position in the business

• Reports to the Head of BigPanda Practice.
• Permanent, full time. One day a week in the London office, on client site when engagements require it, and remote otherwise.
• No line-management responsibility. The role carries a mentoring responsibility for dotslash engineers working on BigPanda engagements.
• Works day to day in the practice's Jira board and follows its sprint cadence.

Areas of accountability

Client Delivery

The core of the role: implementing BigPanda well and leaving clients more capable than we found them.

• Implement and configure BigPanda environments end to end: alert ingestion, enrichment and tagging, correlation patterns, automation policies and incident workflows.
• Build and maintain integrations between BigPanda and the client's monitoring and ITSM estate (Dynatrace, ServiceNow and similar tools) using APIs and webhooks.
• Design correlation and automation approaches grounded in the client's systems and infrastructure architecture, and iterate on them against real alert data rather than assumptions.
• Run discovery and design workshops with client teams, and turn the outcomes into design documents the client can operate against.
• Draft statements of work and delivery plans with the Head of Practice, and keep engagements on scope once they are underway.
• Track your own delivery work in Jira, keep status honest and visible, and raise risks early rather than absorbing them quietly.
• Upskill client teams throughout delivery, through pairing, handover sessions and documentation, so the capability outlasts the engagement.
• Initially deliver within engagements led by the Head of Practice. Over time the expectation is that you grow into owning engagements end to end, including the client relationship.

Pre-sales and sales support

The pipeline that feeds delivery is part of the job, not an interruption to it.

• Join discovery and qualification calls as the technical voice, listening for the operational problem behind the tooling ask.
• Prepare and deliver demonstrations and proof-of-value exercises tailored to a prospect's environment and data.
• Contribute scoping, estimates and the technical narrative to proposals.

Practice building

Every engagement should make the next one easier to sell and deliver.

• Turn delivery experience into reusable practice assets: playbooks, accelerators, templates and reference configurations.
• Contribute to the practice's delivery methodology so engagements are repeatable and not dependent on individuals.
• Mentor and upskill dotslash engineers on BigPanda through pairing and internal sessions, and identify opportunities for process improvement with them.
• Share what you learn: internal write-ups, and contributions to webinars and content alongside the Head of Practice.

Products, subscriptions and BAU

dotslash runs subscription offerings alongside project delivery, and this role helps keep them healthy.

• Provide day-to-day support for dotslash's subscription offerings, as these are defined and evolve.
• Contribute improvements and small features to those offerings, informed by what subscribers actually ask for.
• Treat BAU work with the same discipline as project work: tracked, visible and prioritised in Jira alongside everything else.

Ways of working

• You will run multiple concurrent projects. You are expected to prioritise your own workload, protect delivery commitments and flag conflicts before they bite.
• Work moves through the practice's Jira board on a sprint cadence. Keeping your tickets current is part of the job, because it is how the practice sees itself.
• Communication is plain, direct and honest, especially about problems. Bad news early beats good news late.
• With clients, you question decisions when they deserve questioning and back your own in the room. Authority comes from being right for the client, not from being agreeable.

Development and progression

• Complete the required BigPanda certifications within your probation period.
• Grow towards end-to-end engagement ownership, including the commercial relationship, at a pace agreed with the Head of Practice.
• Maintain a development plan with the Head of Practice and review it regularly.

What good looks like

These are the qualitative signals that will form objectives for the role

• Clients ask for you by name, and renewal and expansion conversations are easier because of the trust you have built in delivery.
• Engagements land on scope, with design documents and handovers the client actually uses after we leave.
• Practice assets you created are being reused by others without your involvement.
• dotslash engineers are measurably more capable on BigPanda than they were the quarter before, because of time spent with you.
• Subscription services are stable, and when something breaks, subscribers hear from us before they have to ask.
• The Head of Practice hears about risks from you first, never from the client.