Lecxe - Senior Product Manager - Product Engineering

Product Strategy & Roadmap:

• Own Lecxes 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 operating system, and sequence them to maximise 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 teams focus without being rigid about client needs.

Engineering Leadership & Daily Coding:

• 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.
• Own the architecture of Lecxes 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, security baseline. 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 & 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 Lecxe 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 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, 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.