I have been trying to transition to RPA development for the past 3 months, but I haven’t received a single call. Currently, I have 2.3 years of experience in my field.
Is it a good idea to continue pursuing a career in RPA, or should I start learning something else?
I’m feeling increasingly insecure and struggling to focus properly. I’m not sure how to overcome this situation. Any guidance would be greatly appreciated.
Do you do any RPA programming or only support? If you want to transition to development you’ll need to learn development first. If you don’t have any programming experience I recommend also taking basic programming courses so you’ll understand programming logic, flow control, variables, vb.net or C# expressions, etc.
UiPath likes to position its product as low-code but honestly it really isn’t. You still need to understand programming.
I would suggest talking to your manager at Capgemini and tell them you want to learn RPA development. Surely they have resources to help you, and likely could move you to entry level development once you have the knowledge foundation from classes.
Yes, I have programming knowledge, and every day I’m implementing small use cases for self-improvement. I’ve been doing support work for 1.5 years, and I’m trying to switch to a development role as soon as possible, but I haven’t received a single call recently.
Because of this, I’m struggling to focus properly. If I continue like this, recruiters’ expectations will increase over the years, and I won’t be able to meet them since I lack development experience.
Also, case studies are good for getting an idea of how RPA is used.
Many of those will be fairly complex processes, since UiPath wants to showcase its power. But I think most organizations have a lot of more simple processes they automate first. Some of our simpler automations:
Take data from a spreadsheet and enter it into a mainframe system
Collect emails from a mailbox (using filters to get the right emails), save the attached files (using filters to get the correct ones), and then uploading the files into a web app
Get customer numbers from a daily spreadsheet, look up information in multiple systems, compile all the data and generate a report in Excel, then email the report
Scrape data (requests for account changes) from a web app, do the updates in another system, update the web app with the results, and send an email summary of what was done (including any failures so the department can handle them manually)
Present the user with a form they can use to select account documents (PDF or TIFF), categorize them, make notes etc, then submit them to another automation that uploads them into a document management system
I started with the training. Did some playing on my own. Then became part of a team in our company that had some existing automations but everyone was new-ish too. We had an outside company that helped us write our first automations, set up Orchestrator etc.
I learned a lot by looking at existing automations.
As I mentioned to Kumar, it is somewhat important to have at least some basic programming knowledge. You’ll need to understand flow control, variables, loops, programming logic, etc.
Some things I wish I had figured out sooner than I did:
Expressions and object properties - if you have a variable and type its name then a period you get a whole list of information you can get from it and things you can do with it (like myDateVar.ToString - ToString is a method of datetime variables)
How to manage packages in Studio - there are activities for just about everything. Don’t make something custom before making sure there’s no activity to do it. I spent quite a bit of time writing my own vb.net script to send emails with SMTP instead of using Outlook…then found out there’s literally a Send SMTP Email activity
No once I started doing my own projects they came from our business analysts who determine which processes are good to automate. BAs talk to the departments and document processes, developers build the automations, and production monitoring deploys and executes the automations.