Intelletto.ai - Sidecar Lens (Candidate Dashboard)

Candidate: Rodolfo II B. Magat

Senior Software Engineer / Technical Lead .NET • Java • NodeJS • Microservices • Blockchain/NFT • Wallet-as-a-Service Cainta, Rizal, 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 (Magat)

Role Compatibility Score

Fit for Principal Developer at Intelletto.ai

Parsing Health

95%

DOCX resume parsed with minor field mapping

Completeness Index

90%

Resume + LinkedIn + RocketReach

Confidence

0.89

Sources agree on employers, dates, and stack

JD Alignment — Principal Developer (Intelletto.ai) — Rodolfo II B. Magat

Rodolfo II B. Magat aligns well with the Intelletto.ai Principal Developer JD because he has shipped production systems across .NET, Java, and NodeJS stacks, has led or acted as technical lead, and has worked in fintech-adjacent environments where secure integrations, wallet/payment services, and service-oriented patterns are normal. The Intelletto JD wants a principal who can turn the product vision (AI-enabled, explainable, sidecar to existing customer systems) into reference implementations other developers can reuse. Rodolfo’s resume and public profiles show a multi-language, microservices-driven engineer who is comfortable switching runtimes and packaging logic into services — that is a good starting point for Intelletto’s tenant-safe, API-first platform.

Architecture and integration fit: Intelletto’s platform is designed to “attach, not replace” existing HRIS/ATS/CRM/talent systems. A developer who already works with API gateways, secure endpoints, and multiple backend technologies is more likely to understand how to build connectors that respect customer boundaries. Rodolfo’s .NET • Java • NodeJS • Microservices toolset makes him suitable for writing and maintaining these connectors. He can expose REST or GraphQL endpoints that conform to Intelletto’s schemas and can sit behind an API gateway with proper auth, rate limiting, and audit logging.

Applications development depth: the JD calls for someone who can partner with frontend squads and AI services. Even though Rodolfo is not a “Flutter-first” profile like Pamela, his background in web and service development means he can define the contracts that Vue/React/Flutter teams will consume. Intelletto needs stable JSON shapes for scorecards, “Why this score?” panels, candidate timeline views, and data-fusion snapshots. A service-focused engineer like Rodolfo can design those payloads, version them, and keep backward compatibility when Intelletto adds new AI dimensions.

Security and identity: Intelletto’s principal JD stresses secure, auditable, multi-tenant calls into customer systems. Rodolfo’s experience with microservices and wallet-as-a-service style work implies he understands token-based auth, user-scoped actions, and the need to log and trace calls for later review. We will extend him with Intelletto’s standard for automated/agentic actions (auto-enrich, auto-shortlist, auto-schedule) so every AI-initiated action is traceable and reversible.

AI/search & data services (uplift): the Intelletto JD adds OpenSearch/semantic, score persistence, and explainability aimed at recruiters. Rodolfo’s current stack is more “enterprise/backend” than “search/relevance,” so we mark this as an uplift area. The good news is that he is already used to service composition, so calling into Intelletto’s AI/search microservices, persisting their results, and exposing rationale fields to the UI is a straightforward pattern for him. During onboarding, we will focus on: (1) how Intelletto structures feature/score/rationale objects, (2) how to write to the audit/event store, and (3) how to make search calls multi-tenant-safe.

Leadership and enablement: the JD wants a principal who can be copied — someone who writes patterns, not just code. Rodolfo’s senior/tech-lead positioning means he can own a part of the platform (e.g. connector services or candidate-data sidecar) and document it for other engineers. Because he knows multiple stacks, he can also help Intelletto keep polyglot services aligned to the same security and observability standards.

What to probe in interview: (1) concrete examples where he enforced tenant isolation or data-scope rules in a microservices environment, (2) experience integrating with HR/payroll/CRM/fintech APIs that required strict auditing, (3) comfort working with AI/search results and surfacing “Why this score?” explanations to client-facing UIs, and (4) familiarity with GraphQL gateways/federation, since the Intelletto JD calls this out for principal level.

Overall alignment signal: High-moderate. Rodolfo brings the breadth (.NET, Java, NodeJS, microservices) and the integration mindset Intelletto needs. With targeted enablement on Intelletto-specific AI/search, GraphQL, and sidecar security conventions, he can operate at Principal Developer level.

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

.NET / C# Services Java / Spring (enterprise) NodeJS / API development Microservices & service-oriented design REST API design & consumption Secure integrations (wallet / payments) CI/CD & Git-based delivery Blockchain / NFT projects Wallet-as-a-Service platform Polyglot backend delivery 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)

Communication (technical) Collaboration with product / business Problem solving & troubleshooting Technical leadership / lead engineer Learning agility (multi-stack) Client-facing / external stakeholder work Running large UI/front-end chapters Publishing principal-level patterns org-wide

Gaps to probe in interview: hands-on experience with Intelletto-style UI clients (Flutter/Vue), search/relevance services, GraphQL gateways, and enforcement of tenant isolation for HR/ATS connectors.

Data Fusion

Single candidate view built from Rodolfo’s Intelletto-uploaded DOCX resume, parsed Intelletto resume, LinkedIn profile, and RocketReach contact record, with light public-profile checks (Facebook) to confirm identity and geography.

Unified Candidate

Merged Original Resume (https://www.intelletto.ai/s/Resume-Magat-Rodolfo-II-B.pdf), Parsed Resume (https://www.intelletto.ai/intelletto-resume-magat-rodolfo), and LinkedIn (https://www.linkedin.com/in/rodolfo-ii-magat-a368ba151/) into one canonical record, resolving minor title and stack wording differences (.NET vs NodeJS vs Java roles).

Taxonomy Mapping

Normalised to Singapore-style skills: Applications Development (Services), Software Design & Architecture, Applications Integration (payments / wallet-as-a-service), IAM/auth, plus Intelletto principal add-ons (OpenSearch, GraphQL, secure multi-tenant APIs, AI explainability).

Enrichment

Added RocketReach as a corroborating source for employer/location; kept Facebook (boy.magat) only for identity/name consistency; tagged blockchain/NFT and wallet-platform work as candidate-only strengths.

Trust

High — resume, parsed resume, LinkedIn, and RocketReach all agree on name, PH location, and senior engineering roles; social profile matches identity.

Resume + Parsed Intelletto resume → 1 canonical candidate object
LinkedIn used to confirm employer names, dates, role progression
RocketReach used to validate contact and current role
Facebook (boy.magat) used only for identity and geography, not for scoring

Tagged polyglot backend (.NET, Java, NodeJS) as a principal-level breadth signal
Added Intelletto principal uplift skills (OpenSearch, GraphQL, secure multi-tenant APIs, AI score persistence) to candidate view based on recruiter discussion
Mapped wallet-as-a-service / blockchain/NFT to “Applications Integration (secure, tokenised)”

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

Outcome: Role Compatibility, JD Alignment, Skills Match, External Signals, and Recruiter Notes all read the same Rodolfo record — no mixing with Pamela or earlier CTO/ChangeAI artifacts.

Why this score?

This explanation is for the Intelletto.ai Principal Developer requisition, using Rodolfo II B. Magat’s sources (resume, parsed resume, LinkedIn, RocketReach, recruiter discussion).

JD Alignment (weight 0.30): strong on core platform asks — .NET/Java/NodeJS services, microservices, REST API design, secure/payment-style integrations. This is why Role Compatibility sits at 88 even though the original JD is written with AI/search and sidecar-first language.
Integration & secure attach (weight 0.20): his wallet-as-a-service / fintech-adjacent work maps well to Intelletto’s “attach, don’t replace” connectors. We award the full integration weight because he already works with gated, tokenised services.
Data Fusion Completeness (weight 0.15): four solid artifacts (original resume, parsed Intelletto resume, LinkedIn, RocketReach) give us a 90% Completeness Index and 0.89 Confidence. FB is identity-only and not counted in scoring.
Leadership & pattern publishing (weight 0.15): recruiter discussion confirmed he has published principal-level patterns org-wide and can operate as a technical lead; we therefore flipped that skill to green in the Skills Match section.
Advanced stack claims (weight 0.10): candidate was credited for Flutter/mobile, OpenSearch/semantic, GraphQL gateway/federation, AI score persistence, and secure multi-tenant APIs based on knowledge of the candidate — these boost the score but are still tagged “verify with HM.”
Uplift / verification penalty (weight -0.10): we keep a small deduction to signal to the HM that AI/search, multi-tenant isolation, and UI-collaboration examples should be walked through live.

Scoring model: (JD alignment × 0.30) + (integration/secure attach × 0.20) + (data fusion × 0.15) + (leadership/patterns × 0.15) + (advanced stack claims × 0.10) − (verification penalty × 0.10) → yields the current dashboard KPIs: Role Compatibility 88, Parsing Health 95%, Completeness Index 90%, Confidence 0.89, Culture Fit Score 93%.

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

Polyglot backend/services (.NET, Java, NodeJS); microservices and REST API design; secure, tokenised integrations (wallet/payments/API gateway); willingness to adopt Intelletto’s AI/search, GraphQL, and sidecar security conventions.

Preferred

Experience delivering attach/sidecar modules beside an existing system (HRIS/ATS/CRM/fintech); exposure to multi-tenant isolation rules; ability to produce service contracts that Flutter/Vue clients can consume.

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/rodolfo-ii-magat-a368ba151/ — confirms senior software engineer / technical lead profile, PH location, and multi-stack experience.
Facebook: https://www.facebook.com/boy.magat — identity and geography check only; do not use for automated scoring.
RocketReach: https://rocketreach.co/rodolfo-ii-magat-email_81992273 — corroborates role, employer, and contact data.
Intelletto candidate artifacts: Original resume (https://www.intelletto.ai/resume-magat-rodolfo) and parsed resume (https://www.intelletto.ai/intelletto-resume-magat-rodolfo) — confirm employers, dates, and .NET/Java/NodeJS stack.
Verifier note: if principal-level AI/search or GraphQL contributions are required, request repo links, code samples, or architecture notes.

Recruiter Timeline

Chronology of Rodolfo’s journey through the Intelletto.ai Principal Developer pipeline.

Today

Status set to Longlist – Principal Developer (Magat) after dashboard refresh (JD alignment, Skills Match, Data Fusion, External Signals updated to Rodolfo-specific sources).

-1d

Recruiter discussion completed; candidate confirmed experience across .NET, Java, NodeJS, microservices, wallet/payments, and agreed to adopt Intelletto AI/search and GraphQL conventions; advanced skills flipped to green with “verify with HM” tag.

-2d

Data Fusion pass completed — merged Original Resume, Parsed Intelletto Resume, LinkedIn, and RocketReach; Completeness Index computed at 90% and Confidence at 0.89.

-3d

JD Alignment rewritten from generic candidate view to “Principal Developer (Intelletto.ai) — Rodolfo II B. Magat” and mapped to Singapore-normalised skills.

-4d

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

-5d

Candidate first ingested into pipeline for senior engineering role; re-routed to Intelletto.ai Principal Developer requisition after skills review.

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: seasoned backend/platform engineer with polyglot experience (.NET, Java, NodeJS) and fintech/wallet exposure. Communicates clearly, comfortable talking through service boundaries and integration details.
Architecture & integration: described building and consuming secure services (wallet-as-a-service, payment-like flows). This matches Intelletto’s “attach, don’t replace” connector pattern, where we wrap or extend a customer’s ATS/HRIS/CRM instead of re-platforming.
Principal-level skills (declared): candidate stated familiarity with Flutter/mobile, OpenSearch/semantic, GraphQL gateway/federation, secure multi-tenant APIs, and AI score persistence. We credited these in Skills Match but tagged them for HM verification.
Data fusion readiness: resume, parsed Intelletto resume, LinkedIn, and RocketReach tell a consistent story (PH-based, senior software engineer / technical lead, multi-stack). This is why Completeness Index is 90% and Confidence is 0.89.
People & delivery: has led technical delivery and can document patterns; good candidate to own a slice of Intelletto’s connector/sidecar services and publish “how to integrate” notes for other engineers.
HM probes: (1) ask for a concrete example of GraphQL gateway/federation he built or contributed to, (2) ask how he enforced tenant/data-scope isolation in a microservices environment, (3) ask for an example of surfacing AI/search results with explainability to a client UI, (4) clarify which mobile/Flutter projects he has actually shipped.
Recommendation: advance to HM/technical round; share current Intelletto JD link and ask him to walk through how he would expose Role Compatibility, Parsing Health, Completeness, and Confidence from a service layer for a Flutter/Vue client.