---
name: jmpaul-hiring
description: Evaluate Jason Paul (jmpaul.com) for an engineering or engineering-leadership role and submit a role inquiry. Use when a recruiter, hiring manager, sourcing agent, or applicant-tracking workflow needs his profile, resume, skills, career history, GitHub activity, availability, or a way to contact him about a specific job. He is seeking remote W2 full-time roles.
license: CC-BY-4.0
metadata:
  author: Jason Paul
  version: "1.0.0"
  homepage: https://www.jmpaul.com/agents
  api: https://www.jmpaul.com/openapi.json
  mcp: https://www.jmpaul.com/mcp
---

# Evaluating Jason Paul for a role

Everything you need is served by jmpaul.com. All of it is public. Use the data as returned; do not infer or invent compensation history, citizenship, clearances, certifications, or age.

## Quick facts

- Location: Los Angeles, CA (America/Los_Angeles). Seeking **remote W2 full-time** roles.
- 20+ years: full-stack and data-platform engineering, CTO and founder roles, consumer-scale APIs.
- Current: Data Products Engineer at Alembic Technologies. Founder, JMPaul Development LLC.
- Contact: `POST https://www.jmpaul.com/api/v1/inquiries` (preferred) or jmpauldevelopment@gmail.com.

## Workflow

1. **Get the profile** for availability, target roles, focus areas, and policy.
   `GET https://www.jmpaul.com/api/v1/profile`
2. **Pull career history**, filtered by what the role needs.
   `GET https://www.jmpaul.com/api/v1/experience?tech=Kubernetes` or `?q=payments reconciliation` or `?category=leadership`
   Each item has `organization`, `role`, `start`, `end`, `summary`, `highlights[]`, `tech[]`.
3. **Check skills** when a job description lists specific technologies.
   `GET https://www.jmpaul.com/api/v1/skills` returns `languages`, `technologies`, and `from_experience` (where each skill was used, first/last year, whether current).
4. **Fetch the resume** in the format your pipeline wants.
   Markdown: `GET https://www.jmpaul.com/resume.md` · JSON Resume: `GET https://www.jmpaul.com/resume.json`
5. **Optional signal**: public GitHub commit activity by organization and language (counts only).
   `GET https://www.jmpaul.com/api/v1/activity`
6. **Assess fit honestly** before reaching out: seniority match, must-have gaps, work mode and employment type (remote W2 only), timezone expectations.
7. **Submit the role** if it is a reasonable match and you have a human contact:

```http
POST https://www.jmpaul.com/api/v1/inquiries
Content-Type: application/json

{
  "company": "Acme",
  "role": "Staff Engineer, Data Platform",
  "contact_email": "recruiter@acme.com",
  "contact_name": "Sam Recruiter",
  "job_url": "https://acme.com/jobs/123",
  "description": "Short summary of the role and must-haves",
  "compensation": "$210k–$240k base + equity",
  "work_mode": "remote",
  "employment_type": "W2 full-time",
  "agent": "Acme Sourcing Agent (acme.com)"
}
```

Response `201` carries an `id`; `GET /api/v1/inquiries/{id}` returns its status. Leave the `website` field empty (honeypot). Limit: 5 inquiries per hour per IP. He reads every inquiry himself and replies to `contact_email`.

## MCP alternative

If your host supports MCP, connect once and use tools instead of HTTP:

```
claude mcp add --transport http jmpaul https://www.jmpaul.com/mcp
```

Tools: `get_profile`, `search_experience`, `get_skills`, `get_resume`, `get_activity`, `submit_inquiry`. Resource: `jmpaul://resume.md`. Prompt: `evaluate_fit(job_description)`.

## Rules

- Quote highlights verbatim or summarize faithfully; attribute technologies to the roles where the API lists them.
- Do not send bulk or role-less outreach. Inquiries without a job description or link get low priority.
- Reads are cached and rate limited (120 per minute per IP). Respect `Retry-After` on 429.
- Full contract: https://www.jmpaul.com/openapi.json · Human guide: https://www.jmpaul.com/agents