I’ve met 150+ Robotic Process Automaton (RPA) developers but these are the 21 signs of a ‘truly exceptional’ RPA developer!
There are ‘so called’ paper certified Robotic Process Automation (RPA) developers, there are ‘citizen developers’ and then there are ‘truly exceptional’ RPA developers.
Whilst the Head of Intelligent Automation is a keystone of an organisations Intelligent Automation program; its RPA developers are its building blocks for success. Get this role right and organisations have the foundations they need to succeed. Get this role wrong and organisations run the very real risk of building the foundations of their intelligent automation program on sand.
Below we outline the skills and attributes needed in your RPA developer roles if they are to add bucket loads of value. Remember each organisation needs to determine which unique set of characteristics are most important for its strategy and business.
1. Strategic yet tactical view
Every employee needs to understand that they exist to deliver business outcomes. They are not employed to ‘do coding’, ‘do marketing’, or indeed ‘do RPA’. They are there to deliver business value that is tightly aligned to organisational objectives.
Too often developers fall in love with their code. They forget that they are employed to deliver strategic business outcomes (i.e. profit from an activity or product for which customers are willing to pay).
“Ask your developer to talk about “Why – What – How” of the automation. A good developer will quickly work out the “What” and “How”, from documents. It is Tactical. A great developer will step up. He/ she will listen actively to users and learn “Why” certain ways certain things happened. Root causes, then real problem solving comes from the “Why”. It is Strategic.”
Eric Nguyen, Robotics & Automation Lead, Keynote Speaker, Datacom.
2. Curious, adaptable and excited by change
Developers need to be adaptable. They need to be able to pivot and change. This change may involve moving between processes or it may mean learning new parts of the business. Having a curious, ‘willing and eager to always learn’ mindset to try new things is as key as possessing the diligence and patience to get the job in hand completed.
If your developer is not excited about emerging technology then, as Jim Collins would say in his excellent book ‘Good to Great’, they are in the wrong seat, on the wrong bus. Hire people who are excited by what new business outcomes can be delivered from new technology. Don’t hire people who are not excited about using new tech to solve business problems.
“The best developers Iāve ever worked with, are those who, when presented with new technology to work with, responded like a kid in a sweet shop. The entire journey from capture to production starts and ends with them, so their enthusiasm will form the foundation of the engagement. I remember sitting in a demo with a developer recently, whose sheer enthusiasm and excitement for what he was about to show me, grabbed my attention by the scruff of the neck and pulled me deep into his demo.“
Edward Halsey, Technology Expert, Evermore Digital.
3. Excellent communication, interpersonal and influencing skills
Excellent communication, facilitation, and relationship building skills are a must. The ability to communicate in order to elicit or impart information to get their job done is key. A concise, clear and well-formed conversation can save hours of typing and days of fixing when something is not properly understood.
“The truly exceptional RPA developer would have a communication mindset that includes stepping out from behind the curtain and communicating with the client or executive stakeholder. It’s one thing for an RPA developer to be seen as a strong peer or team leader, but they also must have the ability to switch gears, take off their propeller hat and explain the current status and next steps to a client or executive.”
Brett Fraser, SVP Operations, Jolt Advantage Group.
Developers need to be able to communicate articulately in: Agile ceremonies (stand-ups, retros, sprints, refinement sessions); during team meetings, problem solving events or code sharing sessions; with onshore and offshore teams; with SMEs, etc. Paired coding is highly recommended as a way of developing understanding and learning through shared communication (see Richard Sheridan’s excellent book on paired coding, Joy, Inc.).
“RPA or any other automation technology will not provide instant miracles. It’s all about people: developing their skills, creating an automation positive culture, engaging your “customers” in design and implementation. Even though tech can be fast, people and company cultures require more time to evolve.”
Jani Rahja, Head of Intelligent Automation at Posti Group Oyj
4. Coding and logical reasoning skills
There are 3 types of developer; citizen developers (i.e. a domain expert or subject matter expert who is not a typical IT user); RPA developers (experienced and or certified in one or more RPA tool) and programmers (experienced is using one or more programming languages such as C#, VBA, dot net, python, etc).
Whilst much is made of low-code; no-code tools and the increasing need NOT to have coding skills; organisations can quickly run out of runway when it comes to completing automation through click, point and record RPA platforms.
“Having a programmer is key to a successful digital transformation program. Programmers will allow your teams to take full advantage of off-the-shelf tools and will pave a road for highly customised in-house tools. Having a programmer on your team, or as a consultant, will significantly lower the overall cost and will improve the effectiveness of company-wide RPA efforts.”
William Roseberry, Owner of RoseberryPi LLC
In order to piece together a puzzle, you need to follow logical steps. The ability to break business problems into coding or sequential visual flows involves logical thinking that calls for structure, for relationships between facts, and for chains of reasoning that make sense.
If you don’t possess a logical and ordered mindset (think Insights profile green and blue) then it is unlikely you will be able to become an excellent developer or programmer.
“You donāt need to have actual programming skills if you want to become an RPA developer. However, if you want to be better than average in this field, you need to be able to think logically ā analyse, reason and deduct ā and programming skills help develop this mindset.ā
Jan Mastalski, Lead RPA Developer at innogy
5. Copywriting skills
The ability to communicate through documentation is a key part of any RPA role. Being able to develop documents that clearly and succinctly communicate an intended message is a key part of any developers role (e.g. solution design documents; test plans; process design instructions; solution designs, DR/BCP plans; emails to managers or SMEs; annotations within code that others can follow; process instruction documents; etc).
āEspecially when working as a 3rd party in a client, the need to document and then gain sign off from process SMEās and senior leaders requires excellent process documentation skills, as well as an ability to be authoritative while collaborative, the skill mix that’s needed goes far beyond that of a great ācoderā.
Wayne Butterfield, Automation Expert, ISG.
Copywriting skills are essential in order to develop the skills necessary to communicate the intended message effectively.
“The best RPA developers I have worked with executed the same level of detail and effort on creating clear-cut documents as on developing automations. Being capable to take a step back, look at their own documents with a fresh pair of eyes and through the lens of the receiver makes the best developers stand out from the average ones.”
Nirmala Chaturi, Senior Manager | Digital Process Excellence, KPMG.
6. Empathy. Automations should not be designed for robots; they should be designed for people
There is no use producing the very best technical solution if the end user cannot work with it. Designing for the digital age should involve the end customer or user. The end user needs to have an excellent robot – person experience (UX) or they will resist engaging with what you are trying to achieve.
“One of the areas where RPA developers may struggle with is, they forget that end users routinely inherit the support of the automations they create. In order for them to be effective at managing these automations in production, they must be armed with telemetry and monitoring tools that speak the ālanguage of the userā. Meaning, screenshots, video recordings and log syncing easily allows an end user to quickly diagnose a problem. They might not be able to fix the problem on their own, but diagnosing it is more than half the battle. Programmers generating hexadecimal error codes wonāt cut it.”
Joe Labbe, VP of Business Development, Knowledge Lake.
Understanding people, the necessity of excellent employee (EX) and customer experience (CX) and then translating that into exceptions user experiences (UX) is key to digital success. Design thinking can help developers understand their customers but emotional intelligence and genuine human empathy should be inbuilt.
“Great developers love the customer, poor developers love the code and the tools”
Paul Arnold, Head of Product and Development at Cortex Intelligent Automation
7. Excel and Visual Basic for Applications (VBA)
Excel is ubiquitous. It is used in finance, HR, customer service, digital marketing, and many more business areas. Excel is used in nearly every industry you can think of. Combing the data manipulation capabilities of Excel and VBA with RPA makes for a far greater range of valuable automations than almost anything else.
“Dead huh? Technology wise YES ā you canāt run it on any browser or mobile devices but in the corporate world, itās the centre of the MI, reporting, collating information universe. Caseworkers breathe in Excel and breathe out more Excel – you canāt go wrong with it! If you want to take Excel to the next level (I mean automating tedious tasks), try programming in VBA. This is a known rule. RPA vendors give you fundamental Excel drag and drop components but in reality, these laborious tasks require a fast, complex solution i.e. VBA. It takes an exceptional developer to exploit this to their and their organisations advantage.”
Tolani Jaiye-Tikolo, Hyper Automation and Intelligent Automation Consultant, HCL Technologies.
8. High attention to detail
Unit, integration, quality assurance and functional testing are required in every automation instance. If your developers vomit out poorly tested automations, not only will your program and teamās reputation suffer, the return from your program most certainly will too.
“An exceptional developer will not only look at the happy path, but will also consider all the various possible exceptions that can occur in their process and aim to build a resilient bot. This not only ensures that the bot works well, it also recovers gracefully from unexpected errors and flags them for review while it continues with its task.”
Nitin Kamra, Senior RPA Manager, Eli Lilly and Company
Untested code results in data errors, broken processes and large quantities of expensive recursive testing and recoding after your program has gone live. This wastes time when your developers should be focused on delivering wave after wave of new value instead.
“When it comes to code development, the devil is even more in the details. Good developers must optimise code performance and resilience “by design”.
ļ»æIt is crucial to ensure that developers build highly maintainable and expandable bots, and not just āToyā bots.”
Ralph Aboujaoude Diaz, Director, Core Tech, GSK.
9. Can do, positive attitude possessing high accountability for results
You can’t train attitude. No one should need to be motivated by their manager to do their job. Individuals should hold themselves accountable and responsible for delivering excellent business outcomes.
“Indeed in RPA development, you need to think about all the best and worst-case scenarios for a bot. You will need a positive attitude to do that. Your positive thinking will give you passion, it will open new doors for you and make you learn and adapt so much easier. Keep in mind you can, you should and you are brave to do it.”
Sarah Ghanem, Intelligent Automation Consultant and Trainer, UiPath.
Inevitably they will be hurdles in any RPA program. Having positive people in your team will help over the bumps in the road that lay ahead. Exceptional coders must be problem solvers; they don’t wait for instructions, if they own it they build it and they support it to the best of their ability because they want to make a difference.
“From my experience, the best results are achieved when a subject matter expert and developer work closely together. If they engage with a positive attitude, embrace new ways of looking at a challenge and combine that with their requisite expertise, then organisations will get the very best results.”
Nina Barfoed Petersen , Head of Robotics, IRS Enterprise Solutions.
10. Agile and/or project management skills (e.g. Scrum Master, PMP, PRINCE2)
In a fast-paced digital world, more and more firms are using Agile to deliver value to their customers faster. Developers with Agile Scrum skills and Agile mind-set will help you ship wave after wave of value to your customers. If your team does not work and deliver in an Agile fashion, then you may never make a return from your investment.
“Agile development is a perfect fit for RPA. Developers need to understand a process, take it apart and find the simplest most value added section of that process. Then deliver it quickly, constantly collaborate with the process SME and demo their work to get feedback. This will ensure the process is fit for use and helps ensure the SME is engaged throughout the development cycle.”
Matthew Coffey ā Global RPA Lead, Pearson
11. Organised and willing to document
Experience with all aspects of Governance controls, including reporting and metrics, RAID management, impediment tracking, financial management, and working and steering groups.
“An excellent developer will sense the suitable level of detail that needs to be documented, notably from an incident and change management perspective. Being able to detect why processes were modified after go-live, with the right documentation and governance in place is something the internal audit department will love you for.”
Nirmala Chaturi, Senior Manager | Digital Process Excellence, KPMG.
12. Transparent and willing to share
Some of the very best RPA developers can be some of the worst team members. Skilled developers with multiple years’ experience are few and far between. Therefore, their openness and willingness to both document and share that knowledge with their colleagues is key in growing your team’s collective capability.
“The most important output of any great developer is more great developers. Always be learning, always be teaching.”
Paul Arnold, Head of Product and Development at Cortex Intelligent Automation
13. Data and process analytical driven
RPA enables the writing of data points that can provide valuable process analytics (e.g. process exceptions, process time, cycle time, wait time, takt time, etc). By redesigning processes for optimal digital flow, a business can save large quantities of time, which may then result in monetary savings. Deriving new and interesting process analytics can lead to new insights that lead to more efficient ways of working.
“SME’s provide the process flow and the data required to automate a process. When code is built, it is 40 % dependent on the process flow but is 60% dependant on the data being pushed through. Each ‘Endpoint’ in a process, which provides output for another handoff in the same process, is measurable. This can be presented as business KPI’s. For example, Invoice processing produced matrices such as: ” Failed to read Invoices input”, “Dollar value processed in an hour”, “No of vendor invoices processed in the SLA”, “Mismatch of Invoice content w.r.t to PO” etc. Endpoint matrices should be coded and reported upon to enable a more effective RPA implementation.”
Shrippad Mhaddalkar, RPA Consultant, CRG Solutions.
Additionally, RPA developers must be able to understand the business case presented and the data behind it. They must be able to confidently talk to this when engaging with colleagues, stakeholders and to understand the value of what they are delivering. Developers must understand data, or more importantly, they must understand the power of data and how it can drive business outcomes in order to be successful.
“Applying the analysis of data from process discovery is an essential skill in delivering a reliable RPA automation that considers technical latency. Truly exceptional developers will have the ability to understand the required outcome, then deliver incremental business value from integrating existing and new data sources into the automated process. Get the data right first though.”
Mark Barrett, Founder and Lead Automaton Consultant, Automation Outcomes Ltd.
14. Machine learning and artificial intelligence
Developers who not only understand the power of data but who can also manipulate it to derive data-driven decisions are like hen’s teeth (i.e. rare to non-existent). RPA is excellent for automating routine, standard, data-driven processes or tasks. RPA is not capable of doing more complex cognitive tasks such as document scanning or higher-level decision making.
RPA is one tool in an intelligent automation digital transformation tool kit. To create a truly digital workforce, you need to have the same capabilities as a human (i.e. acting, thinking, analysing, sensing, etc.). Without cognitive and analytical capability, RPA is a little more than a macro, with limited use. Therefore, you need intelligent automation developers who can also u build or code other intelligent tools to maximise business outcomes (e.g. OCR, chat-bots, etc.).
“RPA is an amazing tool when used right. But RPA only works with structured data. Most of the data in any given company are unstructured. To be able to automate processes or tasks that use unstructured data, you need more intelligent tools in your toolkit. Tools that can take various documents, emails or even spoken words and transform them into structured data. Combine that with RPA and you will be able to deliver business results beyond belief.”
Anna Lagerhed, RPA Lead, SSAB AB.
15. Scale thinkers
Developers need to think about tomorrow and not just solve today’s problems. Processes that require code that enables multiple robots to run sequentially are very, very different from building a ‘one process, one robot’ code model.
“The drive for improvement in quality, scope and scale is infectious and pushes a team to not just meet its targets, but exceed them. In the modern era of Hyperautomation the phrase ‘Think Big, or Go Home’ fits perfectly.”
Arif Khan, Customer Success Manager and AI Ninja, UiPath.
Developers must code for scale. They must build components that can be run by multiple robots. Components must also be built in a way that they can be used in as many different process structures as practicable. They must also be as easy to maintain as possible, be easy to discard and simple to pick up again so as to rapidly build new value.
“Good code looks good to me. Great code looks good to you”
Jeremiah Cose, RPA Director at Kaiser Permanente
16. Patience, empathy and laser focussed on customer and employee experience are crucial
Whilst RPA is sold as a fast technology; transformation is not. It takes time to learn to code properly (i.e. 18 – 24 months to achieve expertise). It takes time to learn a business (i.e. months and months). It takes time to pass on your knowledge and skills to people who are non-technical. Patience and understanding are both keys to developing great automatons that deliver exceptional business outcomes whilst simultaneously delighting and exciting your customers (CX) and employees (EX).
āWall-E was an automated robot gone rogue. For once Iām happy about that. Because he was super patient, he was understanding, he was curious and he wanted things to grow. We need to be more like Wall-E, the journeys we and our customers take should be āout of this worldā. The only way weāre going to make that happen is to use our time effectively on those things otherwise whatās the point in trying to create automated processes with no direction. Everything will be floating up in space. ā
Jessica Levett, RPA Architect, Pega.
17. Actual RPA experience in a business working with processes
There are a great many paper qualified developers whose experience is not worth the digital paper their qualification is written upon.
Gaining certification for any RPA product is just one of the steps towards becoming an exceptional RPA developer but nothing beats real, hard won battle scars to understand what does and does not work in RPA land.
“Being a great āflow logicā (RPA) expert is not the same as having that fundamental understanding of how to answer a business problem with data and mathematics (AI). Knowing what package to load is not the same as understanding why so, and also when it cannot be used either. Soft skills will absolutely add value to any RPA or AI specialist. But knowing a business and why all these skills need to be applied is absolutely vital to delivering actual value for a business.”
Peter Helth, Digital Change Leader, ATP
18. Multiple RPA tool
An exceptional RPA developer knows one RPA tool exceptionally well but does not mind developing in another. No one tool solves every business challenge. The more tools in the developer tool kit, the more likely they are to solve the business challenges using the right tool.
āLetās imagine this, in fact, it may be your reality. Youāre starting out as an RPA developer, or refining your direction. You back multiple RPA tools to hedge relevance in a rapidly changing market and increase the chances of making an impact. Thinking strategically you pick a market leader; as well as taking a punt on a visionary, an innovative tool that has the potential to lead in the future. You develop extensive knowledge and real-world experience in both tools and recognise that fundamental RPA best practices apply in both instances. One of the tools, which your organisation uses, doesnāt have considerable built-in functionality and in-depth training/best practices to enable object-orientated reusable development. Itās leading to duplicated effort; wasting money and impeding the journey to scale. Realising the consequences due to expertise in an additional tool, you work with the Centre of Excellence to enhance its training/best practices. Moreover, to compensate for the comparative lack of built-in functionality, you drive increased discipline through the Design Authority to govern component development, storage, maintenance and promotion into production. With your ability to take a more objective view of multiple RPA tools, your feedback helps vendors sell strengths and prioritise product development. On your journey to becoming an exceptional RPA developer, tools advance, organisations across industries progress and society benefits as a whole.ā
Lewis Walker, Intelligent Automation Architect, Deloitte.
19. API experience
A truly exceptional developer should develop a working knowledge of APIs. RPA can be fragile. RPA depends on GUIs and those may change for all sorts of reasons (e.g. application upgrade). If APIs can be used instead of robots, or preferably as a complementary tool when the job demands, then that can be a very powerful automation solution.
“Being proficient in the different techniques involved in dealing with back end systems from SQL to SOAP and REST methods, delivers reliability, reduced development time and cost. The robot can be delivered to do more than just mimic humans. It can be pointed directly at the source to bypass GUI interactions vastly streamlining the process. An exceptional developer is aware of these techniques and can work with IT to get these integrations developed, signed off and agreed.”
Gavin Price, RPA Jedi, Automation Outcomes Limited.
20. Project Management Skills
Whilst scrum masters are key, exceptional developers should be able to create structure in an uncertain environment. They ought to be able to delegate tasks and stay cool under pressure as they solve one problem after another. They should be able to supervise and organise activities as well as ensure that their goals align with the company’s objectives. A truly exceptional developer is responsible for the successful co-ordination and management of their code inter-dependencies, including oversight of any risks and issues that arise.
“Having Project Management skills does not just translate to being able to create and manage a project plan. It entails understanding and being able to manage all aspects of delivering a successful technology project and coping with all potential barriers to that success. Your best developers will do this instinctively.”
Arif Khan, Customer Success Manager and AI Ninja, UiPath.
21. Data Privacy and Ethical AI
Beyond the creation of applications that perform well, exceptional RPA developers must ensure that their work is compliant with regulations in data privacy and ethical AI. Building code with security, privacy and ethics in mind from day one will ensure that code provided stands the test of time.
“RPA is often used to transform and propagate personal data, and to render decisions that affect natural persons. As such, developers need to be well-versed in regulations pertaining to privacy, autonomous decisioning, and bias. Above all, their work needs to be explainable. Not quite the same as skills in coding, but no less importantā.
Michael Sisselman, MBA, M.Sc, Conversational AI | Intelligent Automation | Customer Experience Analytics | Digital Transformation Expert
Get your decision right
Remember, if you can’t hire a truly exceptional RPA developer then hire someone with the right smarts and train them up. Hire the “smartest person” you can afford, so they can develop the best robots possible. Then encourage and develop their enthusiasm about technology and what it can be used to deliver.
A truly exceptional RPA developer is a smart facilitator: they will always try to find a solution. But hire and develop someone smart who will say ‘no’ when RPA is not the right tool to solve the business problem. Hire someone who loves technology, infrastructure, computing, gaming, solving puzzles and finding solutions to business problems. The harder the challenge, the better!
If you don’t hire or develop the right RPA developer and decide to ‘make do’, your RPA journey is almost certainly over before it has begun. Get that decision right and you are set for an exciting and rewarding journey ahead.
