How do I approach Software Engineering Fundamentals interview questions?

Software Engineering Fundamentals questions require understanding of core concepts and practice. PracHub provides solutions with explanations to help you master software engineering fundamentals interviews.

What difficulty level is this interview question?

This is a medium difficulty Software Engineering Fundamentals question, commonly asked during Onsite rounds at Atlassian.

What role is this question designed for?

This question is commonly asked for Software Engineer candidates at Atlassian during technical interviews.

Design a CI/CD release notification service | Atlassian Interview Question

Quick Overview

This question evaluates object-oriented design skills, modeling of releases and changes, notification and event-driven system reasoning, and handling of deployment lifecycle concerns such as idempotency and version roll-forward behaviors.

CI/CD Release Notifier (OOD)

You are designing an object-oriented component for a service that performs an automated CI/CD release every day.

Requirements

Each release has a deployment version (e.g., v1 , v2 , v3 , …).
Each release contains multiple changes , and each change has an author (e.g., Jason, Mike).
When a deployment succeeds , the system must notify each author whose changes are included in that release.
- The notification should be a JSON-like payload.
- Example (conceptual): Jason and Mike are included in v1 → notify Jason and Mike with payload indicating version v1 .
If a deployment fails , the pipeline automatically rolls forward to the next deployment version (e.g., v1 fails → retry as v2 ).
- Authors whose changes were in the failed deployment should still be notified when their changes eventually deploy.
- In the follow-up deployment, the notification should still reference the version in which their change was originally scheduled (e.g., a change originally planned for v1 that rolls into the next attempt should still be reported as belonging to v1 ).

Deliverables

Propose classes/interfaces and their responsibilities (e.g., Release , Change , DeploymentAttempt , NotificationService , Notifier / Channel ).
Describe the main flows:
- recording a release and its changes/authors
- handling success/failure
- generating and sending notifications
Call out how you would handle:
- idempotency (avoid double-notifying)
- multiple authors per release
- retries / roll-forward versions
- extensibility (adding Slack/email/webhook channels)

Quick Overview

CI/CD Release Notifier (OOD)

You are designing an object-oriented component for a service that performs an automated CI/CD release every day.

Requirements

Each release has a deployment version (e.g., v1 , v2 , v3 , …).

Each release contains multiple changes , and each change has an author (e.g., Jason, Mike).

When a deployment succeeds , the system must notify each author whose changes are included in that release.

The notification should be a JSON-like payload.
Example (conceptual): Jason and Mike are included in v1 → notify Jason and Mike with payload indicating version v1 .

If a deployment fails , the pipeline automatically rolls forward to the next deployment version (e.g., v1 fails → retry as v2 ).

Authors whose changes were in the failed deployment should still be notified when their changes eventually deploy.
In the follow-up deployment, the notification should still reference the version in which their change was originally scheduled (e.g., a change originally planned for v1 that rolls into the next attempt should still be reported as belonging to v1 ).

Deliverables

Propose classes/interfaces and their responsibilities (e.g., Release , Change , DeploymentAttempt , NotificationService , Notifier / Channel ).

Describe the main flows:

recording a release and its changes/authors
handling success/failure
generating and sending notifications

Call out how you would handle:

idempotency (avoid double-notifying)
multiple authors per release
retries / roll-forward versions
extensibility (adding Slack/email/webhook channels)

Design a CI/CD release notification service

Quick Overview

CI/CD Release Notifier (OOD)

Requirements

Deliverables

Solution

Comments (0)

Design a CI/CD release notification service

Quick Overview

CI/CD Release Notifier (OOD)

Requirements

Deliverables

Solution

Comments (0)