Enterprise property management mobile app
Senior Software Engineer — requirements, API, frontend
Jarniel Cataluna, software engineer. Over a decade of software engineering across four titles at one company — spanning mobile, web, backend, and DevOps. Shipped enterprise platforms for finance, real estate, and e-commerce, now focusing on multi-agent orchestration and workflow automation across the organisation.
Propelrr, Nov 2015 — present. The progression is the evidence — there are no gaps in it and nothing to reconstruct.
Carried forward from Team Lead, Technology
Carried forward from Backend Team Lead
Carried forward from Web Software Engineer
Rolling agents into an organisation is a delivery problem before it is a model problem — which is the same problem the last decade was, wearing different tools.
The argument, in one sentence.
A decade of enterprise work sits under NDA. These are the major platforms — not the whole list. The sector, the architecture and my role are all true; the client names stay out of it. Most of them ran on a custom Symfony CMS rather than a product someone bought.
Five builds on one architecture — Symfony + MySQL, no bought product — as Lead Backend Developer.
Senior Software Engineer — requirements, API, frontend
API Developer & Frontend Developer
iOS Developer
Work I can describe end to end, because it was mine from the problem through to the deployment.
A full site built as the orchestrator rather than the author: Claude Code and subagent skills generated the codebase, copy, imagery and architecture. Structured for SEO, geospatial and answer-engine retrieval.
Visit the site

A time-in/time-out system on the Google Chat API. One command authenticates against an employee's email and issues a unique ID per session, so entries pair automatically and cannot be logged on someone else's behalf.
Moved rigid applications into Docker and put the deployment lifecycle behind GitHub Actions, so releases stopped depending on who was running them.
Everything here has been used on something that shipped. It is a record of what the work needed, not a list of what I have read about.
The half of the record that is still being written. Everything here is in use on work that ships, not under evaluation.
Anthropic's builder track. Every one of these resolves to a verification page that is not mine to edit — which is the only reason they are worth listing.
Showing item 01 of 08



The questions that actually get asked, answered in full rather than left to be assembled out of the sections above.
If you are building something where a decade of enterprise delivery and a working knowledge of agent orchestration are both useful, that is the conversation I want.