As part of my 1099 software solutions through Archlife Industries, I built and iterated core product functionality across mobile and backend systems.

• Built Plaid connections, trending investors, and suggested stocks.
• Built social features: direct chat, profiles, posts, likes, emojis, and threaded comments.
• Wrote data-visualization logic for comparing stock and crypto performance.
• Transitioned the React Native codebase from JavaScript to TypeScript.

Archlife also served as a public lab for product ideas that were weird enough to be memorable and technical enough to be real.

• Built an OSS Expo + MetaMask mobile app for a hackathon.
• Shipped a personal life intelligence layer as open source.
• Built a financial categorizer and aggregator dashboard for preparing and filing taxes using agents.
• Published public repos that make the work inspectable instead of only described.

Archlife work also included projects where privacy, auditability, and controlled operations had to show up in the actual engineering work. I treat HIPAA and SOC 2 concerns as system-design requirements, not compliance theater, so the implementation reflects minimum-necessary access, traceable change paths, and operational guardrails that hold up under review.

• Mapped product decisions to least-privilege access boundaries, controlled production permissions, and attributable operational actions.
• Built for auditability with clearer event visibility, traceable release paths, and investigation-friendly system behavior.
• Treated sensitive-data handling as an architecture concern: tighter trust boundaries, reduced unnecessary exposure paths, and stricter interface discipline.
• Hardened release workflows so compliance-sensitive changes had repeatable review and rollback expectations before production.

The clearest production example was Finequities, where SOC 2 readiness translated into concrete engineering work across mobile, backend, and release operations. On the healthcare side, my approach is the same: minimum-necessary data flow, strict access boundaries, and audit trails from day one so protected data can stay safe without destroying usability.

• Finequities: tightened access boundaries, reduced security ambiguity in fast-changing product areas, and improved incident-readiness and evidence quality.
• Finequities: drove TypeScript migration and architecture cleanup that made compliance-sensitive logic easier to reason about.
• Healthcare-oriented systems: design for ePHI boundary discipline, role-scoped access, immutable audit trails, and compliance-aware release gates.
• Across both: translate policy expectations into real software behavior instead of leaving them as documentation-only promises.