Tilt

Financial Planning and Analysis

• Work hand-in-hand with Tilt’s founders and Finance Lead to tackle our biggest financial challenges and fuel our growth
• Own the processes that keep our financials sharp and scalable: month-end, management accounts, investor reporting, tax ops
• Dive into financial and non-financial data to spot patterns, build a live P&L engine, surface insights, and fuel smarter decisions
• Own high-value finance workflows - payroll, VAT, investor reporting - redesign and automate them
• Build and automate systems with spreadsheets, AI Tools, SQL, or Python to make processes faster, smarter, and more scalable
• Take charge of equity ops & lead on and automate filings (HMRC, Companies House, R&D claims, cap tables, option grants, EMI admin)
• Jump into any challenge - fix bottlenecks, solve problems, and keep momentum high
• Equip the leadership team with the numbers and clarity they need to stay focused and move fast

Strategy & Operations, Finance

QA Engineer

• About Tilt… QA isn’t about ticking boxes; it’s about thinking like our users, understanding the intent behind new features, spotting the issues that truly matter, and working closely with Product Owners, designers, and developers to get them fixed fast.
• You’ll be more than a tester - you’ll be a knowledge hub for your area, the person the team turns to when they need to know how something really works in the wild. This is a hands-on, manual testing role focused on mobile and web, but with real scope for ownership, decision-making, and shaping our QA processes for the future. You’ll be working with live environments, testing across devices and network conditions, and using advanced tooling to uncover the bugs that truly matter.
• 0–3 months: Get up to speed on Tilt’s core flows, community, and feature set (both iOS & Android).
• 0–3 months: Write and document initial manual test scenarios in Confluence/TestRail for our most critical paths.
• 0–3 months: Run your first full regression test cycle on a stable release, producing clear, actionable reports.
• 0–3 months: Set a QA bug-reporting standard for the team, including reproduction steps, expected vs actual behaviour, device/OS info, and media evidence.
• 0–3 months: Explore and document platform-specific differences between Android and iOS builds.
• 0–3 months: Start testing the seller dashboard & seller-related features on both web and mobile for consistency.
• 3+ months: Own regression coverage for your focus area (mobile or web) before every major release.
• 3+ months: Collaborate with POs to decide what needs fixing now vs. what can be scheduled for later, balancing quality with delivery speed.
• 3+ months: Prioritise bug reports so the team focuses on high-impact fixes first, keeping a complete record for future reference.
• 3+ months: Test across multiple devices, OS versions, and degraded network conditions.
• 3+ months: Maintain a backlog of known issues with clear impact notes.
• 3+ months: Adapt quickly to feature churn, shifting priorities, and fast delivery cycles without losing focus on quality.
• 3+ months: Draft a long-term automation strategy (tools, scenarios, ROI) for when the time is right.

Strategy & Operations, Finance

Junior QA Engineer