As a UiPath Developer, what are the important tasks you should consider to be part of your job requirements? Join this session to find out more and ask questions from experienced experts. Topics include: Where's your starting point? Are you using a broad use case or a detailed PDD? Are you involved in the Definition/Brainstorming? Are you building and deploying or are you building and sending? Are you in charge of maintaining? What should the maintenance-to-build ratio be? What's your interaction with the C-Suite? What are the KPI requirements? Speakers: Chris Bolin, Senior RPA Engineer @ Gamestop and 2X UiPath MVP Mason Turvey, Intelligent Automation Lead, Academy Bank and UiPath MVP

1. What role do you play as a
Developer?
Section 3
So, you are a UiPath Developer –
What Now?

2. Diana Gray
Community Marketing
Manager AMER
@UiPath
Meet today’s team:
Chris Bolin
Senior RPA Engineer –
GameStop, Inc.
2X UiPath MVP (2022, 2023)
Mason Turvey
Intelligent Automation Lead
Engineer
@SilverInc

3. 3
UiPath developer meetings:
• AMER Developer Community sessions
• Managed by UiPath MVPs in Canada, Latin America & USA
• You are encouraged to network with MVPs and share your LinkedIn url in the
chat box. We want to get to know you
• These sessions are for you to engage with us on topics that interest you or that
you want to share with the UiPath Developer Community
• Please use the chat to place questions until Q&A
• If you have any topics that you want us to cover, please email
diana.gray@uipath.com

4. 4
Date/Time Topic Status
July 13,
3 PM EDT
SNYaUiPath Dev: Environment Recorded
July 17,
3 PM EDT
SNYaUiPath Dev: Stakeholders
Recorded
July 24,
3 PM EDT
SNYaUiPath Dev: What Role Do You Play? Happening Now
July 31,
3 PM EDT
SNYaUiPath Dev: How Do You Manage the Work? Register
Register for Events at community.uipath.com

5. What role do you play as a
Developer?
Section 3
So, you are a UiPath Developer –
What Now?

6. 6
1. A Day in the Life of the RPA Developer
2. Context Matters
3. Where do Developers fit in?
4. What makes a good developer
Role of an RPA Developer

7. A Day in the Life of an RPA
Developer

8. 8
RPA Developer - A Day in
the Life
John is a Senior RPA developer, and he works on a
large team within IT at a large business
Alice is a Citizen Developer in the same company’s
Finance department
Niv is the first RPA developer of a very new team that
sits outside RPA in a different business

9. 9
John
Check Orchestrator/Jira for
process issues
Team Standup
Handle assigned support
cases
Start user story and new
process
Commit code to git, test and
merge into main
Code Review
RPA Developer – A Day in the Life
Alice
One-on-One with her
manager
Learning in UiPath
Academy
Enter a new process idea
into Automation Hub
Build an Automation with
Studio X for her daily
reports
Citizen Developer Office
hours
Run nightly automation from
assistant
Niv
Pulling data on robot
execution in Insights for a
savings report
Defining a new procedure
for automation deployment
Requesting system access
for new automation
Hotfixing a critical
automation issue, working
with the business contact
Setting up a new
Unattended robot to
increase capacity

10. 10
RPA Developer – A Day in the Life
John Alice Niv
Streamlined process Balanced responsibilities
with RPA development
Wears a lot of hats
Tools already in place,
structured environment
Incentivized to automate
work
Drives growth decisions
and determines systems
Opportunity to learn
from a stable
methodology
Benefits from the returns
of automation
A lot of responsibility, but
a lot of freedom
Group responsibility
over individual, but high,
shared stakes
Individual responsibility
with lowered stakes
High stakes, high
individual responsibility

11. Context MATTERS

12. 12
Context Matters
Your role as an RPA Developer will change based on your
environment:
• Who you work with (or report to)
• How many people are at your business
• Whether your program is older or newer
• IT support for program

13. 13
Brand New
Program
Proven
Business Case
Automation
Factory
Different Stages of a Program
What does it look like?
• A few developers
• No tools in place
• Few licenses or deployed bots
What do they need?
• A good pipeline mechanism
• Rapid development over good
development
• Building the business case to
future scaling
• A few teams of developers
• Functional core tools
• Several deployed bots, not
architectural principals yet
• A focus on reusable
components
• Scaling infrastructure
• Figuring out how to automate
building and maintenance
• Several teams, with specialties
• Automated supporting tools
• Bots are architecturally sound
• Catalog of reusable “Automation
Skills
• A mix of good and green
developers
• A focus on process intake
automation
• Solid Intelligent Automation
business cases

14. 14
3
2
1
1
3
2
2
1
3
Intake Development Value

15. Where do Developers Fit In?

16. 16
Know your environment!
Take your whole environment into consideration.
Three questions to ask yourself:
• What level of maturity is my automation program?
• How many potential vs. actual customers/clients do I have (your
internal customers count, too!)
• What do the customers that I build for need out of automation?

17. 17
What will your automation team have ready for you when you start development?
This may include:
• PDD/Steps
• SDD (If you have a dedicated architect)
• Screen recordings
• Stakeholder/process owner contact info
• Data sources/Queries
• Accounts/permission requirements
Know the Input

18. 18
What will you be using to deliver the project?
This may include:
• Source Code repositories
• Work management/tracking software (tickets in Jira, Ideas in Automation Hub)
• Specific implementation templates (REF, Custom templates)
• Development environment (locally or machines in orchestrator)
• Libraries/existing components
• Dashboarding and reporting toolset (Insights, using queues or jobs for
reporting?)
Know the Tools

19. 19
What does your program expect an automation to look like on delivery?
This may include:
• Technical Documentation
• SDD/PDD/Playbook/Runbook
• Security documentation
• Test cases/coverage
Know the Deliverables

20. 20
An Example Automation Program

21. 21
An Example Automation Program

22. 22
An Example Automation Program

23. 23
An Example Automation Program

24. 24
An Example Automation Program

25. 25
An Example Automation Program

26. 26
What If I don’t have this level of methodology yet?

27. What Makes a Good
Developer?

28. 28
1
Owning the
Basics
2
Applying your
Skills
3
Blazing the
Trail
Turning up the Heat

29. 29
Owning the Basics
“Winners don’t just learn the fundamentals, they master them. You
have to monitor your fundamentals constantly because the only
thing that changes will be your attention to them.” – Michael Jordan
• Always know the fundamentals for your toolset
• Studio, Orchestrator
• Secondary tools (workflow, documentation, source code)
Basic Concepts

30. 30
Applying your Skills
• Take the skills you learn, and apply them to a solution
• Learn how things operate in reality, as opposed to theory
• Continue learning newer skills
Applied Knowledge

31. 31
Blazing the Trail
• Start thinking of new ways things can be done
• Bring transformation to your team
• Keep learning and applying new skills
Multi-faceted Architectures

32. 32
Walk before you Run
• If you try to take on big challenges too early, then your pyramid will
topple.
• You need the fundamentals and systems to support larger intiatives

33. 33
Blazing the Trail
In short, a good developer contributes not to the bottom line, but
raises the bottom line.
Always:
• Know or be learning the basics of any system you choose to use
• Look for chances to apply new knowledge
• Think of ways to expand your program through your skillset
• Don’t be afraid to try things that you think are “too hard”

34. Questions?