IT Product Manager, Construction & Facilities

We need to output HTML fragment with sections: About the role? Actually description includes "ABOUT WHO BREW" then "THE JOB", "Requirements", "WHAT YOU'LL DO", "THE SYSTEMS", "YOUR FIRST YEAR", "What We're Looking For", "NICE TO HAVE", "How We Work", "Benefits", "Location", "Compensation details". We must use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to map content to these headings. Use only sections that have real specific content. Avoid filler. We must not repeat job title as heading. No Job ID etc. We need to decide which headings to use: About the role (maybe corresponds to "ABOUT WHO BREW" and "THE JOB"?). Responsibilities (maybe "WHAT YOU'LL DO"). Requirements (maybe "What We're Looking For" plus "NICE TO HAVE"?). Qualifications maybe same as Requirements? But we can combine. Skills maybe from requirements. Benefits from Benefits. Pay from Compensation details. Schedule maybe from Location/Remote? Not exactly schedule; but we have location remote and travel. Could treat as Schedule? Probably not. Better to omit Schedule if no specific schedule info. Pay we have salary range. We must not create sections with placeholder like "not specified". So only include sections where we have concrete info. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay. Possibly also "Location" but not in allowed headings list; we could incorporate into About the role or maybe not needed. The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. Safer to stick to those. We'll create:

About the role

with paragraph summarizing Who Brew, technology team role, etc.

Responsibilities

with

• list of duties from WHAT YOU'LL DO.

  Requirements

  with
  • list from What We're Looking For plus maybe NICE TO HAVE as separate? Could combine but maybe separate sections: Requirements and Skills? But we have Skills heading allowed. Could put technical skills under Skills. Let's do Requirements for education/experience, Skills for specific abilities. Thus:

    Requirements

    with education and experience.

    Skills

    with bullet list of abilities: spreadsheets, SQL, writing specs, data checking, AI tools, etc.

    Benefits

    with
    • list.

      Pay

      with paragraph salary range. We must not include location as separate heading; could embed in About the role or Responsibilities? Probably include in About the role as a sentence. We must preserve all substantive information; not invent or summarize away detail. Must keep details like 44 drive-thru coffee stands, six states, 20 under construction, etc. Must include specifics about systems, tasks, first year timeline, etc. We need to ensure we don't omit any substantive info. That's a lot. We'll need to embed many details in the lists. Let's extract details: About Who Brew: 7 Brew franchisee, 44 drive-thru coffee stands across six states, 20 more under construction, pipeline of sites behind those. Every stand has a life: site found, permitted, built, opened, run for years. Technology team owns systems that carry a stand through that life, and the money that flows through all of it. The Job: Every stand has a life... (the paragraph). Own the systems: Procore, Ecotrak, Smartsheet, Sage Intacct, tools built on top. Rollout job first: Procore rolling out for new projects. Ecotrak goes live this fall for facilities team. Connector moving construction costs from Procore into Sage being configured. Development tracker lives in Smartsheet workspace with folder per site, half company's reporting hangs off. Job: get new stack adopted, retire old one cleanly, ensure data (sites, stage, budget, Sage project) right in one place. Responsibilities (WHAT YOU'LL DO): - Own the request queue for construction and facilities systems. Every ask gets written up, prioritized with development and facilities leads, closed with note on what shipped. - Run the Ecotrak rollout: locations, service providers, users, preventive maintenance schedules loaded and right. Work orders flowing. Facilities team and district managers trained. Repair and maintenance invoices landing in AP without rekeying. - Run our side of the Procore rollout: action plan templates for entitlements and pre-construction, project setup standards, cost code and cost type structure the Sage connector needs, handoff from Smartsheet. - Keep the site pipeline data straight: which sites exist, what stage they're in, what the budget is, what the Sage project ID is. Feeds cash-flow forecast and board reporting, so must be right. - Own the technology checklist for a new stand opening: network, cameras, point of sale, and accounts for manager and crew, all in place before doors open. Make it run same way every time. - Write specs for what we build in house: pre-construction task tool that runs inside Procore, stand roster every other system reads from, access rules that give a new manager the right systems on day one. - Test what gets built against real projects and real stands before it ships. - Own vendor relationships: Procore, Ecotrak, Sage reseller, network and camera vendors. Know who to call and what to ask. - Keep docs current and train people when something changes. Some of that happens at stands and job sites. Systems list (THE SYSTEMS): - Procore: construction management. Action plans, budgets, commitments, invoices. Plus entitlements tool we built that runs inside it. - Ecotrak: facilities. Work orders, preventive maintenance, assets, service providers. - Smartsheet: today's development tracker. Site pipeline, budget estimates, project plans. - Sage Intacct construction module: projects, CIP accounts, cost codes and types. And the Procore connector. Supported by reseller RKL. - Egnyte: project documents and master contact list. - Placer.ai: foot traffic data for site selection. - Our portal: stand roster, people directory, access rules, new-stand provisioning. - Stand infrastructure: network and WiFi, cameras, point of sale hardware, and vendors behind them. - Data warehouse and dashboards built on it. Everything above reports through here. Your First Year: - 30 days: Walk site pipeline end to end with development team, visit a stand under construction and an open one, take over request queue. - 90 days: Ecotrak live for facilities team with every location, vendor, user loaded, work orders flowing. Every new Procore project starts from a template with a Sage project ID on day one. - One year: Smartsheet retired as project tracker. Construction invoice goes from Procore to Sage without rekeying. Repair and maintenance spend visible by stand and by asset. New stand's technology is a checklist that runs same way every time. What We're Looking For: - Bachelor's degree in construction management, information systems, business, engineering, or related field, or equivalent work history. - 1 to 3 years in a role like this: project or construction coordination, facilities coordination, business or systems analyst, implementation or product work, or internship where you owned a process end to end. - You've been close to a build or a facilities team. You know what a change order is, or why a broken ice machine is a today problem. - Spreadsheets are second nature. You can read a SQL query, or you'll learn in first 90 days. We'll teach you. - You write clearly. A 30-minute conversation becomes a one-page spec with no loose ends. - You check the data. When two systems disagree about a stand, you find out which one is right before you tell anyone. - You've used AI tools for real work and have opinions about where they're good and where they're not. - Some travel to stands and job sites. Nice to Have: - Hands-on time in Procore, Ecotrak or another CMMS, Smartsheet, or Sage Intacct. - Multi-site restaurant or retail development. - You've rolled out a system to people who didn't ask for it and got them to like it. - A tracker like Linear or Jira where you kept the queue clean. How We Work: - Small team, close to the business. You'll spend more time with development and facilities teams than with engineers. - We build with AI coding agents under human review. Dev, preview, production. Releases ship most weeks. You decide when something is ready. - Work is tracked in Linear. Docs live in Notion. - Nothing we ship gets relied on until it's checked against the source system. Benefits: - Medical, Dental, and Vision Insurance - Life & AD&D Coverage - Flexible PTO for eligible corporate team members - Paid parental leave for eligible full-time, benefits-eligible team members with at least 12 months of continuous service - Paid Bereavement Leave for qualifying family losses - Benefit eligibility and leave programs are subject to the terms of the applicable Who Brew policies and benefit plans. Location - Remote: Full time. Some travel to stands and job sites. (Candidates in the Central or Eastern time zones are preferred and expected to work Eastern Time hours). Compensation details: 65000-90000 Yearly Salary PIe5027fb765cc-25448-41632386 (the last part looks like a job ID; we should drop minor metadata). So just salary range. Now produce HTML. We'll need to ensure we don't include any boilerplate like EEO etc. Already removed. We'll output only HTML fragment. Let's craft.

      About the role

      Who Brew is a 7 Brew franchisee operating 44 drive-thru coffee stands across six states, with 20 more under construction and a pipeline of sites behind those. Each stand follows a life cycle: site found, permitted, built, opened, and then run for years. The technology team owns the systems that carry a stand through that life and the money that flows through it, including Procore for construction, Ecotrak for facilities, Smartsheet for development tracking, Sage Intacct for finance, and custom tools built on top of those platforms.

      Responsibilities

      • Own the request queue for construction and facilities systems: write up each ask, prioritize with development and facilities leads, and close with a note on what shipped.
      • Run the Ecotrak rollout: load locations, service providers, users, and preventive maintenance schedules; ensure work orders flow; train the facilities team and district managers; make repair and maintenance invoices land in AP without rekeying.
      • Run our side of the Procore rollout: create action plan templates for entitlements and pre‑construction, define project setup standards, establish the cost code and cost type structure needed by the Sage connector, and manage the handoff from Smartsheet.
      • Maintain accurate site pipeline data: track which sites exist, their stage, budget, and Sage project ID; this data feeds cash‑flow forecasts and board reporting.
      • Own the technology checklist for a new stand opening: verify network, cameras, point‑of‑sale hardware, and manager/crew accounts are in place before doors open, and make the process repeatable.
      • Write specifications for in‑house builds: the pre‑construction task tool that runs inside Procore, the stand roster used by other systems, and access rules that give a new manager the right systems on day one.
      • Test new features against real projects