Rootly AI

Driving adoption & ease of use for an AI‑native incident platform used by NVIDIA, LinkedIn, Figma.

Members

1 Product Manager, PM, 2 Senior Designers, 15 Engineers

Members

1 Product Manager, PM, 2 Senior Designers, 15 Engineers

Members

1 Product Manager, PM, 2 Senior Designers, 15 Engineers

Timeline

Aug - Dec 2025 (Ongoing)

Timeline

Aug - Dec 2025 (Ongoing)

Timeline

Aug - Dec 2025 (Ongoing)

Role

Product & Visual Design Intern

Role

Product & Visual Design Intern

Role

Product & Visual Design Intern

TL; DR

What is Rootly?

Rootly is an AI-native, enterprise-grade on-call and  incident management platform loved by 100's of leading companies such as Cisco, NVIDIA, Figma, Squarespace, Canva, and more.

The Challenge

 Rootly's aggressive product velocity helped secure marquee enterprise customers, but rapid shipping introduced UX inconsistencies that created friction during competitive evaluations against mature incumbents like PagerDuty, Opsgenie and Incident.io.

My Role

As Rootly's design intern (and first-ever intern), I established a quality-first design culture during a critical growth phase. I led the delivery of 80+ UX improvements, redesigned core features interfaces, and automated marketing workflows that saved the teams over 10+ hours/campaign. I also co-authored Rootly's first brand guidelines.

From papercuts to product confidence

Led an initiative of low-impact, high-impact UX improvements, raising product quality

Some areas I worked on: Escalation Policy repeats and fallback, workflow condition, and custom form fields.

Leverage AI for speed and scalability

10x workflow for brand & marketing

Improving core platform features

Better view of many teams on-call schedules

Delivering the core product interface

A better way to view on-call schedules across multiple teams and shift owners

A better way to view on-call schedules across multiple teams and shift owners

Before:
  1. The on-call sidebar overwhelms users with too much buried schedule information.

  2. Screen space is wasted when few people are on call, and overcrowded when there are many.

  3. It’s difficult to find who’s on call across multiple teams.

  4. Switching between daily, weekly, and monthly views creates a fragmented mental model.

QoL Enhancements

Be able to page or declare an incident anywhere in the application. Quickly escalate an alert to an incidentt by auto-assigning teams and services

Be able to page or declare an incident anywhere in the application. Quickly escalate an alert to an incidentt by auto-assigning teams and services

 Removed ambiguity in on-call escalation flows by surfacing next-step actions and expected behaviors

 Removed ambiguity in on-call escalation flows by surfacing next-step actions and expected behaviors

Building an AI-driven visual playbook

The marketing team required a steady stream of visual assets, from social media posts, blog banners, and speaker cards to across multiple touchpoints. Initially, production was entirely manual and bottlenecked through a single designer (me), making the workflow unsustainable and impossible to scale as demand grew.


I designed and implemented an AI-powered asset generation system that transformed our production process from dependency to autonomy (Please reach out if you'd want to talk more about this!). In parallel, I took ownership of various verticals in our first brand guideline, developing what became distinct sub-brand expressions.

──── ୨୧ ────

Key Takeaways

Even though it has only been 2 months into my internship, I've learnt more than I could ever asked for.

🔎 Ownership in ambiguity

Startups don't wait for you to catch up. Unlike a “normal” internships, managers lack bandwidth for hand-holding and work isn’t assigned - it’s claimed. Within 2 first months, I delivered full-timer level impact by mastering self-advocacy: identifying gaps, proposing solutions, and proving value through consistent execution whether in brand or product. I learned that asking questions is how you accelerate growth and earn trust in fast-moving environments.

🛠️ Systems thinking over one-off solutions

The real achievement wasn't output volume, it was building a repeatable playbook that outlives individual projects. I applied impact-effort triage to prioritize quick wins, then codified this approach into our design system so future interns could replicate the same measurable impact. In complex platforms like on-call and incident management, stepping back to see systemic connections reveals that many problems share a single root cause. 

🔭 Innovation requires breaking patterns

Observing senior designers and PMs taught me how to operate within established systems, but real breakthroughs happen when you detach from existing variables. While mastery of current frameworks proves you can scale with the organization, strategic pattern-breaking introduces new possibilities. The challenge is knowing when to follow the system and when to rewrite it.

You might find these projects interesting ٩(ˊᗜˋ*)و