Built for candidates and hiring teams · ForumO Jobs is newly launched · Browse openings worldwide · Sign in only when you open a role · Built for candidates and hiring teams · ForumO Jobs is newly launched · Browse openings worldwide · Sign in only when you open a role · Built for candidates and hiring teams · ForumO Jobs is newly launched · Browse openings worldwide · Sign in only when you open a role · Built for candidates and hiring teams · ForumO Jobs is newly launched · Browse openings worldwide · Sign in only when you open a role ·
EngineeringIndiaOnsite1 to 3 yrs₹5 to ₹7Via Wellfound
JavaScriptSQLMachine Learning
Category
Engineering
Work mode
Onsite
Type
Full Time
Experience
1 To 3 Yrs
Salary
About the role
About the role
Nector is a Shopify-native loyalty and rewards platform used by 1,000+ D2C brands to run points, tiers, referrals and rewards programs. Our software sits between live storefronts and real transactions - a bug isn't a broken button, it's a customer not getting points they earned, or a discount applying twice at checkout. Quality is the product. We're a small team, so you won't be executing someone else's test cases all day. You'll own quality for the features you test - understanding what's being built, deciding how to break it, and being the last person who says "this is ready to ship." If you take pride in finding the bug nobody else thought to look for, you'll do well here.
What you'll work on
Testing features end to end before release - merchant dashboards, storefront widgets, points and referral flows, and everything in between
Storefront widget testing across themes, browsers and devices - our widgets land on thousands of different Shopify themes and have to behave on all of them
Testing Shopify integration flows: webhooks, checkout behaviour, order and refund scenarios, and how points/rewards respond to each
API testing with Postman or similar - verifying responses, edge cases, and error handling, not just happy paths
Regression testing around releases, and building lightweight test cases and checklists that make the next release safer
Writing bug reports developers can act on immediately - clear steps, expected vs actual, environment, evidence
Requirements
What we're looking for
Curiosity over checklists - the best testers don't just verify what should work, they hunt for what shouldn't.
₹5 to ₹7
Location
India
1–2 years of manual testing experience in a web product company, ideally Saa S or e-commerce.
Strong test design instincts. Given a feature, you can map out the edge cases - empty states, boundary values, concurrent actions, weird user behaviour - without being handed a spec.
Comfort with browser devtools. You can inspect elements, read console errors, and check network requests to tell frontend bugs from backend ones.
Basic understanding of HTML, CSS and Java Script - enough to understand what you're testing and describe where it breaks.
API testing fundamentals. Requests, responses, status codes, and what a malformed payload should do.
Clear written communication. Your bug reports and test notes should save time, not create questions.
Good to have
Familiarity with the Shopify ecosystem - themes, checkout, apps
Basic SQL to verify data directly in the database
Exposure to test automation - we'd support you growing into automation over time
Experience testing payments, checkout, or transaction-heavy flows
Familiarity with bug tracking tools like Jira, Linear, or Click Up
How you work
This matters as much as the technical bar.
You take ownership - if you signed off on it, you stand behind it, and if a bug slips through, you figure out why your testing missed it.
You're thorough without being slow. You know which flows are critical and deserve deep testing, and which need a quick sanity pass.
You work well without much structure. Nobody hands you detailed test plans - you build your own coverage from a feature description.
You're comfortable pushing back. If something isn't ready, you say so clearly, even when the release is scheduled.
You think about the merchant. A cosmetic bug on the checkout widget matters more than a rare edge case in an admin screen - you prioritize accordingly.
