Joined as Backend Developer... But Couldn't Write Code

SDLC AWS CodePipeline GitHub Rulesets IAM Process Design

Joined Helprr.ai as a backend developer, but recognized an immediate need for engineering structure. With no standard workflows or CI/CD feedback in place, I didn't wait. I designed and led the adoption of a complete SDLC foundation.

Backend Developer → Backend Development Lead

The Problem

1. No Requirements-to-Code Workflow

No documentation system to translate CEO/PM requirements into implementable specs. Developers couldn't design code or database without clear specifications.

2. Isolated Development Environment

Production branch exposed to human error, causing CEO/PM hesitant to give developer access to base repo. Had to work on forked repo, but no third-party credentials, environment config, or mock database existed.

3. No CI/CD Feedback Loop

Developers couldn't see if integration succeeded, failed, or why it failed on the pipeline.

What I Did

I didn't limit myself to my position title.

The situation was challenging: part-time schedules across the team, no development process, limited real-time communication. Development couldn't move forward.

To unblock my own development and set up future developers, I designed and led the adoption of a workflow system that guides each role naturally through the SDLC. That system is now the team's standard reference.

The Result

Led team's first successful SDLC by establishing development infrastructure and workflow:

Workflow: Unblocked stalled development by designing unified feature specification format combining user stories, wireframes, and API contracts, and leading cross-functional team to adopt it as standard reference.

Infrastructure: Resolved bottlenecked backend code integration workflow by configuring GitHub Ruleset and AWS IAM policies on CodePipeline, enabling developer-owned code-to-staging feedback loop.

Role Info

Position	Backend Development Lead
Type	Part-time
Period	Sep 2025 - Present
Location	Toronto, Ontario, Canada (Remote)

Responsibilities: Lead backend development for mental wellness application adding mood-based care features. Mentored junior backend developer through database schema design and API implementation.

SDLC Foundation I Built

Context: Part-time team, Students with limited SDLC experience, Startup environment

Unified Feature Specification

SDLC: Planning & Analysis, Design Phases

User Story
Wireframe & User Action
Frontend Requirements (UI Components, State Management)
Backend Requirements (Business Logic, Validation Rules)
API Contract (Endpoint, Request, Response)
Discussion Points

sequenceDiagram
    participant PM as CEO/PM
    participant DF as Designer/Frontend
    participant Spec as Feature Spec
    participant FE as Frontend Dev
    participant BE as Backend Dev
    participant Next as Code-to-Staging

    rect rgb(55, 105, 150)
        Note over PM,Next: Planning & Design Phase
        PM->>Spec: User Story
        DF->>Spec: Wireframe
        loop UNTIL SPECIFICATION COMPLETE
            DF->>Spec: Map User Interaction
            FE->>Spec: State Management
            BE->>Spec: DB Design, Logic, Error Handling
        end
        Spec->>Next: Specification Complete
    end

Outcome: Enables fully independent development

Unified Feature Specification Template (PDF)

Code-to-Staging Infrastructure

SDLC: Implementation, Testing, Deployment Phases

CodePipeline Permission Setup Guide IAM Permission Verification Demo CodePipeline PR Merge Demo (Video) Dev-Only CodePipeline Access Setup Guide GitHub Branch Protection Setup Guide

Code-to-Production SDLC Workflow

sequenceDiagram
    participant Dev as Developer
    participant PR1 as PR to dev
    participant DevBranch as dev branch
    participant DevEnv as Dev Environment
    participant PR2 as PR to main
    participant Main as main branch
    participant Prod as Production

    rect rgb(55, 105, 150)
        Note over Dev,PR1: Development Phase
        Dev->>PR1: Create PR
        PR1->>DevBranch: Merge (after approval)
    end

    rect rgb(45, 140, 85)
        Note over DevBranch,DevEnv: Testing Phase
        DevBranch->>DevEnv: CodePipeline deploy
        Note over DevEnv: Test on browser
    end

    rect rgb(180, 40, 50)
        Note over PR2,Prod: Production Phase
        DevBranch->>PR2: Create PR to main
        PR2->>Main: Merge (after approval)
        Main->>Prod: CodePipeline deploy
    end

References

Production Website: helprr.ai