Business Systems Manager
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, no invention, no summarizing away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove sections like "Physical Requirements", "Work Environment", maybe they are not required headings but we can include if they have content? The instruction says use headings only for those listed; we can include other headings? Probably not; we should stick to those headings only if content exists. The posting includes sections: About Nuage Designs (company description) maybe "About the role"? Actually there is "The Opportunity" and "What You'll Do". Also "Who You Are" includes qualifications & experience, preferred, physical requirements, work environment. Also "The Offer" includes compensation and benefits. We need to map to headings: About the role (maybe description of role), Responsibilities (duties), Requirements (maybe required qualifications), Qualifications (maybe preferred?), Skills (maybe skills), Benefits, Pay, Schedule. We must not create sections with filler like "commensurate with experience" for Pay; we should only include Pay if posting actually states it. The posting says: "Salary commensurate with experience." That's not a specific number, but it's still stating something about pay. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". So we should NOT create a Pay section because the content is filler. Similarly Benefits: they list "Benefit offerings including medical, dental, vision, and life insurance. 401K with company match. PTO. Holiday Pay." That's specific enough; we can include Benefits section. Schedule: they mention occasional evening or weekend work required to support system cutovers and peak event season. Also "Able to work onsite in Miami, with flexibility to support occasional evening or weekend system cutovers." That's schedule info. So we can include Schedule section. About the role: we have description: "The Opportunity Nuage is growing quickly..." plus maybe "The Role" heading. We'll put that under About the role. Responsibilities: the "What You'll Do" section with duties. Requirements: maybe the "Required" qualifications under Qualifications & Experience. Qualifications: maybe the "Preferred" qualifications. Skills: maybe we can extract skills from responsibilities? But we could also combine. However we need to avoid thin sections. Might combine Skills into Qualifications? But instruction says we can have sections only if posting has real specific content for it. We have content for Skills? Not explicitly a skills list, but we could infer from duties: e.g., "Act as internal system administrator..." but that's more responsibilities. Might be better to omit Skills section if no explicit skills list. However we have "Clear, confident written and verbal communication..." etc. That's a skill. Could be placed under Qualifications or Skills. Since we have both Required and Preferred qualifications, we could put Required under Requirements, Preferred under Qualifications, and maybe Skills under a separate section if we have explicit skill list like "Google Workspace administration, device management (MDM), password management, or security awareness training platforms." Those are skills. So we could have Skills section. Thus sections: About the role, Responsibilities, Requirements (required qualifications), Qualifications (preferred), Skills (technical skills), Benefits, Schedule. We must not include Pay. Now we need to extract content preserving all substantive info, no invention, no summarizing away detail. We must keep details but can format as
or
- . Must not repeat job title. Must not include boilerplate like EEO etc. Also remove duplicated lines.
Let's parse the posting.
First line: "N U A G E D E S I G N S · Miami, FL · Reports to Chief Strategy & Operations Officer · Full-Time - Exempt". This is metadata; we can fold into a short
or drop it. Probably we can include a short paragraph with location and reporting line and employment type. Not a heading. Then company description: "We elevate life’s most meaningful celebrations through inspired design, exceptional service, and genuine care." Then "T H E C O M P A N Y About Nuage Designs ..." We'll include that as part of About the role? Actually About the role is about the role, not company. But we could include company description under About the role? Might be better to have a short intro paragraph about company and role. However instruction: "Do NOT repeat the job title as a heading (the page already shows it)". It didn't forbid including company description. We'll include a
with location, reporting, full-time, and maybe a brief company overview. Then "T H E R O L E The Opportunity ..." We'll put that under About the role heading. Then "W H A T Y O U ’ L L D O Duties & Responsibilities" -> Responsibilities heading. Then "W H O Y O U A R E Qualifications & Experience" with subparts: Required, Preferred, Physical Requirements, Work Environment. We'll split Required into Requirements heading, Preferred into Qualifications heading, and maybe Skills from within Preferred? Actually Preferred includes many items: Bilingual English/Spanish, experience in event rental..., experience implementing or administering an ERP..., Google Workspace administration..., Familiarity with integrations..., Experience managing a managed service provider..., PMP etc. Those are qualifications/skills. We could put them under Qualifications (preferred) and maybe Skills separate for technical skills like Google Workspace admin, MDM, etc. But to avoid thin sections, maybe combine Preferred and Skills into Qualifications. However we have Required qualifications separate. Let's decide: Requirements = Required qualifications. Qualifications = Preferred qualifications. Skills = maybe we can extract technical skills from responsibilities? But we already have many technical items in Preferred. Could make Skills section for those technical items (Google Workspace administration, device management (MDM), password management, or security awareness training platforms, familiarity with integrations, APIs, low-code tools such as Airtable). That seems reasonable. Thus: - About the role: includes company overview, location, reporting, full-time, and the Opportunity paragraph. - Responsibilities: duties list. - Requirements: Required qualifications (bullet list). - Qualifications: Preferred qualifications (bullet list) maybe excluding the technical skills we move to Skills? But we could keep all preferred there and not have Skills. However we have technical skills that could be considered qualifications. The instruction: "Prefer a few substantive sections over many thin ones." So maybe better to have only Requirements and Qualifications (covering both required and preferred) and skip Skills. But we also have Benefits and Schedule. That's 4 sections plus About the role and Responsibilities = 6 sections. That's fine. But we need to ensure we don't miss any substantive info like "Experience managing a managed service provider relationship, or transitioning one." That's a qualification. So we can include in Qualifications. Thus we will not have a separate Skills section. Now Benefits: we have specific benefits. Schedule: we have occasional evening/weekend work, occasional travel to Chicago, flexibility to support occasional evening/weekend system cutovers. Now we need to format. We must not include boilerplate like "Physical Requirements", "Work Environment", "The Offer" heading (we will extract benefits and schedule from there). Also remove lines like "This job description in no way states or implies that these are the only duties..." etc. That's boilerplate; remove. Also remove EEO statements etc. Now produce HTML. Let's craft. First, a short paragraph for metadata and company overview:
Nuage Designs, Miami, FL – Reports to Chief Strategy & Operations Officer – Full‑Time, Exempt. For over two decades, Nuage Designs has set the standard for couture linens and luxury event rentals — trusted by the world’s top event planners, Fortune 500 companies, and luxury hotels to make moments extraordinary. Founded in Miami’s Wynwood district in 2004, we’ve grown into a team of over 140 across Miami, New York, and Chicago.
That captures location, reporting, employment type, and company overview. Now About the role heading:About the role
then paragraph(s) containing the Opportunity description. We need to preserve all substantive info from "The Opportunity" paragraph. Let's copy it: "The Opportunity Nuage is growing quickly, and our technology needs to grow with us. This is the first dedicated internal technology role in the company’s history, and it is a builder’s job: you will take ownership of the business systems, technology vendors, and user access the company runs on, and put real structure behind them. This is not a help desk role. Day-to-day desktop, network, and security support stays with our managed service provider, and our custom applications stay with our development partner. Your job is to make sure all of it is well managed, well documented, and ready for the next stage of growth — and to be the single point of ownership Nuage does not have today. You will work alongside an experienced fractional CIO who is leading our technology roadmap through our rental platform upgrade and customer portal launch in early 2027. Expect hands-on partnership and coaching during your first several months, with full ownership of the function as that work is completed." We'll put that in. Now Responsibilities heading:
Responsibilities
then list duties from "What You'll Do". The duties are grouped under headings: Business Systems Ownership, Projects & Platform Delivery, Technology Vendor & Contract Management, Support Experience & Onboarding, Accounts, Access & Security Coordination, Policy & Enablement. We'll create a- with
- for each duty item, preserving the sub-bullets? The original has bold headings then sentences. We can treat each heading as a separate
- with its description. Let's extract each: - Business Systems Ownership: Act as the internal system administrator and business owner for our core platforms, including our rental management system, ERP, Google Workspace, SaaS productivity and process management tools, phone system, and payment systems. Manage configuration, user roles, and reporting; identify and automate the manual workarounds that have built up over the years. Own the intake process for change requests to our custom applications and website, prioritizing them with business stakeholders before they reach the vendor. Partner with department leaders on data quality and the accuracy of product, inventory, and customer information across systems. - Projects & Platform Delivery: Serve as the internal project lead for technology initiatives alongside our fractional CIO, including our rental platform upgrade, customer portal, warehouse RFID, and the systems work that follows. Gather and document business requirements, coordinate user acceptance testing, organize training, and manage go-live readiness and cutover planning. Report progress, risks, and key measures to the executive team monthly. - Technology Vendor & Contract Management: Own the day-to-day relationship with our managed service provider, software development partner, rental management platform vendor, and the rest of our software portfolio. Maintain a complete contract and subscription register, including owner, term, renewal date, notice period, and service levels. Hold vendors accountable to agreed service levels and scope; lead renewals, escalations, and quarterly service reviews. Review technology invoices with Finance, track spend against budget, and run periodic license true-ups so we pay only for what we use. - Support Experience & Onboarding: Establish and publish one clear front door for technology help, so employees know where to go and nothing gets lost. Oversee the day-to-day performance of our outsourced IT support providers, making sure requests are resolved on time and escalated when needed. Build a repeatable new-hire technology setup: a standard equipment specification, a single purchasing channel, and a checklist that works the same way every time. Maintain an accurate inventory of company computers and equipment. Track support volume and recurring issues