Real Project Experience
Work on scenarios based on actual client requirements, not made-up examples from textbooks.
Financial Technology Skills That Actually Matter
We're running practical workshops starting September 2025. No fluff about overnight success or guaranteed jobs. Just real skills from people who've built fintech products that clients use daily.
Callum Jessop
Payment Systems
Spent eight years building transaction processing systems for mid-sized banks. Knows what breaks at scale and how to fix it before regulators notice.
Dominic Forsythe
API Architecture
Former tech lead at three different fintech startups. Two succeeded, one didn't — which means he's learned from actual mistakes instead of theory.
Lachlan Driscoll
Security Compliance
Works with Australian financial institutions navigating APRA requirements. Understands that security isn't just about encryption — it's about documentation auditors will accept.
Who You'll Learn From
People Who've Actually Built This Stuff
Our instructors work on financial platforms during the day and teach what they use at night. They're not academics reading from outdated textbooks.
Each one has dealt with production incidents at 2am, explained technical decisions to non-technical stakeholders, and debugged code they didn't write. That's the experience they'll share.
-
-
Small Workshop Groups
Maximum 12 participants per session so instructors can review your code individually.
-
Current Industry Practices
Learn tools and frameworks companies are hiring for right now, not what was popular five years ago.
-
Honest Feedback
Get straightforward code reviews that point out what needs improvement instead of generic encouragement.
How The Program Works
Twelve weeks of weekend workshops starting late September 2025. You'll build components for a transaction processing system piece by piece. By the end, you'll have working code you can show potential employers.
Practical Build Sessions
Saturday workshops focus on building specific features — user authentication, payment validation, transaction logging. You write code, get it reviewed, refactor it based on feedback.
Technical Deep Dives
Sunday sessions cover the theory behind what you built — security patterns, database design principles, API versioning strategies. Context matters when you're making architecture decisions.
Code Review Process
Submit your work by Thursday evening, get written feedback by Friday. Instructors point out security issues, performance problems, and maintainability concerns before the weekend session.
Industry Guest Speakers
Once a month, someone from a financial institution talks about what they're actually working on. Recent topics included regulatory compliance challenges and legacy system integration.
Portfolio Development
Final four weeks are for polishing your project into something presentable. Clean up code, write documentation, prepare explanations for technical interviews.
Optional Advanced Topics
Extra sessions available on specialized subjects like blockchain integration, fraud detection algorithms, or mobile payment systems. Only offered if enough people are interested.
What You'll Actually Build
A transaction processing system that handles account validation, payment authorization, and audit logging. Not enterprise-scale, but functional enough to demonstrate understanding.
You'll work with REST APIs, database transactions, error handling, and basic security measures. The kind of components junior developers maintain in their first year at fintech companies.
We start with existing boilerplate code instead of building everything from scratch. Real projects inherit legacy systems — you might as well learn to work with unfamiliar code bases now.
Ask About Next Intake