VP Engineering & Product Development

Job Summary

Drive technology execution and product engineering for the fintech platforms (exchange/white-label exchange/wallet/training systems, MT5 CRM, AI bots, etc.). Provide senior technical level guidance to clients on architecture, roadmaps, and delivery. Scale and secure systems; design effective teams; eliminate firefighting.

Key Outcomes

• Very little bugs/hotfixes — stable releases
• High-volume fintech (latency/reliability/security) scalable architecture
• Strong engineering leadership bench.
• Client builds trust through transparent roadmaps and estimates.

Core Responsibilities

Technical Strategy & Architecture

• Proprietary fintech architectures: trading/OMS integrations, custodial/non-custodial), compliance/audit hooks.
• Create exchange (spot/derivatives, liquidity/matching), wallet (key mgmt/signing/recovery), risk/monitoring.

Product Engineering Execution

• Identify how to reach those goals and map out a roadmap with milestones / who you will need.
• Have rigor: sprints, code reviews, tests, release gates
• Monitoring of DORA metrics (deploy frequency, lead time, failure rate, MTTR), defects, SLOs.

Security, Compliance & Reliability

• Security in your SDLC: threat modelling, secrets mgmt, secure SDLC, pen test
• Allow for Trim Compliance: hooks for KYC/AML, audit logs, data retention D. Team & Leadership
• Build/mentor managers/tech leads.
• Hire seniors in eng/QA/DevOps/security.
• Career ladders, performance and training

Client-Facing Leadership

• Join workshops/reviews/pre-sales.
• Provide estimates based on data; push back against impossible deadlines.

KPIs (Sample)

Must-Have

• 12-18+ years engineering; 5+ years leading multi-team orgs
• Fintech platforms (payments/trading/wallets/exchanges/brokerage/risk).
• Solid system design (distributed/event-driven design, APIs)
• Cloud ops (AWS/GCP/Azure).

Nice-to-Have

• White-label/multi-tenant platforms.
• Low-latency/market data/OMS integrations.
• Blockchain/Web3 for wallets/exchanges.

30/60/90-Day Plan

Days 1-30

• Assess architecture/codebase/bottlenecks.
• Define what “engineering way” means → Add some release gates.

Days 31-60

• Boost QA automation/observability.
• Playbook building around incidents; Streaming stabilizing.

Days 61-90

• Cut defects/escalations; lift throughput.
• Roadmap ready; tech lead layer strong.

Note: Interested candidates may send their resume to [email protected]. Only shortlisted applicants will be contacted.