Installs
Interview Copilot Portfolio
Interview Copilot
Powered by a private knowledge graph — chronology-aware, no buzzwords, honest attribution.
Situation: A live hypothesis suggested recurring bugs might be caused by a deprecated API version used in the engineering stack.
Task: Use only source-backed evidence to explain the decision pattern or operating behavior behind the question.
Action: Retrieved Deprecated API suspicion [2024-11-20] (Private incident discussion); Metrics definition problem [2022-08-16] (Private analytics discussion) as the strongest supporting records.
Result: The answer stays bounded to observed chats, reports, and reflections instead of falling back to resume filler.
Installs
Cumulative GWP
NPS
Organic referral
Expertise Domains
Evidence Ledger
External feedback validated the honesty of the report and suggested softening downside language, not rewriting the substance.
The value was credibility, not polish. That is exactly the kind of evidence a recruiter AI layer should surface.
The hard part was correlating metrics with effort, incidents, and timing rather than just compiling numbers.
The portfolio needs to reflect causal reasoning, not vanity KPI recitation.
A funnel change was justified by observed movement into vehicle-add and comparison flows after reducing sign-up friction.
This is a concrete decision record driven by behavioral evidence.
Important metrics were not clearly defined across daily, weekly, monthly, and quarterly reporting cadences.
Instrumentation quality directly affected decision quality.
A live root-cause hypothesis pointed to integration-version debt behind recurring bugs.
The deployable portfolio should show that technical debt is named plainly and tied to consequences.
Higher costs were explained partly by reactivation effort after a period of product instability.
The business and product story should stay unified.
Challenges Overcome
Situation: The payment path was unstable enough that the team was discussing new gateways, dormant backups, iOS-specific removal, and flexible activation over multiple months.
Task: Keep conversion moving while reducing single-gateway dependency and avoiding a full commercial stall.
Action: Pushed for backup retention of Stripe, asked for gateway flexibility in backend endpoints, and kept product, backend, and sprint planning aligned around gateway activation and rollback choices.
Result: Migration moved through multiple gateways with fallback logic instead of a brittle one-shot cutover.
Situation: Core numbers were visible, but their definitions were not stable enough to support confident weekly, monthly, and quarterly decisions.
Task: Create a reporting system leadership could trust when discussing acquisition, conversion, and investor updates.
Action: Called out the metric-definition problem directly and reframed analytics around effort, events, and outcomes rather than KPI screenshots.
Result: Reporting became useful enough to share externally while staying evidence-led.
Situation: Several 2024 sprint notes show incomplete issues moving forward, BNM implementation delays, and active reprioritization.
Task: Keep delivery credible while acknowledging the gap between planned sprint goals and actual capacity.
Action: Used sprint review/planning cadence, adjusted timelines, and explicitly pushed lower-priority items out when current sprint obligations were more critical.
Result: Schedule pressure was handled transparently rather than hidden behind generic status language.
Decision Register
Mixpanel observations showed users progressed better when they reached value faster.
Decision: Reduce early onboarding friction by removing the sign-up page before users add a vehicle and compare options.
Tradeoff: Improves top-of-funnel movement but reduces immediate identity capture and some CRM structure.
Insurance checkout friction and financing constraints created a conversion ceiling.
Decision: Partner with a BNPL provider that can act as payment gateway and creditor on behalf of iLyF.
Tradeoff: Faster launch and regulatory leverage, with more partner dependency in a sensitive payment path.
Leadership needed clear weekly, monthly, and quarterly visibility, but instrumentation definitions were muddy.
Decision: Rework dashboards around critical business definitions instead of raw event dumps.
Tradeoff: Requires discipline and maintenance, but improves trust in reporting.
App issues, errors, and user complaints were distributed across weakly connected touchpoints.
Decision: Centralize issues, errors, bugs, and user complaints into one channel for triage.
Tradeoff: Improves visibility but can become noisy unless ownership is explicit.
Debt Register
The analytics layer captured events, but the business meaning of core metrics was not stable enough.
Consequence: Decision-making slows down because reported growth cannot be trusted or compared cleanly over time.
Response: Reframe dashboards around explicit business definitions and preserve one reporting spine from weekly to quarterly reviews.
Bug-clearing cycles repeatedly showed up in chats, reports, and launch coordination.
Consequence: Growth campaigns and investor narratives periodically had to account for service instability.
Response: Tie reactivation spend, bug triage, and release readiness together instead of treating them as separate workflows.
A candid root-cause hypothesis pointed to deprecated API usage as a likely source of recurring defects.
Consequence: Invisible fragility resurfaces as customer-facing instability.
Response: Audit integration versions, tighten ownership, and log dependency freshness as an operating metric.
Automation Layer
Current private corpus has been normalized into chronology-aware snapshots, interview briefs, decision records, and debt signals.
Future reports, chats, ADRs, diagrams, reflections, and code excerpts can be added without changing the public schema.
general_document · Mar 2026 · 2026-03-12
This document is an image file named IMG-20260312-WA0012.jpg. No further content or context is available for extraction.
general_document · Mar 2026 · 2026-03-11
This document is identified as the resume of Faidhi Fahmi, an iLyF team member.
url_reference · Mar 2026 · 2026-03-11
This document refers to the professional posts of Faidhi Fahmi, who is identified as the CEO of iLyF, accessible via their LinkedIn profile.
investor_report · Q1 2026 · 2026-03-11
This document is identified as '00000500-[Updated 20230830] -iLyF Monthly Investor Report.pdf', indicating it is a monthly investor report from iLyF, updated on August 30, 2023. Publication date is preserved before metrics are synthesized.
investor_report · Q1 2026 · 2026-03-11
This document is identified as the 'iLyF Quarterly Investor Report - Q22024 v1.2.pdf'. No further content or details are provided for analysis. Publication date is preserved before metrics are synthesized.
investor_report · Q1 2026 · 2026-03-11
This document is identified as a 'Monthly Investor Report' for 'iLyF' from September, version 1.1. The source is not available. Publication date is preserved before metrics are synthesized.
investor_report · Q1 2026 · 2026-03-11
This document is an image file of the 'iLyF Monthly Investor Report' for September, version 1. Publication date is preserved before metrics are synthesized.
investor_report · Q1 2024 · 2024-03-01
This document summarizes iLyF's Q1 2024 investor report, highlighting key metrics, financial performance, growth, product highlights, team structure, and partnerships. iLyF, an Ins Publication date is preserved before metrics are synthesized.
investor_report · Q1 2024 · 2024-03-01
This document is identified as the iLyF Quarterly Investor Report for Q1 2024, version 1, presented as an image file. Publication date is preserved before metrics are synthesized.
whatsapp_chat · Aug 2023 · 2023-08-29
This conversation highlights Faidhi Fahmi's active role in investor relations, including preparing and discussing monthly investor reports, seeking input on content and presentatio Raw chat content remains private and is only used for derived retrieval signals.
whatsapp_chat · Mar 2023 · 2023-03-01
This conversation reveals Faidhi Fahmi's active engagement in investor relations, specifically with Chris Chan and Juxian, regarding iLyF's performance and fundraising strategies. Raw chat content remains private and is only used for derived retrieval signals.
investor_report · Q1 2023 · 2023-03-01
This document is the iLyF Monthly Investor Update for March 2023, version 3.0, marked as P&C (presumably 'Private & Confidential' or 'Property & Casualty'). Publication date is preserved before metrics are synthesized.
whatsapp_chat · Jan 2023 · 2023-01-05
This conversation highlights Faidhi Fahmi's role as a leader and product visionary within iLyF. He is actively involved in onboarding new team members like Farah Design, defining t Raw chat content remains private and is only used for derived retrieval signals.
whatsapp_chat · Oct 2021 · 2021-10-29
This conversation highlights Faidhi Fahmi's active involvement in strategic partnerships, legal reviews, team management, and market research for iLyF. He is focused on securing ag Raw chat content remains private and is only used for derived retrieval signals.
investor_report
Never blend metrics across publication periods without preserving the report date.
whatsapp_chat, investor_report, technical_reflection
Generate STAR-shaped recruiter answers from derived signals only, never from raw private excerpts.
whatsapp_chat, adr, architecture_diagram
Extract context, decision, and trade-off separately so architecture choices are not reduced to outcomes only.
whatsapp_chat, technical_reflection, code_excerpt
Only emit debt signals when the pattern appears over time or is tied to a concrete incident.
Q1 2023
Date-bound summary generated from iLyF Monthly Investor Update - March 2023 v3.0 [P&C].pdf. Metrics and claims stay anchored to 2023-03-01.
Q1 2024
Date-bound summary generated from iLyF Quarterly Investor Report - Q1 2024. Metrics and claims stay anchored to 2024-03-01.
Q1 2024
Date-bound summary generated from iLyF Quarterly Investor Report - Q12024 v1.jpg. Metrics and claims stay anchored to 2024-03-01.
Q1 2026
Date-bound summary generated from 00000500-[Updated 20230830] -iLyF Monthly Investor Report.pdf. Metrics and claims stay anchored to 2026-03-11.
Q1 2026
Date-bound summary generated from iLyF Quarterly Investor Report -Q22024 v1.2.pdf. Metrics and claims stay anchored to 2026-03-11.
Q1 2026
Date-bound summary generated from 00000776-iLyF Monthly Investor Report - September v.1.1.pdf. Metrics and claims stay anchored to 2026-03-11.
Q1 2026
Date-bound summary generated from iLyF Monthly Investor Report - September v.1.jpeg. Metrics and claims stay anchored to 2026-03-11.
Cross-period, chronology preserved
Combines dated report snapshots with operational chat signals to answer recruiter prompts without flattening earlier and later company phases together.
Aug 2023
Aggregates recurring bug load, instrumentation ambiguity, and migration risk into durable debt signals suitable for recruiter-safe publication.
Report Spine
Monthly and quarterly archives kept off the public site.
Used for retrieval and synthesis, never exposed raw.
Reconstructed from operating patterns and architecture artifacts.
Published only as abstracted learnings and trade-offs.
All derived signals are published openly. Third-party names and identities not affiliated with iLyF are replaced with alphabet labels (Person A, Person B, etc.) to protect individual privacy.
Quarterly material reframed progress around revenue quality, retention, and operating discipline rather than top-line user growth alone.
Investor reports became business-development tools and were circulated together with more explicit operational interpretation.
Quarterly analysis linked COGS changes and reactivation effort to an earlier run of bugs.
Early-stage operating snapshot with install growth and funnel improvement, while bug-fixing still constrained release velocity.
Must be interpreted against August as its comparison baseline, not against later 2024 efficiency numbers.
Efficiency and profitability pivot, so lower volume metrics belong beside cost control rather than isolated weakness.
Later-stage snapshot with stronger financial quality; should not be blended with 2023 learning-phase metrics.
Knowledge Atlas
Small on purpose. The graph reads as a working system rather than a decorative force diagram.
Reflections
A March 2023 reflection noted that teammates were too focused on specific tasks and working in silos. The correction was not more process theater, but stronger sensitivity to Mixpanel observations and business signals.
External feedback did not ask for more hype. It validated the report’s usefulness and only suggested moderating the low-light wording so the upside landed more clearly.
The hard part of reporting was described as building correlation between metrics and effort. That is a stronger signal than any isolated KPI.