QA Engineer (Manual + Automation)

About FaithOnline

FaithOnline is building a Gospel-centered digital ecosystem for real spiritual formation, honest connection, and grounded community online. We believe technology should serve growth in Christ, not distraction or noise.

We are pre-launch and moving quickly. Our platform is iOS and Android first, built for believers who want more than a scroll. Every person we bring on shapes both the product and the mission. We are not filling seats. We are looking for builders who care about what they build.

The Role

We need a QA engineer who can do both halves of the job: test the product by hand with real judgment, and build the automation that keeps us from testing the same things by hand forever.

You will be the quality gate for everything we ship across mobile, web, and our internal tools. Right before a launch, that matters more than usual.

This is not a slow corporate role with layers of process. We move quickly, learn quickly, and adjust quickly. Everyone here owns their work and runs with it. No hand-holding required.

This is a contract position at 30 to 40 hours per week.

What You'll Work On

Manual Testing

• Test features against their acceptance criteria before they move to done, on both iOS and Android

• Run regression passes ahead of releases and App Store submissions

• Test the messy paths: empty states, error states, permission boundaries, offline, account switching, edge cases nobody wrote down

• Verify fixes and close the loop on reported bugs

• File clear, reproducible bug reports that an engineer can act on without a follow-up conversation

Test Automation

• Build and maintain our end to end automated test suite across the mobile app and web platforms

• Grow coverage on the flows that break most and cost the most when they break

• Keep the suite fast and trustworthy. A flaky suite nobody believes is worse than no suite

• Automate the regression work so manual testing goes toward genuinely new surfaces

Release and Quality Process

• Own the quality bar on what ships and be willing to say when something isn't ready

• Help shape testable acceptance criteria during refinement, before code gets written

• Track quality signals over time so we know whether we're getting better or worse

Working Together

• Partner closely with product, design, and engineering

• Take part in sprint planning and ticket refinement over Slack and Jira

• Raise issues early, propose solutions, and own your work end to end

Our Stack

You should be comfortable across most of this, or able to get comfortable quickly:

• Mobile: Flutter (iOS + Android)

• Testing: BrowserStack (App Live + App Automate)

• Auth + Database: Supabase

• Infrastructure: GCP (Google Cloud Platform)

• Social / Messaging: GetStream

• Analytics: Mixpanel

• Project Management: Jira, Confluence/Notion, Slack

Who We're Looking For

• You do both. You test by hand with real curiosity and you write automation. People who only do one half will struggle here.

• You think like a user, not a checklist. The best bugs you've found were not in anyone's test plan.

• Mobile testing experience. You know what breaks on real devices and why the simulator lied to you.

• You write bugs engineers thank you for. Clear steps, actual versus expected, the context that makes it reproducible.

• You build with AI tools. Using AI to move faster is a normal part of how you work, not an afterthought.

• Startup-minded. Comfortable with ambiguity and shifting priorities, and you take ownership without being asked.

• A follower of Jesus who wants every part of life, work included, to glorify Him, and who is looking for a place where His name is welcome rather than off-limits.

Nice to Have

• Flutter or Dart test tooling

• Social, community, or content platforms, where state and feeds make testing harder

• App Store and Google Play release processes, TestFlight, Google Play Console

• Performance or load testing

• Accessibility testing

• A background in faith-based, mission-driven, or community-focused products

What Success Looks Like

• Fewer bugs reach users, and the ones that do get found and fixed quickly

• Regression coverage grows so releases stop being nerve-wracking

• Engineers trust your reports and act on them without a back and forth

• You catch the problems that would have been expensive to find after launch

• You grow with the platform as it scales from early traction into a thriving community of believers

A Note on Who We Are

FaithOnline is a Gospel-centered platform built on a clear Statement of Faith. We believe in the authority of Scripture, salvation through Jesus Christ alone, and the call of the Great Commission. We are building technology in service of the Church, not in competition with it.

The person we hire should share this foundation. You do not have to agree with every implementation decision we make, but you should believe in what we are building and why.

"Whatever you do, work at it with all your heart, as working for the Lord." (Colossians 3:23)

Learn more about us: https://www.faith.online/about