Direct AI coding agents to build and ship marketing sites, maintain brand voice and design discipline across five brands, own SEO and information architecture, run competitive research, and review/correct AI-generated code and copy to ensure production-quality outcomes.
This is a remote position.
Location: Currently remote, may transition to onsite in future
Design, build, and ship marketing sites and landing pages across the Spektra portfolio — CloudLabs, CSP Control Center, SaaSify, CloudEvents, and spektrasystems.com — with AI agents as your execution engine. Brand discipline, design, SEO, and craft, not just typing.
About the role Spektra Systems runs four product brands (CloudLabs, CSP Control Center, SaaSify, CloudEvents) plus the parent company site at spektrasystems.com. Each one has its own audience, voice, and pricing motion — labs platform for ISVs and educators, CSP control plane for cloud distributors, SaaS-platform tooling for software vendors, events platform for hackathon hosts.
You own the marketing surface across all of them. Most execution happens through AI coding agents — Claude Code, Cursor, GPT, whatever works. What you bring isn’t typing. It’s taste, brand discipline, and the architectural judgment to know when to trust the agent, when to push back, and when to throw it out and start over.
This isn’t a “prompt engineer” job. It isn’t a “frontend dev who uses Copilot sometimes” job either. It’s a hybrid: you direct AI agents to do the bulk of implementation, you review ruthlessly, and you own the outcome — across five distinct brands.
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.
RequirementsWhat 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.
- 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.
- Years of experience. Show us output.
- Whether you “can also code without AI.” Obviously you can. That’s not the point.
Send links to two or three marketing sites, landing pages, or component libraries you’ve shipped — ideally ones an AI agent helped you build.
In three sentences, tell us:
- What you did vs. what the agent did.
- The single dumbest thing the agent tried to ship that you caught.
- What you’d do differently next time.
Similar Jobs
Automotive • Hardware • Internet of Things • Mobile • Software • App development • PropTech
Architect and build LLM-based, agentic AI systems and production pipelines (RAG, orchestration, memory, tool integration). Lead cross-functional delivery across frontend, backend, and ML, drive tooling/infrastructure choices, mentor engineers, and ensure scalable, observable, production-ready GenAI features.
Top Skills:
AutogenAWSAzureCamelFaissGCPGrpcLangchainLanggraphLlamaindexLlmsMcpMlopsNode.jsPineconePythonRagRasaRestVector DatabasesWeaviate
Cloud • Information Technology • Security • Software • Cybersecurity
Lead product strategy and execution for a principal area of Security AI. Own multi-quarter roadmaps, run enterprise customer discovery, translate insights into requirements and metrics, align Engineering/Design/Security Research/GTM, ship platform and security capabilities, write PRDs and launch narratives, and brief executives and customers.
Top Skills:
A2AAi/MlAPIsData ProtectionIdentity ProtocolsMcpNetwork ProtocolsSaseSecurity ArchitectureTelemetryZero Trust
Aerospace • Hardware • Information Technology • Security • Software • Cybersecurity • Defense
Provide technical oversight and act as COTR for SAR/direction-finding seeker development across LRPF programs. Coordinate supplier SOWs, schedules, requirements, and integration planning; validate RF hardware and seeker software maturation; liaise with government customers and program management; supervise multidisciplinary teams and report technical, cost, and schedule status. Hybrid role with significant on-site presence and up to 50% travel.
Top Skills:
Direction-FindingRadar ModesRfSeeker HardwareSeeker SoftwareSynthetic Aperture Radar (Sar)
What you need to know about the Austin Tech Scene
Austin has a diverse and thriving tech ecosystem thanks to home-grown companies like Dell and major campuses for IBM, AMD and Apple. The state’s flagship university, the University of Texas at Austin, is known for its engineering school, and the city is known for its annual South by Southwest tech and media conference. Austin’s tech scene spans many verticals, but it’s particularly known for hardware, including semiconductors, as well as AI, biotechnology and cloud computing. And its food and music scene, low taxes and favorable climate has made the city a destination for tech workers from across the country.
Key Facts About Austin Tech
- Number of Tech Workers: 180,500; 13.7% of overall workforce (2024 CompTIA survey)
- Major Tech Employers: Dell, IBM, AMD, Apple, Alphabet
- Key Industries: Artificial intelligence, hardware, cloud computing, software, healthtech
- Funding Landscape: $4.5 billion in VC funding in 2024 (Pitchbook)
- Notable Investors: Live Oak Ventures, Austin Ventures, Hinge Capital, Gigafund, KdT Ventures, Next Coast Ventures, Silverton Partners
- Research Centers and Universities: University of Texas, Southwestern University, Texas State University, Center for Complex Quantum Systems, Oden Institute for Computational Engineering and Sciences, Texas Advanced Computing Center
