Full Stack Software Engineer
Backend focused in Django and Laravel, with frontend delivery across React, Vue, Next.js, and AngularJS. Experienced in payroll, HRIS, SaaS, WordPress, digital commerce systems, APIs, integrations, and production support.
Based in the Philippines · Full Stack first, with Backend, Frontend, and WordPress pathways plus an E-commerce systems specialization.
Production payroll & HRIS
Full-stack business systems
WordPress & commerce systems
Employment & selected contracts
Role pathways
One engineering identity, organized into Full Stack, Backend, Frontend, and WordPress hiring paths.
End-to-end delivery across interfaces, APIs, databases, authentication, background jobs, integrations, and production workflows.
Business logic, APIs, databases, asynchronous processing, integrations, validation, and production issue investigation.
Responsive interfaces, dashboards, workflow forms, component systems, API integration, and legacy frontend maintenance.
WordPress platform development across PHP customization, responsive delivery, content systems, membership workflows, integrations, troubleshooting, and ongoing operations.
AI tools on demand
I use agentic coding tools to compress the time between understanding a problem and delivering a verified change. Architecture, security, maintainability, and the final result remain my responsibility.
OpenAI Codex, especially GPT-5.6 Sol, is my primary agentic engineering environment, with Claude Code used alongside it for repository-aware analysis and implementation. I select the tool based on the work, context, and delivery constraints rather than novelty.
Employer and client policies come first. Confidential code, credentials, and customer data stay within approved access and tool boundaries.
Trace the repository, business rule, dependencies, and acceptance criteria so the tool works against the real constraint, not a vague request.
Use AI for focused research, implementation, refactoring, test preparation, and documentation while preserving the project's architecture and conventions.
Review material diffs, inspect edge cases, and run the relevant lint, type, test, build, security, and UX checks before anything is handed off.
Domain specialization
A dedicated systems specialization spanning customer experiences, internal operations, payment workflows, integrations, and delivery through custom stacks, WordPress, or an existing platform.
A Full Stack systems specialization that can be delivered through Django, Laravel, React, Vue, Next.js, WordPress, or an existing platform. The technology follows the workflow: how customers transact, how teams operate, and how data moves after payment.
Best fit for an E-commerce, Full Stack, Web Systems, or WordPress role where customer and internal workflows need continued ownership.
Discuss an employment roleBest fit for a scoped commerce workflow, integration, internal tool, or enhancement to an existing custom or WordPress platform.
Discuss a contract projectSelected engineering case studies
The systems, constraints, implementation decisions, and workflows behind the work.
Ownership is labeled. Employer work is sanitized. Metrics are omitted when they cannot be verified.
01Ongoing engineering contribution to a business-critical payroll and HRIS platform spanning backend services, legacy interfaces, databases, background jobs, and client-specific workflows.
02A full-stack cloud storage product focused on authenticated access, encrypted file handling, resumable uploads, background assembly, and familiar workspace organization.
03A vending workflow connecting a Vue interface, Python backend services, BCH transaction handling, the Paytaca app, and Raspberry Pi hardware control.
04Production contribution to a travel, learning, membership, and business platform through WordPress engineering, Laravel support, responsive campaign pages, custom plugins, and operational troubleshooting.
Additional systems delivered
Two public systems that extend the portfolio into buyer discovery and storefront prototyping without blurring prototype and production claims.
A responsive trade-event experience that guides international buyers from Filipino craft storytelling into category, exhibitor, and registration journeys.
An AI-assisted commerce prototype spanning product discovery, responsive multi-route navigation, cart entry, trust messaging, and customer-contact flows.
Production experience
Current work first, with the system context, technical contribution, and operational value made explicit.
Current · Present
Maintains and extends a production payroll and HRIS platform across backend services, legacy frontend workflows, asynchronous processing, databases, and client-specific business rules.
Nov 2024 — Nov 2025
Supported a live travel, membership, learning, and business platform across WordPress, Laravel, responsive campaign pages, custom functionality, and technical operations.
Feb 2024 — Jul 2024
Developed API-driven web applications and hardware-integrated workflows in a collaborative environment.
Dec 2019 — Jun 2023
Delivered custom web and desktop systems for client requirements across application development and deployment.
Engineering capabilities
Current software engineering strengths lead. Earlier hardware, networking, and support experience adds context without diluting the core role.
Business rules and data flows that hold up under real operational constraints.
Responsive interfaces shaped around dashboards, forms, and business workflows.
Practical ownership across databases, local environments, storage, and debugging.
Digital systems that connect content, memberships, payments, and operations.
Cross-discipline context that helps diagnose systems beyond a single code layer.
A solutions provider approach
I do not begin with code alone. I first understand how the workflow operates, identify the technical or operational gap, and build the smallest reliable solution that improves the process without unnecessary complexity.
The goal is not only to ship a feature. It is to make the system clearer, more dependable, and easier to operate.
Map how people, data, approvals, and exceptions move through the current process.
Separate the actual operational gap from symptoms, assumptions, and unnecessary scope.
Implement the smallest reliable change across the layers the workflow genuinely needs.
Check edge cases, related behavior, and the handoff the people operating the system will inherit.
Credentials & continued learning
These are Certificates of Training—not professional certifications. Sensitive identifiers and signatures are intentionally omitted from the public site.
Technical Education and Skills Development Authority (TESDA)
Delivered by Northridge Institute of Business and Technology Inc.
Training covering statistical concepts, dataset preparation and summarization, and data visualization.
Supports reporting, payroll and HRIS analysis, database workflows, and data-informed business decisions.
Public summary and an independent applied exercise are available below. Original document verification is available on request.
The public summary omits the learner identifier, certificate and training numbers, QR code, signatures, and exact training location.
Technical Education and Skills Development Authority (TESDA)
Delivered by Northridge Institute of Business and Technology Inc.
Foundational training in monitoring and reporting cyber threats and conducting vulnerability scanning.
Supports secure development awareness, logging, monitoring, access control, and production support.
Public summary and a defensive applied lab are available below. Original document verification is available on request.
The public summary omits the learner identifier, certificate and training numbers, QR code, signatures, and exact training location.
About
I am Xyrel Vaughn Delos Santos, a software developer based in the Philippines. My work spans production HRIS and payroll systems, SaaS applications, WordPress platforms, APIs, data workflows, and technical operations.
My background across development, support, integrations, and systems troubleshooting helps me consider how users work, how data moves, how failures appear, and how a solution can remain maintainable after release.
Hiring & collaboration FAQ
Answers for recruiters, hiring managers, and clients evaluating role fit, engagement fit, delivery practices, evidence, and privacy.
My primary target is Full Stack Software Engineer, with dedicated pathways for Backend Engineer, Frontend Engineer, and WordPress Web Developer roles. I am also open to E-commerce and Web Systems work where the scope includes real platform behavior—not page building alone.
Yes. I am open to remote employment opportunities and selected contract engagements. Employment discussions can cover long-term product ownership; contract discussions should begin with a defined workflow, scope, access boundary, and expected handoff.
My public evidence combines WordPress and PHP platform work at Starlegends, production business-system engineering, and a payment-backed vending prototype that coordinated transaction state with physical fulfillment. Together they support commerce work across customer experiences, internal operations, integrations, and payment workflows without overstating an unbuilt storefront.
Depending on the workflow, I can contribute to customer-facing storefronts or service portals, order and inventory administration, fulfillment states, membership access, payment or external API integration, notifications, reporting, and supporting internal tools. Delivery can use Django, Laravel, React, Vue, Next.js, WordPress, or the existing platform when replacing it would add unnecessary risk.
Yes. Much of my production work involves tracing existing workflows, respecting current business rules, and implementing the smallest reliable change. I am comfortable working across modern and legacy interfaces when a full rewrite would create more risk than value.
I can work across PHP or Python backend behavior, APIs, databases, authentication, integrations, background processing, responsive interfaces, troubleshooting, and documentation. The goal is to support the complete business workflow behind the screen.
I use public product context and sanitized descriptions of my contribution. I do not publish private source code, internal URLs, client records, proprietary business rules, or unverified performance metrics.
Yes. I use OpenAI Codex, especially GPT-5.6 Sol, and Claude Code when they can reduce research, implementation, refactoring, test preparation, or documentation time. I treat them as force multipliers, not autonomous decision-makers: I define the scope, inspect repository context, review every material diff, run the project's checks, and remain accountable for security, maintainability, and the result. For employer or client work, usage follows the team's policy, confidentiality rules, and approved data boundaries.
The public portfolio shows the issuer, provider, completion date, duration, competencies, and applied portfolio proof. Original source documents are kept private because they contain identifiers, QR codes, signatures, and administrative details. A recruiter or client may request verification directly.
A useful first brief includes the current platform, the workflow that is not working, the intended users, known constraints, access limitations, and the desired outcome. I can then help separate the essential change from optional scope.
I am based in the Philippines in UTC+08:00 and am open to remote collaboration. Working hours, overlap, communication cadence, and delivery expectations can be agreed during the initial discussion.
Let's talk
I am open to remote engineering roles and selected WordPress or E-commerce systems engagements where I can contribute across business logic, interfaces, integrations, and production support.
