IT Support Engineer
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading (the page already shows it). Do NOT put Job ID / Job ID etc. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. Output ONLY HTML fragment.
We need to parse the posting and extract sections.
The posting includes:
- Intro about company: description of ePayPolicy, mission, etc. Could be "About the role"? Actually "About the role" maybe not present. There's description of company and mission. Could be "About the role" or "About the company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to these headings if appropriate.
We have:
- "What You’ll Build & Own" -> responsibilities.
- "What You Bring (Concepts Over Tools)" -> requirements/qualifications/skills.
- "Who You Are" -> maybe skills or qualifications? It's about personal traits.
- "Why ePayPolicy" -> benefits, pay, schedule, culture etc.
- "Competitive salaryComprehensive benefits package..." -> benefits and pay.
- "Fully-stocked kitchen..." etc -> benefits.
- "We operate on a hybrid schedule..." -> schedule.
- "Embracing AI at ePayPolicy" -> maybe responsibilities? but could be part of culture.
- Diversity statement etc -> maybe not needed.
We need to avoid filler like "commensurate with experience" etc. Not present.
We need to ensure we don't create sections with no real content.
Let's extract substantive content.
**About the role**: Could be the introductory paragraph describing the role? The posting didn't have a explicit "About the role" heading, but we could create one using the initial description: "Every day, ePayPolicy helps over 10,000 insurance companies speed up incoming and outgoing payments..." That's more about company, not role. Might be better to put under "About the role" a brief description of the role: maybe the mission and upside? The section "The Mission & The Upside" describes why you should join. That could be considered "About the role". We'll include that.
**Responsibilities**: from "What You’ll Build & Own" bullet points: Automate Automate Automate, Identity & Access Management, Fleet & Endpoint Architecture, Scaling Securely. Also maybe "Working alongside a lean team, you will share the support queue while focusing on:" then list.
**Requirements / Qualifications / Skills**: "What You Bring (Concepts Over Tools)" includes IdP, MDM, OS Mastery & Networking, Automation Mindset. Also "Who You Are" includes Scrappy & Root-Cause Obsessed, Fiercely Collaborative. Could be skills.
We need to decide which headings to use. We have three categories: Responsibilities, Requirements, Qualifications, Skills. Could combine Requirements and Qualifications into one? But we must follow allowed headings; we can include multiple if they have content.
We need to avoid thin sections. Let's see if we have enough for each.
- Responsibilities: we have several bullet points; good.
- Requirements: maybe technical concepts: IdP, MDM, OS Mastery & Networking, Automation Mindset. That's enough.
- Qualifications: maybe "Who You Are" traits? Could be considered qualifications. Or we could put those under Skills.
- Skills: maybe the same as Requirements? Might be redundant.
Better to have: Responsibilities, Requirements, Skills. And maybe Benefits, Pay, Schedule.
Let's map:
**Responsibilities**: from "What You’ll Build & Own" list.
**Requirements**: from "What You Bring (Concepts Over Tools)" technical concepts.
**Skills**: from "Who You Are" personal traits.
**Benefits**: from "Why ePayPolicy" bullet list: Competitive salary, Comprehensive benefits package with employer-paid basic life and disability premiums, 401K, Flexible Paid Time Off Policy (FTO), Company-sponsored quarterly “ePayItForward” initiatives, Supportive and inclusive company culture..., Fully-stocked kitchen, Lunch stipend when working onsite, Open communication..., Huge opportunity for growth.
**Pay**: maybe we need to extract salary specifics? The posting says "Competitive salary" but no number. That's filler? It's not a specific number, but it's still mention of pay. The rule: do NOT create Pay section unless posting actually states them. It states "Competitive salary" which is vague but still states pay exists. Is that considered filler? The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive salary" is similar to placeholder? It's not a specific number but it's still a statement. Might be considered filler? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive salary". So we can include Pay section with that line. However we should avoid filler like "commensurate with experience". "Competitive salary" is somewhat generic but still states that there is a competitive salary. I'd include it.
**Schedule**: from "We operate on a hybrid schedule for in-office employees. Standard schedules are three days per week in the office, however, the cadence and days are determined by each team and manager." That's specific enough.
Now we need to format.
We must not include any markdown fences. Just raw HTML.
We need to use
for section headings.
Inside sections, we need to use
for prose, and
- for any list of duties/requirements/benefits.
We need to preserve ALL substantive information; do not invent or summarize away detail.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes at end: "We strive to create an accessible and inclusive experience for all candidates. If you need an accommodation during the application or recruiting process, please submit a request to our team via this Interview Accommodation form: https://forms.gle/xKppyKTSqfTUi7hz5". That's application instructions/accommodation; should be removed.
Also "Check out our almost 5-star customer reviews." maybe keep? It's part of company description; not boilerplate. Keep.
Also "Founded in 2014, our growing team is based in Austin, TX, and has clients in all 50 US states. We’ve grown over 300% in the last three years - with big plans for the future." Keep as part of About the role maybe.
Now we need to decide which content goes where.
**About the role**: Could include company description, mission & upside. Let's craft a paragraph(s) summarizing: "Every day, ePayPolicy helps over 10,000 insurance companies speed up incoming and outgoing payments. By helping them move from manual, outdated forms of payment collection to modern payment tools, we help their companies work faster and more efficiently. (Check out our almost 5-star customer reviews.) How do we do it? With powerful payment tools that just work. Our secure, online ACH and credit card payment page is the core product for many of our companies. But we also provide an integrated suite of helpful features for insurance companies of all sizes, including point-of-sale financing, payables network tools, and check reconciliation, all within a single dashboard. Our expert, live support team helps deliver exceptional care every day, with an industry-leading 97% customer retention rate. Our customers love us. We love them. Founded in 2014, our growing team is based in Austin, TX, and has clients in all 50 US states. We’ve grown over 300% in the last three years - with big plans for the future. The Mission & The Upside: We are a hyper-growth startup in the Payments space. Because we operate in a highly regulated industry, security and compliance aren't afterthoughts—they are the product. We treat IT as a strategic engineering multiplier, not a basement helpdesk. Top-tier engineers have options. Here is why you should leave a comfortable legacy job to come build with us: The Compliance Puzzle: Your challenge is to build automated, frictionless IT workflows that flawlessly pass strict audits (SOC 2, PCI, etc.) without slowing the company down. We don't want you to manually manage red tape; we want you to engineer it away. The 'Blank Canvas' Thrill: You aren't maintaining someone else's legacy technical debt. You will have the autonomy to make foundational architectural decisions that define our security posture. Skin in the Game: We offer massive career velocity as we scale, backed by highly competitive bonus structure. When the company wins, you share in the financial upside."
That's a lot but we need to preserve all substantive information; we can't summarize away detail. However we can keep as prose paragraphs; we can break into multiple
tags.
But we must not invent or summarize away detail; we can keep the sentences as is.
We'll need to ensure we don't include duplicated lines. There's some duplication? Not obvious.
Now Responsibilities: list items:
- Automate Automate Automate: Provide white-glove L1-L3 support, but your ultimate directive is to design self-service workflows and L1 bots to aggressively engineer repetitive tickets out of existence.
- Identity & Access Management: Administer the heartbeat of our access. Manage our Identity Providers (IdP) to ensure secure authentication, SSO, and automated, zero-touch onboarding/offboarding pipelines.
- Fleet & Endpoint Architecture: Engineer our Mobile Device Management (MDM) platforms. Enforce security postures and build zero-touch provisioning so a new hire can securely get to work on day one.
- Scaling Securely: Partner with the IT Manager and Security team to execute infrastructure scaling projects, respond to incidents, and roll out new security initiatives.
We should keep each as
- maybe with the heading bold? But we just need to preserve text. We'll put each as
- containing the sentences.
Now Requirements: from "What You Bring (Concepts Over Tools)":
- Identity & Access (IdP): You deeply understand SSO, SAML/OIDC, directory services, and lifecycle management—whether your past experience is with Microsoft Entra, Okta, Ping Identity, or JumpCloud.
- Device Management (MDM): You understand the philosophy of zero-touch deployment and endpoint compliance—regardless of whether you've used Jamf, Intune, Kandji, or Workspace ONE.
- OS Mastery & Networking: Strong proficiency in managing macOS and Windows endpoints, plus a solid grasp of standard office networking (TCP/IP, DNS, VPN architecture).
- The Automation Mindset: You look at manual tasks as bugs to be fixed. You have experience (or a strong desire to learn) using APIs, integration tools, or scripting (Bash, PowerShell, Python) to automate the boring stuff away.
Now Skills: from "Who You Are":
- Scrappy & Root-Cause Obsessed: You thrive without a fully written playbook. You don't put bandaids on problems; you dig until you engineer permanent, scalable solutions.
- Fiercely Collaborative: You check your ego at the door, share knowledge freely, and are always willing to jump into the trenches with your team.
Maybe also include "We value diversity..." but that's more company policy; could be omitted as not
for prose. Do NOT repeat job title as heading (the page already shows it). Do NOT put Job ID / Job ID etc. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. Output ONLY HTML fragment. We need to parse the posting and extract sections. The posting includes: - Intro about company: description of ePayPolicy, mission, etc. Could be "About the role"? Actually "About the role" maybe not present. There's description of company and mission. Could be "About the role" or "About the company". But we only have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should map content to these headings if appropriate. We have: - "What You’ll Build & Own" -> responsibilities. - "What You Bring (Concepts Over Tools)" -> requirements/qualifications/skills. - "Who You Are" -> maybe skills or qualifications? It's about personal traits. - "Why ePayPolicy" -> benefits, pay, schedule, culture etc. - "Competitive salaryComprehensive benefits package..." -> benefits and pay. - "Fully-stocked kitchen..." etc -> benefits. - "We operate on a hybrid schedule..." -> schedule. - "Embracing AI at ePayPolicy" -> maybe responsibilities? but could be part of culture. - Diversity statement etc -> maybe not needed. We need to avoid filler like "commensurate with experience" etc. Not present. We need to ensure we don't create sections with no real content. Let's extract substantive content. **About the role**: Could be the introductory paragraph describing the role? The posting didn't have a explicit "About the role" heading, but we could create one using the initial description: "Every day, ePayPolicy helps over 10,000 insurance companies speed up incoming and outgoing payments..." That's more about company, not role. Might be better to put under "About the role" a brief description of the role: maybe the mission and upside? The section "The Mission & The Upside" describes why you should join. That could be considered "About the role". We'll include that. **Responsibilities**: from "What You’ll Build & Own" bullet points: Automate Automate Automate, Identity & Access Management, Fleet & Endpoint Architecture, Scaling Securely. Also maybe "Working alongside a lean team, you will share the support queue while focusing on:" then list. **Requirements / Qualifications / Skills**: "What You Bring (Concepts Over Tools)" includes IdP, MDM, OS Mastery & Networking, Automation Mindset. Also "Who You Are" includes Scrappy & Root-Cause Obsessed, Fiercely Collaborative. Could be skills. We need to decide which headings to use. We have three categories: Responsibilities, Requirements, Qualifications, Skills. Could combine Requirements and Qualifications into one? But we must follow allowed headings; we can include multiple if they have content. We need to avoid thin sections. Let's see if we have enough for each. - Responsibilities: we have several bullet points; good. - Requirements: maybe technical concepts: IdP, MDM, OS Mastery & Networking, Automation Mindset. That's enough. - Qualifications: maybe "Who You Are" traits? Could be considered qualifications. Or we could put those under Skills. - Skills: maybe the same as Requirements? Might be redundant. Better to have: Responsibilities, Requirements, Skills. And maybe Benefits, Pay, Schedule. Let's map: **Responsibilities**: from "What You’ll Build & Own" list. **Requirements**: from "What You Bring (Concepts Over Tools)" technical concepts. **Skills**: from "Who You Are" personal traits. **Benefits**: from "Why ePayPolicy" bullet list: Competitive salary, Comprehensive benefits package with employer-paid basic life and disability premiums, 401K, Flexible Paid Time Off Policy (FTO), Company-sponsored quarterly “ePayItForward” initiatives, Supportive and inclusive company culture..., Fully-stocked kitchen, Lunch stipend when working onsite, Open communication..., Huge opportunity for growth. **Pay**: maybe we need to extract salary specifics? The posting says "Competitive salary" but no number. That's filler? It's not a specific number, but it's still mention of pay. The rule: do NOT create Pay section unless posting actually states them. It states "Competitive salary" which is vague but still states pay exists. Is that considered filler? The rule says never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). "Competitive salary" is similar to placeholder? It's not a specific number but it's still a statement. Might be considered filler? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive salary". So we can include Pay section with that line. However we should avoid filler like "commensurate with experience". "Competitive salary" is somewhat generic but still states that there is a competitive salary. I'd include it. **Schedule**: from "We operate on a hybrid schedule for in-office employees. Standard schedules are three days per week in the office, however, the cadence and days are determined by each team and manager." That's specific enough. Now we need to format. We must not include any markdown fences. Just raw HTML. We need to use
for section headings. Inside sections, we need to use
for prose, and
- for any list of duties/requirements/benefits.
We need to preserve ALL substantive information; do not invent or summarize away detail.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The posting includes at end: "We strive to create an accessible and inclusive experience for all candidates. If you need an accommodation during the application or recruiting process, please submit a request to our team via this Interview Accommodation form: https://forms.gle/xKppyKTSqfTUi7hz5". That's application instructions/accommodation; should be removed.
Also "Check out our almost 5-star customer reviews." maybe keep? It's part of company description; not boilerplate. Keep.
Also "Founded in 2014, our growing team is based in Austin, TX, and has clients in all 50 US states. We’ve grown over 300% in the last three years - with big plans for the future." Keep as part of About the role maybe.
Now we need to decide which content goes where.
**About the role**: Could include company description, mission & upside. Let's craft a paragraph(s) summarizing: "Every day, ePayPolicy helps over 10,000 insurance companies speed up incoming and outgoing payments. By helping them move from manual, outdated forms of payment collection to modern payment tools, we help their companies work faster and more efficiently. (Check out our almost 5-star customer reviews.) How do we do it? With powerful payment tools that just work. Our secure, online ACH and credit card payment page is the core product for many of our companies. But we also provide an integrated suite of helpful features for insurance companies of all sizes, including point-of-sale financing, payables network tools, and check reconciliation, all within a single dashboard. Our expert, live support team helps deliver exceptional care every day, with an industry-leading 97% customer retention rate. Our customers love us. We love them. Founded in 2014, our growing team is based in Austin, TX, and has clients in all 50 US states. We’ve grown over 300% in the last three years - with big plans for the future. The Mission & The Upside: We are a hyper-growth startup in the Payments space. Because we operate in a highly regulated industry, security and compliance aren't afterthoughts—they are the product. We treat IT as a strategic engineering multiplier, not a basement helpdesk. Top-tier engineers have options. Here is why you should leave a comfortable legacy job to come build with us: The Compliance Puzzle: Your challenge is to build automated, frictionless IT workflows that flawlessly pass strict audits (SOC 2, PCI, etc.) without slowing the company down. We don't want you to manually manage red tape; we want you to engineer it away. The 'Blank Canvas' Thrill: You aren't maintaining someone else's legacy technical debt. You will have the autonomy to make foundational architectural decisions that define our security posture. Skin in the Game: We offer massive career velocity as we scale, backed by highly competitive bonus structure. When the company wins, you share in the financial upside."
That's a lot but we need to preserve all substantive information; we can't summarize away detail. However we can keep as prose paragraphs; we can break into multiple
tags. But we must not invent or summarize away detail; we can keep the sentences as is. We'll need to ensure we don't include duplicated lines. There's some duplication? Not obvious. Now Responsibilities: list items: - Automate Automate Automate: Provide white-glove L1-L3 support, but your ultimate directive is to design self-service workflows and L1 bots to aggressively engineer repetitive tickets out of existence. - Identity & Access Management: Administer the heartbeat of our access. Manage our Identity Providers (IdP) to ensure secure authentication, SSO, and automated, zero-touch onboarding/offboarding pipelines. - Fleet & Endpoint Architecture: Engineer our Mobile Device Management (MDM) platforms. Enforce security postures and build zero-touch provisioning so a new hire can securely get to work on day one. - Scaling Securely: Partner with the IT Manager and Security team to execute infrastructure scaling projects, respond to incidents, and roll out new security initiatives. We should keep each as
- maybe with the heading bold? But we just need to preserve text. We'll put each as
- containing the sentences. Now Requirements: from "What You Bring (Concepts Over Tools)": - Identity & Access (IdP): You deeply understand SSO, SAML/OIDC, directory services, and lifecycle management—whether your past experience is with Microsoft Entra, Okta, Ping Identity, or JumpCloud. - Device Management (MDM): You understand the philosophy of zero-touch deployment and endpoint compliance—regardless of whether you've used Jamf, Intune, Kandji, or Workspace ONE. - OS Mastery & Networking: Strong proficiency in managing macOS and Windows endpoints, plus a solid grasp of standard office networking (TCP/IP, DNS, VPN architecture). - The Automation Mindset: You look at manual tasks as bugs to be fixed. You have experience (or a strong desire to learn) using APIs, integration tools, or scripting (Bash, PowerShell, Python) to automate the boring stuff away. Now Skills: from "Who You Are": - Scrappy & Root-Cause Obsessed: You thrive without a fully written playbook. You don't put bandaids on problems; you dig until you engineer permanent, scalable solutions. - Fiercely Collaborative: You check your ego at the door, share knowledge freely, and are always willing to jump into the trenches with your team. Maybe also include "We value diversity..." but that's more company policy; could be omitted as not