Sheshi AI
Website:
sheshi.ai
Job details:
Backend Technical Lead
ABOUT SHESHI
Bringing Sanctity to Numbers
Sheshi is a Financial Operating System — the governed infrastructure layer that converts raw financial data into results that organisations can completely trust. Governed, auditable, period-locked, and traceable to the source.
Finance is one of the last enterprise functions to get infrastructure-grade software. The opportunity is large, the problem is real, and the timing is right. Sheshi is building the category from the ground up.
We are headquartered in Bengaluru, India, building an enterprise-grade product for the global market.
THE ROLE
As Backend Technical Lead, you will own the architecture and quality of the system that sits at the heart of Sheshi's platform. You will work directly with the Head of Engineering and the product team to design, build, and evolve a backend that enterprises depend on for their financial operations.
You will lead a pod of engineers, set the technical standard, and be the final word on backend architecture decisions. This is a hands-on role, you will design, review, and build, not just direct.
WHY SHESHI
The Challenges That Will Define Your Work
Engineering a Financial Operating System is a different class of problem. A few things that will shape your work here:
- Financial-grade correctness. The backend powers numbers that flow into board packs, investor reports, and statutory outputs. Accuracy and traceability are central to everything built here — systems are designed to reconcile, and data flows are built to be auditable.
- Domain depth. Areas like multi-entity consolidation, period locking, intercompany eliminations, and chart of accounts bring a level of backend complexity that is both challenging and meaningful. There is an opportunity to work deeply within this space and shape how these problems are solved.
- Scale with purpose. As the platform grows from enterprise use cases to a broader global footprint, architectural decisions made today naturally influence how the system evolves and scales.
- Real ownership. The backend is not a supporting layer, it is a core part of the product. There is space to take end-to-end ownership of architecture, quality, and long-term direction.
RESPONSIBILITIES
What You Will Build and Own
Technical Ownership
- Own the backend architecture of the Sheshi platform: data models, API design, service structure, and system reliability.
- Make and enforce architectural decisions across the backend with full accountability for correctness and performance.
- Define and uphold backend engineering standards, code quality, review culture, testing discipline, and documentation.
- Lead backend design reviews; ensure every significant change is assessed for correctness, scalability, and long-term maintainability.
Backend Engineering
- Design and build APIs that are clean, consistent, versioned, and enterprise-grade.
- Own the data model, financial hierarchies, period structures, entity relationships, and audit trails at PostgreSQL level.
- Ensure backend performance under the load of financial close cycles, multi-entity consolidation, and concurrent enterprise usage.
- Drive query optimisation, indexing strategy, and database reliability with PostgreSQL as the primary RDBMS.
- Build and maintain event-driven patterns and background processing where financial workflows require async execution.
- Ensure full auditability of data mutations, every change recorded, every state transition traceable.
Release and Change Management
- Lead release planning and execution - versioning, branching strategy, change logs, and patch management.
- Work hands-on with the DevOps team through each release cycle, from build to deployment to post-release validation.
- Maintain release hygiene across all environments - semantic versioning, tagging, and rollback readiness.
On-Premise and Deployment Architecture
- Design the application to support on-premise deployment alongside cloud -configuration-driven and environment-agnostic.
- Own the packaging, installation, upgrade, and rollback approach for on-prem customer deployments.
- Build deployment scripts and infrastructure-as-code that work consistently across both cloud and on-prem environments.
Security, Compliance, and Technical Audits
- Embed security into backend development, OWASP alignment, input validation, secure API design, and dependency management.
- Own backend data protection standards, encryption at rest and in transit, access control at data layer, secrets management on AWS.
- Support audit readiness, ensure backend systems can demonstrate traceability, access logs, and data integrity to enterprise customers and auditors.
Team and Collaboration
- Lead the backend pod, mentor engineers, review code, enforce standards, and develop the next layer of technical capability within the team.
- Work closely with the Frontend Technical Lead to ensure clean API contracts and smooth integration..
- Partner with the QA team to ensure backend quality is validated at unit, integration, and system levels.
- Collaborate with Product, Design and the Head of Engineering to translate complex financial requirements into sound backend design
WHAT WE ARE LOOKING FOR
Your Background and Strengths
Experience
- 7–12 years in software engineering, with at least 3 years in a backend technical lead or senior backend role.
- Proven experience building and owning complex backend systems for B2B SaaS products — fintech, ERP, accounting, or enterprise software strongly preferred.
- Experience scaling engineering teams in early-stage or growth-stage startups.
- Track record of designing data models and APIs that have held up at production scale.
Technical Depth
- Deep Node.js expertise, architecture, performance, async patterns, and production reliability at scale.
- Strong PostgreSQL command, schema design, complex queries, indexing, performance tuning, and financial-grade data integrity.
- Solid AWS experience, RDS, EC2/ECS, S3, SQS, CloudWatch, IAM; comfortable making infrastructure decisions for the backend layer.
- MongoDB familiarity for document-oriented data where applicable in the platform.
- Python experience for data processing, scripting, or analytical backend workflows.
- Strong understanding of REST API design principles, versioning, and enterprise integration patterns.
- Application security knowledge, OWASP, secure data handling, and compliance-oriented backend design.
How You’ll Be Working
- Start by understanding the requirement clearly, what needs to be built and why, before jumping into design or code.
- Break down features into clear backend tasks with timelines and discuss them with the team.
- Design solutions keeping the full flow in mind, how data moves, how modules interact, and what can go wrong.
- Stay hands-on, review code regularly, guide the team, and step in when needed.
- Work closely with frontend, QA, and DevOps so things move smoothly without last-minute surprises.
- Keep communication simple and clear so everyone knows what’s happening and what to expect.
- While building for today, keep an eye on what will matter tomorrow, performance, scale, and maintainability.
Nice to Have
- Exposure to SOC 2, ISO 27001, or enterprise security compliance requirements.
- Experience designing multi-tenant SaaS backends with entity-level data isolation.
Click on Apply to know more.