Cyber City, DLF Phase 2, in Gurugram is where this Junior RPA Developer role is based. It's full-time, on-site, and pays up to INR 40,000 a month.
What you'll be doing
- Implement new features based on project requirements coming in from the automation pipeline
- Debug and resolve technical issues in bots that stop behaving the way they're supposed to
- Document your work clearly enough that a teammate can pick it up without needing a walkthrough
- Participate in code reviews, both submitting your own work and reviewing others'
Picture a bot built to pull invoice data from PDFs and log it into an accounting system. One day it starts failing on a subset of files, and tracing that back shows the vendor changed their invoice template just enough to break the extraction logic. Fixing it means updating the recognition pattern, testing it against a batch in the new format, and documenting the change so the next person who touches that bot knows why it looks different from the others.
Some days lean heavily toward building something new in response to a fresh requirement. Other days are almost entirely spent chasing down why a bot that worked fine last week suddenly doesn't. Both halves of the job matter equally, even though the debugging side rarely gets mentioned first when people describe what an RPA developer does.
Code review here isn't just a formality before merging. A workflow that looks fine in testing can still fail once it hits real production data with all its inconsistencies, so a second set of eyes catching an edge case before release saves everyone a scramble later. Junior developers are expected to review others' work too, not just have their own reviewed.
Skills that matter here
Hands-on comfort with UiPath or Automation Anywhere is the core requirement, along with a solid grasp of process automation and workflow design. Freshers coming out of a bootcamp or a strong final-year project on either platform are genuinely in the running here, not just candidates with paid work experience.
Good to have
- A certification on UiPath or Automation Anywhere, even a foundational-level one
- Basic scripting in VB.NET or Python for handling edge cases automation tools can't solve on their own
- Exposure to OCR or document-processing tools used for extracting data from scanned files
- Some familiarity with exception handling patterns specific to RPA workflows
A candidate missing all four of these can still be a strong hire if the fundamentals are solid. These are the kinds of skills that come naturally within the first few months on the job, not gatekeeping requirements meant to filter out otherwise capable freshers.
Who can apply
The degree bar here is computer science, information technology, or something in that neighborhood. There's no minimum prior experience for this one, so it's genuinely built for someone starting out. Naukri Mitra sees a fair number of these fresher-friendly RPA developer roles come through Gurugram specifically, given how many automation teams are based in and around the city.
What tends to matter more than a resume line is whether a candidate can walk through a bot they actually built, even something small from a course project, and explain why they made the design choices they did. That conversation reveals a lot more than a list of tools someone claims to know.
A zero-experience requirement doesn't mean zero preparation matters. Candidates who spent even a few weekends building something in UiPath's community edition, working through a broken workflow until it actually ran end-to-end, tend to interview noticeably better than those who only completed guided tutorials without ever debugging their own mess.
Pay and benefits
- Health insurance
- Paid time off
- Provident fund contributions
- On-site cafeteria access
- Cab or commute support
The cab and cafeteria perks are common among Cyber City employers, given the area's long commutes and limited nearby food options outside the office parks.
Working in Cyber City
DLF Phase 2 sits in one of Gurugram's busiest commercial pockets, packed with IT and consulting firms and connected by the Rapid Metro. That density has upsides and downsides. Traffic during peak hours can turn a short commute into a long one, but it also means plenty of other tech professionals around, which tends to make networking and eventually switching teams or employers easier down the line.
Being on-site as a junior developer has real value early on. Watching a senior developer debug something live, or asking a quick question across the desk instead of typing it into a chat and waiting, speeds up how fast someone actually learns the platform. That kind of proximity is harder to replicate once a team goes fully remote, and it matters even more for a fresher who's still figuring out how the platform behaves under real, messy conditions rather than in a clean tutorial.
RPA teams in Gurugram tend to be younger than many other software development groups, since the field itself is relatively new compared to backend development. That means a less rigid day-to-day hierarchy, though it also means fewer people around with a decade of experience to lean on for the hardest edge cases.
Applying
A resume with even one concrete RPA project, whether from coursework, a hackathon, or a personal build, will stand out more than a general list of programming languages. The interview process includes a practical exercise building or troubleshooting a small automation workflow, followed by a conversation about how the candidate approaches debugging when a bot fails silently rather than throwing an obvious error.
Candidates without a finished project to show can still make a strong case by walking through a partially built project and honestly explaining where they got stuck. Being able to describe a real obstacle and how it was worked through, even without a clean resolution, tends to land better than a polished demo that skips over anything that went wrong along the way.
