Document Controller
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We must not include Job ID etc. Remove boilerplate. We need to preserve substantive info. Let's parse the posting: - Job Type: Full Time | Location: Fort Worth, Texas | Department: Engineering | Reporting to: VP of Engineering | Work Location Type: #hybrid We can include location and maybe work type in a short
maybe under "About the role"? The instruction: "Prefer a few substantive sections over many thin ones." We can combine some. We need sections: About the role (maybe a paragraph summarizing role). Responsibilities (list). Requirements (list). Qualifications? Might duplicate with Requirements. Could combine. Skills maybe separate. Benefits (list). Pay: The posting mentions compensation but not specific numbers; says "Actual compensation will be determined based on factors such as experience, qualifications, and market data for the region." That's vague; we should not create Pay section if only vague? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state compensation package includes base salary, annual performance incentives, equity programs, etc. That's substantive enough? It says "Actual compensation will be determined based on factors..." but also mentions base salary, incentives, equity. That's specific enough to include a Benefits? Actually compensation is separate from Benefits. The instruction: "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')". The posting says "Actual compensation will be determined based on factors such as experience, qualifications, and market data for the region." That's somewhat vague but also mentions base salary, annual performance incentives, equity programs. That's specific enough? I'd say we can include a Pay section with that description. However they also have a Benefits section later with details. So we can have Benefits and Pay separate. Schedule: Not mentioned besides hybrid work location type. No explicit schedule (e.g., Monday-Friday). So we should not create Schedule section. Now we need to output HTML fragment only. Let's craft:
About the role
IREN is a vertically integrated AI Cloud provider delivering large-scale data centers and GPU clusters for AI training and inference. Reporting to the Vice President of Engineering, the Document Controller will manage the creation, distribution, revision, and storage of engineering and maintenance documentation across the organisation. This role ensures that all engineering and technical documents—including drawings, specifications, procedures, manuals, reports, and vendor data—are accurate, current, and easily accessible to project teams, maintenance staff, and engineering stakeholders. The position is full‑time, hybrid‑based in Fort Worth, Texas, within the Engineering department.
Then Responsibilities as- ... each bullet.
We need to preserve all substantive responsibilities. Let's list them from the responsibilities paragraph.
Responsibilities list:
- Maintain, organize, and update engineering documents in alignment with company standards and procedures.
- Manage document workflows, including creation, review, approval, issuance, and archiving of documents.
- Ensure proper document numbering, coding, metadata assignment, and formatting.
- Control technical records for engineering projects, design packages, as-built documentation, and maintenance files.
- Enforce revision control to ensure teams are always working with the latest approved documents.
- Ensure compliance with regulatory, quality, and internal standards (ISO, engineering codes, project requirements).
- Track document changes, maintain revision histories, and manage controlled copies.
- Administer internal and external electronic document management systems (EDMS) or engineering document control tools (e.g., Procore, SharePoint).
- Create and manage user permissions, folder structures, and workflows within the system.
- Provide system support, troubleshooting, and basic training for users.
- Coordinate with engineering, procurement, construction, operations, and maintenance teams to ensure timely document flow.
- Assist in compiling engineering documentation packages such as design deliverables, RFI responses, test records, vendor dossiers, and construction records.
- Support project close-out by ensuring all as-built and final documentation is collected, validated, and archived.
- Perform regular audits to ensure data accuracy, correct file storage, and adherence to document control standards.
- Identify and resolve discrepancies, missing documentation, or non-compliant file structures.
- Ensure engineering documents are classified, tagged, and searchable for efficient retrieval.
- Act as the focal point for document distribution between internal teams, contractors, and external stakeholders.
- Provide timely notifications and updates to project teams regarding document status and deliverables.
- Maintain trackers, logs, and reports on document progress and approvals.
Now Requirements: list from "Job Requirements". Let's extract:
- Degree in engineering, technical administration, information management, or a related field.
- 2–5+ years of experience in document control, preferably in engineering, construction, manufacturing, energy, or industrial sectors.
- Training or certification in document control principles is an asset.
- Experience with electronic document management systems (EDMS) or project collaboration platforms.
- Understanding of engineering drawings, technical terminology, and project documentation conventions.
- Proficiency in Microsoft Office, with focus on MS SharePoint; familiarity with PDF markup tools and technical file formats.
- Exceptional attention to detail, accuracy, and organisation.
- Strong communication and coordination skills.
- Ability to manage multiple priorities and deadlines.
- High level of integrity and commitment to maintaining data quality.
- Experience supporting multidisciplinary engineering teams is highly desirable.
- Knowledge of engineering design workflows and project documentation lifecycles.
- Other important requirements: Pre-employment screening, including background check and substance testing may be required according to company policies.
- Must provide own steel-toed work boots; other PPE will be supplied.
- Must be able to reliably commute to the work site daily or have plans to relocate before starting work.
We could separate "Qualifications" maybe same as Requirements. But we can have Requirements and Skills separate. However we have many items that could be considered skills (proficiency in MS Office, SharePoint, etc.). The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can decide to use Requirements for education/experience, Skills for technical proficiencies, Qualifications maybe for certifications? But we should avoid thin sections. Perhaps combine Requirements and Qualifications into one section called Requirements (includes education, experience, certifications). Then Skills section for technical proficiencies (MS Office, SharePoint, PDF markup, etc.). Benefits section for benefits. Pay section for compensation details.
Let's do:
Requirements
- Degree in engineering, technical administration, information management, or a related field.
- 2–5+ years of experience in document control, preferably in engineering, construction, manufacturing, energy, or industrial sectors.
- Training or certification in document control principles is an asset.
- Experience supporting multidisciplinary engineering teams is highly desirable.
- Knowledge of engineering design workflows and project documentation lifecycles.
- High level of integrity and commitment to maintaining data quality.
- Ability to manage multiple priorities and deadlines.
- Strong communication and coordination skills.
- Exceptional attention to detail, accuracy, and organisation.
- Pre-employment screening, including background check and substance testing may be required according to company policies.
- Must provide own steel-toed work boots; other PPE will be supplied.
- Must be able to reliably commute to the work site daily or have plans to relocate before starting work.
Skills
- Proficiency in Microsoft Office, with focus on MS SharePoint.
- Familiarity with PDF markup tools and technical file formats.
- Experience with electronic document management systems (EDMS) or project collaboration platforms.
- Understanding of engineering drawings, technical terminology, and project documentation conventions.
- ... . Let's extract:
- Highly competitive compensation package that includes base salary, annual performance incentives, and opportunities to build long-term wealth through equity programs.
- Total Rewards package designed to support health, well-being, and long-term success.
- Compensation: Actual compensation will be determined based on factors such as experience, qualifications, and market data for the region. Total Compensation package may be inclusive of short-term and long-term incentives.
- Relocation (as applicable and based on successful candidate circumstances)
- Health & Wellness:
* Medical, dental, and vision insurance coverage – 100% company paid for employees, 75% company paid coverage for dependents
* Company-paid life and disability insurance
* Voluntary life, critical illness, and accident coverage available
* Health Savings Accounts (HSA) – when combined with the High-Deductible Health Plan
* Employee Assistance Program and wellness resources
- Financial Well-Being:
* 401(k) retirement plan with company match
* Financial wellness tools and resources
- Time Off & Flexibility:
* Paid Time Off (PTO) and paid holidays
* Flexible work arrangements
- Growth & Development:
* Opportunities for advancement and internal mobility
* Training and personal development opportunities
- Lifestyle & Culture:
* Company events and team-building activities
* We value diverse perspectives and believe that skills can be developed.
We need to avoid filler like "as applicable and based on successful candidate circumstances" maybe still okay. It's specific enough.
We'll create Benefits section with subheadings? Not allowed; only
headings. We could just list all benefits as list items, maybe grouping with commas. But we need to preserve all substantive info. Could break into multiple
- but each under same heading? Probably okay to have one
- ? Not prohibited but better to keep simple text.
We'll do:
Benefits
- Competitive compensation package including base salary, annual performance incentives, and equity opportunities for long‑term wealth building.
- Total Rewards package supporting health, well‑being, and long‑term success.
- Compensation determined by experience, qualifications, and regional market data; may include short‑ and long‑term incentives.
- Relocation assistance (as applicable).
- Health & Wellness: medical, dental, and vision insurance – 100% company paid for employees, 75% for dependents; company‑paid life and disability insurance; voluntary life, critical illness, and accident coverage; Health Savings Account (HSA) options; Employee Assistance Program and wellness resources.
- Financial Well‑Being: 401(k) retirement plan with company match; financial wellness tools and resources.
- Time Off & Flexibility: Paid Time Off (PTO) and paid holidays; flexible work arrangements.
- Growth & Development: opportunities for advancement and internal mobility; training and personal development opportunities.
- Lifestyle & Culture: company events and team‑building activities; commitment to diverse perspectives and skill development.
- with many items, each item can contain subdetails.
Let's craft each benefit as a list item, possibly with line breaks using
inside - ? Not prohibited but better to keep simple text.
We'll do: