Intelletto.ai - Sidecar Lens (Candidate Dashboard)

Candidate: John Paolo G. Jamon

Principal Software Engineer / Technical Lead Node.js / Nest.js • Java / Grails • KYC & Payments • Open Finance • Kafka 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%

After Data Fusion enrichment incl. FB identity

Confidence

0.91

Model certainty (0 to 1)

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

John 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 — John 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.” John 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. John’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 John 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. John’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. John 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. John 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 — Hard and Soft Skills

Green = in JD and candidate, Blue = candidate only, Red = in JD but missing/weak in candidate

JD proficiency: FND WRK PRO ADV EXP

All skills from JD and candidate are shown as pills. Color shows source/coverage: Green = in JD and candidate, Blue = candidate only, Red = in JD but missing/weak in candidate. Columns below are by skill type (Hard vs Soft).

Hard Skills

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

Soft Skills

Technical communication Collaboration with product / ops Problem solving in regulated environments Technical lead / principal-level ownership Running large UI/front-end chapters Publishing principal-level patterns Vendor / partner coordination

Use red pills as interview probes; use blue pills to highlight candidate’s additional value not requested in the JD.

Data Fusion

Single candidate view built from multiple artifacts (resume versions, public profiles, recommendations, internal system data) with normalization and trust scoring — so Intelletto.ai reviewers see one clean record, not five partial ones.

Unified Candidate

Merged Original Resume, Parsed Resume, and LinkedIn 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).

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 — sources agree on identity, career arc, and fintech scope.

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: one reliable candidate object that downstream scoring (JD alignment, skills pills, culture heatmap) can consume without re-parsing.

Why this score?

JD Alignment (weight 0.30): High match on secure, API-first fintech/open-finance delivery — Node.js/Nest.js, Java/Grails, payments/KYC.
Integration & secure attach (weight 0.20): John has already integrated to bank/KYC/payment services with strict payloads and auditing.
Data Fusion Completeness (weight 0.15): 92% Completeness Index. 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.
AI/search, GraphQL (weight 0.10): The JD requires these; John’s sources do not explicitly show them, so we add them as “uplift via Intelletto onboarding” rather than full credit.
Verification penalty (weight -0.10): Deduction to signal to the HM that we must probe GraphQL and multi-tenant isolation.

Methodology: weighted blend aligned to Intelletto.ai values; signals fused from resume, public profiles, and recommendations; confidence upweighted by cross-source agreement.

Culture Fit at Intelletto.ai

Sidecar-first delivery - 93/100 secure services payments
Secure integrations - 95/100 tokens auditing
Engineering standards - 92/100 patterns contracts
Product collaboration - 90/100 boundaries payloads
AI/search uplift - 88/100 open search explainability
Regional delivery fit - 93/100 fintech PH based

Comparator - Principal Developer (Intelletto.ai)

Non-negotiables

Node.js / Nest.js or Java / Grails services; microservices; secure, gateway-protected integrations; willingness to adopt Intelletto’s AI/search conventions.

Preferred

Attach/sidecar modules beside existing systems (HRIS/ATS/CRM/fintech); event-driven delivery on Kafka.

Gap prompts

Concrete examples of AI explainability panels, OpenSearch/vector implementations, GraphQL gateway/federation, and enforcement of secure multi-tenant API rules.

External Signals

LinkedIn: Confirms principal/senior software engineer profile, PH location, and fintech/open-finance stack.
Facebook: Identity and geography check only; do not use for automated scoring.
Intelletto candidate artifacts: Original resume and parsed resume confirm employers, dates, Node/Nest + Java/Grails stack, and payments/KYC work.

Recruiter Timeline

Today

Moved to Longlist – Principal Developer (Jamon) after dashboard refresh.

-1d

Recruiter discussion completed; candidate confirmed Node.js/Nest.js, Java/Grails, payments/KYC.

-2d

Data Fusion pass completed; single candidate view generated; trust set to High.

-3d

JD Alignment rewritten to “Principal Developer (Intelletto.ai) — John Paolo G. Jamon”.

-5d

Candidate sourced/ingested into pipeline for Principal Developer role.

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 & modernization: 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.
Principal-level behaviours: can define payloads/contracts that frontend teams will consume; used to documenting integration steps and operational considerations (latency, retries, partner SLAs).
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).
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.
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.

Additional Notes

Add dated recruiter notes. Stored locally in your browser for this candidate dashboard.

New note