The team

One team across all three layers.

Design, engineering, and automation under one roof, with quality assurance running through the last two. No department walls: coverage comes from overlap, not headcount.

Meet the team Work with us

01 Founder
Chris Javier Oliveros
Senior Frontend Engineer · UI/UX Specialist · Automation Engineer
Leads product direction, frontend architecture, and design systems.
Works in
Design · Engineering · Automation
View Chris’s resume

02 Co-founder
Jake Christian Oliveros
Software Engineer · DevOps
Builds application logic, integrations, and the technical architecture behind them.
Works in
Engineering · Automation
View Jake’s resume

03 Junior Designer
Dave Mark
Graphic Artist · Illustrator
Makes the icons, illustrations and graphic assets the interfaces use.
Works in
Design
04 Quality Assurance
Dan Marco
QA Specialist
Owns functional QA, regression testing, and release validation.
Works in
Engineering · Automation

Working principles

How we hold the work to one standard.

Design and engineering should share the same system.
Automation extends that system; it does not replace either layer beneath it.
Quality assurance is part of delivery, not a final gate.
If a workflow cannot be described clearly, it is not ready to be automated.
Performance and accessibility are product requirements.
Technical decisions should remain explainable to the people who inherit them.

What we do

Each layer hands a system to the next.

The same people carry the work across the hand-offs, so nothing is re-explained at the boundary. Quality assurance runs through engineering and automation instead of waiting at the end.

Layer 01
Design
Design decides what the product is and gives engineering a clear, reusable system to build from.
Process
Wireframing · Prototyping · UI/UX Design · Design Systems
Selected tech
Figma · Claude Design
Team
Chris · Dave
Shape the experience
Hands off a system
Layer 02
Engineering
Engineering makes the design real and maintainable, with the schemas, APIs, and contracts automation depends on.
Process
Frontend Architecture · Development · Integrations · Testing
Selected tech
WordPress · HTML · Angular · NodeJS · Supabase · Git · Cloudflare
Team
Chris · Jake
Build the foundation
Hands off a workflow
Layer 03
Automation
Automation reduces work around systems the team can understand, test, and change; it does not replace the layers beneath it.
Process
Workflow Automation · AI-assisted Systems
Selected tech
n8n · OpenClaw
Team
Chris · Jake
Scale the workflow

Quality AssuranceContinuous testing catches issues early, protects reliability, and makes both layers safer to change.Dan

Shared work

Built together, owned individually.

Every case states what the team accomplished and what each person personally owned.

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
Who owned what
- Chris Javier OliverosLead UI/UX Designer, Lead Frontend Engineer
  Designed the brand's design system and the pipeline every visual passes through, then architected the front end to match — one SCSS file per design component — ending in one codebase both platforms install.
- Jake Christian OliverosLead Developer
  Owned the WordPress side: built the plugin's 22 blocks and wired its site settings.
- Dave MarkGraphic Artist
  Made the icons, illustrations and other graphic assets most featured sections use, and fitted his SVGs into Chris's components in Figma.
- Dan MarcoQA
  Owned QA on releases once more went through the release pipeline and more could break.
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
Who owned what
- Chris Javier OliverosCreative Director
  Designed the site and built its front end, and built the automation behind it, the pipeline that distils his interview answers into the data each case-study page renders.
- Jake Christian OliverosCTO
  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.

One team across all three layers.

Chris Javier Oliveros

Jake Christian Oliveros

Dave Mark

Dan Marco

Design

Engineering

Automation

A Shared Foundation for Two Platforms

Building the Room You're Standing In

Building something, or hiring? Talk to the team.