Website Platform - Design Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include boilerplate like EEO, legal, etc. Must preserve all substantive info. We need to parse the posting. Key sections: - About ReminderMedia (company description) maybe not needed? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include sections that correspond to content. The posting includes "About ReminderMedia", "About The Platform", "About The Role", "Essential Functions" (list of duties), "What You'll Work With", "What This Role Is Not", "The Environment", "Requirements Required Qualifications", "Preferred Qualifications", "Compensation And Growth", "How We Hire", "How To Apply", "How We Measure Success In This Role", plus repeated Benefits etc. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. - About the role: we have "About The Role" paragraph. Also maybe "Essential Functions" could be Responsibilities. So we can put About the role content in

About the role

with paragraph(s). Then Responsibilities: list of essential functions (Theme and Site Design, UX Across the Product, Client Support as Design Research, AI-Native Product Development, Growing Ownership). Use

• . - Requirements: maybe "Required Qualifications" list. Also "Preferred Qualifications". Could combine? But we need separate sections: Requirements and Qualifications. The instruction says use headings Requirements and Qualifications. Likely Requirements = required qualifications; Qualifications = preferred qualifications? Or maybe Requirements = required, Qualifications = preferred. We'll do that. - Skills: maybe "What You'll Work With" (tech stack) could be Skills. Also "What This Role Is Not" maybe not needed. Could also include "Deep fluency in modern web fundamentals" etc. But we can put Skills as the tech stack and AI tools. - Benefits: we have "Compensation And Growth" includes benefits description. Also later repeated Benefits section. So we can include Benefits heading with list: medical, dental, vision, 401(k) with company match, paid time off, equipment provided. - Pay: we have base salary range $95,000 to $125,000. Also mention flexible for exceptional candidates. So include Pay heading with that. - Schedule: maybe mention fully remote (US). Also "This is a fully remote position, based anywhere in the eligible states listed below." That's schedule/location. Could be Schedule heading with "Fully remote (US)". Also maybe mention "Permanent residency in one of the following states is required: ..." That's location requirement, could be under Requirements? But schedule heading maybe just remote. We'll include Schedule heading with "Fully remote (US)". Also we could include location requirement under Requirements? But we already have Requirements for qualifications. Might be better to include location under Requirements? However instruction: Use headings as given; we can add location under Requirements or maybe under Schedule? The schedule heading is for work schedule (hours, remote). We'll put remote info there. We must not include boilerplate like EEO, legal, etc. Also must not include duplicated lines. Also must not include application instructions (How To Apply, How We Hire, etc). Also must not include "How We Measure Success". Also must not include "About ReminderMedia" and "About The Platform" maybe not needed as they are company description; but could be considered part of About the role? Probably not needed. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." So we can drop company description if not needed for sections. But we need to preserve ALL substantive information; do NOT invent or summarize away detail. If we drop company description, we lose substantive info about the company. However the instruction says we should include sections only when posting has real, specific content for it. It didn't say we must include company description; but we must preserve ALL substantive information. That suggests we need to keep that info somewhere, maybe in a paragraph under About the role? But About the role heading is for role description, not company. Could we add a

  before headings? The instruction says output ONLY the HTML fragment — no /, no markdown code fences. It didn't forbid extra paragraphs outside headings. We could include a brief intro paragraph about the company before headings. That would preserve info. However the instruction about headings: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other content. So we can include a

  with company description and platform description before the headings. Thus structure:

  About ReminderMedia ...

  About The Platform ...

  Then

  About the role

  with paragraph(s) from About The Role. Then

  Responsibilities

  with ul of essential functions. Then

  Requirements

  with ul of Required Qualifications. Then

  Qualifications

  with ul of Preferred Qualifications. Then

  Skills

  with ul of What You'll Work With (tech stack) maybe also AI tools. Then

  Benefits

  with ul of benefits. Then

  Pay

  with p of salary range. Then

  Schedule

  with p of remote and location requirement? Actually location requirement is not schedule but maybe we can include location under Requirements? But we already used Requirements for qualifications. Could add location under Requirements as a separate bullet? But that would mix qualifications with location. Might be okay but maybe better to add location under Schedule as "Permanent residency in one of the following states required: AL, AZ, CO, DE, FL, GA, IN, KY, MI, MN, MO, NC, NJ, NM, NV, OK, PA, SC, TN, TX, UT, or VA." plus "Fully remote (US)". That seems appropriate. We must not include boilerplate like "Equal Employment Opportunity", etc. Also must not include "How We Hire", "How To Apply", "How We Measure Success". Also must not include duplicated Benefits section (we have one). Also must not include "Compensation And Growth" duplicated; we will use Pay and Benefits sections. We must not include "What This Role Is Not", "The Environment", etc unless we can fit them somewhere. But we need to preserve ALL substantive information. If we omit those, we lose info. However maybe we can incorporate some of that content into existing sections: e.g., "What This Role Is Not" could be omitted as it's not essential? But it's substantive. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that info somewhere. Could we add a section like "Additional Notes"? Not allowed headings list but we could add a

  after sections. The instruction only says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

  for section headings (e.g. ...)". It implies we should use those headings for sections; but we could still add other headings if needed? Safer to stick to those headings only. But we need to preserve info from "What This Role Is Not" and "The Environment". Could we fold that into Responsibilities or About the role? Possibly incorporate as bullet points under Responsibilities? For example, "What This Role Is Not" clarifies what the role is not; we could add a note under Responsibilities as a clarification. Similarly "The Environment" could be added as a note under About the role or Responsibilities. We must not invent or summarize away detail; we can rephrase but keep meaning. Thus we can include those details as part of existing sections. Let's extract content: About ReminderMedia: "ReminderMedia is a leading marketing services provider that has helped over 100,000 small businesses grow their client base through a powerful suite of digital and direct-mail marketing tools. We serve real estate agents, insurance professionals, financial advisors, and other relationship-driven small businesses with branded lifestyle magazines, digital marketing platforms, and creative content that keeps our clients top-of-mind with the people who matter most to their business." About The Platform: "We've built an AI-native website platform for real estate agents. One codebase serving many premium, fully-branded client sites, with AI onboarding that builds a complete site from a form, an editor clients use by chatting (including from their own Claude or ChatGPT), AI-generated photography and hero video, and fair-housing compliance built into every word. It's live, clients are on it, and sales are ramping now." About The Role: "We are hiring a Design Engineer with exceptional taste and serious growth potential. Someone who will shape how this platform looks and feels today, and who wants to grow into owning more of the product over time. You don't need to be an engineer. You need great taste, real fluency with AI tools, and the hunger to become someone who ships end-to-end. This role has a defined growth path toward Founding Design Engineer level ownership. We're hiring your trajectory as much as your current skills. We care how good you are and how fast you're getting better, not how long it took you to get here. There's no years-of-experience requirement; your work is the requirement. This is a fully remote position, based anywhere in the eligible states listed below." Essential Functions (list): - Theme and Site Design - Design the themes that define what "premium" means on our platform. Our architecture makes themes pure design work. A theme is a component that plugs into onboarding, the editor, and publishing automatically. - Own the craft heart of the platform: typography, spacing, hierarchy, restraint, and the details that make a site feel premium. - Design and iterate on the visual systems that scale across many client sites while preserving individuality. - UX Across the Product - Improve the experiences clients touch every day: the admin, the AI editor, onboarding flows, and the public-facing sites. - Design for a multi-tenant platform where every improvement compounds across the client base. - Partner with the platform team to ship design changes end-to-end, using AI tooling as your primary leverage. - Client Support as Design Research - Handle escalated client tickets. Our AI triage layer catches the routine ones, and you'll work the ones that require judgment. - Turn every ticket into a design fix. Every ticket is a UX flaw, a content gap, or a docs gap. Your job is to make whole categories of them disappear. - Feed the pattern of what you learn from support directly back into the product roadmap. - AI-Native Product Development - Use AI tools (Claude Code, Replit, Cursor, Figma AI, and others) as the daily workflow to design and build. This is not a novelty. It is how the work gets done here. - Document AI-assisted work in accordance with ReminderMedia's AI Use Policy. - Ship faster and further than traditional design roles allow, by combining exceptional taste with real fluency in AI-augmented development. - Growing Ownership - Progress along a defined growth path toward end-to-end ownership of features and, over time, major pieces of the product. - Take on progressively broader technical scope as your ability to ship independently matures. What You'll Work With