Backend Lead
Company Invisia Software
Location Bengaluru, India
Experience 6–10 years backend engineering
Reports To EM
Type Full-Time | Technical Leadership
ABOUT INVISIA SOFTWARE
Invisia Software is a growing software product company building modern, scalable digital platforms. We operate at the intersection of thoughtful engineering and user-centric design, with a team that values ownership, technical rigour, and a bias for shipping. As we scale, we are investing in the people and infrastructure needed to move fast without breaking things — and every hire at this stage has a direct impact on the trajectory of the company.
THE ROLE
The Backend Lead will own Invisia's core server-side systems — the booking engine, availability and inventory logic, payments flow, and the APIs that power everything from the mobile app to third-party integrations. You will be the technical anchor for backend engineering: setting the standard, mentoring the team, and making the key system design decisions.
This is a high-ownership role. You will not just be contributing features — you will be the person who decides how the backend scales, what the data model looks like, and how the team approaches reliability. You will work closely with the Frontend, Mobile, and DevOps functions to ensure the platform performs under real-world load.
CORE RESPONSIBILITIES
System Design & Ownership
– Design and evolve APIs, data models, caching strategies, and message queue architectures across Invisia's core backend services
– Own the performance and reliability of backend systems
— set SLOs, monitor dashboards, and proactively address degradation before it impacts users
– Make the key decisions on database choice, query optimisation, indexing strategy, and data partitioning as the platform scales
– Lead the design of Invisia's payments integration — ensuring security, reliability, and reconciliation accuracy
Engineering Quality & Standards
– Set and enforce backend coding standards, testing requirements (unit, integration, contract), and observability practices
– Lead backend code reviews; give feedback that improves code quality and helps engineers grow
– Own backend-specific postmortems; ensure root causes are identified and systemic fixes are implemented, not just patched
Team Leadership & Mentoring
– Mentor and technically guide backend engineers at junior and mid-levels
– Participate in backend hiring — define the bar, conduct technical interviews, and provide calibrated feedback – Collaborate with DevOps to right-size infrastructure, optimise cloud spend, and maintain deployment reliability
MUST-HAVE SKILLS & EXPERIENCE –
6–10 years of backend engineering experience with clear examples of owning and scaling complex systems
– Deep proficiency in at backend language (Node.js/TypeScript)
– Strong command of relational and non-relational databases; you know when to use each and how to optimise both
– Hands-on experience with caching layers (Redis or similar) and message brokers (SQS, Kafka, RabbitMQ, or equivalent)
– Payment gateway integration experience — you understand the reliability, idempotency, and reconciliation requirements that come with money movement (Preferred: Stripe)
– Experience building and maintaining RESTful and/or GraphQL APIs at production scale
– AWS-specific experience (Lambda, DynamoDB, RDS, Elastic ache, SES/SNS, API Gateway)
– Familiarity with event-driven Programming
– Exposure to observability tools like Datadog, Splunk etc and log monitoring tools such as CloudWatch & Grafana
NICE-TO-HAVE
– Experience building booking, availability, or inventory management systems
WHAT SUCCESS LOOKS LIKE
✓ Core API response times are consistently within defined SLOs across peak load
✓ The backend codebase has meaningfully improved test coverage and observability within 6 months
✓ Payment integration runs with zero reconciliation errors over a rolling quarter
✓ Junior and mid-level engineers are visibly growing in system design confidence under your mentorship
✓ Postmortems produce real systemic improvements, not just incident reports
INTERVIEW PROCESS
1. Intro and background discussion
2. System design session: booking availability and payment flow
3. Performance tuning case study — given a slow query or API, walk through how you diagnose and fix it
4. Code review exercise: review a backend PR and give structured feedback
5. Culture and team fit conversation with VP Technology.
