Tech Lead

Left Right Mind; Pune District; Hybrid; INR 4,000,000 - 7,000,000; Full time

Job summary

Left Right Mind in Pune (Hybrid) is seeking a hands-on Tech Lead to own technical design and architecture from concept to release. You will lead and unblock a team of engineers, mentor talent, and personally contribute to critical design decisions.

The role emphasizes building with Python 3.10+, cloud-native approaches on Azure/AWS, and practical AI/LLM capabilities (RAG, embeddings). You will drive delivery discipline and ensure robust releases in a hybrid work setup.

Qualifications

• Strong backend development in Python 3.10+ with API design experience.
• Experience with cloud native development on Azure or AWS.
• Data modelling across relational, document, and vector stores; SQL proficiency.
• Testing discipline: unit, integration, and the judgement to know how much of each is enough.
• Experience with LLMs, RAG pipelines, and prompt design.

Responsibilities

• Own the technical design/architecture of features from concept through to release.
• Lead a team of engineers through design, build, review, and release.
• Mentor engineers and help them grow into more ownership.
• Size work and keep delivery predictable; run technical planning and refinement.
• Support releases end to end, including what happens after deployment.

Skills

Python 3.10+

REST API design

Async patterns

Azure

AWS

CI/CD pipelines

SQL proficiency

Unit testing

Code review

Release management

LLM engineering

RAG pipelines

Agent orchestration

Prompt design

Embeddings and retrieval

Security fundamentals

Observability

RBAC and secrets management

Job description

Designation: Tech Lead

Location: Pune (Hybrid)

Experience: 7+ years, including 2+ years leading an engineering team

About the Role

This is a hands‑on role. You will spend your time across design discussions, pull requests, and the hard problems that block your team, rather than managing from a distance. It suits an engineer who wants technical ownership and is willing to be accountable for what ships.

What You’ll Do

Technical Direction

• Own the technical design/architecture of features from concept through to release.
• Break down complex work into a sequence a team can actually deliver.
• Evaluate tools, libraries, and approaches, and make a clear call rather than leaving options open.

Engineering Quality

• Set and enforce engineering standards: code review, testing, observability, and security practices.
• Review pull requests and give feedback that raises the level of the team, not just the code.
• Keep technical debt visible and negotiate the time to address it.

Leading the Team

• Lead a team of engineers through design, build, review, and release.
• Unblock people quickly - pair, prototype, or write the tricky piece yourself when that is the fastest path.
• Mentor engineers and help them grow into more ownership.

Delivery

• Work with the team to size work and keep delivery predictable.
• Run technical planning and refinement; flag risks early rather than at the deadline.
• Support releases end to end, including what happens after deployment.

Skills We’re Looking For

Core Engineering

• Strong backend development in Python 3.10+ with solid API design (REST, async patterns).
• Cloud‑native development on Azure or AWS - containers, managed services, CI/CD pipelines.
• Data modelling across relational, document, and vector stores; comfort with SQL beyond the basics.
• Testing discipline: unit, integration, and the judgement to know how much of each is enough.
• Git workflow, code review practice, and release management.

AI and LLM Engineering

• Practical experience building with LLMs - RAG pipelines, agent orchestration, prompt design.
• Evaluation of non-deterministic systems: defining quality criteria and measuring against them.
• Understanding of embeddings, retrieval, and the failure modes of each.

Enterprise Concerns

• Security and access control: authentication, RBAC, secrets management, data boundaries.
• Observability - logging, tracing, and metrics that make production behaviour explainable.
• Awareness of deployment constraints in regulated or restricted environments.

Ways of Working

• Clear technical writing. You can produce a design document or decision record that someone else can act on.
• Ability to explain a technical trade‑off to a non‑technical stakeholder without losing the substance.
• Mentoring and code review skills that lift the people around you.
• Comfort making decisions with incomplete information, and revisiting them when better information arrives.