Operations, logistics, compliance, and systems automation.

I build practical software for workflows where physical operations, systems of record, and compliance requirements have to stay aligned: shipping documentation, scheduling, inventory data, defect tracking, audit evidence, and secure multi-tenant applications.

Current positioning: Operations & Compliance Specialist with 7+ years in logistics environments, supported by 14+ years of broader hands-on operations, systems, and process improvement experience.

• LinkedIn: https://linkedin.com/in/joel-abraham-cv
• Portfolio: https://secureyour.tech
• Email: hire.joel.abraham@gmail.com

Operational scheduling and roster-management platform for youth sports administrators.

Built to convert registration data into balanced rosters, practice schedules, game schedules, facility workflows, reporting, and administrative coordination.

• Live: https://squadlogic.secureyour.tech/
• Repo: https://github.com/JoelA510/SquadLogic
• Stack: React, Vite, Supabase, PostgreSQL, Edge Functions, RBAC, RLS, Vitest, Playwright-BDD
• Operational value: replaces spreadsheet-heavy scheduling workflows with structured import, generation, review, and reporting flows
• Engineering value: CI gates, bundle checks, advisor linting, security documentation, and test coverage around high-risk workflows

Shipping-document workflow platform for logistics records, document conversion, and shipment search.

Designed around real logistics pain points: repeated document preparation, Commercial Invoice / Shipper's Letter of Instruction style data, classification data, and fast retrieval across shipment records.

• Repo: https://github.com/JoelA510/FormWaypoint
• Status: active rewrite / WIP
• Stack: Turborepo, pnpm, Hono, React, TanStack Router, PostgreSQL/Neon, ParadeDB, Prisma, Zod, Python FastAPI
• Operational value: targets shipment-document conversion, OCR/prediction workflows, and searchable logistics records
• Engineering value: monorepo architecture, shared schema package, typed API/client boundary, vertical-slice backend organization

Production Expo/Supabase application for survivor-focused California legislation.

The app provides plain-language bill summaries, representative lookup, vote history, outreach tooling, localization, and privacy-conscious data flows.

• Live: https://www.ai-advocate.org/
• Repo: https://github.com/JoelA510/AIAdvocate
• Stack: Expo Router, React Native, Supabase, PostgreSQL, Edge Functions, pg_cron, pgvector, i18next, OpenAI summaries
• Security/governance value: RLS-protected writes, RPC/edge-function mutation paths, no survivor-identifying information collected, documented operational runbooks
• Engineering value: scheduled ingestion, vote syncing, bilingual summarization, semantic search, verification SQL, release process documentation

Supabase-backed workflow platform for multi-phase planning, task management, role-based access, and safe schema evolution.

• Repo: https://github.com/JoelA510/PlanterPlan-Alpha
• Stack: React, TypeScript, Supabase, PostgreSQL, RLS, Vitest, Playwright
• Operational value: converts a complex multi-phase process into structured projects, phases, tasks, teams, dates, and reporting
• Engineering value: single-source-of-truth architecture docs, safe migration protocol, ADRs, testing strategy, and machine-readable agent context

I use AI-assisted development, but not as a substitute for architecture or review.

My usual pattern:

1. Define the operational workflow and failure modes.
2. Lock the schema, permissions, and data boundaries.
3. Generate or refactor code against explicit constraints.
4. Run type checks, tests, linting, and targeted verification scripts.
5. Review the result for security, maintainability, and real workflow fit.
6. Document the operational runbook and follow-up risks.

This matters because most of my projects sit near high-friction boundaries: physical operations vs. systems of record, public clients vs. protected data, automation speed vs. auditability, and AI-generated code vs. production reliability.

I am most aligned with roles that combine operations knowledge, systems thinking, reporting, and automation:

• Operations Analyst
• Logistics Analyst
• Business Systems Analyst
• Technical Operations Specialist
• ERP/WMS Analyst
• Inventory Control Analyst
• Quality / Hardware Lifecycle / RMA Coordinator
• IT Support / Junior Systems Administrator
• GRC Analyst or SOC Tier 1, when the role values operations/compliance background

• CompTIA Security+
• CompTIA A+
• ISC2 Certified in Cybersecurity (CC)
• AWS Certified Cloud Practitioner
• Google AI Essentials

This profile is not just a code sample archive.

It is evidence of a working pattern:

• understand the real operational workflow
• model the data cleanly
• automate the repetitive parts
• protect sensitive boundaries
• test what can fail
• document how to operate and recover the system