# Raam Pujangga Sadewa

> Product Design Engineer for checkout, payments and marketplace products. Almost 7 years with teams in Indonesia, Singapore, Sri Lanka, the US and New Zealand. Open to remote Senior Product Designer roles.

This is the text version of the portfolio. The home page is an interactive sticker desk, so the same facts are written out here for AI tools and screen readers.

## About

Hi, I'm Raam. I design checkout, payments and marketplace products, where small friction costs real money.

For almost 7 years I've worked with teams in Indonesia, Singapore, Sri Lanka, the US and New Zealand. At FLIK I own merchant products end to end, from research and PRDs to QA and launch, and I build in code with Claude Code.

- **Location:** Remote · Jakarta (UTC+7)
- **Email:** raamps3@gmail.com
- **Resume (PDF):** https://raamportfolio.vercel.app/RaamPujanggaSadewa_CV.pdf

## How I work now

At FLIK, with no dedicated PM, I take merchant features from first request to release:

1. **Requirements:** Gathered from Sales, the CEO and merchant feedback.
2. **PRD:** I write it and agree the scope with the team.
3. **Design:** Flows and high-fidelity screens.
4. **Build:** In code with Claude Code, on the merchant dashboard.
5. **QA and release:** Tested in staging and production, then announced to the right merchants.

## Results

- **1 mo → 1 wk**: Refund time, Pegipegi
- **+35%**: Class completion, Sekolah.mu
- **100K+**: Downloads, Tetanggaku
- **350+ hrs**: Teaching UI/UX

## FLIK: Making one-click checkout worth logging in for (2023–25)

Source: https://raamportfolio.vercel.app/work/flik-checkout

FLIK's checkout is only one-click for shoppers who log in, yet most of them skipped login. Over four phases I found out why, and redesigned the way into checkout so it's faster and gives shoppers a reason to log in.

- **Problem:** FLIK's value (saved details, cashback, one-click buying) only works when shoppers log in. Once guest checkout launched, it out-converted login by 5.15%, and later shoppers started dropping off at the login step.
- **Role:** Product Designer, leading the research. One of two designers, working with the CEO, two PMs and engineering.
- **What I did:** Four phases of research and redesign: a heuristic audit, an unmoderated Maze study, a session fix with engineering, and a one-step flow refined through guerrilla testing.
- **Outcome:** Shipped a one-step checkout that shows the shopper's potential reward right where they pay, and logins that last a month instead of 48 hours. Conversion impact isn't measured yet (see “Impact, honestly”).
- **Timeline:** Aug 2023 – Jun 2025
- **Platform:** Mobile and desktop web checkout, embedded on merchant sites
- **Methods:** Heuristic evaluation, funnel data, unmoderated testing (Maze), guerrilla testing

### The short version

*Video: The whole project in about 80 seconds, narrated: https://raamportfolio.vercel.app/videos/flik.mp4*

### The trade-off behind every phase

Brands add FLIK to their own websites as a one-click checkout. When a shopper clicks “checkout” on the merchant's site, they land on FLIK. If they're logged in, their address and payment are already filled in, on every FLIK merchant, and they earn cashback.

*Diagram: Checkout flow: browse, add to cart and click checkout on the merchant's site; logged-in shoppers go straight to FLIK checkout, others log in or register first. The merchant's site hands the shopper over to FLIK at checkout. This project covers the FLIK side.*

> The easiest path for a shopper is guest checkout. The path that makes FLIK valuable is logging in. Every phase of this project was about making checkout easier without making login feel optional.

### Four phases in 30 seconds

- **Phase 1 · Audit and redesign:** No data yet, so I started with a heuristic review of the live checkout and shipped a cleaner page.
- **Phase 2 · A 5.15% gap:** Guest checkout beat login. Research showed shoppers wanted the rewards but chose guest because it felt faster.
- **Phase 3 · A drop-off at the login step:** A one-month session fix shipped right away, while a one-step flow was tested.
- **Phase 4 · Balancing the two paths:** Three more test rounds of a cashback-first checkout, then the version that's live today.

### Phase 1 · Start with what you can see

- **Trigger:** An open brief from the CEO: improve checkout. No target metric, no analytics.
- **Method:** Heuristic evaluation on Android, then 4 rounds of feedback with the CEO.
- **Result:** A clearer checkout, plus FLIK's first desktop version. Not measured.

This was my first project at FLIK, and the company was a year old, so there was no data to start from. I reviewed the live checkout against standard usability heuristics and found **14 issues**. Most were about clarity: a logo too small to read, repeated information, a cluttered coupon section, and a “Pay now” button that failed silently when no courier was chosen.

*Image: The original checkout annotated with 14 numbered usability issues. The 14 issues, each mapped to a usability heuristic.*

I took low-fidelity fixes through four rounds with the CEO, then moved to high fidelity. With no PM yet, I also briefed engineering and ran the handoff. The CEO then asked for a desktop version, which FLIK hadn't had.

*Image: Checkout page before and after the phase 1 redesign. Before and after: shipping, payment, cart and order summary in clear sections.*

> Takeaway: without a baseline, I couldn't show whether this worked. From then on, each phase started from data or research.

### Phase 2 · Shoppers wanted rewards, but chose speed

- **Trigger:** Three months after guest checkout launched, it converted **5.15% better** than login.
- **Method:** Unmoderated study in Maze with recent guest and logged-in buyers.
- **Result:** A new understanding of the problem, and a recommendation to make the reward visible.

FLIK added guest checkout to reduce friction: pay with just a name, email and phone number. Another designer led it. I'd argued it would undercut login, then committed to making it work. Three months later the data showed the risk: on the page where shoppers choose, guest checkout was winning.

*Diagram: Guest checkout added a log-in-or-guest choice before checkout; guest converted 5.15% better than login. Guest checkout added a choice before checkout, and guest won it.*

*Image: The login page with Checkout Now and Save more by logging in buttons, and the 5.15% gap. The decision page itself: “Checkout Now” for guests versus “Save more by logging in or signing up”.*

The obvious move was to rearrange the buttons. I wanted to know **why** people chose guest first. The study asked what shoppers cared about before showing any screen, then had them check out and explain their choice.

- **100%** said they'd rather save with rewards
- **68%** still chose guest checkout
- **9.1/10** rated checkout easy

> Shoppers wanted what logging in gives them, but chose guest because it felt faster, even though logged-in checkout is the faster one. The benefit of logging in was invisible.

**Decision:** keep the layout, because guest checkout supported the business priority at the time (transaction volume), and make the benefit of logging in obvious, with clearer copy on the login prompt and a subtle shimmer to draw the eye. Engineering had other priorities, so it waited, but this insight shaped every phase after.

### Phase 3 · Fix the leak now, redesign the step next

- **Trigger:** The PM spotted a significant drop-off on the log-in-or-guest page.
- **Method:** Root cause with engineering, then guerrilla testing of a one-step flow (10 people, Figma prototype).
- **Result:** Logins extended from 48 hours to 1 month (shipped). One-step flow validated, with a new risk.

*Diagram: The same flow with the log-in-or-guest step circled as the drop-off point, and returning shoppers sent back to it every 48 hours. Shoppers were leaving at the decision step itself, and expiring logins sent returning shoppers back to it.*

**The quick fix.** Logged-in shoppers should skip that page entirely, but logins expired every 48 hours, sending returning shoppers back to it. The 48 hours existed for security on shared devices and to keep stored carts small. Engineering said cart size was manageable. As for security, being logged in never moves money on its own: QRIS and virtual-account payments are approved in the shopper's own bank or e-wallet app, and cards go through 3-D Secure. So we extended logins to **one month**, and it shipped.

**The bigger fix.** After a competitor review and a brainstorm with the PM, we proposed removing the page altogether: click checkout, land on checkout.

*Diagram: Before: click checkout, a logged-in check, then a log-in-or-guest choice. After: click checkout and land straight on FLIK checkout. From a fork to a straight line.*

It was a big change, so we tested it quickly: 10 people recruited near our office tried today's flow and the prototype, on phones and laptops.

- **What worked:** it felt more straightforward, with fewer decisions and less commitment before seeing the order.
- **What didn't:** people still didn't know logging in earns cashback, and guest checkout became even more dominant.

> We'd removed the friction but created a new problem: with no reason to log in shown, guest checkout would win even more often.

### Phase 4 · Make logging in the obvious choice

- **Trigger:** The one-step flow made guest checkout too dominant.
- **Method:** Three more rounds of iteration and usability testing.
- **Result:** Clicks between guest and login evened out in testing. A one-step checkout that shows the reward shipped.

The answer came from phase 2: shoppers log in when they can see what they'll get. So I tested a checkout that opens with the shopper's **actual potential cashback** and a single “Continue with FLIK” button, while guest checkout stays one tap away. It's one step for everyone, with a visible reason to log in.

The CEO preferred a different look for the final screen, so I rebuilt it around the same tested principles: one step for everyone, with the shopper's **potential reward** shown in the cart and right under the pay button. That version is live today.

*Image: Four versions of FLIK checkout: the original, the phase 1 redesign, the tested cashback-first version, and the live version. From left: the original, phase 1, the tested cashback-first version, and the checkout that's live today. Contact details are blurred.*

### Impact, honestly

- **Shipped:** a redesigned checkout and FLIK's first desktop version, logins that last a month instead of 48 hours, and a one-step entry that shows the shopper's potential reward where they pay.
- **Changed how the team saw the problem:** the gap between guest and login was about perceived value, not button placement.
- **Not measured yet:** FLIK doesn't currently track the checkout funnel, so I can't claim a conversion number. The first thing I'd measure is the share of logged-in checkouts before and after launch, then A/B test how the reward is shown.

### What I'd do differently

- **Agree on a success metric before designing.** Phase 1 shipped with nothing to measure it against; I now put a metric in every brief.
- **Ask for an experiment before big launches.** I disagreed with how guest checkout launched; a test with a clear success metric would have settled it with data.
- **Pair small tests with funnel data.** Ten guerrilla participants give direction, not proof.

> "I highly recommend Raam as a talented product designer. He elevated my vision beyond expectations with his creativity and user-centric mindset. A true team player, he integrates user needs seamlessly and delivers intuitive designs. Any project in his hands will exceed expectations!" (Kandika Bagaskara, Worked with Raam at FLIK)

## Pegipegi: Cutting refund time from a month to a week (2022)

Source: https://raamportfolio.vercel.app/work/pegipegi-refunds

Travellers waited about a month for refunds because every request passed through manual checks between two teams. Redesigning the back-office workflow brought that down to about a week.

- **Problem:** A refund took about a month to reach the traveller, because Customer Service and Finance handled every request by hand.
- **Role:** UX Designer. I worked with the PM, the Finance and Customer Service teams, and engineering.
- **What I did:** Shadowed and interviewed both teams, mapped the process, and designed a new workflow and an internal refund dashboard over 4 iterations.
- **Outcome:** Refunds reach travellers in about a week instead of a month: 76% faster.
- **Timeline:** 1.5 months, 2022
- **Users:** Internal: Finance and Customer Service teams
- **Methods:** Shadowing, interviews, process mapping, co-design sessions

### The short version

*Video: The whole project in about 85 seconds, narrated: https://raamportfolio.vercel.app/videos/pegipegi.mp4*

### Why this mattered

A refund usually follows a cancelled flight, hotel or train: a moment when the traveller is already let down. Waiting **about a month** for their money turned one bad experience into two, and every slow refund meant more follow-up for the teams handling it.

The work behind each refund was almost entirely manual. That made it slow, and every manual step was another chance for a mistake.

### Where the month went

I shadowed the Finance and Customer Service teams and mapped a refund from request to payout. The delay wasn't one slow step; it was the manual work between steps.

*Diagram: The old refund process: Customer Service created each request, Finance sorted and checked them by hand, and invalid data sent Customer Service back to the traveller; about a month per refund. The old process. Red steps were done by hand: Finance sorted and checked every request, and Customer Service chased travellers to fix their data.*

- **Customer Service** created each refund request by hand, then contacted users to validate their details.
- **Finance** sorted and grouped the requests by payment method, then checked every request's data one by one before approving.
- Neither team could easily see where a refund was, so requests stalled between them.

### Three decisions

### Decision 1: Let the system do the sorting

- **Context:** Finance spent its time grouping requests by payment method before any real checking started.
- **Instead of:** Give Finance a better spreadsheet or filters.
- **Why:** Grouping follows fixed rules, so it doesn't need a person. Removing it frees Finance for the checks that do.
- **Result:** The new flow groups requests by payment method automatically.

### Decision 2: Ask the traveller directly, not through a person

- **Context:** Customer Service had to contact users one by one to confirm their refund details.
- **Instead of:** Add a checklist to make the manual follow-up faster.
- **Why:** The traveller is the person who knows their details. Asking them directly removes a round trip between two people.
- **Result:** The system now contacts users to validate their data, a step that used to be manual.

### Decision 3: One dashboard both teams share

- **Context:** Refunds stalled because neither team could see where a request was.
- **Instead of:** Separate tools for each team, with handoffs over chat.
- **Why:** A shared view of every refund and its status removes the “where is this one?” questions between teams.
- **Result:** A payment-out dashboard listing every refund, its status and the next action.

*Diagram: The new refund process: Customer Service enters one field and the rest auto-fills, the system groups requests and asks travellers to confirm their data; about a week per refund. The new process. Green steps are automated: entry auto-fills, the system groups requests and asks travellers to confirm their own details. Finance still checks each request.*

### Getting both teams on board

Back-office changes fail when the people doing the work don't trust them. I ran brainstorming sessions with Finance, Customer Service and product, then took the design through **4 rounds of feedback** with the PM and both teams until the concept was approved.

*Image: Board of payment-out dashboard explorations dated 24 and 25 August 2022. Two days of dashboard explorations, August 2022.*

### Impact

- **1 mo → 1 wk** for a refund to reach the traveller (approx.)
- **76%** faster

### What I'd do differently

- Measure more than speed. Tracking errors and refund-related contacts would show the full effect on both teams and travellers.
- Treat internal tools like products. The people using them every day are users too, and their speed becomes the customer's experience.

> "I highly recommend Raam as a diligent product designer. His strong user-centric mindset and attention to detail result in intuitive designs. He integrates user needs seamlessly and embraces feedback, making him a valuable team player and asset in product design." (Athur Muharam, Worked with Raam at Pegipegi)

## Tetanggaku: Designing a ride-hailing ecosystem as the only designer (2022–24)

Source: https://raamportfolio.vercel.app/work/tetanggaku

A small team set out to compete with Gojek and Grab. As the only designer for two years, I designed every screen across three apps, which together passed 100K downloads.

- **Problem:** Launch a ride-hailing service in a market Gojek and Grab already own, with a fraction of their team and no design function.
- **Role:** Sole UI/UX designer (freelance) for two years, working directly with the PM, CEO and CTO.
- **What I did:** Designed every screen of the customer app and both driver apps, from requirements to developer walkthroughs.
- **Outcome:** 100K+ downloads and 4.3★ on Google Play from 2,200+ reviews.
- **Timeline:** Apr 2022 – Mar 2024
- **Company:** Tetanggaku (PT. Tetangga Saling Bantu), Indonesia
- **Apps:** Customer · motorbike driver · car driver
- **See it on Google Play:** https://play.google.com/store/apps/details?id=com.tetanggaku

### The short version

*Video: The whole project in about 70 seconds, narrated: https://raamportfolio.vercel.app/videos/tetanggaku.mp4*

### The challenge

Tetanggaku, “my neighbour”, entered a market where riders and drivers already know Gojek and Grab inside out. The team was small, briefs were usually verbal, and there was no other designer, so the experience had to be right without the time or people to explore widely.

- **100K+** downloads
- **4.3★** Google Play, 2,200+ reviews
- **3** apps, one designer

### Three decisions

### Decision 1: Familiar patterns over novel ones

- **Context:** Every rider and driver in Indonesia already knows how Gojek and Grab work.
- **Instead of:** Design a distinctive new booking flow to stand out.
- **Why:** A new flow would force people to relearn something they do daily, for no benefit. A small team's effort was better spent making the familiar flows clear and quick.
- **Result:** I studied both leaders' flows and adapted their proven patterns to what our team could build and maintain.

### Decision 2: Straight to high fidelity, with early alignment

- **Context:** Requirements arrived as verbal briefs, and the business needed screens fast.
- **Instead of:** The textbook path: wireframes, then low fidelity, then high fidelity.
- **Why:** With one designer, each extra stage delayed delivery. Shaping requirements with the PM and aligning with the CEO and CTO up front reduced the risk of skipping stages.
- **Result:** I designed directly in high fidelity and walked the team through each journey before it was built.

### Decision 3: Design both sides of every trip together

- **Context:** A ride involves two people looking at two different apps at the same moment.
- **Instead of:** Design the customer app first and treat the driver apps as an afterthought.
- **Why:** A confused driver means a late ride, so driver experience is customer experience.
- **Result:** Customer and driver screens were designed as one journey, so what a rider sees always matches what their driver sees.

### What I designed

*Diagram: One trip across both apps: the customer books, is matched, tracks the driver, rides, then pays and rates; in step, the driver goes online, gets the order, accepts, picks up, drops off and gets paid. One trip, two apps. Blue lines are the moments where what the rider sees has to match what the driver sees.*

- **Customer app:** Motorbike and car rides, item delivery (Titip), e-wallet, referral program and more.
- **Motorbike driver app:** Receiving and managing orders, e-wallet, referral program and more.
- **Car driver app:** The same core flows, adapted for car trips.

### Close to the users

In my last few months at Tetanggaku, the team also asked me to host its **TikTok Live** for about three months: teaching drivers how to use the app and promoting the service.

*Image: Raam hosting a TikTok Live on the Tetanggaku account. Live on Tetanggaku's TikTok, walking drivers and riders through the app.*

It turned into a regular feedback loop. Drivers asked their questions live, and where they got stuck showed me what wasn't clear yet. Some of that feedback went straight back into the design.

### What I'd do differently

- Build a small component library earlier. Designing three apps alone, shared components would have kept them consistent with less effort.
- Write lightweight specs. Verbal briefs were fast, but a one-page summary per feature would have reduced back-and-forth during development.

> "The team understood our complex requirements and provided a user-friendly, high-performing website that stands out in the market." (Bairuni Hasibuan, CEO, Tetanggaku)

## Experience

### FLIK: Product Design Engineer (Jul 2023 – Present)

A merchant checkout and payments platform. Brands add FLIK's one-click checkout to their own sites, plus a shipping aggregator (expanding to Malaysia and Singapore), a landing page builder, QRIS payments and merchant financing. · Jakarta

**Owning the product end to end (late 2025 – now)**

- With no dedicated PM, I own merchant products from start to finish: gathering requirements from Sales, the CEO and merchant feedback, writing PRDs, designing, briefing engineering, and running QA in staging and production.
- Plan and send release announcements to targeted merchant segments (SendGrid), deciding who gets each update.

**Building in code (2026)**

- Building FLIK's merchant dashboard with AI-assisted development (Claude Code), taking features from design to working code.
- Built AI research tooling (Claude Code + Google Apps Script) that turns a research question into a live survey and a synthesised findings deck.

**Research and checkout**

- Led a four-phase redesign of checkout entry (Aug 2023 – Jun 2025): a heuristic audit, an unmoderated Maze study, guerrilla testing and three rounds of refinement.
- Found why shoppers chose guest checkout over login (a **5.15%** conversion gap): **68%** picked guest because it felt faster, though all of them valued rewards.
- Shipped a one-step checkout that shows the shopper's potential reward where they pay, and worked with engineering to extend logins from **48 hours to one month**.
- Optimised login and guest checkout flows to reduce friction and drop-off for first-time shoppers.
- Ran a three-month post-onboarding study with merchants to find behaviour patterns and engagement gaps.

**Platform and design system**

- Played a key role in FLIK's move into shipping aggregation: redesigned the merchant dashboard and designed new logistics products, contributing to merchant acquisition.
- Started and established FLIK's design system to improve consistency and speed up design-to-development.
- Partner with Operations, Sales and Engineering to turn business needs into specs and user-centred solutions.

### GoodHood.SG: Product Designer (Jan – Jul 2023)

A hyperlocal community platform in Singapore where neighbours buy, sell, donate and share services. · Remote · Singapore

- Worked daily with the CEO, turning the product vision into concrete designs and feature specs.
- Ran competitive analysis across local and international platforms to find gaps, differentiation and feature priorities.
- Owned end-to-end design, from user flows and interaction patterns to aligning design decisions with business goals.
- Worked closely with developers on requirements and feasibility throughout implementation.
- Led design QA, reviewing every release for visual accuracy and usability.

### Pegipegi: UX Designer (May 2022 – Jan 2023)

One of Indonesia's leading travel booking platforms for flights, hotels and trains. · Hybrid · Jakarta

- Cut refund time from **about a month to about a week (76% faster)** by redesigning the manual refund workflow with the Finance and Customer Service teams, based on shadowing, interviews and four rounds of iteration.
- Led research and redesign of the homepage, using user interviews and desirability studies to improve content hierarchy, navigation and engagement.
- Designed and launched a referral program to support user acquisition and retention.
- Designed e-wallet and credit card management, giving travellers more flexible ways to pay.
- Created user flows, wireframes and low-fidelity designs, and validated decisions with research and stakeholders.

### Sekolah.mu: UX Designer, Academics tribe (May 2021 – May 2022)

Indonesia's first blended learning platform, combining online and offline learning for students, educators and professionals. · Remote · Jakarta

- Raised class completion by **35%** with a redesigned, more engaging learning page.
- Led the revamp of the Academic Dashboard, making it faster and easier for academic and operations teams.
- Set UX standards for the Academic Dashboard to keep it consistent and scalable.
- Owned end-to-end UX for academic features, turning complex business and academic requirements into clear flows, working with Product, Engineering, Business and Academic teams.

### Axiata Digital Labs: Lead UI/UX Designer (Dec 2020 – May 2021), Associate UI/UX Designer (Dec 2019 – Dec 2020)

Axiata Group's digital consultancy, headquartered in Sri Lanka, delivering telecom, fintech, analytics and cloud products across Asia. · Jakarta

**As Lead**

- **Promoted to Lead within 12 months.** Led and mentored a team of three designers, assigning work to each person's strengths.
- Helped win client deals worth **$60K+** through pitch strategy, design narratives and live pitches.
- Facilitated Design Sprints with clients to define problems and validate ideas before development, and taught the team the method.
- Earned client trust and follow-on work for the next MVP phase through design quality and clear expectation management.

**As Associate**

- Started as the only UI/UX designer in the Indonesia office, owning design for several clients while working with engineers in Sri Lanka.
- Delivered multiple client projects as a fresh graduate, and helped create pitch and stakeholder decks.

### Freelance

**Service-Plus Connect** (🇺🇸 United States): Product Designer, Dec 2024 – Aug 2025

- Designed the entire platform, a marketplace connecting customers with service providers, for both sides.
- Worked with the CEO on product strategy and key features, and bridged the CEO and developers to keep delivery on track.
- Ran development in Jira: writing tickets, tracking progress and prioritising work.
- Helped hire the product and engineering team, and created pitch decks for business development and funding.

**Tetanggaku** (🇮🇩 Indonesia): UI/UX Designer (sole designer), Apr 2022 – Mar 2024

- Designed every screen of an Indonesian ride-hailing ecosystem, which reached **100K+ downloads** and **4.3★** on Google Play.
- Customer app: motorbike and car rides, item delivery (Titip), e-wallet, referral program and more.
- Driver apps: order handling for motorbike and car drivers, referral program, e-wallet and more.
- Hosted Tetanggaku's TikTok Live for about three months, teaching drivers the app and promoting the service; drivers' questions fed back into the design.

**OOSH** (🇳🇿 New Zealand): UX Designer

- Designed flows for posting Facebook, Instagram, TikTok and Snapchat content to car-mounted digital billboards through the OOSH app, plus UX improvements across the app.

**WAWN** (🇸🇬 Singapore): UX Designer, Apr – Sep 2022

- Designed a social app for Chinese speakers worldwide: design system, onboarding, login and registration, creating posts, the home feed and comments.

**Artpedia** (🇮🇩 Indonesia): UX Designer, Mar – Oct 2022

- For Indonesia's first NFT marketplace: revamped the product detail page and analysed MagicEden, LooksRare, Coinbase NFT and Paras Comic.
- Designed NFT transfer, a WYSIWYG editor, ERC-1155 support, a launchpad and centralised NFTs.

### Teaching

350+ hours teaching UI/UX.

- **Cakap**, UI/UX Design Facilitator (Sep – Dec 2024): UX research, intro to UI/UX, design thinking, portfolios and soft skills, for college students.
- **Binar Academy**, UI/UX Design Facilitator (Feb – Mar 2024): UX research, Figma, wireframes, low- and high-fidelity design, prototyping and portfolios, for fresh graduates.
- **Binar Academy**, UI/UX Design Facilitator (Jun – Sep 2022): The same bootcamp curriculum, for a mixed cohort.

## Lab: tools built with Claude Code

- [Survey automation](https://github.com/RaamPujanggaSadewa/survey-automation): Describe a research question; it writes the survey, creates the Google Form and summarises the answers.
- [PRD automation](https://github.com/RaamPujanggaSadewa/prd-automation): Turns a product brief into a structured PRD draft.
- [Design automation](https://raam-design-automation.vercel.app): Four ways to go from a reference to working code with AI, each in a single prompt.
- [QA with Playwright](https://github.com/RaamPujanggaSadewa/Playwright-Exercise): Automated tests to understand how QA protects product quality.

## Recommendations

> "I highly recommend Raam as a talented product designer. He elevated my vision beyond expectations with his creativity and user-centric mindset. A true team player, he integrates user needs seamlessly and delivers intuitive designs. Any project in his hands will exceed expectations!" (Kandika Bagaskara, Worked with Raam at FLIK)

> "I highly recommend Raam as a diligent product designer. His strong user-centric mindset and attention to detail result in intuitive designs. He integrates user needs seamlessly and embraces feedback, making him a valuable team player and asset in product design." (Athur Muharam, Worked with Raam at Pegipegi)

> "The team understood our complex requirements and provided a user-friendly, high-performing website that stands out in the market." (Bairuni Hasibuan, CEO, Tetanggaku)

> "Working with Raam was a pleasure. He elevated my vision beyond expectations with his creativity and expertise, making the process seamless. I highly recommend him—any project in his hands will exceed expectations!" (Ibraheem Olasupo, CEO, Service-Plus Connect 🇺🇸 · freelance client)

> "Raam is great to work with. Smart and experienced" (Bevan Hockly, CEO, OOSH 🇳🇿 · freelance client)

## Education

- B.Eng. Computer Engineering, Telkom University (2015–2019). IEEE publication: *Fire Detection Using Image Processing Techniques with Convolutional Neural Networks*.

## Contact

- **Email:** [raamps3@gmail.com](mailto:raamps3@gmail.com)
- **LinkedIn:** [in/raamps3](https://www.linkedin.com/in/raamps3)
- **GitHub:** [RaamPujanggaSadewa](https://github.com/RaamPujanggaSadewa)
- **Resume:** [Download PDF](https://raamportfolio.vercel.app/RaamPujanggaSadewa_CV.pdf)
- **Call:** [Book 30 minutes](https://calendly.com/raamps3/30min)