Skip to content

LankeshHalangoda

Product Experience Engineer

I connect product thinking, UI/UX, and engineering so SaaS products are clear to use and able to evolve as complexity grows.

/Services

  • Product Research

    User and stakeholder conversations, competitor study, and market research, held together as product discovery.

  • UX Research & Usability Testing

    Behaviour, usability studies, and task analysis, with friction treated as something to validate rather than guess past.

  • Product Strategy & Discovery

    Problem definition, opportunity mapping, and a product direction that feature prioritisation can stand on.

  • Information Architecture & Experience Design

    Product structure, workflows, navigation, and user journeys, organised so a complex system stays followable.

  • Product UI/UX Design

    Interfaces and interactions for responsive experiences, including the enterprise and SaaS products people work in all day.

  • Design Systems & Experience Standards

    Design systems, component architecture, and UX patterns that keep the experience consistent from one product to the next.

  • Product Prototyping & Validation

    Rapid prototypes and proofs of concept, tested with stakeholders and clients before the idea hardens.

  • Product Experience Engineering

    A validated experience carried into a production-quality frontend, with existing products improved in use.

/Experience

    • Lead the UI/UX decisions as Product Experience Engineer, then stay with the change until the interface is in production.
    • Take an internal initiative from a business goal to a workflow people can actually follow.
    • Sit with product, engineering, and stakeholders so the priority in the room is the one that gets built.
    • Prototype early, including with AI in the loop, and only carry forward the version that holds up in use.
    • User experience
    • Product design
    • UI/UX
    • Product experience
    • Shaped client solutions on the platform around the job the customer was trying to get done, not a generic setup.
    • Carried the work from discovery through configuration, build, and the support that follows go-live.
    • Treated the interface as part of the implementation, so the workflow and the screen were decided together.
    • Kept the client and the engineers in one conversation: demos, walkthroughs, and the feedback that changed the next version.
    • SaaS
    • UI/UX engineering
    • Solutions delivery
    • Teach diploma through undergraduate groups where people arrive with very different technical starting points.
    • Turn a concept into work students do in the room, then ask them to explain it back.
    • Judge the session by whether they can use the idea, not by whether they can repeat the slide.
    • Lecturing
    • Presentation
    • Public speaking
    • Built and kept production software running inside a small agile team, remote.
    • Turned a requirement into an interface that still made sense after the ticket was closed.
    • Wrote the technical notes and kept the client conversation clear enough that delivery did not depend on memory.
    • Software development
    • UI/UX engineering
    • Agile
    • Built features on both sides of the stack and learned where the frontend promise meets the backend limit.
    • Changed the interface when the ticket and the person using it were asking for different things.
    • Left handover notes so the next person could continue the work without a re-explanation.
    • User interface design
    • Full-stack development
    • Helped ship data-driven web applications and learned the stack by working inside it.
    • Built interface pieces that had to be correct on a real screen size, not only in a mock.
    • Fixed defects inside the team’s sprint rhythm, with seniors reviewing the change.
    • Software development
    • Front-end development
    • Helped build application features while learning how the screen, the API, and the data connect.
    • Worked the same way as the team: git, reviews, and a tracked list of tasks.
    • Wrote interactive interface pieces in JavaScript and had them read by someone else before they landed.
    • SDLC
    • Git
    • Software development

/Education

    • Upper Second-Class Honours in computer science and software engineering.
    • Learned to take a system apart, build it, and defend why it was built that way.
    • Research and team projects where the work had to be analysed, finished on a date, and presented.
    • Awarded with Merit.
    • Programming, systems design, and documentation, from a written requirement to software that runs.
    • Capstone work under a deadline and a review: plan it, test it, and explain the result.
    • Physical Science: mathematics and the habit of taking a problem apart before choosing an answer.
    • Selected for Wayamba University of Sri Lanka. The national intake timing did not fit, so the computing path continued privately.

/Certifications

UX & product

  • User Experience Design Course

    Encap Developers · Feb 2022

  • The Fundamentals of Digital Marketing

    Google Digital Garage · May 2022

  • SRE Fundamentals with Google

    Uplimit · Jan 2025

Platforms & engineering

  • REST API (Intermediate)

    HackerRank · May 2026

  • API Beginner Path v12

    Postman · May 2026

  • Introduction to Cybersecurity

    Cisco Networking Academy · May 2026

  • Linux Unhatched

    Cisco Networking Academy · May 2026

  • Python for Beginners by Department of Computer Science & Engineering, Faculty of Engineering

    University of Moratuwa · Apr 2022

/Recommendations

I had the privilege of working with Lankesh on a group project during our university days. As a fellow FE developer, I was truly impressed by his natural instinct for UI/UX design. He consistently prioritized user experience, always thinking about the bigger design picture, not just the code. A solid designer who genuinely cares about the user experience. Would recommend without hesitation.

Rashmi Liyanage

Software Engineer at Fcode Labs

Studied together · April 20, 2026

Tell me where the product gets hard to follow.

I take the bet, the journey, and the interface through to something a team can ship. SaaS and complex tools, including the quiet screens people actually use. Send the problem, who it is for, and what keeps breaking.

Lankesh Halangoda