Free · takes a minute · your resume fills your profile
CoreHRx never asks candidates for money. If anyone does, .
Role at a glance
You will
Test features on our web platforms to find, reproduce and clearly document bugs.
Write automated tests in Python using Playwright or Selenium, and help maintain existing ones, with guidance from the QA lead.
Run existing test suites, check the results, and flag failures for review.
Experience
2+ years
Must-have skills
GitGitHub ActionsPlaywrightPostmanPyTestPython
How well do your skills match this job?
Sign in to see your fit: the skills, experience and location this job asks for, checked against your profile.
Job description
Location: New Delhi, India
Who We Are We at CivicDataLab work with the goal of using data, tech, design and social science to strengthen the course of civic engagement in India. We harness the potential of the open-source movement to enable citizens to engage better with public reforms. Our work is centred around building data strategy, data platforms and data science applications to push data-driven decision-making at scale. We work closely with governments, non-profits, think tanks, media houses and academia to build overall data and tech capacity. What We're Looking For A QA Fellow early in their career, with up to 2 years of hands-on experience in software testing and test automation. Recent graduates with strong testing project work are also welcome. You will work alongside our QA lead on one focused testing task at a time, learning how real-world platforms are tested and taking on more ownership as you grow. We value curiosity, attention to detail and a willingness to learn as much as prior experience. Requirements What You'll Be Doing
Test features on our web platforms to find, reproduce and clearly document bugs.
Write automated tests in Python using Playwright or Selenium, and help maintain existing ones, with guidance from the QA lead.
Run existing test suites, check the results, and flag failures for review.
Write and update test cases, and help keep test reports and bug logs up to date. Skills You Should Bring
Some hands-on experience in software testing - manual, automated or both - through a previous role, a fellowship or substantial project work.
Programming in Python, enough to write and debug test scripts.
Hands-on experience with Playwright or Selenium - automated tests you have written in a previous role, a fellowship or a personal project.
Understanding of testing fundamentals: test cases, manual vs automated testing, and how to write a clear bug report.
Basic Git, and a basic understanding of how web applications work - browsers, APIs, requests and responses.
Clear written communication, attention to detail, and eagerness to learn. Good to Have
A GitHub profile or portfolio with test automation work, however small.
Experience with pytest, API testing tools such as Postman, or running tests in a CI pipeline such as GitHub Actions.
An interest in open source, open data or civic tech. Benefits Why Work With Us You will learn testing on real platforms used by governments, civil society organisations and citizens, with hands-on mentorship from our QA lead. Our code is open source, so your work is visible and portable. Fellows who perform well may be considered for a full-time role. Other Details
Location: Delhi
Language: English, Hindi
Engagement: 12-month fellowship (full-time), with the possibility of conversion to a full-time role based on performance. Immediate start (rolling evaluation).
Reporting: Reports directly to the QA Lead.
Stipend: Up to INR 20,000-25,000 per month, depending on experience. Our Commitment to Diversity We are committed to inclusive hiring and strongly encourage applicants from diverse and underrepresented gender and caste identities and/or sociocultural backgrounds to apply for this role. Our organisational policies are gender-neutral, including the POSH policy and leave policy.
This guide is for freshers and working developers in India who use Git every day and now have to explain it in an interview: campus hires, engineers at service companies moving to product teams, and leads who review pull requests. It has 60 questions in three levels. Easy covers the staging area, commits, branches, merges and remotes. Medium covers what goes wrong at work: rebasing, conflicts, reset versus revert, lost commits, rejected and forced pushes. Hard covers Git internals, branching strategies, protected branches, merge queues, large repositories and GitHub Actions security. Every command output shown comes from running Git 2.43 on small practice repositories. Run the commands in a scratch repository of your own, then take the mock test.
Questions you may be asked
What is the difference between Git and GitHub?
What are the working tree, the staging area and HEAD?
What is the difference between git diff and git diff --staged?