Principal Tech Lead

• React (hooks, state management)
• Node.js
• TypeScript
• Supabase (Postgres, RLS, Edge Functions, Auth)
• REST/API design
• Git/GitHub workflows
• CI/CD (GitHub Actions, Vercel)
• Claude API / LLM integration experience
• Prior experience leading a small engineering team
• Has built and delivered a SaaS web application from scratch
• Exposure to infrastructure/DevOps practices

• Strong problem-solving — breaks down ambiguous or complex issues and drives them to resolution
• Initiative — proactively identifies what needs doing and acts on it, keeping actions aligned to agreed plans and priorities rather than going off on independent tangents
• Decisive under ambiguity — willing to make a call and own it
• Pragmatic prioritisation to balance delivery speed with engineering best practice — knows when to move fast and when to slow down for quality
• Communicates trade-offs clearly to the CTO and non-technical stakeholders
• Puts team throughput ahead of individual output — this team treats sprint goals as a shared outcome, not a personal scoreboard
• Mentoring and constructive code review

8+ years software engineering, 3+ years in a tech lead or principal/staff engineer capacity, experience shipping and operating a production SaaS application.

• Weeks 1–4: Onboard into RCP and the Digital Team — meet the CTO, Product Manager, and wider team; get hands-on with the RCP Platform codebase and the team's Scrumban sprint cadence; start contributing with small, well-scoped pieces of sprint work alongside onboarding.
• Weeks 5–8: Deepen contribution — active in code review, taking on larger sprint work, and joining the CTO in early architecture discussions on current roadmap priorities.
• Weeks 9–12: Take clear ownership of a defined slice of the platform's architecture; established working rhythm with the CTO on technical decisions; actively mentoring across the team.