Job Description

The Role

We're hiring a Product Manager who ships production work within their first 6-8 weeks. Not a stretch goal — the bar.

You'll own product direction across Etera's verticals, working backwards from users and business outcomes to define what gets built and in what order. You operate alongside engineering using the same agentic tools they use — Claude Code, Codex, Cursor — producing specs, documentation, prototypes, and product artifacts directly through them. You manage a physical team of humans and a virtual team of AI-powered workflows, and you're accountable for the output of both.

This role requires a sharp eye for UI/UX. Etera's product philosophy is premium, calm, and detail-obsessed — every pixel earns its place. You don't need to be a designer, but you need to see what a designer sees. You catch the misaligned padding, the inconsistent type weight, the interaction that feels off before anyone files a bug. You hold the quality bar for what the user actually experiences, not just what the spec described.

You report to the Head of Product. You work shoulder-to-shoulder with the Engineering Manager.

What You'll Own

• Product direction. You own the what and the when across Etera's verticals. What gets built, in what order, for whom, and why. You make prioritization decisions grounded in user insight, business impact, and engineering feasibility — not opinion, not trend-chasing. You scope ruthlessly: ship the right slice, validate through user feedback and data, and kill what doesn't work
• Specs that are ready to build from. You write lean, precise product specs — problem statements, success metrics, scope boundaries, edge cases. Good enough that an engineer can start building without a clarification meeting. You use Claude Code, Codex, and Cursor to produce these specs, generate user flows, build lightweight prototypes, and validate ideas before committing engineering time. Vague specs are bugs in the product process
• UI/UX quality. You are the last line of defense before anything reaches users. You review every feature, every screen, every interaction with the eye of someone who understands that trust is built through craft — typography, spacing, hierarchy, motion, responsiveness. You represent the user with conviction and rigor, and you push back when the output doesn't meet the bar, regardless of who produced it
• User and market understanding. You know who Etera's users are — corporate travel managers, business travelers in the GCC, travel operations teams replacing legacy TMCs. You talk to users. You read support tickets. You watch session recordings. You run discovery end-to-end: user interviews, competitive research, usability testing, data analysis. Your product instincts are grounded in evidence, not assumptions
• A virtual product team. Beyond the human team, you build and maintain AI-powered product workflows — competitive analysis, spec formatting, documentation updates, changelog generation, user feedback synthesis. You define what gets automated, configure the workflows, and validate the output. Every piece of repetitive product work gets removed from your plate so you focus on judgment and decisions
• Cross-functional coordination. You are the bridge between product, engineering, design, and business. You don't throw specs over the wall. You're in the thread when architecture decisions are made, when trade-offs surface, and when scope needs to flex. You equip sales, support, and marketing so they can effectively communicate value to customers. You make the call on scope; the Engineering Manager makes the call on implementation
• Shipping cadence. Features go to production in days and weeks, not months and quarters. You break large initiatives into shippable increments and resist the temptation to hold everything for a big reveal. You check with users and metrics to learn what works and what should be iterated on or killed. You measure yourself by what's live, not what's planned
• Metrics and outcomes. You define and analyze the metrics that inform product success. You instrument features before launch, monitor impact after, and use data to drive the next iteration. You present findings to the team with clarity and conviction, and you change course when the numbers say you're wrong
  
  

• Daily drivers — you're already proficient:
• Claude Code, Codex, Cursor — for spec writing, documentation, prototyping, agent workflow configuration, and direct production of product artifacts. This is non-negotiable
• Jira — for epic structuring and ticket management. You write lean epics with problem statements and scope boundaries, not verbose requirement documents
• Figma — for reviewing designs, annotating feedback, and understanding design constraints at the detail level. You spot issues before engineering starts building
• Expected — you know these or pick them up fast:
• Analytics tools (Mixpanel, Amplitude, or equivalent) — for measuring feature impact and making data-informed decisions
• Confluence or equivalent — for maintaining living documentation, PRDs, and product decision logs
• Markdown — your default writing format for specs, docs, and async communication
  
  

• 5+ years of product management experience shipping consumer or B2B SaaS products. You have a track record of features that went live, moved metrics, and survived contact with real users — not just roadmaps that got approved
• Proficiency with Claude Code, Codex, and Cursor. You use these tools daily to produce real work. Not as a curiosity. As infrastructure. If they've fundamentally changed how you work, you're in the right place
• A sharp, trained eye for UI/UX. You understand visual hierarchy, typography, spacing, interaction design, and responsive behavior at a level where you catch quality issues that most PMs miss. You have strong opinions on what makes a product feel premium versus generic, and you can articulate why
• Fast ramp-up ability. You can absorb a new product, market, and tech stack quickly enough to ship production work within 6-8 weeks. You've done this before — joined a team and delivered real output in the first two months
• Strong product writing. Your specs are precise, your prioritization rationale is clear, your async communication is sharp. In a remote-first, written-first culture, your writing is your primary tool for alignment
• Technical fluency. You don't write production code, but you understand how software systems work. You can read an API contract, follow an architecture discussion, and make scope trade-offs that account for technical complexity. Engineers respect your judgment because you understand their constraints
• Data-driven decision making. You define success metrics before building, instrument features, and use quantitative and qualitative data to inform what ships next. You present findings with rigor, not narrative convenience
• Experience managing distributed or remote teams. You've run product processes across time zones with async-first communication. Written documents are your default, not meetings
• Ownership mentality. You don't wait for permission. You don't escalate decisions you can make yourself. When something isn't working, you fix the process, not just the output

Skills Required

• Product Management