ServiceNow Developer • ITSM & Workflow Automation • Application Development
As a ServiceNow Developer, I build scoped applications, automate workflows, and advance IT Service Management capabilities for a global enterprise. I think critically about every technical decision—which tool to use, how everything connects, and whether a request will actually accomplish what the requester intends. I believe the best solution is often the simplest one, because my goal is always to build what people will actually use.
My path here was intentional. During my seven years as a Clinical Social Worker, I built a career around navigating layered systems, identifying pain points, and creating intervention plans to address them. When I entered the RiseUp With ServiceNow (previously NextGen) externship program, it all clicked: Here was a platform where I could apply that same systems thinking at scale. I was making a career pivot, but the foundation was already there.
I research obsessively, translate freely between technical and plain language, and take pride in solutions that are thoughtful and well executed.
Scaling CMDB Data Migration Across CI Classes
Details have been generalized for confidentiality.
Context:
As part of an instance data replication redesign, existing CMDB records needed to be copied from a core table into a staging table within a scoped application across approximately 10 CI classes. Flow Designer was selected for its reusable, repeatable, visual logic structure; the intent was to configure the initial run as a scheduled job set to execute once, with a recurring frequency to be established later for ongoing automated replication.
Problem:
Nearly one million records needed to be migrated. The initial flow timed out due to Flow Designer's built-in 10,000 record lookup limit. Raising the max result threshold did not resolve the issue; even if it had, Flow Designer is not natively built for continuous batch pulling at that scale, making it an insufficient long-term fix regardless.
Troubleshooting:
A looping structure was engineered within the flow to process records incrementally. This successfully pulled records, but only for one of the ten CI classes. It became clear that a single universal flow could not handle all classes reliably; the path forward was a dedicated flow per CI class. Throughout this process, the staging table needed to be cleared repeatedly. Depending on the scope, this was handled using Data Management Jobs or direct deletion through Tables and Columns. When deactivating a flow failed to stop an already-running job from continuing to populate the table, the job was manually terminated through Active Transactions (All Nodes).
Final Result:
Delivered a scalable CMDB migration pattern using dedicated looped flows per CI class, operating within system constraints and structured for future conversion to scheduled automation for ongoing instance data replication.
Tools & Skills
Flow Designer, Data Management Jobs, Tables & Columns, Active Transactions (All Nodes), Scheduled Jobs
Automating Testing for Service Catalog Items
Details have been generalized for confidentiality.
Problem:
Following each ServiceNow instance upgrade, Service Catalog items required regression testing to confirm existing functionality was not impacted. Testing was being conducted manually, making the process time consuming, inconsistent, and difficult to scale.
Action:
Designed and developed an ATF test suite to automate regression testing for existing catalog items. Each suite validates three critical components: the form, form validation, and the fulfillment flow.
Solution:
Reduced manual testing overhead and established a repeatable testing process that supports faster and more reliable deployments. Going forward, all newly created catalog items include a corresponding ATF test suite, making quality control a standard part of the development process.
Tools & Skills
Automated Test Framework (ATF), Service Catalog, Flow Designer
Sprint 1: Scoped Application Build
App architecture, menu structure, modules, UI policies, and key features that establish the foundation of the loaner vehicle system.
Sprint 2: Approval Flow & Client Scripts
Multi-stage approval logic, client-side scripting for dynamic form behavior, and security configurations for proper access control.
Sprint 3 Part 1: Service Portal
Front-end user experience built in the Service Portal, giving users visibility into available vehicles and a transparent request submission flow.
Sprint 3 Part 2: Business Rules & Automation
Back-end fulfillment automation triggered on catalog item submission to reduce manual work and enforce data consistency.