Joshua Valle

I turn messy operational problems into usable systems

My work spans AI implementation, workflow automation, and full-stack development, from mapping the problem and defining requirements through testing, rollout, and support

2019–2026

Experience

Six roles across technical support, data, development, and AI delivery.

Time in role

AJAIA

Technical Project Manager, AI Implementation & Delivery

Apr 2026–Present

Supported AI implementation, product rollout, and workflow automation across client-facing and internal projects.

Work included

  • Discovery, requirements, and workflow mapping
  • QA, deployment planning, and launch readiness
  • Onboarding, access, and support workflows
  • Implementation documentation and rollout playbooks
  • Stakeholder communication and blocker resolution

What I did

  • Worked across stakeholders, product, operations, and engineering to translate workflows, feedback, support issues, and implementation ambiguity into requirements, rollout plans, QA checks, and source-backed project updates.
  • Coordinated implementation work across discovery, requirements, workflow mapping, solution design, testing, deployment planning, launch readiness, and post-deployment support.
  • Supported onboarding, access provisioning, SSO planning, pilot coordination, usage visibility, monitoring, support paths, and rollout readiness.
  • Built onboarding guides, implementation documentation, technical follow-ups, project trackers, meeting archives, knowledge-base content, and scalable rollout playbooks.
  • Partnered with clients, executives, operators, product managers, and engineers to prioritize work, resolve blockers, and improve deployment quality.

All experience

Roles, dates, and organizations at a glance.

Selected work

From requirements to rollout

I help move implementation work from an unclear operational problem to a tested release, keeping requirements, owners, blockers, and evidence clear along the way.

01 / 05

Understand the work before prescribing the software

I trace who is involved, which systems are already in the path, where the handoff breaks, and which constraints cannot be ignored. The goal is a problem statement narrow enough to act on.

  • Current pathPeople, systems, source material, and handoffs as they exist today.
  • ConstraintsAccess, policy, timing, ownership, and technical limits surfaced early.
  • Decision recordConfirmed facts separated from assumptions and open questions.
Inside the delivery work
Selected step Discovery

This view follows the step selected above

The question
What is happening now, where does the handoff break, and which constraints are real?
What I kept visible
People, systems, source material, access limits, confirmed facts, assumptions, and open questions.
What moved forward
A narrow problem statement, the right owners, and a clear next investigation or decision.

Web and workflow automation for small businesses

Through Business Solutions Agency, I build websites and connected workflows for small businesses, joining the customer-facing experience to the operational steps behind it.

How I approach the work

  1. 01
    Map the work

    Trace the existing path, the owner at each handoff, and the friction worth solving.

  2. 02
    Choose the connection

    Use the smallest dependable mix of native tools, APIs, webhooks, and custom code.

  3. 03
    Test the full path

    Check validation, notifications, failure states, ownership, and what happens next.

  4. 04
    Launch and support

    Document the workflow, watch the first real use, and improve what the evidence shows.

More about the work
The need
Lean client projects where the public website and the work behind it needed to function as one maintainable system.
What I owned
Co-founder and lead developer. I handle discovery, scoping, implementation, testing, launch, and iteration with business owners.
How I built it
Websites and intake paths connected to the CMS, CRM, API, webhook, reporting, or support tools the workflow actually needs.
What it produced
Built maintainable paths between public touchpoints and the operational tools behind them.

What I handled

  • Public sites and landing pages connected to intake, CRM, scheduling, email, payment, or support tools.
  • Automations for lead capture, outreach, order processing, reporting, data movement, and internal handoffs.
  • API, webhook, and native-integration paths selected for maintainability rather than novelty.
  • Validation, failure paths, notifications, ownership, and recovery checked before launch.
  • Plain-language workflow documentation, launch support, and post-launch iteration.
  • APIs
  • Webhooks
  • CMS/CRM workflows
  • JavaScript
  • Python

Vehicle telemetry over CAN bus

Lexus capstone setup with a laptop, cabling, and OBD hardware Carloop and OBD hardware connected inside the vehicle
The real laptop, cabling, and OBD hardware used for the capstone.
01 / 05
Actual setup

The real laptop, cabling, and OBD hardware used inside the Lexus

Swipe to see all views

View the Arcadia capstone record

More about the work
The need
Arcadia University capstone investigating a web-based path for collecting and analyzing vehicle electrical-system data.
What I owned
I developed the Particle C++ firmware, handled OBD-II request and response processing, connected the cloud data path, and built the dashboard presentation.
How I built it
2016 Lexus / Vehicle HS CAN → OBD-II and Carloop → local Wi-Fi → Particle Cloud integration → InfluxDB on a cloud VM → Grafana.
What it produced
Collected OBD-II readings such as RPM, vehicle speed, engine load, fuel-level input, and coolant temperature. Recovered artifacts visibly show RPM, speed, and engine load in Grafana during a recorded drive, while source and console materials document the additional readings.

What I handled

  • Requested standard OBD-II PIDs and processed ECU responses in C++.
  • Sent readings through Carloop and Particle Cloud into InfluxDB.
  • Visualized RPM, vehicle speed, and engine load in the recovered Grafana dashboard during a recorded driving session.
  • Built and tested the full path across in-vehicle hardware, cloud services, storage, and visualization.
  • Preserved the original setup, console output, architecture, dashboard, and recorded-drive evidence shown here.
  • C++
  • OBD-II / CAN bus
  • Carloop
  • Particle Cloud
  • InfluxDB
  • Grafana

Computer vision studies

Two Python studies focused on face similarity and image-to-text extraction, including preprocessing, model integration, validation, and failure handling.

Face similarity
  1. Webcam
  2. Preprocess
  3. Embed
  4. Compare
  5. Rank
Image to text
  1. Scan
  2. Preprocess
  3. OCR
  4. Parse
  5. Review
Face similarity study
Webcam frames become embeddings and are ranked against a small image set using cosine similarity.
Image-to-text study
OpenCV preprocessing and Tesseract OCR extract contact details from scanned-card images.
What I focused on
Input cleanup, failed detections, model integration, validation, and readable output.
More about the work
The need
Personal studies focused on how computer-vision pipelines handle real inputs, failed detections, and noisy images.
What I owned
Input handling, preprocessing, model integration, validation, and result presentation across two study paths.
How I built it
Python, OpenCV, NumPy, DeepFace / FaceNet, scikit-learn, Pillow, and Tesseract OCR.
What it produced
The source covers two complete processing paths: ranking face similarity from webcam frames and extracting contact details from scanned-card images.

What I handled

  • Worked with image files and webcam frames through Python and OpenCV.
  • Generated FaceNet embeddings and compared them with cosine similarity.
  • Handled missing faces, invalid inputs, and other failure paths instead of assuming a clean result.
  • Used OpenCV preprocessing and Tesseract OCR in a separate image-to-text workflow.
  • Documented failure cases separately from successful outputs so the behavior could be reviewed.
  • Python
  • OpenCV
  • NumPy
  • DeepFace / FaceNet
  • Tesseract OCR
  • Data validation
  • Model testing

Skills and tools

  • BuildJavaScript · HTML/CSS · Python · C++
  • ConnectAPIs · Webhooks · CMS/CRM · Particle Cloud
  • Data & visionOpenCV · NumPy · InfluxDB · Grafana
  • ShipGit · Jekyll · GitHub Pages · QA

Web & integration

Interfaces and integrations built around the workflow they need to support.

Used inClient systems, workflow automation, and this portfolio

  • JavaScript, HTML & CSSInteractive websites and browser-based experiences.
  • APIs & webhooksBusiness-system and workflow integrations.
  • CMS/CRM workflowsWebsites, intake paths, content operations, and customer records.
  • Jekyll & GitHub PagesThe static-site and deployment foundation used for this portfolio.
  • GitSource control, isolated branches, and preview workflows.

Education and certifications

Learning that supports the work

Education

Bachelor’s degree in Computer Science

Arcadia University

Completed 2023

Certifications

Claude Certified Architect — Foundations

Anthropic

Issued Jun 2026 · Expires Dec 2026

Building with Claude

Anthropic

Issued Apr 2026

Claude Code in Action

Anthropic

Issued Apr 2026

Contact

Get in touch.

Email me about a role or project.

Submissions use Formspree.