1. Role Purpose
This role exists to handle the day-to-day work that currently lands on the CTO — client questions, bugs, and getting small changes done — so the CTO can spend more time on bigger technology decisions and growing the business.
The person in this role runs delivery on a daily basis. They only go to the CTO for things that genuinely need his decision — big scope changes, pricing, or anything that could seriously affect a client relationship.
2. Key Responsibilities
2.1 Handling Client Queries
- Be the first point of contact for day-to-day client questions and sort out what can be sorted out directly.
- Keep clients updated regularly on project status and next steps, instead of only replying when they ask.
- For anything that can't be resolved directly, pass it to the right person or bring it to the CTO with a clear recommendation.
- Keep track of every open query until it's actually closed.
2.2 Bug & Issue Handling
- Take in bugs and issues reported by clients or found by the QA team.
- Assign each issue to the right person (Development or Design) and set a clear timeline for it.
- Follow up until the fix is done, tested, and confirmed with the client.
- Keep a simple, up-to-date list of open issues for each client that the CTO can check anytime.
2.3 Implementing Website & Front-End Changes
- Work with the SEO team to understand what changes they need made on the website or front-end, based on their recommendations.
- Get those changes done through the Development team, and check that they've been implemented correctly.
- This role is not responsible for SEO strategy — only for making sure the technical changes the SEO team asks for actually get done.
2.4 Coordinating the Team
- Run regular check-ins with Development, Design, and QA to see what's on track and what's stuck.
- Keep an eye on every ongoing project so nothing slips without someone noticing early.
- Flag it early if two projects need the same person at the same time, so work doesn't get delayed.
- Make sure the team is actually following the standard process for each project, not skipping steps.
2.5 Keeping the CTO in the Loop
- Give the CTO a short, regular update on how delivery is going — the important things only, not every small detail.
- Only bring things to the CTO that genuinely need his decision — money, contracts, big scope changes, or a client relationship at risk.
- Use good judgement on what needs to go up to the CTO and what doesn't — this is the main value this role adds.
3. What This Role Can and Cannot Decide
- Can decide: who on the team works on what, in what order, and how something should be technically built, within work that's already agreed.
- Can decide: day-to-day technical approach and code/design quality — this person is the final technical word on delivery, without needing the CTO's sign-off each time.
- Cannot sign: proposals, contracts, NDAs, or agreements. Only the CTO can sign these.
- Cannot approve: pricing, discounts, or any change to what was commercially agreed with a client. These go to the CTO.
- Can directly ask: any team member in Development, Design, QA, or SEO for help on an active issue, without needing approval first.
4. Skills & Experience Needed
4.1 Technical Skills (Hands-On, Team-Lead Level)
- Strong, current hands-on experience with the MERN stack (MongoDB, Express, React, Node.js), Next.js, and PHP/Laravel — able to read code, review pull requests, and make real technical calls, not just talk about it at a high level.
- Solid understanding of REST APIs and how multi-client systems are built, enough to guide the team's decisions on how something should be built.
- Strong hands-on experience with WordPress, Shopify, and Webflow, including page builders like Elementor, plus enough database and site-speed knowledge to diagnose a slow or broken site personally.
- Working knowledge of Flutter and React Native, and how apps actually get published on the Play Store and App Store, so mobile projects can be reviewed properly.
- Comfortable working with AI tools and APIs (such as OpenAI or Anthropic), writing good prompts, and understanding how AI features get built into a website or product — this is a growing part of what clients ask for.
- Hands-on comfort with Linux servers, common hosting panels (like cPanel), and basic server security, enough to troubleshoot a site that's down without waiting on someone else.
- Understands common website security risks and what good security practice looks like, enough to make sure the team isn't cutting corners.
4.2 Team Leadership
- Has actually led a technical team before — reviewing work, unblocking people, and making the call when two approaches are being debated.
- Can mentor junior developers and designers, and can tell the difference between someone who's stuck and someone who just needs more time.
- Comfortable being the final technical word on day-to-day delivery decisions, even without being the CTO.
4.3 Coordination & People Skills
- Able to read a bug report or a client complaint and quickly figure out how serious it is and who should fix it.
- Comfortable using task-tracking tools and disciplined about keeping them updated.
- Calm and clear when talking to clients, even about a problem — doesn't need the CTO in the room to handle a tough conversation.
- Good at getting other team leads to act quickly, even though they don't report directly to this role.
5. Qualifications & Experience
- Graduate degree in Computer Science, IT, Engineering, or equivalent hands-on experience.
- At least 5–7 years in software development or technical delivery, including real time spent building things personally before moving into a leadership role.
- Proven experience leading a technical team, not just writing code solo.
- Current, hands-on experience across most of the technologies listed above — this should not be someone who learned these years ago and has since moved fully into management.
- Comfortable directly reviewing code and technical work, not just relying on what the team reports.
Pay: ₹1,200,000.00 - ₹1,500,000.00 per year
Benefits:
- Flexible schedule
- Paid sick time
- Paid time off
- Work from home
Ability to commute/relocate:
- Mumbai, Maharashtra (Mumbai): Reliably commute or planning to relocate before starting work (Required)
Experience:
- Project management: 3 years (Required)
- Web development: 5 years (Required)
Work Location: Hybrid remote in Mumbai, Maharashtra (Mumbai)
