Behind the scenes of university registration systems and corporate payrolls sits a decade and a half of unglamorous, unbelievably hard engineering. One name keeps showing up in the fine print: Ujwal Dyasani.
Nobody throws a parade for the person who makes a report run in four minutes instead of eighteen hours. There is no highlight reel for rewriting the security model of a Fortune-500 payroll system so that the right people, and only the right people, can see what they need to see. And yet, on the roster of unsung engineering heroics that keep giant institutions from grinding to a halt, few names come up more often, once you start asking the right people, than Ujwal Dyasani.
Dyasani’s career reads less like a resume and more like a slow-motion demolition of bottlenecks. Over roughly fifteen years, he has moved through two of the biggest enterprise software ecosystems on the planet, PeopleSoft and Workday, leaving behind a trail of systems that got faster, safer, and dramatically less painful to maintain. He is, in the best possible sense, an infrastructure guy. And infrastructure guys, as any developer will tell you, are the reason everything else works.
The PeopleSoft Years: Learning to Speak Fluent Bureaucracy
Dyasani’s career began in 2006 inside PeopleSoft’s Student Financials module, a piece of software responsible for one of the least forgiving jobs in higher education: making sure tuition, fees, and financial aid actually reconcile at scale, every single term, for tens of thousands of students who all have slightly different situations. He configured the module against constantly shifting institutional rules, built Application Engine-Component Interface programs to load student records directly into delivered components, and led a legacy-to-PeopleSoft data migration that is the unglamorous, high-stakes work universities rarely talk about in public but absolutely cannot survive without.
Then there is the number that keeps getting repeated whenever people describe this stretch of his career: eighteen hours to four minutes. That is the before-and-after runtime of a critical SQR report Dyasani optimized, a change so dramatic it effectively turned an overnight batch job that risked bleeding into the next business day into something a person could run on a coffee break. He also built the interfaces that connected PeopleSoft Campus Solutions to WebCT, an early learning management platform, stitching together two systems that were never designed to talk to each other.
An eighteen-hour report that runs in four minutes is not a tweak. It is the difference between a system that barely survives its own workload and one that has room to breathe.
By 2009, Dyasani had moved into PeopleSoft security architecture and system administration, a discipline that is equal parts engineering and diplomacy. He configured permission lists, roles, and user profiles; implemented security at the row, department, page, and component level; and managed the LDAP and Active Directory integrations that decide who gets to see what inside a sprawling institutional system. He administered the PeopleSoft Internet Architecture, Application Server, and Process Scheduler, the plumbing most users never think about until it breaks. And he wrote the SQRs that converted legacy HR, Benefits, and Payroll data into PeopleSoft, while customizing the Benefits and Payroll modules through extensive PeopleCode development.
The Jump to Workday: Betting on the Cloud Before It Was Obvious
In 2010, Dyasani made a move that, in hindsight, looks a lot like betting on the future early: he shifted into Workday, then a comparatively young cloud HCM platform challenging decades of on-premise enterprise software orthodoxy. He spent his first year on Workday’s foundational data conversion work, writing the technical specifications that would guide multiple rounds of conversion activity, including the notoriously stressful move-to-production phase where every migrated record either works or becomes somebody’s Monday morning emergency. He also designed specs for custom modules, including a claims module, and built the custom components, processes, reports, and interfaces that filled the gaps between what Workday delivered out of the box and what a real organization actually needed.
From 2011 through 2015, that early conversion work matured into something more ambitious. Dyasani built and supported inbound and outbound integrations using Workday’s EIB tooling, Core Connectors, and the more powerful Workday Studio environment. He also took on one of the more elegant pieces of engineering in his portfolio: consolidating twenty-three separate benefit programs down to four, not by cutting benefits, but by designing more sophisticated eligibility and event rules that let a smaller set of programs do the work the old sprawling structure used to require. It is the kind of simplification that looks obvious after the fact and is genuinely difficult to pull off before it.
A Side Quest, Solved for Fun
In 2015 and 2016, between enterprise engagements, Dyasani did something that says a lot about how he thinks: he independently designed and built a course-registration bolt-on system to fix a scalability limitation in an existing university registration platform. Nobody assigned him this. It was production ERP experience applied, unprompted, to a real operational bottleneck that was frustrating actual students and staff. In the nerd world, we have a word for people who fix things nobody asked them to fix simply because the problem was bothering them: those are the good ones.
Studio, Scale, and the Documentation Nobody Else Wanted to Write
Since 2016, Dyasani has been operating at a different altitude entirely. He has designed and implemented more than forty-five Workday integrations, a portfolio that includes complex Studio-based solutions well beyond what Workday’s out-of-the-box connectors can handle. One integration, in particular, became something of a legend internally: by applying advanced XSL techniques to re-engineer its transformation logic, he cut its runtime from three hours down to four point six minutes, a performance gain that reads more like a typo than a real engineering result until you understand exactly how much waste was hiding in the original design.
He did not stop at Workday’s native toolset, either. When problems showed up that Workday could not solve natively, Dyasani expanded his own toolkit to include Python and Selenium, building automation where the platform itself hit a wall. He engineered a cryptographic file transfer flow using the MoveIT tool, adding real security rigor to how sensitive HR data moves between systems. And he led the PeopleSoft-to-Workday data conversion across North American Payroll, Benefits, HCM, and Absence, essentially bridging the two ecosystems that have defined his entire career.
Perhaps most quietly influential, though, is something that will never show up in a system performance benchmark: Dyasani pioneered a documentation methodology that combines Visio diagrams, plain-language explanations, and instructional videos. Anyone who has ever inherited an undocumented enterprise integration at 2 a.m. during an outage knows exactly why that matters. Good documentation is not a nice-to-have. It is the difference between a five-minute fix and a five-hour incident.
The Research Begins
In the last two years, Dyasani has also started building a public research record, publishing technical papers that formalize the lessons learned across a decade and a half of hands-on systems work. His first, published in October 2019, is titled ‘Optimizing XSLT Transformation Pipelines in Workday Studio: Reducing Integration Runtime from Hours to Minutes,‘ and it reads like the technical autopsy of exactly the kind of performance win described above.
He followed that in April 2020 with ‘Secure File Transfer Architectures for Cloud HCM Systems: A Cryptographic Approach Using Managed File Transfer Protocols,‘ a paper grounded directly in his MoveIT-based engineering work, and in September 2020 with ‘Data Conversion Frameworks for PeopleSoft-to-Workday Migration: Handling Payroll, Benefits, and Absence Domains,‘ which distills years of migration scars into a repeatable framework. In May 2021 came ‘Role-Based vs. User-Based Security Group Models: Access Control Strategies in Enterprise HCM Platforms,‘ a direct descendant of his early PeopleSoft security architecture work, and in August 2021, ‘Leveraging PRISM Analytics for Cross-Functional Reporting in Workday Financials and HCM,’ which tackles the perennial enterprise headache of getting financial and HR data to actually talk to each other.
Five papers in under two years, each one traceable directly to a real system he built and a real problem he personally had to solve, is not a bad start for a research career that is, by his own account, still in its early chapters.
Why Any of This Should Matter to You
It is easy to assume that the most important engineering happens in flashy consumer products, the apps on your phone, the algorithms that decide what you watch next. But somewhere behind almost every paycheck, every university enrollment, and every benefits election most working adults will make this year, there is a system like the ones Dyasani has spent his career building, and rebuilding, and quietly making faster, safer, and less likely to fail at the worst possible moment. That is not a small thing. That is the plumbing of modern institutional life. Somebody has to be excellent at it, and right now, one of the people doing that work at the highest level is a systems engineer most of the public has never heard of: Ujwal Dyasani.
