experience
Software Engineer · 35
Software engineer contributing shipped features across CMS sites, B2B SaaS products, and digital tools inside active client delivery teams.
Organization
35
Period
Internship
Sep 2024 - Jan 2025
Part-time
Feb 2025 - Present
Context
Feature delivery inside client product teams
Focus
Feature delivery across CMS sites, B2B SaaS, and digital tools
Overview
At 35 I work inside existing product teams, codebases, and release rhythms to move real client products forward. The focus is feature delivery: understand the surrounding system, translate product intent into clean implementation, and ship changes that hold up in live CMS, SaaS, and digital-tool environments.
Related cases
Academy35
Flexible learning platform for managing training, enrolments, and progress tracking across organizations.
Greenchoice Lumi
AI energy assistant from Greenchoice that gives households more personal guidance on saving energy and improving sustainability.
Peakview
Strategic progress overview that brings scattered project and programme information together above day-to-day operational tools.
Detail
The role spans CMS-driven sites, B2B SaaS applications, and digital tools that already have users, stakeholders, and delivery pressure around them. That means stepping into existing context quickly, understanding how the product already works, and shipping features that strengthen the system instead of creating extra maintenance for the team.
The clearest proof in this role is dependable delivery inside live products: features shipped, interfaces refined, and releases supported without needing a blank slate to do useful work. Moving between marketing-heavy surfaces, operational SaaS flows, and AI-enabled experiences sharpened judgment around performance, content structure, data fit, and where automation genuinely improves the workflow.
React and Next.js are central on the frontend, with SQL in the mix whenever the work touches data-backed behavior. Agentic workflows become useful when AI needs to support a real product or team flow rather than sit as a disconnected demo, so the method stays practical: understand the surrounding system, clarify the user-facing behavior, and ship the smallest clean change that improves the product without creating avoidable complexity for everyone else.
- Delivered features inside live client products where release rhythm, stakeholder feedback, and existing technical decisions already shaped the work.
- Contributed across CMS surfaces, B2B SaaS flows, and digital tools without treating each request as an isolated ticket or greenfield rewrite.
- Supported data-backed and AI-enabled workflows where reliability, clarity, and practical fit mattered more than novelty.
Skills & Tooling