AJ JubaraDesign Engineer / Systems Architect
The operator

They think they are hiring
a seller. An operating system
walks in.

I spent years selling technical software to the people paid to break it: CISOs, IT directors, MSP owners, and the compliance officer who reads every line before signing. Then I started building the systems instead of pitching them. Same buyers. Same standard. Nothing ships that I would not defend in a security review.

I still sell, support, de-escalate, and expand accounts. Building the systems did not replace that work, it sharpened it. The standard on a live call is the standard in the code: clean execution, and it compounds.

38.8% close rate on technical demos $500K+ pipeline owned and forecast 294/294 tests passing in production Tampa Bay
01Trust surface What the customer sees. Nothing else lives here.
02Intake and validation Nothing enters the system unvalidated.
03Deterministic core The same inputs return the same price. Every time.
04Payment rail Invoices reconciled against signed events, never guesses.
05Ledger Every state transition recorded. A crashed run self-heals.
06Human approval No external action fires until a person says so.
Object state / Sealed

Six layers, one object. The surface is the only part most people ever see. That is the entire purpose of the surface.

01 Who it is built for

Real businesses. Real money. Real consequences when it breaks.

One spine, adapted per vertical. The intake, the pricing logic, the approval step, and the ledger stay the same. What changes is the language of the business.

01

Cafes and hospitality

Direct ordering, table and reservation intake, service timing.

02

Service businesses

Lead to cash: quoting, scheduling, dispatch, invoicing, follow-up.

03

Medspas

Consultations, deposits, package tracking, rebooking cadence.

04

Private practices

Intake forms, confirmations, records discipline, no-show recovery.

05

IT firms

Ticket intake, client reporting, recurring billing, renewals.

02 Flagship systems

Not a portfolio of screens. A portfolio of operating systems.

Each was taken from an empty repository to a deployed platform in production. Interface, security, automation, and business logic designed as one decision, not bolted together afterward.

Service-business revenue infrastructureAristova OS
Production / Private core
What it does

An owned lead-to-cash operating system on a Postgres source of truth. A public trust surface captures intent. A gated command center runs the business. Structured AI turns every inbound into a draft, and a human approves it before anything reaches the customer. The pricing engine is deterministic: the same inputs return the same number, computed on the server where nobody can quietly edit it.

System depth
Atomic RPC state machineRow-level securitySigned webhook reconciliationStructured AI tool useIdempotent work claimingOutbox workflowsSigned-cookie vault authPII redaction at the boundary
Verified
294 / 294 tests passingRecoverable provider callsRace-condition guards
Read the architecture brief
Admin core gated
Cinematic hospitality operating systemHospitality OS
Production
What it does

A full hospitality operating system carrying a distinct cultural identity. Direct ordering, table and reservation intake, a guided bundle assistant, and a signature three-dimensional moment rendered live in the browser. Warm charcoal and ember surfaces, hand-built detail, volumetric light. The interface is the brand, and the brand is why a guest orders here instead of somewhere else.

System depth
Server-trusted pricingReservation state machineWebGL interface momentSMS outboxStructured AI enrichmentServer actions
Verified
147 unit tests36 end-to-end scenariosRendered QA before ship
Private walkthrough on request
Identity built, not templated
03 Security and compliance

I learned to build from the people paid to say no.

Before I built systems, I answered for them. I owned the vendor security questionnaire cycle for cybersecurity buyers: the long spreadsheets, the evidence requests, the follow-ups. You do not forget what a control is after you have had to defend one.

Frameworks I have answered to

I ran the response cycle end to end for enterprise and MSP security reviews, coordinating across security and product to return clean, on-time evidence. That is a different kind of knowledge than reading the standard.

SOC 2ISO 27001GDPR Vendor security questionnairesEvidence and audit response

What that becomes in the code

Security is not a section of the build. It is the shape of it. Access is scoped and signed. Data is redacted at the boundary before it reaches a model or a log. Nothing external fires without a person approving it, and every attempt is written down.

Row-level securitySigned, scoped sessionsPII redaction Human-in-the-loop approvalSecret scanning before deploy

Identity and access: SSO, SAML, and SCIM at a working and demonstration level. Architectural depth on identity protocols belongs to specialists, and I say so in the room.

04 The reversal

The seller was the training for the architect.

Years of selling technical software to CISOs, IT directors, and MSP owners. That fluency was never left behind. It became the method.

Buyer discovery. Reading what a technical buyer actually needs, underneath what they asked for
Product architecture that answers the objection before it is raised
Demo discipline. Sequencing a room of skeptics to a decision
Interface sequencing that moves a visitor to a decision without friction
Security questionnaire ownership. SOC 2, ISO 27001, and GDPR, defended line by line
Secure defaults that ship first, not as a later hardening pass
Pipeline discipline. $500K+ forecast clean in CRM, nothing lost between stages
Operating-system thinking. Every state tracked, no silent failures
Outbound intensity. 100+ daily touches, $5,250 monthly expansion revenue
Founder-level execution. Empty repository to deployed system, alone
Native Arabic and English. A commercial wedge into Arabic-speaking technical buyers
Reach most teams cannot replicate with the org chart they have
Contact

Bring the whole system into the build.

Open to founding engineer, principal frontend, design engineer, and systems architect work. The systems are already in production. The only question is whether the next one gets built for your company.

LinkedIn
No contact address is published on this page. Wesley Chapel / Tampa Bay