Available now · no current contracts

Jake Christian Oliveros

Software Engineer · DevOps

Engagement & rate
$20/hr
Weekly retainers of 2–5 days, rolling, at rates on request. Long-term relationships preferred over one-off projects.
Book a call

01 What I do

I build the application logic, the integrations, and the architecture behind them.

Co-founder of IMCO. Lead developer on a two-site WordPress platform since 2024, and CTO on the studio's own site.

The two layers I work across

  1. 01

    The platform layer

    The WordPress side of a shared platform: the plugin's 22 blocks, and the site settings they read.

  2. 02

    The backend layer

    Services wired end to end: a contact form that Resend receives, Supabase keeps, and Resend sends back on as a notification.

02 Case studies

The work, written up in full.

All works

  • Case 01Enterprise Network Security

    A Shared Foundation for Two Platforms

    DesignEngineering

    Problem

    A brand with no design identity of its own, and later a second platform on a separate codebase: every section was built twice, and a change of mind meant a code push nobody could preview first.

    Scope

    Hired in 2018 to remake the design, with the front end added two months in; from 2019 the second platform too, and from 2024 the WordPress side, graphics and QA.

    Solution

    A design system for the brand, and one codebase both of its platforms install: the same sections on each, with per-site settings deciding the difference.

    Read case study
  • Case 02In-house

    Building the Room You're Standing In

    DesignEngineeringAutomation

    Problem

    Three portfolios started and none finished, and every case study meant up to two weeks of writing by hand while working out the template it had to fit.

    Scope

    Our own site, from May 2026: the design language, the front end, and the automation that turns an interview into a case study.

    Solution

    A portfolio built from one design language and one set of components, where every case study starts as an interview and reaches the page in about two hours.

    Read case study

03 Engagement timeline

Two engagements since 2024, across every layer.

Engagements run side by side, not one after another. Each bar is one engagement, start to finish; each pin is a moment its case study records.

Fig. 01 — The engagements

2024 — present

Experience

  1. Engagement 02

    2026 — nowMay 2026 — present

    Tenure
    6 mos
    Basis
    In-house
    Client
    IMCO
    Layers
    Design, Engineering, Automation
    Team of 2
    With Chris (Creative Director)

    Building the Room You're Standing In

    CTO

    Set up the backend, starting with the contact page: Resend receives the message, Supabase keeps the data and sends it back through Resend as a notification to Chris, over Supabase's custom SMTP. Made the case for Astro with its stats.

    Stack
    • Astro
    • SCSS
    • GSAP
    • Supabase
    • Resend
    • NodeJS
    • Whisper
    • Figma
    • Claude Design
    • Claude
    • GitHub
    Read the case study
  2. Engagement 01

    2024 — 2026May 2024 — Oct 2026

    Tenure
    2 yrs 5 mos
    Basis
    Contract
    Client
    Enterprise Network Security
    Layers
    Design, Engineering
    Team of 4
    With Chris (Lead UI/UX Designer, Lead Frontend Engineer), Dave (Graphic Artist), Dan (QA)

    A Shared Foundation for Two Platforms

    Lead Developer

    Owned the WordPress side: built the plugin's 22 blocks and wired its site settings.

    Stack
    • WordPress
    • Elementor
    • Gutenberg Blocks
    • HTML
    • SCSS
    • PHP
    • Figma
    • VSCode
    • GitHub
    • Git
    Read the case study