I was hired as a full-stack mobile app engineer to build Finequities, an investing platform that combined retail trading, social-network mechanics, and AI-driven portfolio guidance. The product direction was to make investing collaborative and data-informed: users could trade, follow investors, compare performance, and act on recommendation flows in one app.
At Finequities, I treated SOC 2 readiness as core product engineering work, not a side process for audits. In a social investing app, controls are not abstract: account integrity, transaction trust, production access discipline, and incident response quality all show up directly in user risk and platform credibility. My role was to translate control requirements into real software behavior and operational guardrails across mobile, backend, and release workflows. That meant reducing security ambiguity in high-change areas, making production actions attributable, and tightening system boundaries so control owners could actually prove what was happening in the environment.
I mapped day-to-day engineering decisions to SOC 2 trust-service expectations so control coverage could be explained in product terms, not just compliance language. That meant defining exactly where each control lived in the delivery lifecycle: design decisions, code paths, deployment controls, runtime monitoring, and incident response. The practical model stayed consistent. Security was implemented through access hardening, role boundaries, and tighter privileged workflows. Availability was reinforced through release discipline, rollback readiness, and clearer operational response loops. Confidentiality was protected through stricter data-scope handling and boundary awareness across features and integrations. Processing integrity was improved by reducing ambiguous execution paths and making critical system behavior easier to verify under change. I also treated evidence quality as part of the work. Controls are only valuable when teams can prove they operated as intended, so I emphasized traceability in both technical implementation and operational process.
Finequities was not a single-feature trading app. It blended execution, social proof, and personalization in one user flow so discovery and allocation could happen in the same interface.
I worked across product surfaces and platform plumbing. The fastest way to explain my contribution is by ownership zones:
The core team was small: two full-time developers, one project manager, and one UI/UX designer. With a lean team and broad scope, speed depended on disciplined separation of concerns, rapid handoff loops between design and engineering, and aggressive prioritization of features tied directly to user behavior.
Public artifacts indicate a mobile architecture centered on React Native clients with brokerage, AI, and onboarding partners layered into the stack:
As of April 17, 2026, the most material diligence item is regulatory status. A Federal Register notice states SEC intent to cancel registrations of certain advisers and includes Finequities LLC. The listed hearing-request deadline was May 11, 2026. This is a notice of intent, not by itself a final fraud finding, but it is significant and should be checked directly against current IAPD/SEC records before relying on older marketing claims about active registration.
Finequities was a serious full-stack fintech build with credible product depth: multi-asset trading flows, social investing mechanics, recommendation systems, and partner-backed brokerage infrastructure. The strongest public execution window appears in 2021 to 2024, with visible iOS continuity into 2025. The open regulatory question in 2026 is the key gating factor for any present-tense operating claims.
