Programmer Analyst (VBA, RPA, Python)

HireSetu's note

Macros, bots and small scripts

VBA, RPA and Python together point to a particular kind of work: macros that replace a manual Excel report, bots that move data between systems, short scripts that clean files or close a gap in a process. Most of it serves colleagues inside Renault-Nissan rather than outside customers, so the hard part is rarely the code. It is understanding how a process runs today, including the steps nobody wrote down, then rebuilding it without breaking month-end.

If your Python so far is DSA practice and web projects, this is a different flavour: compact scripts, real deadlines, users who are not engineers. Two years here can lead to RPA lead or automation architecture work, or sideways into application development and data engineering inside the same IT centre. Ask which RPA platform the team runs on, since UiPath, Automation Anywhere and Power Automate skills do not transfer cleanly.

Spreadsheets, scripts and flaky bots

Revise Python at the level of file handling, strings, lists and dictionaries, plus one library for spreadsheets or data, openpyxl or pandas. For VBA, the Excel object model matters: Workbook, Worksheet, Range, and how to trap errors so a macro fails loudly instead of quietly writing wrong numbers into a report. For RPA, know what selectors, queues, retries and exception handling are for, and what happens when a screen shifts under a bot that has run fine for months.

Delivery on time with accuracy sums up the pressure. A macro that finishes in three minutes but gives a wrong total is worse than no macro at all. Have one small automation you built end to end that you can walk through: what it replaced, how you tested it, and where it broke once real users got hold of it.

Drafted with AI from Renault Nissan Technology & Business Centre India's job posting and checked by Prashanth Jakkula before publishing. See our Editorial Policy.