We need a Remote Research Scientist to take on a batch of open technical questions. The schedule bends around you, not a nine-to-five block. Anyone coming from a lab where clocked hours counted more than output should notice the difference fast.
The Shape of the Work
Weeks usually swing between building a hypothesis, testing it, then picking apart what the numbers say. One project might run for months. Other times three smaller ones sit on your desk at once, each one further along than the last. Nobody's tracking where you sat while doing the work. A kitchen table three time zones away counts the same as a home office down the hall.
- Build and run experiments tied to whatever question is active
- Pull data sets apart and turn the mess into something someone downstream can use
- Put results into writing that holds up for a specialist and a stranger to the field alike
- Keep an eye on published research and call out what's worth chasing
- Loop in other teams once a project needs skills outside your own corner
- Walk findings through internally, dialing the technical depth up or down depending who's listening
The label
remote research scientist gets stretched to cover a lot of different jobs. This one sits on the broader end. Expect to build studies, work through the numbers, and then walk someone else through what you found without them having sat beside you the whole time. A fancy degree matters less than whether the conclusions survive someone pushing back on them.
What You'll Need
- A Master's or PhD in a relevant scientific or technical field — or research experience that adds up to roughly the same thing
- A history of running research mostly on your own steam, documented in some form, papers, internal write-ups, doesn't matter which
- Real quantitative chops, plus working knowledge of at least one analysis tool or programming language
- Writing a non-specialist could pick up and follow without needing a translator
- Enough discipline to run your own timeline across time zones without daily hand-holding
Bonus Points For
- Already having worked on a distributed or remote team
- Papers with your name on them, peer-reviewed or otherwise published
- Time spent mentoring junior researchers or reviewing their drafts
- Knowing Python, R, or whatever tool your particular field leans on
People fresh out of grad school apply for this alongside folks who've spent a decade doing research work. Seniority mostly decides how much you're handed, not whether the door's open.
Compensation and Setup
Pay
is $140,000 per year. Both part-time and full-time arrangements are open, depending on what fits your life. Naukri Mitra builds its research roles around what actually gets produced, not hours logged on a timesheet. Nobody added that line to sound generous — it's how the team runs day-to-day.
Culture, Honestly
Remote research teams usually fall apart the same way: nobody writes anything down, and context disappears between people who never share a room. This team pushes against that pretty hard. Updates get documented for real. Meetings stay short and rare. People explain their reasoning out loud instead of assuming everyone caught the same thread somewhere. Even an experiment that goes nowhere counts for something — ruling out a bad idea is still work.
Where This Can Lead
Some researchers here dig deeper into one narrow area until they're the go-to person for that exact problem. Others drift toward shaping research direction across several projects. Either route gives more control over what gets studied next and, eventually, more say in how the whole research side runs.
Next Steps
Send a resume, plus writing samples, publications, or project summaries that show how you actually work through a problem. Credentials get skimmed. The thinking behind them gets the real look.
