Assistant Product Manager (Laravel)

Core Product Skills (Non-Negotiable) • Break high-level requirements into clear, structured product specs. • Create wireframes, user flows, acceptance criteria, and edge-case handling. • Prioritize features based on impact vs. complexity. • Define MVPs ruthlessly and prevent scope creep. • Run backlog grooming, sprint planning, and feature readiness checks.

This is not a project coordinator — this is a product thinker.

Technical Understanding (Laravel + Vue.js)Minimum Expectations • Understands how Laravel MVC architecture works (routes, controllers, jobs, queues, Eloquent ORM). • Understands Vue.js component structure, props, state flow, and API integration. • Can discuss feasibility with engineers without looking lost. • Knows what is “easy vs. hard” in Laravel + Vue, so they don’t propose impractical ideas. • Able to read code snippets or API responses well enough to make informed product decisions.

If they cannot have a technical conversation with developers, they will become a bottleneck.

Execution & Delivery

This is where weak PMs fall apart. We need someone who can: • Own the product roadmap at a tactical level. • Write clear PRDs, user stories, and acceptance tests. • Track development progress and unblock issues quickly. • Test features before calling them “done.” • Coordinate between designers, developers, QA, and stakeholders. • Ensure features ship correctly, not just “done on Jira.”

SaaS & Web App Experience

They must have worked on: • Multi-role systems, permissions, and dashboards. • CRUD-heavy backend tools, admin panels, data tables, and filters. • User onboarding and retention flows. • Notification and communication flows (email, SMS, in-app).

Anyone who only worked on mobile apps or small websites: reject.

Soft Skills That Actually Matter • Strong analytical thinking — asks the right questions. • Writes clearly and concisely (weak writers = weak PMs). • Pushes back when requirements are weak or unrealistic. • Communicates with developers in engineering language, not fluff. • Obsessed with product quality, not just feature count.

Expected Outcomes

A strong Assistant PM should: • Reduce back-and-forth between founders and developers. • Increase delivery speed by removing ambiguity. • Improve product quality through better specs and testing. • Bridge the gap between business → design → engineering. • Identify workflow inefficiencies and propose improvements.

Job Types: Full-time, Permanent

Pay: ₹700,000.00 - ₹1,000,000.00 per year

Benefits: • Flexible schedule • Leave encashment • Paid sick time • Paid time off

Work Location: In person