I went through it as if I were a founder deciding whether to hire you. This is the version I woul...

I went through it as if I were a founder deciding whether to hire you. This is the version I woul...I went through it as if I were a founder deciding whether to hire you. This is the version I woul...

The network for creativity

Join 1.25M professional creatives like you

Connect with clients, get discovered, and run your business 100% commission-free

Creatives on Contra have earned over $150M and we are just getting started

Back to feedPost

Damilola Oludayo

• 18h

I went through it as if I were a founder deciding whether to hire you. This is the version I would publish.

While testing Expirel as a public user, I identified a usability issue in the email verification flow that resulted in a confusing authentication error after successful verification.

I documented the issue with clear reproduction steps, expected behavior, actual behavior, and testing environment details before submitting it to the product team.

The team successfully reproduced the issue, acknowledged the UX concern, and later confirmed that the reported bug had been fixed.

This case study demonstrates my approach to identifying reproducible issues, communicating them clearly, and contributing to product quality through structured QA and UX testing.

If you’re building a SaaS, mobile, or Web3 product and want critical issues identified before your users find them, I’d be happy to help.

qatester qaexpert bugreport Quality Assurance Testing Gmail

Franco Beltramella

pro

• Aug 4

A few months ago, this client hired me to build a website. Today, I was inside GoHighLevel building the system behind it: Booking, lead qualification, follow-ups, and CRM workflows. The best client relationships rarely stay inside the original scope.

Webflow gohighlevel freelance

Idris Lamina

pro

• Aug 3

Veranda, a luxury residential concept landing page

Veranda is a concept build I created for a fictional luxury residential brand. It is not client work or a real property. The images and hero motion were generated with AI as part of the creative process.

I wanted to explore something that matters when building high-fidelity landing pages: after several rounds of changes, how do you make sure the final page still looks like the design that was approved?

The site is built in Next.js with responsive layouts, self-hosted fonts, GSAP motion and an interactive walkthrough. I also built in a proper QA process around it, not just checking that the page loads and the buttons work.

It compares 12 sections across five screen sizes against approved visual baselines. It flags visual drift, missing baselines and changes that have not been reviewed. I also tested interactions, accessibility, contrast, performance, browser behaviour and reduced-motion states.

The main lesson for me was simple: a page can pass functional tests and still no longer be the page that was agreed.

UI Design Web Development GSAP Next.js Web Design

Maty Sandoval

max

• Aug 4

Building a QA process that flags visual drift against approved baselines is such an underrated skill, most people just eyeball it after changes go in. What first made you start checking for that instead of trusting the build looked right?