Software Tester

Confidential Startup SaaS Company; India; On-site; INR 500,000 - 800,000; Full time

Job summary

Confidential Startup SaaS Company is seeking a Software Tester to join our engineering team as the sole QA voice. In this manual testing role, you will assess various SaaS products, desktop applications, and consumer-facing software across Mac, Windows, Android, and iOS.

Your responsibility includes identifying and documenting software bugs before release. The ideal candidate has 2+ years of experience in manual software testing and strong skills in bug reporting and cross-platform testing.

Qualifications

• 2+ years of manual software testing experience across desktop and mobile applications.
• Hands-on testing experience on Mac, Windows, Android, and iOS.
• Ability to write detailed, reproducible bug reports.
• Experience testing SaaS products and consumer-facing applications.

Responsibilities

• Test across multiple platforms and operating systems.
• Document findings clearly for developers.
• Catch bugs before release and ensure test reports are actionable.

Skills

Manual software testing experience

Cross-platform testing

Clear bug reporting

Self-prioritization

Familiarity with bug tracking tools

Tools

Jira

Linear

Job description

If you are interested in applying for this role, please submit your application using our application tracking system. Submissions received via LinkedIn will not be reviewed. The direct link is: https://itsordely.com/apply/PGLBzvmpqnyAtA

We're looking for a sharp, skeptical Software Tester who joins our engineering team as the sole QA voice across a range of SaaS products, desktop applications, and consumer-facing software. You won't be handed a checklist and asked if things work — you'll be expected to hunt for what doesn't work, what's inconsistent, what breaks under real-world conditions, and what a user would find frustrating before they ever file a support ticket. Your job is to think like the most demanding user in the room.

This is a manual testing role covering Mac, Windows, Android, and iOS. You'll test across multiple platforms and operating system versions, comparing behaviour, flagging inconsistencies, and documenting findings clearly enough that any developer can act on them immediately. Because you'll be the only dedicated tester, you need the independence and confidence to prioritise your own workload and raise issues without being asked.

Success in this role looks like bugs being caught before release — not after. It looks like test reports that are specific, reproducible, and actionable. It looks like developers trusting that when something passes your review, it genuinely works. Over time, as the team grows, there may be opportunity to move into automation testing, but for now the focus is entirely on doing thorough, methodical manual QA across a varied and growing product portfolio.

What we're looking for

• 2+ years of manual software testing experience across desktop and mobile applications
• Hands‑on testing experience on all four platforms: macOS, Windows, Android, and iOS — not just familiarity, but actual test execution across these environments
• Experience testing SaaS products and consumer‑facing applications in a professional setting
• Ability to write clear, detailed, reproducible bug reports — including steps to reproduce, expected vs actual behaviour, environment details, and severity assessment
• Strong cross‑platform mindset: able to spot inconsistencies in UI behaviour, performance, and functionality across operating systems and device types
• Experience working from functional requirements, user stories, or product specs to derive test cases independently — no hand‑holding required
• Comfortable working as the sole QA tester, self‑prioritising across multiple products or releases simultaneously
• Familiarity with bug tracking and project management tools such as Jira, Linear, or similar
• Exposure to testing different app types — SaaS web apps, installable desktop software, and native or hybrid mobile apps
• A mindset oriented toward finding failure, not confirming success — you question assumptions and test edge cases as a default