# Technology, software, tools and service experience

Russ Watson-Thomas | Source-graded working inventory | 24 October 2026

> This is the complete *evidence-classified technology map* behind the four targeted CVs. “Complete” means the named items supported by our recovered records, not a claim that every historic company system has been reconstructed.

The key distinction is **what I configured, used or tested myself; what I helped deliver; what appeared on a programme; and what is only known from an employer’s wider estate.** No individual admin/coding claim is inferred from a brand name. Historic inaccessible source artefacts remain closed at their present evidence level.

## Evidence and ownership legend

- **Direct configuration / authored / operational use**: `direct`
- **Hands-on testing and integration assurance**: `tested`
- **Delivery or platform leadership**: `led`
- **Evaluated / exploratory use**: `explored`
- **Contemporaneously listed familiarity**: `historical`
- **Employer or project estate only, NOT a personal skill**: `estate`
- **Planned, proposal or roadmap only**: `roadmap`

## Career-period frame

- **Venda:** Jul 2006–Jul 2013 · **Bright North:** Jul 2013–Dec 2014 · **Spindrift:** 2015–2016 · **Michael Kors:** 2016–2017 · **Harrods:** 2017–Jul 2026 · **Independent:** ongoing.

## Reconciled catalogue

### Work management, ALM and service workflows

| Named technology / system | Level | Period / employer | Actual involvement and boundary | Private source map |
|---|---|---|---|---|
| Jira, JQL, workflow administration, dashboards, issue types and CSV migration | Direct configuration / authored / operational use | Venda; Spindrift | Configured workflow/issue changes and reporting; contributed to RT consolidation; retained Jira super-admin access. Canon workflow-design involvement is distinct from confirmed production configuration. | CAP-01; CAP-17 |
| Request Tracker (RT) | Direct configuration / authored / operational use | Venda | Operated legacy ticket workflows during a successful RT-to-Jira consolidation programme. | CAP-01 |
| Azure DevOps Boards, work items, processes, permissions and REST APIs | Direct configuration / authored / operational use | Harrods | Administered work tracking, onboarding/access, custom fields, work-item migration and API-based troubleshooting. | CAP-02 |
| Azure DevOps Test Plans, Suites, Cases and access entitlements | Direct configuration / authored / operational use | Harrods | Used and administered test-management and API/reporting capabilities; not Azure cloud-subscription administration. | CAP-02; CAP-04 |
| Team Foundation Server (TFS) | Delivery or platform leadership | Harrods | Participated in migration to Azure DevOps and work-process improvement. | CAP-02 |
| Confluence and internal knowledge wikis | Direct configuration / authored / operational use | Venda | Used and organised technical/test documentation and team working guidance. | Toolchain A |
| ServiceNow | Direct configuration / authored / operational use | Spindrift; Harrods | Used IT service-management systems as part of work; not full service-platform administration. | Toolchain B |
| Freshservice (Freshworks) | Direct configuration / authored / operational use | Harrods | Operational experience during ServiceNow-to-Freshservice transition; not migration lead or full administrator. | Toolchain B |
| HP ALM | Direct configuration / authored / operational use | Spindrift | Used application lifecycle/test management; no asserted complete administration. | CAP-16; Toolchain B |
| Bugzilla defect tracking | Contemporaneously listed familiarity | Venda | Explicitly listed on 2012 CV as a tool familiarity, not proof of Bugzilla administration. | ATS 2012 original CV |
| Jira Service Desk / Freshservice identifiers |  | Harrods | Referenced in work-item data schema; no confirmed independently engineered connector. | Stack map C |
| Trello device lab planning and checklists | Direct configuration / authored / operational use | Spindrift/Canon | Dated device coverage and hardware checklist actions; not proof the proposed permanent lab was built. | CAP-17 |
| Google Drive and Google Sheets project trackers | Direct configuration / authored / operational use | Venda; Harrods; independent | Historical QA roadmaps, issue trackers and collaboration records; document/project use, not enterprise administration. | Primary artefacts |
| Jira Software / Jira Service Management |  | Venda; Harrods | Work and service-desk uses evidenced, but exact historic product editions and administration differ across employers. | Toolchain C |

### Test automation, APIs and quality engineering

| Named technology / system | Level | Period / employer | Actual involvement and boundary | Private source map |
|---|---|---|---|---|
| Selenium Builder; Selenium RC; Selenium WebDriver | Direct configuration / authored / operational use | Venda | Recorded critical paths, debugged locators and exported tests for review; Selenium framework development by colleagues not claimed. | CAP-08 |
| Ruby-format WebDriver exports | Direct configuration / authored / operational use | Venda | Prepared, adapted and handed off exported tests; not Ruby product engineering. | CAP-08 |
| Gherkin / behaviour-driven development (BDD) | Direct configuration / authored / operational use | Venda | Produced structured acceptance/test specifications and worked with developer handoffs. | CAP-08 |
| Subversion (SVN) repository tooling |  | Venda | Mentioned in engineering/test repository environment; no attributable personal repository administration evidence. | Toolchain C |
| Cucumber |  | Venda | Present in team automation practices; personal step-definition framework ownership unproven. | ATS catalogue |
| SoapUI, SOAP, WSDL and XML payload testing | Direct configuration / authored / operational use | Venda | Constructed manual and reusable web-service requests, investigated gift-certificate/order services and response behaviour. | CAP-07 |
| REST / JSON APIs and Postman | Direct configuration / authored / operational use | Harrods | Tested and investigated REST endpoints; Azure DevOps API, project access and reporting examples. | CAP-02; CAP-22 |
| JavaScript test-harness helpers | Direct configuration / authored / operational use | Spindrift / Canon | Authored harness/environment-readiness helpers and executed automated tests, not production ATG code. | CAP-16 |
| AngularJS, jQuery, Bower, Bootstrap, Sass/LESS in Social Superstore frontend |  | Bright North | Present in original 2014 project messages and PR context, but no proof Russ coded these framework features. | Stack map P |
| Page Object Model and AngularJS frontend test automation | Direct configuration / authored / operational use | Bright North | Designed/tested page-object-oriented web automation around AngularJS application behaviour. | CAP-13; CAP-14 |
| Apache JMeter | Evaluated / exploratory use | Spindrift; early Harrods | Exploratory multistep load/performance scenarios across storefront, API and backend; not a mature benchmark programme. | CAP-16; Toolchain B |
| Sauce Labs / remote Selenium | Evaluated / exploratory use | Venda | Investigated remote browser/testing integration; not a proven production deployment. | Toolchain A |
| C#, SpecFlow and Visual Studio | Evaluated / exploratory use | Harrods | Referenced in prototype/design work on BDD/test architecture; not established as production application coding. | ATS catalogue |
| Cross-browser, device/OS lab and mobile QA coverage | Direct configuration / authored / operational use | Spindrift; Venda; Harrods | Worked on device/OS test coverage and checklist readiness; permanent lab was proposed, not confirmed built. | CAP-17 |

### Build, delivery and technical operations

| Named technology / system | Level | Period / employer | Actual involvement and boundary | Private source map |
|---|---|---|---|---|
| Hudson / Jenkins continuous integration | Direct configuration / authored / operational use | Venda | Participated in CI/test-execution coordination and troubleshooting; not infrastructure administrator. | CAP-08 |
| TeamCity |  | Venda | Documented in QA/build-release organisational adoption; hands-on admin not established. | Toolchain B |
| Chef and Puppet |  | Venda | Configuration-management tools within engineering adoption programmes; no verified personal infrastructure configuration. | Toolchain B |
| Git, GitHub and repository-backed test assets | Direct configuration / authored / operational use | Venda; independent products | Worked with test-asset repositories and now uses GitHub for independently developed products. | CAP-08; CAP-23 |
| GitHub Actions | Direct configuration / authored / operational use | Independent products | Repository-based build/check and deployment workflows in current projects. Individual script authorship varies by assisted implementation. | CAP-23 |
| Snowman QA/release environment tools | Direct configuration / authored / operational use | Venda | Created/accessed QA release candidate environments and coordinated platform tests. | Toolchain A |
| SSH, FTP, grep and practical log inspection | Direct configuration / authored / operational use | Venda | Used operational diagnostics and interface/test environment access; not blanket systems-administrator credentials. | Toolchain A |
| Linux, Windows, HTML, XML and SQL | Contemporaneously listed familiarity | Venda | Listed in contemporary CV; known general familiarity, with more specific checkout/log examples where proven. | ATS original CV |
| Nagios alerts | Direct configuration / authored / operational use | Venda | Used QA monitoring/alert outputs when investigating platform health. | Toolchain A |
| Dynatrace dashboards | Direct configuration / authored / operational use | Harrods | Operational dashboard use and issue awareness for customer platforms; not platform-wide rollout owner. | CAP-22 |
| Zeus / ZTM traffic manager |  | Venda | Considered traffic telemetry in release/operational reasoning; direct traffic-manager admin unproven. | Toolchain A |
| Azure Functions / Azure cloud tooling | Evaluated / exploratory use | Harrods | Referenced in direct earlier prototyping; not proof of Azure tenant/cloud infrastructure ownership. | Toolchain B |
| GitHub Desktop | Evaluated / exploratory use | Venda | Historic local Git preparation and repository setup attempts; avoid claiming successful team-wide rollout. | Toolchain A |

### Retail commerce, payments and data integrations

| Named technology / system | Level | Period / employer | Actual involvement and boundary | Private source map |
|---|---|---|---|---|
| Venda Control Panel (VCP), Venda Payment Services (VPS) | Direct configuration / authored / operational use | Venda | Configured/tested storefront, promotions, products, pricing, payments, fulfilment and live QA retailer journeys. | CAP-05; CAP-09 |
| Promotions 2.0, vouchers, rules and pricing permutations | Direct configuration / authored / operational use | Venda | Collaborative product contribution plus functional/regression testing and promotion setup; not sole backend developer. | CAP-09 |
| Urban Outfitters PayPal V2, callbacks and IPN | Direct configuration / authored / operational use | Venda | Personally described rollout and configuration; surviving QA payment/refund evidence, production cutover not independently recovered. | CAP-06 |
| PayPal, DataCash and 3-D Secure / Maestro | Direct configuration / authored / operational use | Venda | Troubleshot merchant profiles, returns, payment errors and checkout QA. | CAP-06; CAP-07 |
| Checkout by Amazon (CBA) | Direct configuration / authored / operational use | Venda | Validated payment flows and profiles in QA; no blanket assertion about production retailer launches. | CAP-07 |
| Givex store credit / gift cards | Hands-on testing and integration assurance | Venda | Participated in store-credit and gift-certificate integration QA. | CAP-07 |
| Sabrix tax | Hands-on testing and integration assurance | Venda | Direct involvement in scheduled test/release work; no complete tax-solution admin claim. | Toolchain A |
| SOAP order services, gift certificates and SWMS | Direct configuration / authored / operational use | Venda | Constructed web-service requests and investigated failure states; SWMS expansion left unguessed. | CAP-07 |
| Apache Solr search/indexing | Hands-on testing and integration assurance | Venda | Diagnosed field/index behaviour, availability and retailer QA dependencies. | CAP-11 |
| Multi-region pricing, currency, bundling and order refunds | Hands-on testing and integration assurance | Venda | Validated complex catalogue-to-checkout and settlement journeys. | CAP-09; CAP-11 |
| Oracle ATG / Oracle Commerce | Hands-on testing and integration assurance | Spindrift/Canon; Michael Kors | Led and personally participated in integrated commerce QA, content, checkout and relaunch; not ATG product software engineering. | CAP-16; CAP-18 |
| Spindrift Site Builder CMS | Direct configuration / authored / operational use | Spindrift/Canon | Changed content/configuration while validating integrated storefront behaviour. | CAP-16 |
| Worldpay XML/payment integration | Hands-on testing and integration assurance | Spindrift/Canon | Validated checkout, callback and settlement behaviours; not gateway integration coding. | CAP-16 |
| Syncreon fulfilment, returns, RMA/CSC workflows | Hands-on testing and integration assurance | Spindrift/Canon | Tested order, fulfilment and reverse logistics handoffs; vendor implementation unclaimed. | CAP-16 |
| Farfetch platform and APIs, Adyen / Apple Pay | Delivery or platform leadership | Harrods | Coordinated mobile-commerce and payments service dependencies and programme QA; not every component personally configured. | CAP-22 |
| SAP CPI / Integration Suite, SAP CDC and SCAYLE | Delivery or platform leadership | Harrods | Worked across mediated commerce/customer identity and integration boundaries with engineering and architecture. | CAP-22 |
| Akamai edge/cache | Delivery or platform leadership | Harrods | Analysed and coordinated platform boundary/cache behaviours; no claim of writing every edge policy. | CAP-22 |
| SAP Commerce (Hybris); IBM WebSphere / Sterling Commerce |  | Harrods | Enterprise commerce estate and programme context; no automatic individual implementation claim. | Stack map C |
| SAP Customer Data Cloud / SAP BTP |  | Harrods | Customer-identity/integration estate and architectural context; do not claim deployment of every service. | Stack map C/E |
| PIM, OMS and catalogue/orchestration systems |  | Harrods | Commerce project and vendor architecture context; specific component ownership not automatically proven. | Stack map C/E |

### Mobile, identity, customer experience and digital products

| Named technology / system | Level | Period / employer | Actual involvement and boundary | Private source map |
|---|---|---|---|---|
| iOS and Android application platforms | Delivery or platform leadership | Harrods | Led supplier/integration/release and ongoing operating ownership of customer mobile experiences. | CAP-19 |
| Xcode and CocoaPods | Direct configuration / authored / operational use | Harrods | Worked with iOS build/dependency and compatibility tooling; not an assertion of native feature implementation. | CAP-19 |
| Firebase CI/CD and TestFlight | Direct configuration / authored / operational use | Harrods | Worked within app release/testing and continuous-delivery workflow. | CAP-19 |
| Apple Wallet, NFC customer recognition | Delivery or platform leadership | Harrods | Led cross-party customer identity, payments/hardware, security and retail integrations. | CAP-21 |
| Digital Rewards, tier/loyalty and customer data | Delivery or platform leadership | Harrods | Platform direction across loyalty, tier expansion, Wallet and customer-identity services. | CAP-21 |
| In-Store Ordering and assisted selling | Delivery or platform leadership | Harrods | Owned platform priorities, operational readiness and evolution of customer/colleague journeys. | CAP-20 |
| Drybar UK, MyBeauty and mobile platform dependencies | Delivery or platform leadership | Harrods | Within wider platform remit; feature-level involvement varies. | Career archaeology |
| Google Analytics | Delivery or platform leadership | Harrods | Experience optimisation/measurement ecosystem exposure, specific dashboard ownership not claimed. | ATS catalogue |
| Dynamic Yield and Emarsys | Delivery or platform leadership | Harrods | Personalisation/messaging and customer-marketing platform integration/exposure; do not imply sole daily administration. | CAP-22 |

### Independent web products and current engineering (2026)

| Named technology / system | Level | Period / employer | Actual involvement and boundary | Private source map |
|---|---|---|---|---|
| DunDunSee live consumer product | Direct configuration / authored / operational use | Independent | Founder-led product delivery, service operation and releases; UK redundancy calculation context. | CAP-23 |
| React, TypeScript and Vite |  | DunDunSee / Work repos | Verified modern application stack in current repo manifests; exact personal source authorship varies with AI assistance. | CAP-23 |
| Framer Motion |  | Current DunDunSee repo | Modern UI-animation dependency in project manifest; personal component authorship not separately established. | Stack map P |
| Vitest and Playwright |  | Current projects | Test tooling in repository manifests and verification practices; avoid inventing test counts/coverage. | CAP-23 |
| Tailwind CSS |  | Current products | UI toolkit used by specific repository sources; not blanket implementation across every project. | CAP-23 |
| Next.js and Supabase |  | Quality Platform | Repository/project technology, including data-backed prototyping, distinct from live employer usage. | CAP-23 |
| Stripe checkout/payment links and webhooks | Direct configuration / authored / operational use | DunDunSee | Integrated and operated digital payments, including Apple Pay / Google Pay checkout options. | CAP-23 |
| Vercel hosting and deployments | Direct configuration / authored / operational use | Independent | Current project delivery, deployments and site maintenance. | CAP-23 |
| Cloudflare Web Analytics | Direct configuration / authored / operational use | DunDunSee | Configured privacy-conscious web analytics on live product. | CAP-23 |
| Google Search Console, sitemap and DNS migration | Direct configuration / authored / operational use | DunDunSee | Managed discovery/SEO migration and operational launch activities. | CAP-23 |
| SwiftUI and native app planning | Evaluated / exploratory use | DunDunSee | Native app parity and implementation planning; avoid describing a shipped native release. | CAP-23 |
| AI-assisted development and agent-led prototyping | Direct configuration / authored / operational use | Independent | Used AI-assisted tooling to develop/test products and standards; not employer production AI-platform ownership. | CAP-23 |

### Historical platform/estate-only context (not claimed skills)

| Named technology / system | Level | Period / employer | Actual involvement and boundary | Private source map |
|---|---|---|---|---|
| Perl, Catalyst, Moose and LAMP | Employer or project estate only, NOT a personal skill | Venda | Contemporaneous engineering job advertisements; not evidence of personal Perl/application development. | Stack map E |
| PostgreSQL, Memcached, Apache and RPM packaging | Employer or project estate only, NOT a personal skill | Venda | Referenced in operations/engineering discussions; personal administration or package authorship unproven. | Toolchain C |
| Review Board, VOSS, NRPE and QTP/BrowserStack | Employer or project estate only, NOT a personal skill | Venda | Seen in teams and programme discussion, not confirmed personal specialist use. | Toolchain C |
| Mailchimp transactional templates |  | Spindrift/Canon | Test-message artifacts in contemporary correspondence; no personal Mailchimp configuration shown. | Stack map P |
| MongoDB search/data evaluation | Planned, proposal or roadmap only | Venda | Team explored MongoDB test planning; no evidence of personal MongoDB development or a production migration. | Stack map R |
| 10CMS, Avail Intelligence, ChannelAdvisor | Employer or project estate only, NOT a personal skill | Venda | Historical commerce integrations/roadmap and QA context; integration delivery level varies. | Stack map P/R |
| SAML and Facebook/Torex integrations | Planned, proposal or roadmap only | Venda | 2011 roadmap mentions, not proof of shipped work. | Stack map R |
| CyberSource, UPS, DPD and Oracle Endeca | Employer or project estate only, NOT a personal skill | Michael Kors | Historic project and vendor context; deliberately not individualised as personal expertise. | CAP-18 |
| Salesforce CRM / Canon ID and global localisation | Employer or project estate only, NOT a personal skill | Spindrift/Canon | Wider Canon programme components, some from colleague accounts spanning periods beyond direct proven work. | Stack map C |
| SAP ECC, CAR, BW, Event Mesh, Cloud Foundry and API Management | Employer or project estate only, NOT a personal skill | Harrods | Employer-wide architecture or vendor material; personal deployment/administration unproven. | Stack map E |
| Enactor POS, AWS, Contentsquare, Klarna and Sinch | Employer or project estate only, NOT a personal skill | Harrods | Public employer case-study technology; not confirmed personally operated and effective dates may vary. | Stack map E |
| AWS hosting / cloud provider at Bright North | Planned, proposal or roadmap only | Bright North | AWS was an illustrative scaling option in Social Superstore scope, not a verified deployed cloud environment. | CAP-14 |
| Convolo and Affilinet affiliate platform | Employer or project estate only, NOT a personal skill | Bright North | Product and affiliate integration documented publicly after departure; personal delivery not established. | Stack map E |
| Microsoft SQL Server and IBM DB2 | Employer or project estate only, NOT a personal skill | Harrods | Historic architecture diagrams; not proof of personal database engineering. | Stack map E |

## Boundaries that stay closed

- No personal Perl/Catalyst/Moose production software engineering, AWS architecture deployment on the 2013 Bright North Social Superstore project, or personal SAP middleware coding is asserted.
- No personal administration of all TeamCity, Jenkins, Chef, Puppet, SAP, Freshservice, HP ALM or cloud services is implied by inclusion.
- Michael Kors remains deliberately high-level in the main CVs; historical vendor names above are explicitly programme context.
- 2011 Venda roadmap items are not presumed delivered. Historical automation source, SOAP project XML, corporate release cutovers and old HR paperwork will not be requested again.
- 2026 repo manifests prove technology is used within products, not that each dependency was personally coded by hand.
- No original sensitive workbooks, transaction data, live internal hostnames, passwords, personnel records or private IRC are published.

## How the four CVs use this information

- **Product:** customer journeys, commerce, mobile, loyalty, analytics, product delivery and the live DunDunSee product, backed by enough technical tooling to be credible.
- **Platform:** developer tooling, RT/Jira and TFS/ADO transformation, API/payment integration, enterprise commerce and identity/edge boundaries.
- **Engineering:** direct test engineering, Selenium/SoapUI/JavaScript, automation and CI coordination, service tooling, observability and distributed technical leadership.
- **Delivery:** operational release control, Jira/ADO, APIs, payments/fulfilment, programme integrations, mobile releases and supplier coordination.

All four remain targeted CVs. The table above is the full companion inventory; stuffing it unfiltered into each downloadable CV would imply false equivalence between personally implemented systems and external employer architecture.

**Private source index:** `RWT_Toolchain_Archaeology_Private_Evidence_Register_2026-10-24.md`, `RWT_Source_First_Technology_Stack_Map_2026-10-24.md`, `RWT_Evidence_Backed_ATS_Technology_Keyword_Catalogue_2026-10-24.md`, `Russ_Watson-Thomas_Career_Technology_Archaeology_2026-10-24.md`, and `Job_Hunt_Capability_Achievement_Catalogue_2026-10-24.md`.