Key responsibilities :

- Own a part of a product area end to end: its services, its features, its quality and most importantly its impact on our customers.

- Own the quality and health of what you ship, and resolve customer issues directly.

- Own the long-term health of your sphere.

- Set the design and code standard for it, review designs and changes from other pods within an agreed time, and approve or push back with reasons.

- Escalate disagreements through the right path rather than blocking.

- Lead a pod's delivery: plan timelines, dependencies and who works on what; budget real time for review, known unknowns, and unknown unknowns; spot risk early; build a Plan B before you need it, and trigger and communicate it when the data says so.

- Manage a team of engineers, some of whom work in pods led by others.

- Gather evidence of their work from the people they work with, give honest and timely feedback, deal with performance issues directly, and help each person excel in their field, and help Mindtickle raise its performance bar continuously.

- Partner with Product on the roadmap.

- Shape what gets built, not just relay it.

- Push back on requirements that create fragile or disparate systems and offer something better.

- Make AI part of how your pod and your sphere: in grooming, design, coding, review, testing, and operations, debugging, tech debt elimination, and what not, and inside the product where it beats rules written by hand.

- Know where it helps, where it fails, and how to manage.

- Check its output to achieve quality and speed that beats purely human effort.

- Define and own the engineering metrics for your area, and use them to fix problems before they are noticed and / or reported by our customers.

Required qualifications :

- Significant software engineering experience, including several years managing engineers while staying close to the technical work.

- Scope and impact is what matters, not the title held.

- Hands-on technical depth.

- You can design a system, write production code, and review a design or a change and meaningfully, productively critique it and find what is wrong with it.

- You will be interviewed on high-level system design and on AI-assisted coding with low-level design also.

- End-to-end ownership of services in production: you shipped them, ran them, handled their incidents, and improved them.

- Delivery in a constrained environment across dependencies: you have worked in an environment which has factors beyond your control, you have planned and delivered work that depended on other teams, and you can show how you planned and managed the risks posed by these constraints.

- People leadership: you have hired, grown and given hard feedback to engineers, and dealt with performance problems, high performing engineers, team players, and solo adventurers directly.

- Influence without direct authority: you have influenced, guided, and led people who did not report to you to a delivery outcome.

- Native and preferred use of AI: AI is your tool of first choice given any problem.

- You are not only excited about AI usage, you understand its nuances, make it productive for you, your team and Mindtickle in presence of its challenges, daily, practical use of AI tools in engineering work, and examples of helping a team adopt them.

- Clear written communication: plans, design reviews, status updates and decisions that others can act on.

Preferred qualifications :

- Experience in B2B SaaS, multi-tenant systems, or products where customers vary widely in configuration, integrations and data.

- Experience in a matrix or pod-based model, where people's day-to-day direction and their line management were held by different people.

- Experience building AI features into a product and evaluating their quality and output whether they work.

- Experience owning a shared component or platform that other teams changed or built on.

- Familiarity with AWS and the cost, reliability and security trade-offs that come with it.

- Familiarity with sales enablement, learning systems, content intelligence or call analytics is welcome but not required.