Website Platform - Design Engineer
ReminderMedia · Collegeville, PA · 1 mo ago
Engineering$95k–$125k/yrFull-time
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.
First, there is "About ReminderMedia" and "About The Platform" and "About The Role". The "About The Role" section includes description. We'll treat that as "About the role". Then "Essential Functions" with bullet points: Theme and Site Design, UX Across the Product, Client Support as Design Research, AI-Native Product Development, Growing Ownership. Those are responsibilities. Could be under Responsibilities.
Then "What You'll Work With" (tech stack) maybe Skills.
Then "What This Role Is Not" maybe not needed.
Then "The Environment" maybe not needed.
Then "Requirements Required Qualifications" list bullet points: Required Qualifications (list). Then "Preferred Qualifications". Those go under Requirements and Qualifications? The instruction: Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map.
- About the role: description from "About The Role" paragraph(s). Could include the paragraph about hiring a Design Engineer etc.
- Responsibilities: list of essential functions (Theme and Site Design, UX Across the Product, Client Support as Design Research, AI-Native Product Development, Growing Ownership). Also maybe "Handle escalated client tickets" etc.
- Requirements: maybe the "Required Qualifications" bullet list.
- Qualifications: maybe the "Preferred Qualifications" bullet list.
- Skills: maybe "What You'll Work With" (React 18, TypeScript, Tailwind, shadcn/ui, Node/Express, PostgreSQL, AI tooling). Also mention deep fluency in HTML/CSS, JS, AI tools.
- Benefits: from "Compensation And Growth" includes base salary range, benefits package, equipment provided, defined growth path, fully remote. Also "Compensation And Growth" repeated later. So we can put Benefits: medical, dental, vision, 401(k) with company match, paid time off, equipment provided.
- Pay: base salary $95,000 to $125,000.
- Schedule: maybe not explicitly stated; there is "Fully remote (US)" but schedule not given. There's no mention of hours, full-time etc. Could infer full-time but not explicit. We should not create Schedule unless posting actually states it. It does not. So omit Schedule section.
Also need to include location requirement: permanent residency in certain states. That could be under Requirements or maybe under About the role? Probably under Requirements as a qualification. We'll include in Requirements list.
We must not include boilerplate like EEO, legal, etc. Also must not include "How We Hire", "How To Apply", etc. Must remove application instructions. Also remove duplicated lines like repeated "Compensation And Growth". We'll keep only once.
We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the specifics: e.g., "Exceptional design taste demonstrated through a portfolio. Your work makes people feel something. You have strong opinions about typography, spacing, and restraint, and you can articulate why something is beautiful." etc.
We need to format as HTML: use for section headings. Use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must output only HTML fragment, no /, no markdown fences.
Let's craft.
First, About the role: combine paragraphs from "About The Role". The section includes:
"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."
Also earlier "About ReminderMedia" and "About The Platform" maybe not needed for role but could be considered about the role? The instruction: Use heading About the role for section headings (e.g. About the role, Responsibilities...). So we should put the role description there. Could include the company description? Probably not needed; but we can include if it's substantive. However "About ReminderMedia" and "About The Platform" are about company and platform, not the role. Might be considered part of role context but not required. Safer to stick to the "About The Role" paragraph.
Thus About the role
with that text.
Responsibilities: list of essential functions. We'll create
with each bullet as - . Include the sub-bullets? The essential functions have headings and then description. We could combine each as a list item containing the heading and description. Eg:
- Theme and Site Design: Design the themes that define what "premium" means on our platform....
We need to preserve all substantive information. So include the description under each heading.
Let's extract each:
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.
We'll put each as - with the heading bolded.
Requirements: Required Qualifications bullet list:
- Exceptional design taste demonstrated through a portfolio. Your work makes people feel something. You have strong opinions about typography, spacing, and restraint, and you can articulate why something is beautiful.
- Deep fluency in modern web fundamentals: HTML and CSS at an expert level, JavaScript at a comfortable working level.
- Genuine daily use of AI tools for design and development (Claude, Replit, Cursor, Figma AI, or equivalent). You should be able to describe your workflow specifically, with concrete examples of what these tools let you ship that you couldn't before.
- Portfolio of shipped design work required. Live sites strongly preferred over mockups. Submit links to work you have shipped, with a brief description of what you personally owned.
- A learning trajectory that surprises people. You may not ship production code end-to-end today, but you want to, and you pick things up at a pace that stands out.
- Willingness to handle escalated client support tickets as part of the role. Ego about support work is a dealbreaker in both directions.
- Ownership mindset. When something is broken, unclear, or ugly, you fix it or flag it. You do not wait to be asked.
- Clear professional written communication in English.
- Authorization to work in the United States.
- Permanent residency in one of the following states is required: AL, AZ, CO, DE, FL, GA, IN, KY, MI, MN, MO, NC, NJ, NM, NV, OK, PA, SC, TN, TX, UT, or VA.
We'll put as
- .
Qualifications: Preferred Qualifications bullet list:
- Prior shipped work with React, TypeScript, Tailwind, and shadcn/ui.
- Experience designing for multi-tenant or theme-based platforms.
- Experience shipping product end-to-end (design plus build), even if AI-augmented.
- Prior work in a startup or small-team environment where you wore multiple hats.
- Experience designing for regulated verticals (real estate, financial services) or for small business audiences.
- Prior experience with Node/Express, PostgreSQL, or similar backend fundamentals.
We'll put as
- .
Skills: "What You'll Work With" plus maybe deep fluency in HTML/CSS/JS and AI tools. We'll combine:
- React 18, TypeScript, Tailwind, and shadcn/ui on the front end; a multi-tenant Node/Express platform with PostgreSQL behind it; and AI tooling (Claude Code, Replit, Cursor) as the daily workflow.
- You do not need to know this stack today. The AI tools close most of the gap; your taste and momentum close the rest.
Also mention deep fluency in modern web fundamentals (HTML/CSS expert, JS comfortable) and genuine daily use of AI tools.
We'll create a
list.
Benefits: from "Compensation And Growth": Comprehensive compensation package with base salary range (but that's Pay). Benefits: Full benefits package includes medical, dental, vision, 401(k) with company match, paid time off, and much more. Equipment needed to work remotely is provided by the company. Defined growth path: compensation and scope review at 12 months, with a clear track toward Founding Design Engineer level ownership (and the compensation that comes with it) as your end-to-end shipping matures. Fully remote (US). We'll put benefits as list: medical, dental, vision, 401(k) with company match, paid time off, equipment provided, defined growth path with review at 12 months toward Founding Design Engineer level ownership.
Pay: base salary $95,000 to $125,000, calibrated to craft and trajectory. Range is flexible for exceptional candidates.
Schedule: not present, omit.
We must not include duplicated lines. Ensure we don't repeat the compensation paragraph twice.
Now produce HTML.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
...
Qualifications
...
Skills
...
Benefits
...
Pay
...
No Schedule.
Make sure to not include any extra text outside HTML.
Let's craft the HTML.
Be careful to escape any special characters? Not needed.
Now produce
for prose. We must output only HTML fragment, no /, no markdown fences. Let's craft. First, About the role: combine paragraphs from "About The Role". The section includes: "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." Also earlier "About ReminderMedia" and "About The Platform" maybe not needed for role but could be considered about the role? The instruction: Use heading About the role for section headings (e.g. About the role, Responsibilities...). So we should put the role description there. Could include the company description? Probably not needed; but we can include if it's substantive. However "About ReminderMedia" and "About The Platform" are about company and platform, not the role. Might be considered part of role context but not required. Safer to stick to the "About The Role" paragraph. Thus About the role
with that text. Responsibilities: list of essential functions. We'll create
- with each bullet as
- . Include the sub-bullets? The essential functions have headings and then description. We could combine each as a list item containing the heading and description. Eg:
- Theme and Site Design: Design the themes that define what "premium" means on our platform.... We need to preserve all substantive information. So include the description under each heading. Let's extract each: 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. We'll put each as
- with the heading bolded.
Requirements: Required Qualifications bullet list:
- Exceptional design taste demonstrated through a portfolio. Your work makes people feel something. You have strong opinions about typography, spacing, and restraint, and you can articulate why something is beautiful.
- Deep fluency in modern web fundamentals: HTML and CSS at an expert level, JavaScript at a comfortable working level.
- Genuine daily use of AI tools for design and development (Claude, Replit, Cursor, Figma AI, or equivalent). You should be able to describe your workflow specifically, with concrete examples of what these tools let you ship that you couldn't before.
- Portfolio of shipped design work required. Live sites strongly preferred over mockups. Submit links to work you have shipped, with a brief description of what you personally owned.
- A learning trajectory that surprises people. You may not ship production code end-to-end today, but you want to, and you pick things up at a pace that stands out.
- Willingness to handle escalated client support tickets as part of the role. Ego about support work is a dealbreaker in both directions.
- Ownership mindset. When something is broken, unclear, or ugly, you fix it or flag it. You do not wait to be asked.
- Clear professional written communication in English.
- Authorization to work in the United States.
- Permanent residency in one of the following states is required: AL, AZ, CO, DE, FL, GA, IN, KY, MI, MN, MO, NC, NJ, NM, NV, OK, PA, SC, TN, TX, UT, or VA.
We'll put as
- .
Qualifications: Preferred Qualifications bullet list:
- Prior shipped work with React, TypeScript, Tailwind, and shadcn/ui.
- Experience designing for multi-tenant or theme-based platforms.
- Experience shipping product end-to-end (design plus build), even if AI-augmented.
- Prior work in a startup or small-team environment where you wore multiple hats.
- Experience designing for regulated verticals (real estate, financial services) or for small business audiences.
- Prior experience with Node/Express, PostgreSQL, or similar backend fundamentals.
We'll put as
- .
Skills: "What You'll Work With" plus maybe deep fluency in HTML/CSS/JS and AI tools. We'll combine:
- React 18, TypeScript, Tailwind, and shadcn/ui on the front end; a multi-tenant Node/Express platform with PostgreSQL behind it; and AI tooling (Claude Code, Replit, Cursor) as the daily workflow.
- You do not need to know this stack today. The AI tools close most of the gap; your taste and momentum close the rest.
Also mention deep fluency in modern web fundamentals (HTML/CSS expert, JS comfortable) and genuine daily use of AI tools.
We'll create a
- list.
Benefits: from "Compensation And Growth": Comprehensive compensation package with base salary range (but that's Pay). Benefits: Full benefits package includes medical, dental, vision, 401(k) with company match, paid time off, and much more. Equipment needed to work remotely is provided by the company. Defined growth path: compensation and scope review at 12 months, with a clear track toward Founding Design Engineer level ownership (and the compensation that comes with it) as your end-to-end shipping matures. Fully remote (US). We'll put benefits as list: medical, dental, vision, 401(k) with company match, paid time off, equipment provided, defined growth path with review at 12 months toward Founding Design Engineer level ownership.
Pay: base salary $95,000 to $125,000, calibrated to craft and trajectory. Range is flexible for exceptional candidates.
Schedule: not present, omit.
We must not include duplicated lines. Ensure we don't repeat the compensation paragraph twice.
Now produce HTML.
Structure:
- ... ...
About the role
...
Responsibilities
Requirements
- ...
Qualifications
- ...
Skills
- ...
Benefits
- ...
Pay
...
No Schedule. Make sure to not include any extra text outside HTML. Let's craft the HTML. Be careful to escape any special characters? Not needed. Now produce
- .
Skills: "What You'll Work With" plus maybe deep fluency in HTML/CSS/JS and AI tools. We'll combine:
- React 18, TypeScript, Tailwind, and shadcn/ui on the front end; a multi-tenant Node/Express platform with PostgreSQL behind it; and AI tooling (Claude Code, Replit, Cursor) as the daily workflow.
- You do not need to know this stack today. The AI tools close most of the gap; your taste and momentum close the rest.
Also mention deep fluency in modern web fundamentals (HTML/CSS expert, JS comfortable) and genuine daily use of AI tools.
We'll create a
- .
Qualifications: Preferred Qualifications bullet list:
- Prior shipped work with React, TypeScript, Tailwind, and shadcn/ui.
- Experience designing for multi-tenant or theme-based platforms.
- Experience shipping product end-to-end (design plus build), even if AI-augmented.
- Prior work in a startup or small-team environment where you wore multiple hats.
- Experience designing for regulated verticals (real estate, financial services) or for small business audiences.
- Prior experience with Node/Express, PostgreSQL, or similar backend fundamentals.
We'll put as