Senior Engineers: Finance Intelligence Platform

Senior Engineering Team — Financial Intelligence Platform (5 Roles | Long-Term)

Description:
I am building a global financial intelligence platform that maps ownership structures and detects hidden relationships across companies, people, assets, and jurisdictions — think Palantir-level data infrastructure for AML, KYC, and entity resolution.
This is a serious, long-term build. I am not looking for people to start coding. I am looking for engineers who can design their layer correctly first, then execute against a locked blueprint.
I have five open roles. Apply for the one that matches your strongest skillset.

THE PLATFORM STACK
AWS (VPC, IAM, S3, RDS, ECS/EKS, KMS) · PostgreSQL · Neo4j or Neptune · OpenSearch · FastAPI or NestJS · React / Next.js · Airflow or Prefect · Docker · GitHub Actions · Kafka or SQS

OPEN ROLES
1 — Backend Engineer (×2)
Build the core API layer, service architecture, and data access patterns. FastAPI or NestJS. Must have experience with multi-service architectures and RBAC. Performance targets: search under 1.5 seconds, 500 concurrent users.
2 — Data Engineer
Design and build the global data ingestion and normalization pipeline. Multiple source types: APIs, scraping, file ingestion, document parsing. Must handle messy real-world data at scale. Airflow or Prefect. Experience with entity normalization (names, addresses, jurisdictions) strongly preferred.
3 — Frontend Engineer
React / Next.js. Building investigative intelligence interfaces — graph visualizations, search UX, entity profile pages, risk dashboards. Must be comfortable consuming complex API schemas. Design sensibility matters; this is not a CRUD interface.
4 — DevOps Engineer
AWS infrastructure execution. ECS/EKS deployment, CI/CD via GitHub Actions, Docker, monitoring, secrets management (KMS), environment management across dev/staging/prod. Must be able to work against an architecture blueprint without hand-holding.

HOW THIS ENGAGEMENT WORKS
∙ Written scope is locked before sprint 1. No ambiguity.
∙ Each engineer owns one subsystem. Ownership is explicit.
∙ 1-week sprints. Friday demos are mandatory — working software, not status updates.
∙ Definition of done: code reviewed, unit tested, 80%+ coverage, deployed to staging, demoed live.
∙ This is a long-term engagement for the right people. I am not running a one-time project.

WHAT I AM LOOKING FOR IN YOUR APPLICATION
Do not send a generic proposal. Answer these three questions:
1. Which role are you applying for?
2. What is one architectural decision you would make for that layer, and why?
3. What is a relevant system you have built that is closest to this?
Applications without answers to these three questions will not be reviewed.

PREFERRED LOCATIONS
Eastern Europe · Argentina · Brazil · Southeast Asia
ENGAGEMENT TYPE
Hourly or milestone-based. Open to discussion based on role.
START
Immediate for the right candidates. Show More