Head of Engineering

Increscotech; Coimbatore District; Hybrid; INR 2,500,000 - 4,200,000; Full time

Job summary

Increscotech in India seeks a Senior Engineering Lead to own delivery across web/backend systems and cloud infrastructure. You will lead 5–15 engineers, define technical plans, and ensure timely releases while balancing speed and stability.

This role requires hands-on architectural oversight and strong collaboration with product and business units. Ideal candidates have 8–12 years of software experience, 3+ years in leadership, and a proven track record of shipping scalable production software.

Qualifications

• 8–12 years of software development experience.
• 3+ years leading teams (5–15 engineers).
• Strong background in web/backend systems and databases.
• Experience with cloud infrastructure (AWS/GCP/Azure).
• Proven track record shipping production software at scale.

Responsibilities

• Own delivery with end-to-end sprint planning, execution, and release quality.
• Build and mentor engineers, raise standards, and retain top talent.
• Stay hands-on in architecture and critical code paths.
• Partner with product and business to translate requirements into technical plans.
• Improve CI/CD, infra, monitoring, and incident response.

Skills

Team leadership

End-to-end delivery

Architectural design

Backend development

Cloud platforms

Node.js/Java/Python

CI/CD & DevOps

Stakeholder management

Education

Bachelor's degree in CS/Engineering

Tools

Node.js

Java

Python

PostgreSQL/MySQL

Docker/Kubernetes

Job description

Incresco is an AI-driven technology consulting firm. We build across multiple stacks—web, mobile, cloud, and AI—with our sharpest focus on what's next: AI agents for Salesforce and WhatsApp. We've built our name delivering premium engineering for global clients, fast—production in weeks, not months.

Headquartered in Bangalore with our delivery hub in Coimbatore, we keep teams small and senior, ownership real, and the quality bar high.

Job description

Experience: 8–12 years

Reports to: CTO / Founder

Why this role exists (read this carefully)

We are past the “everyone codes and vibes” stage. This role exists to turn engineering effort into predictable business outcomes. If you’re looking to just manage Jira tickets or coast on past tech glory—don’t apply.

What you’ll actually do (not what you’ll say in interviews)

1. Own delivery. No excuses.

• End-to-end ownership of sprint planning, execution, and release quality

• Ruthlessly remove blockers—technical, people, or process

• Ensure timelines are realistic and met

• If delivery slips, you explain why and what changes, not who to blame

2. Build and lead engineers (not babysit)

• Hire, mentor, and retain strong engineers

• Identify underperformers early and act decisively

• Set engineering standards for code quality, reviews, testing, and documentation

• Turn good engineers into dependable ones

3. Stay technical (this is non-negotiable)

• Hands-on involvement in architecture and critical code paths

• Review PRs and challenge bad design decisions

• Make pragmatic tech trade-offs—no overengineering for ego

• Ensure systems scale without becoming fragile or unmaintainable

4. Partner with product & business

• Translate product requirements into clear technical plans

• Push back on vague specs and unrealistic timelines

• Balance speed vs stability like a grown-up

• Align engineering priorities with revenue, customers, and ops

5. Improve systems, not just ship features

• Continuously improve CI/CD, infra, monitoring, and incident response

• Reduce tech debt deliberately—not “when we have time”

• Build processes that survive people churn

What you must bring to the table

Experience & skills

• 8–12 years of software development experience

• 3+ years leading teams (5–15 engineers)

• Strong background in web/backend systems (Node.js / Java / Python / similar)

• Solid understanding of databases, APIs, cloud infrastructure (AWS/GCP/Azure)

• Proven track record of shipping production software at scale

Mindset (this matters more than tools)

• You take ownership, not credit

• You’re comfortable saying “no” and defending it

• You hate chaos but don’t worship process

• You think in systems, not tasks

• You care about business impact—not just clean code

What will disqualify you instantly

• “I don’t code anymore”

• Blaming product, QA, or juniors for delivery failures

• Obsession with titles over outcomes

• Waiting for instructions instead of taking charge

• Overengineering to look smart

What success looks like in 12 months

• Delivery is predictable

• Engineers trust your decisions

• Product teams want to work with you

• Tech debt is controlled, not exploding

• You’ve built at least one strong successor under you