Filipe Gonçalves
-
Filipe Gonçalves
October 14, 2025 at 2:05 pm in reply to: Stablecoins for payroll — anyone doing this live?Explainability docs unblocked risk within two meetings. If the key metric doesn’t move in 14 days, revert. Decide this with numbers, not vibes.
-
Filipe Gonçalves
October 13, 2025 at 7:08 pm in reply to: How to get licensed to lend in multiple states fast?Automate sticky edge cases to save analyst time. Process tip that prevented a week of rework. Schedule a retro after the first month.
-
Filipe Gonçalves
October 13, 2025 at 4:05 am in reply to: Stablecoins for payroll — anyone doing this live?Small anecdote that might help. Keep dependencies boring and well‑documented. A one‑pager playbook helped on-call engineers a lot.
-
Filipe Gonçalves
October 13, 2025 at 2:08 am in reply to: How to get licensed to lend in multiple states fast?Decide this with numbers, not vibes. We hit rate limits on day three; lightweight caching saved us. If the key metric doesn’t move in 14 days, revert.
-
Filipe Gonçalves
October 10, 2025 at 10:22 pm in reply to: Anyone using FIDO passkeys in production for banking apps?If the key metric doesn’t move in 14 days, revert. We hit rate limits on day three; lightweight caching saved us. Decide this with numbers, not vibes.
-
Filipe Gonçalves
October 9, 2025 at 8:11 pm in reply to: Top cybersecurity risks for fintechs this year?Process tip that prevented a week of rework. Tighten feedback loops with weekly reviews. Set crisp ownership so decisions don’t stall.
-
Filipe Gonçalves
October 8, 2025 at 11:09 am in reply to: PCI DSS 4.0 — what changed for small teams?Process tip that prevented a week of rework. Watch hidden dependencies that slow audits. Run a pre-mortem; it surfaces surprises early.
-
Filipe Gonçalves
October 8, 2025 at 3:19 am in reply to: Tax-loss harvesting — is it still worth it at low fees?Small anecdote that might help. Rotate credentials on a calendar, not only after incidents. The real cost driver was reprocessing, not inference.
-
Filipe Gonçalves
October 4, 2025 at 10:47 am in reply to: How do you explain portfolio risk to retail users clearly?Bias toward tools the team can actually operate. Counterpoint based on what stuck in reality. Ignore shiny features until you validate ROI.
-
Watch hidden dependencies that slow audits. Process tip that prevented a week of rework. Schedule a retro after the first month.
-
Filipe Gonçalves
October 2, 2025 at 8:03 am in reply to: What data do we actually need for ML underwriting?Shadow‑run the new stack for a week before go‑live. Quick checklist that saved us time. Push data contracts upstream so APIs don’t drift.
-
Filipe Gonçalves
October 2, 2025 at 4:21 am in reply to: Remote vs onsite for fintech engineering — what works?Biggest risk is invisible complexity creeping in. Log sample payloads (PII redacted) to speed debugging. Keep the system operable by the smallest competent team.
-
Filipe Gonçalves
September 30, 2025 at 2:34 am in reply to: Gas fees on L2s are low — what hidden costs should we expect?Process tip that prevented a week of rework. Automate sticky edge cases to save analyst time. Use feature flags generously for safe tests.
-
Filipe Gonçalves
September 29, 2025 at 9:58 pm in reply to: How do you price usage-based insurance fairly?A thin rules layer filtered 80% of noisy alerts. Small anecdote that might help. Ship small and often to limit blast radius.
-
Filipe Gonçalves
September 29, 2025 at 3:28 pm in reply to: How to build trust during onboarding for a new neobank?Ignore shiny features until you validate ROI. Watch hidden dependencies that slow audits. Counterpoint based on what stuck in reality.
Details
Filipe
filipe-g