AI-Native Web Developer

About the role

What you’ll do

• Ship marketing pages, landing pages, and microsites across all five Spektra properties using Claude Code (or equivalent) as your primary execution engine. You iterate via screenshots, browser inspection, and tight critique loops — not line-by-line typing.
  
• Hold each brand’s voice and visual identity distinct — CloudLabs is opinionated and transparent (publishes pricing competitors hide); CSP Control Center is procurement-focused and technical; SaaSify is partner-channel-led; CloudEvents is energetic and event-driven; Spektra Systems is the trust-and-compliance parent. You can rewrite any AI-generated copy so it sounds like the right one.
  
• Maintain design discipline across the portfolio — semantic tokens (no raw hex), component reuse where it fits, custom where it doesn’t. Catch the agent when it reaches for bg-emerald-500 instead of bg-primary.
  
• Own SEO end-to-end across every site: canonical URLs, redirects, structured data, internal linking, top-traffic-URL protection through migrations. You spot when the agent silently breaks SEO and you recover before it ships.
  
• Architect information for messy real-world products. CloudLabs alone sells four distinct things (pre-built labs, VM Labs platform, annual Platform contract, hackathons) with four different buyers. CSP and SaaSify each have their own audience archetypes. You design IA for that.
  
• Run competitive research  and translate findings into design and content choices that fit each brand — not just bullet points.
  
• Decide when to share components across brands and when to keep them separate. Build a shared design-system foundation where it accelerates work, fork where each brand’s identity demands it.
  
• Push back on AI output when it’s wrong. The agent will produce visually generic, brand-violating, SEO-broken, or copy-bloated work confidently. Your job is to catch it before merge.
  

What you’ll do

• Ship marketing pages, landing pages, and microsites across all five Spektra properties using Claude Code (or equivalent) as your primary execution engine. You iterate via screenshots, browser inspection, and tight critique loops — not line-by-line typing.
  
• Hold each brand’s voice and visual identity distinct — CloudLabs is opinionated and transparent (publishes pricing competitors hide); CSP Control Center is procurement-focused and technical; SaaSify is partner-channel-led; CloudEvents is energetic and event-driven; Spektra Systems is the trust-and-compliance parent. You can rewrite any AI-generated copy so it sounds like the right one.
  
• Maintain design discipline across the portfolio — semantic tokens (no raw hex), component reuse where it fits, custom where it doesn’t. Catch the agent when it reaches for bg-emerald-500 instead of bg-primary.
  
• Own SEO end-to-end across every site: canonical URLs, redirects, structured data, internal linking, top-traffic-URL protection through migrations. You spot when the agent silently breaks SEO and you recover before it ships.
  
• Architect information for messy real-world products. CloudLabs alone sells four distinct things (pre-built labs, VM Labs platform, annual Platform contract, hackathons) with four different buyers. CSP and SaaSify each have their own audience archetypes. You design IA for that.
  
• Run competitive research  and translate findings into design and content choices that fit each brand — not just bullet points.
  
• Decide when to share components across brands and when to keep them separate. Build a shared design-system foundation where it accelerates work, fork where each brand’s identity demands it.
  
• Push back on AI output when it’s wrong. The agent will produce visually generic, brand-violating, SEO-broken, or copy-bloated work confidently. Your job is to catch it before merge.
  

What we’re looking for

• AI fluency. You’ve shipped real production work with Claude Code, Cursor, or similar. You know which model to reach for, when to start fresh vs. continue a session, when to spawn a sub-agent, and how to give an agent the context it actually needs (paths, line numbers, prior-art file references — not vibes).
  
• Design taste.  You know that monochromatic isn’t always bad and that color variety isn’t always good. You don’t confuse “looks like a generic SaaS template”with “shipped.”
  
• Multi-brand judgment. You can hold five distinct voices in your head and switch fluently between them. You don’t homogenize everything to the same template.
  
• Frontend chops. Astro, Next, React, Tailwind v4, modern build tooling, OKLCH color, dark/light theming. You read code fluently even when you didn’t type it. You know git.
  
• SEO depth. You know what a canonical loop is and why it hurts. You know when a 301 is right and when it isn’t. You’ve broken SEO  and recovered from it
  
• Bias to ship. You’d rather merge an iteration today than perfect tomorrow.
  
• Comfortable with brutal feedback loops. Most of what you build will get critiqued and reworked. You don’t take it personally; you take it as signal.
  

What we don’t care about

• Years of experience. Show us output.
  
• Whether you “can also code without AI.” Obviously you can. That’s not the point.
  

How to apply

1. What you did vs. what the agent did.
   
2. The single dumbest thing the agent tried to ship that you caught.
   
3. What you’d do differently next time.