Lead Automation Anywhere Developer, MIDC Ambad — Nashik
A manufacturing-adjacent company based in MIDC Ambad, Nashik, is hiring a full-time, on-site Lead Automation Anywhere Developer. This role expects 11 years of relevant development experience and is built for someone ready to own a portfolio of production bots, not build their first one on the job.
The bots running here automate a mix of finance and operations workflows, and when one breaks, it usually doesn't announce itself loudly. A bot pulling invoice data from a supplier portal once kept running for three days after the portal's layout changed slightly, quietly logging incorrect totals into a downstream system because nobody had built in a check for that kind of shift. Catching that class of failure, the quiet kind rather than the obvious crash, is a core part of what this role exists to prevent.
The work here includes:
- Implementing new automation workflows based on project requirements from business stakeholders
- Debugging and resolving technical issues in existing bots and automation processes
- Documenting workflow logic and decisions for future reference by other developers
- Participating in code reviews for automation builds created by other team members
Automation Anywhere proficiency is required, along with real process automation experience and strong workflow design skills, the kind that come from building something that has to survive contact with messy, inconsistent real-world data rather than a clean demo environment. Someone who can describe a workflow they built that had to handle edge cases nobody anticipated at first tends to interview better here than someone who can only list bot components they've configured. A few additional skills would help, though they aren't required: experience with another RPA platform such as UiPath or Blue Prism, scripting ability in Python or VBScript for handling logic the platform can't cover cleanly, and some exposure to document processing tools for handling scanned or unstructured input.
Education requirements here don't go past a bachelor's degree, and the company isn't fussy about which discipline, since eleven years of hands-on automation work speaks louder than the transcript behind it. What matters more in practice is a demonstrated history of shipping and maintaining bots that actually run in production over time, not just ones that worked during initial testing.
Compensation for this role runs up to ₹149,500 a month, on-site, full-time, positioned toward the senior end of what automation anywhere developer jobs in Nashik currently pay. Benefits attached to the position include:
- Health insurance
- Paid time off
- Performance-linked bonuses
- Relocation assistance and accommodation support for candidates moving to Nashik
MIDC Ambad is one of Nashik's established industrial and IT zones, home to a mix of manufacturing operations and the automation teams that support them. Naukri Mitra sees a fairly steady stream of RPA and automation roles from this area, and this one sits well above the category average given its seniority.
This role reports to the head of process automation and comes with real say over how new automation projects get scoped and prioritized, not just how they get built. Junior developers on the team bring their workflow designs to this person for review before anything moves into production, so a meaningful part of the week goes toward mentoring and quality checks alongside hands-on development.
Bots occasionally need attention outside standard hours, particularly around month-end financial close when volume spikes and a stalled process can hold up reporting deadlines. That's treated as a predictable part of the role's rhythm rather than something flagged separately, and it tends to settle back down once the close period wraps up.
Interviews for this role generally start with a technical round covering real automation design problems, followed by a conversation with the head of process automation about past projects the candidate has led. Someone who can walk through a bot they built end to end, including a specific failure they had to diagnose and fix after deployment, usually comes across better than someone who can only speak to features configured in a training environment.
Applications are reviewed on a rolling basis, and given how specific the experience requirement is, this process tends to move quickly once a strong candidate applies. Anyone currently based outside Nashik should raise that early, since the relocation conversation gets folded into the process rather than handled only at the offer stage.
The bot portfolio here runs primarily on Automation Anywhere's cloud-native platform, though a handful of older bots still run on an on-premises setup that hasn't been fully migrated yet. Part of this role's mandate is deciding which legacy bots are worth moving over versus rebuilding from scratch, since some of the older logic was written before the team settled on current design standards and might not be worth preserving as-is.
Exception handling gets more attention here than most junior developers expect when they come into automation work. A bot that fails cleanly and alerts someone is far less costly than one that keeps running on bad assumptions and produces wrong output that looks correct at a glance. Building that kind of resilience into new workflows, and retrofitting it into older ones that lack it, makes up a real share of this role's ongoing work.
There's no formal management track attached to this position, but the lead developer here has meaningful input into how the automation team gets structured as the company takes on more processes to automate. A previous lead in a similar role moved into a broader digital transformation position within the company after roughly two years, which offers some sense of where this kind of experience can lead without guaranteeing the same outcome for every hire.
Nashik's industrial base has pushed steady demand for automation talent over the past several years, particularly among manufacturing and logistics companies looking to cut down on manual data entry and reconciliation work. That demand has kept experienced RPA developers in reasonably short supply locally, which is part of why compensation for a lead-level role like this one has climbed to where it currently sits.
