Job Summary

Why this role needs a high-skill engineer 

• The platform is live-event critical: defects can affect attendee access, sponsor/exhibitor value, webinar delivery, registration, meetings or event-day operations. 

• Many changes cross old and new architecture boundaries, including web/mobile clients, Express API modules, database state, Redis caches, websocket events, lambdas and deployment infrastructure. 

• The role requires engineering judgement, domain understanding and safe refactoring discipline rather than narrow ticket execution. 

Role purpose 

• Provide hands-on technical leadership for production operations, escalations and live webinar delivery. 

• Bridge client teams and engineering by turning incidents into clear diagnoses, mitigations, engineering changes, follow-up work and runbook improvements. 

A senior technical lead to provide technical ownership for live event and webinar operations, production incidents, customer-impacting issues and engineering resolution. 

Platform context 

Large-scale event and webinar platform: React web app, React Native mobile app, Express/Node API, Socket.IO/websocket service, async worker services, AWS-hosted micro-lambdas for bulk email, file conversion, sync, upload/export and integrations, Puppeteer-based video playback services, Redis caching, Jenkins builds, ECS/Fargate workloads, VPC-managed infrastructure, and MySQL Aurora. 

Key Responsibilities

• Own technical triage and resolution for production incidents across web, mobile, API, websocket, worker, lambdas, video playback services, Redis, Aurora and third-party integrations. 

• Provide engineering coverage for live event and webinar operations, including attendee access, agenda/session issues, registration, meetings, chat, stage/media problems, email delivery and integration failures. 

• Read logs, API payloads, database records, queue messages and dashboards to separate configuration issues from platform defects. 

• Coordinate incident response, including severity assessment, stakeholder communication, engineering mobilisation, mitigation and post-incident follow-up. 

• Create and maintain technical playbooks for common event-day failures, release issues, sync problems, app-store/mobile release risks and customer-specific configuration questions. 

• Validate fixes and mitigations in staging and production-like contexts, and lead controlled releases or rollbacks where appropriate. 

• Identify recurring production patterns and translate them into product, engineering, QA and infrastructure improvement backlogs. 

• Mentor engineers in technical diagnosis, evidence gathering and concise engineering handover notes. 

• Contribute directly to complex refactors, production-critical endpoints, integration work, performance hardening and event-readiness activities. 

Skill Requirements

• Senior software, platform or production engineering background on SaaS, event or webinar platforms. 

• Ability to understand and diagnose React web, React Native, Node/Express APIs, SQL/Aurora, Redis, AWS Lambda, ECS/Fargate and websocket behaviour at a practical engineering level. 

• Strong SQL reading/debugging, log analysis, API testing and production incident-management discipline. 

• Clear written communication for customer-facing and engineering-facing updates. 

• Comfort working under live event pressure with incomplete information and time-sensitive customer impact. 

• Experience creating runbooks, operational dashboards, escalation workflows and post-incident engineering actions. 

• Ability to make safe code or configuration changes and work effectively across legacy and modern architecture boundaries. 

Other Requirements

Expected deliverables / outcomes 

• Reliable engineering coverage and reduced time-to-diagnosis and resolution for live issues. 

• Actionable incident records with evidence, impact, mitigation, technical owner and follow-up engineering tasks. 

• Improved operational runbooks for event-day operations, webinars, mobile releases, integrations and email/sync workflows. 

• Recurring issue analysis and engineering changes that reduce operational load over time. 

• More resilient, observable and maintainable platform components across the event lifecycle. 

Senior leadership expectations 

• Operate with high autonomy, making sound technical decisions where requirements are incomplete or cross multiple systems. 

• Influence architecture, delivery approach, quality standards and production readiness across squads or vendors. 

• Handle high complexity and high business impact, especially during event build-up, release windows and live event operations. 

• Communicate clearly with engineering, QA, product, client teams and leadership, including trade-offs, risk, mitigation and sequencing. 

• Leave systems more understandable through documentation, runbooks, tests, observability and maintainable implementation patterns. 

Relevant platform complexity to understand 

• Monorepo split across web, API, websocket, worker, shared API Gateway packages, lambdas, docs portals and deployment tooling. 

• API bootstrap combines Express, LaunchDarkly, Firebase Admin, Sentry, request-scoped Context, legacy auth flows, route groups and global error handling. 

• Backend actions use getter/processor/setter conventions, yup validation, GlobalError handling, Sequelize models, raw SQL paths, transactions and event/user context checks. 

• Web state is highly coordinated through Recoil atoms, atomFamily/selectorFamily, derived selectors, callback hooks, Redux models, route gates, sockets, meeting popups, chat and stage state. 

• Stage/webinar flows include publisher registries, local device state, presenter state, archiving/composite flags, media files, projector/poll surfaces and socket-driven route behaviour. 

• Serverless processing spans SQS, DynamoDB, S3, MySQL, Secrets Manager, MediaConvert, API Gateway, scheduled syncs, file conversion, bulk export, media upload and third-party integration handlers. 

• Mobile app is a multi-brand React Native shell with native iOS/Android bridges, APNs/FCM, deep links, Fastlane, Detox/Jest, Stallion bundle resolution, CrowdConnected/ExpoFP floorplan integrations and flavour-specific resources. 

• Operational stack includes Redis-backed token/cache usage, Jenkins/CI build steps, ECS/Fargate scale policies, VPC/NAT concerns, Aurora query performance and production incident ownership.