Skip to content
Jesus Rosario
Back to selected work

Professional work at PRI

GovQuest 2.0

From a legacy application to a multi-tenant platform

GovQuest helps government agencies manage public records requests. At PRI, I led the architecture and launch of GovQuest 2.0 on AWS and continue to lead engineering delivery, with hands-on responsibility for backend systems and relational data models.

My role
Lead Software Engineer
Focus
Backend systems and data
Product reach
agencies across more than 30 U.S. states

The engineering challenge

GovQuest 2.0 needed to replace a legacy product and support agencies with different departments, groups, access roles, and request processes. The challenge was to model those differences within a shared platform while keeping background workflows recoverable when processing fails.

My role and scope

I work hands-on across application code, data models, and AWS infrastructure. I also guide technical planning, design and code reviews, and mentorship, and work with product and leadership on delivery priorities.

Engineering decisions and implementation

Multi-tenant data and agency structures

Agencies organize requests across departments and groups, with different responsibilities and access needs.

I designed tenant-scoped MySQL data models and modules for departments, groups, and task management. This gave the platform an organizational model that could support different agency structures while keeping data scoped to each tenant.

Durable background processing

A request update can trigger background work. A failure between saving that update and dispatching the work can leave the two out of sync.

I built background processing in TypeScript with a transactional outbox, recording pending work in the same transaction as the business change. Deduplication, retries, and delivery checkpoints support recovery when processing is interrupted.

Production workflow automation

Agencies need configurable workflows for request events, requester inactivity, and upcoming or overdue deadlines.

I designed and built an automation engine with event and time-based triggers, conditional rules, business-day calendars, and ordered actions. I separated trigger evaluation from execution and committed each action's database changes together with its recovery checkpoint. On retry, the executor can skip completed database actions; run history makes execution easier to inspect and troubleshoot.

Payments and billing

Payment outcomes need to stay connected to records requests, including refunds and invoicing.

I built Stripe workflows for request charges, refunds, pricing rules, and custom PDF invoicing. Webhook-driven updates keep payment state connected to the application workflow.

Security and compliance

Agency systems need enterprise sign-in and access controls appropriate to staff responsibilities and security requirements.

I implemented enterprise SSO, multi-factor authentication, and role-based access control aligned with CJIS requirements and integrated with agency organizational models. I also contribute engineering work to GovQuest's ongoing FedRAMP compliance preparation.

Outcome and continued ownership

Agency staff can organize requests around departments and groups, configure workflow rules, and manage payments and access within one platform. GovQuest 2.0 and its automation engine are used in production. I continue to lead engineering delivery and develop backend capabilities.