Intent
A high-intent traveller still needs a clear promise before comparing price, coverage, and alternatives.
Roamless · (Senior) Product Manager — Web
Built inside the eSIM journey. Ready to own more of it.
I am a frontend developer with six years of experience building consumer web products. My current commercial work is on eSIM.io, where I build web experiences, ship A/B variants, work closely with analytics, and research competitors. I have not held a formal Product Manager title; I am applying because the product category and its web problems are already familiar, and I want to take direct responsibility for discovery, prioritization, delivery, and outcomes.
- Current commercial experience inside a consumer eSIM product.
- Hands-on A/B page delivery and close analytics collaboration.
- Six years of technical judgment across real web products.
- Competitor research grounded in build and measurement reality.
The familiar web journey
Connectivity starts before the device connects.
The web experience has to earn confidence before checkout, keep the technical promise legible through delivery, and create evidence for the next decision.
Confidence
Compatibility, activation, coverage, and payment must feel understandable before the user commits.
Delivery
Performance, tracking, state ownership, and failure handling directly affect trust in the journey.
Learning
A shipped variant matters only when evidence changes the next prioritization or product decision.
Relevant evidence
Product work already present inside my development work
eSIM.io · Teknasyon
Visit productMy current commercial context is a consumer eSIM purchase experience. It has given me direct exposure to how acquisition intent, product explanation, technical delivery, performance, experimentation, and analytics meet in the same web journey.
- Build web experiences with Next.js, TypeScript, and Tailwind CSS.
- Ship page variants used in A/B testing and collaborate closely with analytics.
- Research public competitor experiences and possible product moves.
- Contribute to SEO, PageSpeed, image loading, and user-facing improvements.
Experimentation and analytics
Building a variant is only the implementation layer of an experiment. Working close to analytics has made me increasingly interested in the hypothesis, measurement plan, interpretation, and next decision—not only whether a page shipped.
- Translate experiment direction into production-ready web variants.
- Bring feasibility, tracking, and delivery constraints into the conversation early.
- Use analytics collaboration to understand what should be investigated next.
- Treat implementation feedback as input to the product decision.
Nesine.com
Visit productHigh-traffic consumer React experience taught me that rendering, loading behavior, and regressions are product quality signals. I worked in a frontend monorepo while legacy .NET surfaces moved toward a React SPA.
- Used React Profiler and component update analysis.
- Worked with virtual-list patterns and production performance constraints.
- Shipped within established product and monorepo conventions.
- Connected technical performance with user-perceived quality.
Datapad
Visit productA data-focused startup gave me closer exposure to product decisions under uncertainty. It showed me the value of testing assumptions early and the cost of moving quickly without enough evidence.
- Built data-heavy product surfaces connected to multiple sources.
- Worked with Next.js, TypeScript, and Tailwind CSS.
- Participated closer to product decisions than in a conventional delivery role.
- Experienced fast iteration, changing assumptions, and startup pressure.
A non-traditional PM profile
What transfers directly—and what I am deliberately growing into
Positioning principle
Domain experience and technical fluency are evidence. They support a product transition; they do not manufacture a PM title or ownership history.
eSIM and travel-connectivity context
I already work inside a consumer eSIM product. The category vocabulary, user uncertainty, web purchase context, and need to translate technical connectivity into clear product communication are familiar rather than theoretical.
Consumer web product judgment
My experience spans acquisition-facing Next.js work, high-traffic React delivery, data-heavy products, performance, SEO, and complex UI states. I can reason about the web journey beyond an isolated screen.
Data and experimentation
I build A/B page variants and work closely with analytics. I understand the delivery side today and want direct accountability for framing the question, defining success, reading the evidence, and deciding what follows.
Technical fluency
Six years of engineering helps me surface dependencies, API and integration constraints, instrumentation needs, delivery risks, and UX consequences early. It supports product judgment without replacing customer or business evidence.
Cross-functional clarity
I already work across product, analytics, frontend, and backend-facing conversations. I can keep a customer or business outcome connected to implementation trade-offs throughout delivery.
An honestly framed growth edge
I have not held a formal Product Manager title or owned a multi-year PM roadmap. Direct customer interviews, prioritization authority, go-to-market, and adoption accountability are responsibilities I am intentionally seeking—not experience I claim to have already completed.
My reading of Roamless
A web surface turning telecom complexity into borderless confidence
Public-source research kept separate from claims about Roamless's internal roadmap, metrics, or team decisions.
01
Roamless combines one global eSIM with pay-as-you-go credits, data plans, calls, SMS, and local numbers across 200+ destinations.
The customer promise is simple, but the underlying choice and connectivity system is not. Product work has to make coverage, price, compatibility, activation, balance, and continuity feel understandable without exposing unnecessary telecom complexity.
Roamless product overview02
The web is already more than a marketing surface: users can create an account, purchase credits or plans, and access balance and usage through browser-based experiences.
Owning web means connecting acquisition, checkout, account state, and repeat use. That is a product system with conversion and retention consequences—not a collection of landing pages.
Roamless account overview03
The role owns an established high-traffic website and a new web product from discovery through delivery and adoption.
The assignment combines optimization with zero-to-one work. It needs someone who can learn from existing behavior while keeping technical constraints, positioning, and measurement aligned from the start.
Role description04
Roamless announced a $12M Series A after reporting nearly five-times year-on-year growth, while the role describes a globally distributed team scaling beyond 70 people.
That suggests a product organization formalizing while the market and surface area are still moving quickly. Clear decisions, focused experiments, and cross-functional communication become more important as the company scales.
Series A announcement05
Roamless describes its culture through customer curiosity, speed, looking under the hood, focus, and ownership.
That combination is a credible fit for a technical product transition: stay close to the customer, understand the system deeply, and remain accountable for what the team learns and ships.
Roamless careersCommunication proof
Making technical trade-offs understandable is already part of my work
Product ownership depends on making a problem, assumption, constraint, and decision legible across disciplines. My public talks are one practical signal of that communication habit.