Operations Specialist

We need to output HTML fragment with sections: About the role? Actually the posting includes "About Dauntless Industrial" (company description) and "Position Summary". The instructions: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include. The posting includes: About Dauntless Industrial (company description). Position Summary. Key Responsibilities (with sub-bullets). Qualifications (Required and Preferred). What We Offer (benefits). Also contact info: "Please Contact Alex Buchana For More Information Images" (likely contact). Also location: Dauntless Industrial LLC — Mesa, AZ (maybe location). The instructions: do not put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include location and contact in a short

maybe. We need to use

for section headings. So sections: About the Company? The instruction list includes "About the role" as example, but we can use "About Dauntless Industrial" as heading? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can use those exact headings if content matches. But we have company description, position summary, responsibilities, qualifications, benefits. Could map: - About the role: maybe position summary? Or we could use "About Dauntless Industrial" as a heading but not in list. However they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should use those headings when applicable. But we can also use other headings? The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we can use other headings if needed, but likely they want those specific headings for sections. However they also say "Do NOT repeat the job title as a heading (the page already shows it)". So we shouldn't add a heading for the job title. The posting does not have explicit headings like "About the role", but we can create sections accordingly. We need to preserve all substantive information. So we need to include company description, position summary, responsibilities, qualifications, benefits, maybe location/contact. We need to decide which headings to use: - About the role: could contain Position Summary. - Responsibilities: list of duties. - Requirements: could contain Qualifications Required. - Qualifications: maybe Preferred? But they have both Required and Preferred. Could combine under Qualifications. - Skills: maybe not needed separately. - Benefits: What We Offer. - Pay: they mention "Competitive pay based on experience" - that is pay info. So we should include Pay section. - Schedule: not mentioned explicitly; maybe not include. We need to avoid filler like "commensurate with experience". "Competitive pay based on experience" is specific enough? It's not a specific number but it's still substantive. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Competitive pay based on experience". So we can include Pay section with that sentence. Benefits: they list "Competitive pay based on experienceA small, close-knit team environment with direct access to ownershipOpportunity to grow into a broader operations role as the company expandsTuition reimbursementIndividual healthcare reimbursement (Dauntless does not offer group health insurance)". Actually the text: "What We Offer Competitive pay based on experienceA small, close-knit team environment with direct access to ownershipOpportunity to grow into a broader operations role as the company expandsTuition reimbursementIndividual healthcare reimbursement (Dauntless does not offer group health insurance)". There's missing spaces but we can parse. Thus Benefits section includes those items. Schedule: not mentioned, so we should not create Schedule section. Now we need to output only HTML fragment, no /, no markdown. We'll produce something like:

About the role

The Operations Specialist keeps the day-to-day business of Dauntless running smoothly — coordinating scheduling, customer communication, compliance documentation, and office administration so that the field and shop teams can focus on the technical work. This role is the central point of contact for customers, vendors, and subcontractor compliance platforms, and plays a key part in supporting bids, project tracking, and general business operations. This is not a technical fabrication role, but it does involve regular time out of the office — visiting customer sites, meeting with clients face-to-face, and occasional field support. It's a great fit for someone with strong organizational skills, a customer-service mindset, and the ability to learn our industry's processes and terminology quickly.

Responsibilities

• Customer & Office Administration: Serve as a primary point of contact for incoming customer calls, emails, and quote requests; maintain professional, responsive communication with clients throughout project lifecycles; manage general office administration: filing, correspondence, supply ordering, and day-to-day logistics.
• Scheduling & Project Coordination: Coordinate scheduling across field crews, shop work, and customer site visits; track project status and deadlines, flagging conflicts or delays to leadership; support subcontractor and vendor coordination, including scheduling and basic communications.
• Compliance & Documentation: Manage ISNetworld (ISN) and similar contractor compliance/prequalification platforms — submissions, renewals, and documentation upkeep; maintain certificates of insurance, licensing documentation, and safety program paperwork; support internal safety and quality documentation processes.
• Bid & Proposal Support: Assist with reading and organizing bid documents (scopes of work, specs, addenda) and tracking submission deadlines; help assemble bid packages, capability statements, and proposal materials under leadership's direction; track upcoming bid opportunities and renewal dates for existing contracts/prequalifications.
• Field Work & Customer Visits: Regularly visit customer sites to maintain relationships, check in on active projects, and represent Dauntless in person; provide occasional light field support as needed; travel locally within the Phoenix metro area (and occasionally beyond) as part of routine duties.
• Purchasing & Inventory Support: Assist with material and consumables ordering and tracking; support basic inventory oversight for shop supplies and equipment.
• Financial & HR Administration Support: Support invoicing, basic bookkeeping tasks, and payroll administration alongside leadership/bookkeeping resources; assist with onboarding paperwork for new hires.

Requirements

• Strong organizational skills and comfort managing multiple priorities and deadlines
• Excellent customer service and professional communication skills (phone, email, in-person)
• Proficiency with standard office software (email, spreadsheets, document management)
• Willingness and ability to learn industry-specific processes: ISN compliance, construction bid documents, and industrial service terminology
• Reliable, self-directed, and comfortable working in a small-company environment where responsibilities span multiple areas
• Valid driver's license and reliable transportation for regular customer site visits

Qualifications

• Experience with QuickBooks (or similar accounting software)
• Experience with a shop management or job-tracking software platform
• Experience with ISNetworld or similar contractor prequalification/compliance platforms
• Familiarity with construction, industrial services, or trades environments
• Prior experience in an operations, office management, or administrative role

Benefits

• Competitive pay based on experience
• Small, close-knit team environment with direct access to ownership
• Opportunity to grow into a broader operations role as the company expands
• Tuition reimbursement
• Individual healthcare reimbursement (Dauntless does not offer group health insurance)

Pay

Competitive pay based on experience

But we have duplicated pay info in Benefits and Pay. Might be redundant. The instruction: prefer a few substantive sections over many thin ones. Could combine pay into Benefits, and not create separate Pay section. However they said never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state pay, but we could include it under Benefits. The Benefits section already includes "Competitive pay based on experience". So we could omit a separate Pay section. That would reduce redundancy. Thus we have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits. We also need to include company description? The About Dauntless Industrial description is not captured. Could be placed under About the role? Or we could add a section "About the company". But the instruction list didn't include About the company, but we can still use

for any section heading. However they said "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't forbid other headings, but they gave examples. To be safe, we could incorporate company description into About the role section, maybe as a preceding paragraph. Or we could add a section "About Dauntless Industrial". But that might be considered extra heading not in examples; but likely acceptable. However they said "Prefer a few substantive sections over many thin ones." Adding another section increases count. Might be better to incorporate company description into About the role or maybe a short paragraph before sections. We need to preserve ALL substantive information. So we must include the company description. We can put it in a

before the first heading, or as part of About the role. Let's put a

with company description, then

About the role

with position summary. Thus:

Dauntless Industrial LLC is a premium industrial fabrication, millwright, and repair services company based in Mesa, Arizona. Since 2016, we've built a reputation for structural welding, pipefitting, millwright work, and equipment repair — backed by an in-house 3D scanning and CAD modeling capability that sets us apart from competitors in the region. We are a fully licensed contractor serving industrial, municipal, and construction clients across Arizona.

About the role

Position summary...

Then responsibilities, requirements, qualifications, benefits. We also need to include location/contact? The posting includes "Dauntless Industrial LLC — Mesa, AZ" at start, and "Please Contact Alex Buchana For More Information Images". That's minor metadata; we can fold into a short

maybe after company description or at end. Could add a

Location: Mesa, AZ. Contact: Alex Buchana.

but that's minor. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we can include a short