Principal Software Engineer (Onsite- Bangalore)

Experience 9.00 + years Salary Confidential (based on experience) Expected Notice Period 30 Days Shift (GMT+05:30) Asia/Kolkata (IST) Opportunity Type Office () Placement Type Full Time Permanent position(Payroll and Compliance to be managed by: A fintech platform that enables businesses)

**(*Note: This is a requirement for one of Uplers’ client - A fintech platform that enables businesses)

**What do you need for this opportunity?

Must have skills required: Java, Node.js, Python, Golang, Go, Kotlin, Distributed Systems, Microservices, backend architecture, System Architecture, Software Architecture, Architecture Design, AWS, GCP, Azure, Kubernetes, Docker, Terraform, Fintech, Payments, Digital wallet, Wallet, Banking, BFSI, Crypto, Blockchain, Solana, Ethereum, EVM, CTO, Chief technology officer, VP Engineering, Head of engineering, Principal engineer, Director Engineering, Staff engineer, Director, neobanking, Baas, CaaS, Transaction Platforms, Startup Mindset, Founder-facing, build-vs-buy

A fintech platform that enables businesses is Looking for: Principal Software Engineer / CTO Fintech Wallet | Fiat + Crypto | Early-Stage Startup** **Location: Bengaluru - WFO

Reporting to: Founder / CEO

Team Size: ~15 people

Employment: Full-time | Leadership

Experience: 8+ year

Role Type: Hands-on technical leadership

Own the complete technology function for a Fiat + Crypto Wallet platform.

Principal Software Engineer / CTO — Role Summary

• Experience: 8+ years in software engineering with senior technical leadership experience.
• Domain: Strong background in Fintech, Payments, Banking, Wallets or Financial Infrastructure.
• Core Requirement: Hands-on ownership of technology strategy, architecture, engineering, security and infrastructure.
• Technical Must-Have: Strong backend, distributed systems, cloud architecture and financial transaction systems experience.
• Financial Systems: Experience with ledger, payments, settlement, reconciliation, transaction processing and auditability.
• Leadership: Proven ability to hire, mentor and lead engineering teams in a startup/scale-up environment.
• Cloud & Infra: AWS/GCP/Azure, Kubernetes, Docker, Terraform, CI/CD, PostgreSQL, Redis and Kafka.
• Security: Strong understanding of authentication, authorization, encryption, KMS/HSM, secrets management and transaction security.
• Crypto — Good to Have: Crypto wallets, blockchain, stablecoins, custody, MPC/HSM, on/off-ramp and blockchain integrations.
• Preferred Languages: Java, Go, Kotlin; Python and Node.js are also relevant.
• Ideal Profile: A hands-on CTO/Principal Engineer who can architect systems, write/review code, troubleshoot production issues and build the engineering team.

Team Structure Initially, the CTO may directly manage a small engineering organization consisting of:

• Backend Engineers
• Frontend Engineers
• Mobile Engineers
• DevOps/SRE
• QA
• Security/Infrastructure

As the company grows, establish teams around:

PE/ CTO:

│

├── Core Wallet / Ledger

│

├── Payments

│

├── Crypto

│

├── Consumer App

│

├── Merchant Platform

│

└── Platform / Infrastructure

The exact structure should evolve with product and transaction volume.

Vendor & Technology Management Own technical evaluation of vendors.

Responsibilities include:

• Vendor selection
• Architecture reviews
• Security assessments
• SLA evaluation
• Technical negotiations
• Integration planning
• Vendor performance monitoring
• Vendor exit strategy

Avoid excessive vendor lock-in for critical financial infrastructure.

Budget & Technology Costs Own the technology budget covering:

• Cloud infrastructure
• Engineering tools
• Security tools
• Monitoring
• Third-party APIs
• Blockchain infrastructure
• KYC/KYB
• Development tools
• Software licenses
• Infrastructure vendors

Continuously optimize infrastructure and vendor costs.

Key Metrics The CTO should establish a technology scorecard.

Platform

• Uptime: 99.99%+
• API latency
• Transaction success rate
• Crash rate
• Error rate

Engineering

• Deployment frequency
• Lead time for changes
• Change failure rate
• MTTR
• Sprint/release predictability

Security

• Critical vulnerabilities
• Secur…