Technical Product Manager

The core responsibilities for the job include the following:

Product Strategy and Roadmap:

• Own Lecxe's product roadmap: define what we build, in what order, and why, grounded in client feedback, field data from clients, and your own judgment about where the leverage is.
• Translate business strategy into products and AI solutions: identify the modules and capabilities that move MSME clients from chaos to an operating system, and sequence them to maximize adoption and retention.
• Write clear product specs, not decks, not PRDs that gather dust. Specs that engineers can build from and clients can review the same day.
• Decide what not to build. Scope creep is the enemy; you protect the team's focus without being rigid about client needs.

Engineering Leadership and Daily Coding Hands-On Building:

• Write some parts of production code every day. You are an active contributor to the codebase, not a reviewer who last shipped two years ago. Your commits appear in standup. Build hands-on, daily. When a new engagement kicks off, you do the initial implementation or lay down the architecture yourself, especially for phase one of a multi-phase build, where phase two and three need to already be in mind. You are not someone who only tells engineers what to build; you get in and build alongside them.
• Own the architecture of Lecxe's Business OS for your particular clients: agent orchestration (LangGraph), API design (FastAPI), data model (Postgres), and frontend patterns (Next.js ).
• Set and enforce engineering standards: code review, testing, deployment hygiene, observability, and security baseline. Test what your team ships as thoroughly as you can, automate testing and workflows wherever they repeat, and review code at a high level for security exposure, redundant components that duplicate what already exists, and deviations from the codebase's established patterns. You are the bar everyone else is measured against.
• Lead the design, R& D, and build of new product surfaces: voice-first WhatsApp agents, vendor negotiation flows, inventory and finance modules, agentic ERP workflows, and similar products
• Make calls on technical debt, refactoring priorities, build vs. buy, and where to use AI to reduce engineering load permanently.

Team Leadership and Development:

• Lead a team of forward-deployed engineers and junior developers. You are their primary technical mentor and the person setting the quality bar.
• Run structured code reviews, design reviews, and 1:1s. You give feedback that makes people better, not just feedback that fixes the immediate problem.
• Onboard new engineers to ship within their first week and operate independently within their first quarter.
• Build the engineering and product culture: how we write, review, and ship code; how we recover when something breaks; how we talk to clients when the news is not good.

Client-Facing Delivery:

• Lead technical discovery at client sites: sit with founders, operators, and floor teams; map their actual workflows; identify what is worth automating and what the system will never replace.
• Be the senior Lex presence in high-stakes client conversations, scoping calls, escalations, QBRs, and go-live meetings. Clients should feel that the person who built the product is also the person accountable for its success.
• Translate ambiguous, contradictory business problems into a clean technical scope, then into a working pilot typically in weeks, not quarters.
• Run implementation end-to-end: integration with client systems (Tally, ERPs, WhatsApp Business API, payment gateways), data migration, user training, and go-live.
• Own the post-go-live relationship: you are the person the client calls when something needs to change and the person who decides whether that change goes into the roadmap.

Requirements:

• A background that is genuinely both technical and commercial. Ideal profile: B. Tech or B. E. from a top engineering institution, followed by an MBA from a top business school or equivalent, demonstrated depth on both sides.
• 4+ years of total experience with at least 2 years of hands-on software engineering in production systems you genuinely owned, and at least 1 year in a product management or product-adjacent leadership role.
• You write code today. Not "used to" today. You build hands-on today. Not "used to" today. You can still sit down and do the initial implementation or debug something gnarly when a project needs it. Strong working knowledge of TypeScript/Next.js, Python/FastAPI, and Postgres is expected and will be tested.
• Hands-on experience with LLMs in production: prompt design, agent orchestration (LangGraph or equivalent), tool use, RAG, and evals. You know where AI adds leverage and where it breaks down.
• Demonstrated ability to lead and grow engineers: code review, design review, structured feedback, and the patience to explain the same thing three different ways until it lands.
• Excellent spoken and written English. You can lead a technical discovery session by yourself, write a spec an engineer can build from the same afternoon, and present at a board-level review without notes.
• Commercial and analytical rigor: you think in unit economics, retention curves, and prioritization frameworks, not just features and timelines.
• High agency and composure under ambiguity. You make good calls with incomplete information, own the outcome, and do not wait for someone above you to clarify before acting.
• Willingness to travel to client sites across India, including Tier-2/Tier-3 cities and MSME floors, regularly.

Nice-to-Haves:

• Prior consulting, founder's office, or solutions-architect experience: you have been the person walking into a client with a half-formed brief and shipping something that worked.
• Exposure to MSME operations, supply chains, ERP systems, or Indian B2B SaaSyou understand the environment we deploy into.
• Open-source contributions, technical writing, or conference talksanything that shows you can make complex ideas accessible.

Effective Use of AI Coding Tools:

• You are expected to use Cursor, Claude Code, or equivalent AI coding tools as part of your daily engineering practice, not occasionally as a shortcut.
• The expectation is that you move significantly faster because of these tools while exercising sharp independent judgement about when the agent is wrong, incomplete, or misleading.
• At the senior level, your judgement about the tool is part of what makes you valuable: you know when to trust it, when to steer it, and when to set it aside.