PeopleSoft Enterprise Recruiting
Recruiting Enhancements & HR Automation
PeopleSoft eRecruit enhancements and HR process automation — recruiting workflow automation, applicant screening logic, candidate disposition improvements, plus a concept for an internal AI assistant with no external LLM dependency.
Automated
Workflows
Improved
Screening
Optimized
Reporting
In-house
LLM
Business challenge
Government and enterprise HR teams run manual, multi-step recruiting inside monolithic ERP systems, causing delays, inconsistent candidate dispositions and heavy reliance on tribal knowledge to navigate.
What I built
I delivered eRecruit enhancements: automated recruiting workflows, improved applicant screening logic and candidate disposition, and optimized SQL reporting. I also created a roadmap for an internal AI assistant to help staff navigate and get support — designed with no external LLM dependency to fit government/enterprise constraints.
Why it matters
In regulated and government contexts, modernization has to happen inside the existing ERP and its security model — and often without sending data to external LLMs. Improvements must be maintainable and upgrade-safe.
How it's designed
Interface
How the intelligence flows
- 01Assistant concept — internal navigation and support helper.
- 02Retrieval over internal documentation and process guides.
- 03No-external-LLM design to satisfy data-residency constraints.
- 04Roadmap for phased rollout within the ERP security model.
How data is modeled
- Enterprise ERP schema with recruiting and applicant tables.
- Optimized, set-based SQL for HR reporting.
- Disposition and workflow-state modeling within PeopleSoft.
Key endpoints
Integration BrokerSecure, permission-scoped integrations with external systems.Technologies
Key features
- Automated recruiting workflows in eRecruit.
- Improved applicant screening logic.
- Candidate disposition improvements.
- Optimized SQL reporting for HR leadership.
- Internal AI assistant concept (no external LLM).
- Upgrade-safe, maintainable customizations.
Challenges & trade-offs
Working within ERP constraints
Enhancements had to respect the platform's upgrade path, so I built maintainable, isolated customizations.
Modernizing without external LLMs
Government/enterprise data constraints ruled out third-party LLMs, so the assistant concept was designed to run entirely in-house.
Code snippet
-- Route screened applicants to the correct disposition queue
UPDATE ps_applicant a
SET a.disposition = t.disposition,
a.status = 'ROUTED'
FROM ps_screen_rule t
WHERE a.job_id = t.job_id
AND a.score BETWEEN t.min_score AND t.max_score
AND a.status = 'SCREENED';How it ships
- Delivered through the organization's managed ERP release process.
Security
- — Role-based access within the ERP security model.
- — Audited, permission-scoped integrations.
- — No external data egress for the assistant concept.
Scalability
- — Set-based SQL for large HR datasets.
- — Batch processing for high-volume operations.