Multi-team engineering automation hackathon (tech)
Code: ENG-HACK | Track: technical | Duration: 0.5-1 day in-person
Bring your engineering teams together in person for a focused build day: shared tooling briefing, one priority automation per team, and closing demos with peer review.
Context
Multiple engineering teams ready to each ship one priority automation in a single day, with peer review built in.
Who it's for
Engineering and platform teams
Prerequisites
- Per-team targets agreed at diagnostics calls; repo and environment access, API keys with spend caps or Claude Code licences in place per team; one room with screens per team plus a plenary space
Format
- In person
Programme structure
- Per-team diagnostics and target selection - A short call with each team to select one high-priority, feasible target and confirm repo access, keys and spend caps for the day. (1x 0.5-1 hr call / team)
- The engineering hackathon - An in-person day in three phases: opening tooling briefing, parallel engineering sprints with our engineers pair-programming on blockers, and closing demos with structured peer review. (0.5-1 day in-person)
- Follow-on implementation support - Per-team engineer support after the event to debug, unblock and harden each build into a deployable workflow. (1x 0.5-1 hr call / team)
Session details
- Total time: 0.5-1 day in-person hackathon + one diagnostics and one follow-on call per team
- Participants: 3-5 engineering teams, up to 10 per team
- Delivery: In person only (UK; other locations by arrangement)
- What you leave with: One shipped automation per team - deployed live where access allows, otherwise deployment-ready with runbook, technical brief - plus a recorded demo library, peer-review notes and a cross-team extension plan