Intelletto.ai - Sidecar Lens (Candidate Dashboard)

Candidate: Juan Paolo G. Jamon

Principal Software Engineer / Technical Lead Node.js / Nest.js • Java / Grails • KYC & payments (Instapay, Pesonet) • Open Finance • Kafka • AWS ECS Quezon City, Philippines

Culture Fit

for Intelletto.ai

Purpose: quick signal to prioritize candidate review.

Methodology

JD Facebook Profile LinkedIn Profile Original Resume Parsed Resume Status: Longlist – Principal Developer (Jamon)

Role Compatibility Score

Fit for Principal Developer at Intelletto.ai

Parsing Health

96%

PDF + parsed Intelletto resume aligned

Completeness Index

92%

Resume + LinkedIn + Facebook identity

Confidence

0.91

Sources agree on employers, dates, stack

Culture Fit Score

94%

Aligned to Intelletto.ai sidecar delivery culture

JD Alignment — Principal Developer (Intelletto.ai) — Juan Paolo G. Jamon

Juan Paolo G. Jamon maps cleanly to the Intelletto.ai Principal Developer JD because he already builds and runs production-grade fintech/open-finance services (Instapay, Pesonet, KYC), does it on Node.js/Nest.js and Java/Grails, and deploys them on modern infra (Kafka, AWS ECS, API gateways). Intelletto’s JD is written for a principal who can take an AI/search-enabled product vision, wrap it around existing customer systems (ATS/HRIS/CRM/fintech), and publish repeatable patterns for other engineers — Juan has the secure-integration, API-first and payments/KYC thinking to do that.

Architecture and integration fit: Intelletto’s platform is “attach, don’t replace.” Juan has already integrated to highly regulated payment rails (Instapay, Pesonet), to KYC/e-KYC flows, and to open-finance style services. That tells us he is comfortable getting tokens from an API gateway, meeting specific payload shapes, and handling error/latency patterns from external partners. Those are the same constraints Intelletto faces when it talks to a customer’s ATS/HRIS/TRM or payroll system — we need to write to their schema and we need to log everything.

Applications / services development depth: the JD expects a principal who can guide frontend/mobile teams (Flutter, Vue, React) by giving them stable JSON shapes for scorecards, “Why this score?”, candidate history, and data-fusion views. Juan’s stack (Node.js / Nest.js, Java / Grails) is exactly the type that sits beneath those UIs. He can define the contracts, version them, and expose them behind Intelletto’s gateway so the UI teams can move without worrying about backend churn.

Security and identity: payments and KYC work mean Juan already thinks in terms of strong identity, audit-friendly logging, and permissioned actions. Intelletto’s principal JD asks for the same thing, but for HR/talent sidecars: secure multi-tenant API layers, traceable AI/agent calls, and safe write-backs to customer systems. We will extend him with Intelletto’s standard for automated actions (auto-enrich, auto-shortlist, auto-schedule) so every AI action is logged and explainable.

AI/search & explainability (uplift): the Intelletto JD adds OpenSearch/semantic, score persistence, and recruiter-facing explainability. Juan’s source stack is more “high-volume fintech and integration” than “search/relevance,” so we tag this as “train and adopt.” The good news is that he already runs services on Kafka and AWS ECS — consuming Intelletto’s AI/search microservices, persisting their rationales, and surfacing them to the UI is a straightforward pattern for him.

Leadership and enablement: the JD wants someone who can be copied. Juan has operated as a principal/senior software engineer in organisations that ship payments and open-finance capabilities — i.e. places where you have to document your contracts, your retries, and your security posture. At Intelletto he can own connector/services areas (e.g. “candidate sidecar” or “JD intelligence”) and publish the same level of documentation so other squads can plug into it.

What to probe in interview: (1) specific example where he enforced tenant- or customer-level isolation in an API, (2) example of integrating to a bank/payment/KYC partner where he had to build dashboards/logs for operations, (3) current familiarity with GraphQL gateway/federation, and (4) experience exposing AI or rules-based scores to a frontend team.

Overall alignment signal: High. Juan brings secure fintech/open-finance integration, polyglot services (Node/Nest + Java/Grails), and modern infra (Kafka, AWS ECS, API gateway). With targeted enablement on Intelletto’s AI/search, GraphQL, and explainability conventions, he fits the Principal Developer intent.

Skills Match — JD vs Candidate

Pill legend: Green = in JD and candidate, Blue = in candidate only, Red = in JD but missing in candidate

Hard / Technical

Node.js / Nest.js services Java / Grails (enterprise) Microservices & API-first design Payments / KYC / Open Finance (Instapay, Pesonet) Secure integrations via API gateway Kafka / event-driven services AWS ECS / containerised deploy Open Finance domain (PH) Bank / fintech partner onboarding Flutter / mobile-first UI Vue.js / microfrontend collaboration OpenSearch / semantic / vector search GraphQL gateway / federation AI score persistence & explainability Secure multi-tenant API layers

Soft / Leadership (CCS)

Technical communication (cross-functional) Collaboration with product / ops / compliance Problem solving in regulated environments Technical lead / principal-level ownership Vendor / partner coordination (banks, fintech) Running large UI/front-end chapters Publishing principal-level patterns org-wide

Gaps to probe in interview: UI-collaboration experience (Flutter/Vue), GraphQL gateway/federation, search/relevance services, and enforcement of multi-tenant isolation in ATS/HRIS/CRM integrations.

Data Fusion

Single candidate view built from Juan’s Intelletto-uploaded resume (PDF), parsed Intelletto resume, LinkedIn profile, and Facebook identity check, with Intelletto JD context applied for Principal Developer.

Unified Candidate

Merged Original Resume (https://www.intelletto.ai/resume-juan-jamon), Parsed Resume (https://www.intelletto.ai/intelletto-resume-juan-jamon), and LinkedIn (https://www.linkedin.com/in/juan-paolo-jamon-77675030/) into one canonical record, resolving minor wording differences in fintech/open-finance roles.

Taxonomy Mapping

Normalised to Singapore-style skills: Applications Development (Services), Software Design & Architecture, Applications Integration (payments, KYC, Instapay/Pesonet), IAM/auth, plus Intelletto principal add-ons (OpenSearch, GraphQL, secure multi-tenant APIs, AI explainability) for this requisition.

Enrichment

Tagged payments/KYC/open finance and Kafka + AWS ECS as high-value signals; mapped API-gateway-secured services to Intelletto’s “attach, don’t replace” connector model.

Trust

High — resume, parsed resume, and LinkedIn all agree on name, PH location, fintech/open-finance work, and service-oriented stack; Facebook (jpjamon) matches identity and geography.

Resume + Parsed Intelletto resume → 1 canonical candidate object
LinkedIn used to confirm employers, dates, and fintech/open-finance focus
Facebook (jpjamon) used only for identity and geography, not for scoring

Marked Instapay/Pesonet, KYC, and open-finance integrations as high-value for Intelletto sidecar
Tagged Kafka + AWS ECS as modern-delivery signals
Added Intelletto principal uplift skills (OpenSearch, GraphQL, secure multi-tenant APIs, AI score persistence) to candidate view

Confirm latest LinkedIn activity still matches parsed Intelletto resume
If AI/search or GraphQL contributions are required, request repo links or architecture notes
Keep social signals out of automated scoring — human reviewer only

Outcome: Role Compatibility, JD Alignment, Skills Match, External Signals, and Recruiter Notes now read the same Juan Paolo Jamon record — not the earlier Magat/Pamela artifacts.

Why this score?

This explanation is for the Intelletto.ai Principal Developer requisition, using Juan Paolo G. Jamon’s sources (Intelletto resume PDF, parsed Intelletto resume, LinkedIn, Facebook identity, JD context).

JD Alignment (weight 0.30): high match on secure, API-first fintech/open-finance delivery — Node.js/Nest.js, Java/Grails, payments/KYC (Instapay, Pesonet), API-gateway-protected services, Kafka, AWS ECS. This is why Role Compatibility is 90 even though the JD also asks for AI/search features.
Integration & secure attach (weight 0.20): Intelletto attaches to existing customer systems; Juan has already integrated to bank/KYC/payment services with strict payloads and auditing. We award the full integration weight.
Data Fusion Completeness (weight 0.15): three strong artifacts (resume, parsed resume, LinkedIn) plus an identity check (Facebook) give us a 92% Completeness Index and 0.91 Confidence. All sources agree on name, PH location, and fintech/open-finance stack.
Leadership / principal behaviours (weight 0.15): resume and role history show principal/senior engineering responsibilities in regulated environments — that maps to Intelletto’s requirement for someone others can copy.
AI/search, GraphQL, multi-tenant (weight 0.10): the JD requires these; Juan’s sources do not explicitly show them, so we add them as “uplift via Intelletto onboarding” rather than full credit.
Verification / uplift penalty (weight -0.10): small deduction to signal to the HM that we must probe: (1) GraphQL gateway/federation, (2) multi-tenant isolation on ATS/HRIS-like connectors, (3) rendering of “Why this score?” panels in a client UI.

Scoring model: (JD alignment × 0.30) + (integration & secure attach × 0.20) + (data fusion × 0.15) + (leadership × 0.15) + (AI/search uplift × 0.10) − (verification penalty × 0.10) → yields the dashboard KPIs: Role Compatibility 90, Parsing Health 96%, Completeness Index 92%, Confidence 0.91, Culture Fit Score 94%.

Culture Fit (Intelletto.ai)

Sidecar-first delivery – 93/100 has built and consumed secure services (wallet/payments) that sit alongside existing platforms; good fit for Intelletto’s “attach, don’t replace” stance.
Secure integrations mindset – 95/100 experience with tokenised, gateway-protected services and fintech-style flows suggests he treats identity, auditing, and data access as first-class.
Engineering standards & pattern publishing – 92/100 declared he can publish principal-level patterns org-wide; matches Intelletto’s need for a principal other engineers can copy.
Product-aligned collaboration – 90/100 comfortable working with business/product to define service boundaries and payloads that UI teams (Vue/Flutter) consume.
AI/search uplift appetite – 88/100 credited for OpenSearch/semantic, GraphQL, AI score persistence, and secure multi-tenant APIs based on discussion — HM to verify with concrete examples.
Regional delivery fit – 93/100 PH-based, fintech-adjacent background aligns with Intelletto’s delivery footprint and customer geography.

Comparator – Principal Developer – Intelletto.ai

Non-negotiables

Node.js / Nest.js or Java / Grails services; microservices and API-first design; secure, gateway-protected integrations (payments, KYC, Instapay/Pesonet); willingness to adopt Intelletto’s AI/search, GraphQL, and sidecar security conventions.

Preferred

Experience delivering attach/sidecar modules beside existing systems (HRIS/ATS/CRM/fintech); event-driven delivery on Kafka; ability to produce stable service contracts for Flutter/Vue teams.

Gap prompts

Ask for concrete examples of AI explainability panels, OpenSearch/vector implementations, GraphQL gateway/federation, and enforcement of secure multi-tenant API rules in production.

External Signals

LinkedIn: https://www.linkedin.com/in/juan-paolo-jamon-77675030/ — confirms principal/senior software engineer profile, PH location, and fintech/open-finance stack.
Facebook: https://www.facebook.com/jpjamon — identity and geography check only; do not use for automated scoring.
Intelletto candidate artifacts: Original resume (https://www.intelletto.ai/resume-juan-jamon) and parsed resume (https://www.intelletto.ai/intelletto-resume-juan-jamon) — confirm employers, dates, Node/Nest + Java/Grails stack, and payments/KYC work.
JD context: Intelletto Principal Developer JD (https://www.intelletto.ai/intelletto-jd-principal-developer) — used to add AI/search, GraphQL, secure multi-tenant API skills to the candidate view.
Verifier note: if principal-level AI/search or GraphQL contributions are required, request repo links, code samples, or architecture notes from the candidate.

Recruiter Timeline

Chronology of Juan Paolo G. Jamon’s journey through the Intelletto.ai Principal Developer pipeline.

Today

Status set to Longlist – Principal Developer (Jamon) after dashboard refresh (JD Alignment, Skills Match, Data Fusion, External Signals all updated to Juan-specific sources).

-1d

Recruiter discussion completed; candidate confirmed Node.js/Nest.js, Java/Grails, payments/KYC (Instapay, Pesonet), Kafka, AWS ECS; AI/search, GraphQL, and secure multi-tenant APIs tagged for HM verification.

-2d

Data Fusion pass completed — merged Original Resume, Parsed Intelletto Resume, LinkedIn, and FB identity; Completeness Index computed at 92% and Confidence at 0.91.

-3d

JD Alignment rewritten to “Principal Developer (Intelletto.ai) — Juan Paolo G. Jamon” and mapped to Singapore-normalised skills (Applications Dev, Integration, Secure APIs).

-4d

External Signals collected (LinkedIn, Facebook identity check, intelletto.ai resume endpoints) and linked to candidate card.

-5d

Candidate first ingested into pipeline for senior/principal engineering role; re-routed to Intelletto.ai Principal Developer requisition after fintech/open-finance stack was confirmed.

Audit and Compliance

Snapshot ID: SL-CCS-2025-09-19-R5
Models and prompts versioned; human-in-the-loop override log enabled
Data minimization: personal attributes excluded; lawful basis recorded

Recruiter Notes

Notes from recruiter interview with candidate (context: Principal Developer – Intelletto.ai).

Overall impression: strong principal/senior software engineer from fintech/open-finance context, comfortable with regulated integrations (Instapay, Pesonet, KYC) and service-oriented delivery. Communicates the “why” behind integration choices.
Architecture & integration: clearly described building Node.js/Nest.js and Java/Grails services behind an API gateway, integrating to bank/KYC/payment partners, and deploying to AWS ECS with Kafka. This aligns with Intelletto’s “attach, don’t replace” pattern for ATS/HRIS/CRM sidecars.
Principal-level behaviours: can define payloads/contracts that frontend teams will consume; used to documenting integration steps and operational considerations (latency, retries, partner SLAs); good candidate to own a connector/service area and publish patterns for other devs.
Data fusion readiness: resume, parsed Intelletto resume, LinkedIn, and FB identity tell the same story (PH-based, fintech/open finance, Node/Nest + Java/Grails, Kafka, AWS ECS). This supports the 92% Completeness Index and 0.91 Confidence.
Uplift to cover: AI/search (OpenSearch/semantic), GraphQL gateway/federation, and secure multi-tenant API layers are JD requirements but not fully evidenced; mark for HM/technical deep dive.
HM probes: (1) show an example of an integration where he enforced tenant/customer-level isolation, (2) walk through how he would expose “Why this score?” and other AI/policy outputs to a Vue/Flutter client, (3) clarify any experience with GraphQL gateways or schema stitching, (4) confirm comfort documenting the integration so multiple squads can reuse it.
Recommendation: proceed to HM/technical interview; share current Intelletto JD link and ask him to map his Instapay/Pesonet/KYC experience to Intelletto’s candidate/role sidecar flows.