QA Analyst Intern
"Walk into your next job interview with the ability to confidently say: I was a QA analyst for a pre-seed FinTech startup's trading journal during its paid-tier launch. I joined an existing QA cohort and systematically broke edge cases across four asset classes — stocks, futures, forex, and crypto — and my work directly prevented production bugs from reaching paying customers. I owned end-to-end test cycles: test plans, bug reports, regression checks, and sign-off, working closely with the team and the founder."
The Role
SignalDeck is a trading journal built for serious retail traders. We're in beta and approaching our first paid launch — and before real money is on the line, we need methodical testers who find what others miss. You'll be joining an existing QA cohort and contributing systematic test coverage across every feature we ship: trade logging, analytics, charts, import flows, and account management across stocks, futures, forex, and crypto. If you enjoy finding the one edge case that nobody thought of, and you want real proof-of-work that goes beyond "I ran a test plan," this is it.
🎯 The Goal
This role has one clear north-star metric. We aren't measuring success in bugs filed alone — we're measuring whether production ships clean.
SignalDeck is transitioning from free beta to paid tiers (Free / Pro $30 / Elite $50) around mid-2026. Your job is to make sure the features that matter most to our first paying customers actually work — and that the edge cases that would cause churn get caught before they ship, not after.
What You'll Be Doing
- Expand Test Coverage: Join an existing QA cohort and contribute test plans, checklists, and regression suites for SignalDeck's core features — trade entry, analytics, charts, import flows, and account management — across stocks, futures, forex, and crypto.
- Break Things Systematically: Go beyond the happy path. Test edge cases: partial fills, overnight positions, multi-account imports, unusual lot sizes, timezone edge cases, and anything else a real trader might throw at the system.
- Document Bugs Clearly: Write detailed, reproducible bug reports with steps, expected vs. actual behavior, screenshots, and severity classifications — the kind a developer can act on in five minutes.
- Own Regression Testing: Each time we ship a new feature or fix, run a targeted regression pass to confirm nothing adjacent broke.
- Team Collaboration: Work closely with your QA cohort and the founder to prioritize what to test next based on the current sprint and upcoming launch milestones.
- Asset-Class Deep Dives: Become the specialist for one or more asset classes (e.g. forex pips and swap rates, crypto funding rates and perpetuals) and own QA for those specific flows end-to-end.
- Pre-Launch Sign-Off: Participate in go/no-go decisions before major feature releases — your sign-off means something here because the team is tiny.
Who You Are
- Methodical by Nature: You don't just click through the happy path — you think about what could go wrong and go looking for it with a plan.
- Detail-Oriented: You notice when a number is off by one cent, a tooltip is missing, or a chart axis doesn't match the underlying data. Nothing slips past you.
- A Clear Communicator: Your bug reports are so well-written that the developer can reproduce the issue without asking a single follow-up question.
- Curious About Trading: You don't need to be a trader, but genuine curiosity about how trading works — P&L, R-multiples, drawdown, asset classes — will make your QA dramatically better.
- Self-Directed: You can look at a new feature, figure out what needs testing, and get started without a manager handing you a test script.
- Bonus — You Trade: Any hands-on experience with a trading journal, broker platform, or prop firm challenge is a significant plus (not required).
Why Join Us?
- Direct Founder Access: Work 1:1 with the person making every product decision — your feedback shapes what gets built next.
- Real Ownership: You're joining an existing cohort but you own your coverage areas end-to-end — your name is on the test cases you write and the bugs you catch.
- An Undeniable Case Study: "I was part of the QA team for a FinTech startup's paid launch and helped keep the P0 bug count at zero" is exactly the kind of proof-of-work that stands out in QA interviews.
- Ground-Floor Impact: At a company this size, a single well-written bug report can change the roadmap. Your work matters immediately, not in six months after a committee reviews it.