Jobs · Information Technology · Tennessee

Principal Data Hall Designer

Oracle · Nashville, TN · 4 wk ago
Information Technology$115k–$235k/yrFull-time
We need to output HTML fragment with sections: About the role? Actually we need to include sections only when posting has real content. The posting includes: Key Responsibilities (list), JOB DESCRIPTION (maybe not needed), then many bullet points under responsibilities. Then "QUALIFICATIONS" section with disclaimer, salary range, benefits, etc. Also "About Us". Also "Core Responsibilities" (maybe duplicate). We need to parse and produce sections: About the role? Not present. Responsibilities: we have many bullet points. Requirements/Qualifications: we have qualifications section. Skills? Not explicit. Benefits: we have benefits listed. Pay: we have salary range. Schedule: not present. So we include sections: Responsibilities, Qualifications, Benefits, Pay. Possibly also About Us? Not requested as a heading; headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. About Us not in list, so we should not create a heading for it. We should incorporate About Us content maybe into Responsibilities? No, it's not relevant. Probably we should drop it as boilerplate? It's not EEO etc but it's a company description; not in allowed headings, so we should drop it. Also we need to remove duplicated lines, cookie/navigation/legal/EEO etc. The posting includes EEO statement at end; we should drop that. Also disclaimer about immunization etc maybe part of qualifications? It's under QUALIFICATIONS disclaimer; we can keep as part of qualifications paragraph. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits, and

    for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities, qualifications, benefits, pay. We need to avoid repeating job title as heading (not present). Do not put Job ID/requisition numbers as headings (none). Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Disclaimer: Certain U.S. based..." maybe keep as part of qualifications? It's a disclaimer about immunization etc; it's not boilerplate? It's a legal disclaimer; maybe we should drop? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. This disclaimer is legal; likely should be removed. However it's under QUALIFICATIONS section; but it's a legal disclaimer about immunization/occupational health mandates, drug testing. Might be considered legal boilerplate; safer to remove. But we need to preserve ALL substantive information; is this substantive? It's a condition of employment; maybe considered substantive. However it's a legal disclaimer; instruction says remove legal boilerplate. I'd remove it. Also "Range and benefit information provided in this posting are specific to the stated locations only US: Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." That's pay info; keep. Benefits list: many items; keep. Also "The role will generally accept applications for at least three calendar days from the posting date or as long as the job remains posted." That's application instruction; remove. "As part of Oracle's onboarding process..." about biometric info; that's legal; remove. "Accommodations to this requirement may be granted following an individualized assessment." also legal; remove. "About Us" section: we drop as not allowed heading. "Oracle is an Equal Employment Opportunity Employer..." EEO boilerplate; remove. "Oracle will consider for employment qualified applicants with arrest and conviction records pursuant to applicable law." also EEO; remove. Now we need to structure. We have responsibilities split into many bullet points under headings like "Key Responsibilities JOB DESCRIPTION", then subheadings: White Space and Infrastructure Design, Cross-Functional Collaboration..., Project and Program Leadership, Operations Support..., Standards Development..., Technical Innovation..., Network Expertise, Automation. Also later "Core Responsibilities" with subheadings Planning & Execution, Collaboration & Partnership, Problem Solving, Continuous Learning, Continuous Improvement, Performance and Development. We need to combine all responsibilities into a single

    • list? The instruction: Use
      • for any list of duties/requirements/benefits. So we can make one big list combining all bullet points. However we might want to keep subheadings? Not allowed; only headings from list. So we cannot add extra headings like "White Space and Infrastructure Design". We could embed them as part of list items prose. But we must preserve ALL substantive information; we can include the subheading text as part of the list item. Eg: "
      • White Space and Infrastructure Design: Leads the planning, design, and optimization ..." That preserves. Similarly for other sections. We need to avoid duplication: there may be duplicate lines; we should deduplicate identical sentences. Let's extract responsibilities bullet points. I'll copy the text and parse. Responsibilities section (starting after "Key Responsibilities JOB DESCRIPTION"): White Space and Infrastructure Design: - Leads the planning, design, and optimization of data center white space, including rack layout, hot/cold aisle containment, power distribution, cable pathways, and build phases. - Creates and maintains detailed white space documentation such as room layouts, rack elevations, bill of materials, and structured cabling designs. - Develops design standards and Basis of Design (BoD) documents to guide internal and partner teams in delivering consistent white space fit-outs. - Develops low voltage structured cabling system designs to support scalable, high-performance compute, storage, and network systems. - Reviews new site layouts and proposed fit-out designs and failover configurations, to ensure compliance with standards. Cross-Functional Collaboration and Stakeholder Engagement: - Collaborates with colocation providers, developers, and internal teams (e.g., facilities, construction, operations) to gather, translate, and implement requirements into executable white space designs. - Interfaces with multidisciplinary engineering functions (e.g., Mechanical, Electrical, Plumbing, Fire, Controls) to ensure robust integration and reliable system performance. - Leads project coordination meetings to align on scope, timelines, and critical design updates. - Leverages relationship with technology partners (e.g., network, compute, carrier) to locate information and resources. Project and Program Leadership: - Contributes to white space design initiatives and related engineering projects from concept through execution independently. - Leads internal and external project team members, including contractors and vendors, during design, fit-out, and commissioning phases. - Ensures project deliverables align with company expectations, standards, and schedules. - Provides expertise and guidance in contract administration, including review of change orders, cost forecasts, and engineering documentation. - Provides mentorship and training to junior engineers and new team members to build organizational capability. Operations Support and Site Validation: - Travels to new and existing data centers to conduct on-site design validation, commissioning, and engineering analysis. - Acts as a subject matter expert for mission-critical systems, validating integration with ongoing operations. - Provides engineering support during live events and incident investigations to ensure rapid resolution and operational continuity. - Ensures all documentation is effectively captured, stored and shared with operations and field engineering teams. Standards Development and Governance: - Executes and contributes to the evolution of global data center infrastructure standards, policies, and procedures. - Reviews and develops documentation for standards adherence, commissioning protocols, and system testing. - Participates in design summits, policy reviews, and commissioning activities to ensure continuous improvement. Technical Innovation and Engineering Excellence: - Researches and evaluates new designs, materials, and construction methods for mission-critical systems in data centers. - Develops and tests engineering solutions using advanced modeling, component testing, and engineering principles. - Creates and validates digitized data center models to support design integrity and capacity planning. - Evaluates the reliability and performance of components, systems, and installation methods used in production environments, providing feedback to team on maintenance changes as needed. - Leads internal engineering seminars, training programs, and knowledge-sharing initiatives. Network Expertise: - Collaborates with networking teams on network-related efforts (e.g., building fabrics). Automation: - Partners with software engineering team to design data into digital systems for automation. - Coordinates design data to work with internal systems and databases. Then later "Core Responsibilities" with subheadings: Planning & Execution: - Manages and coordinates moderately complex tasks, monitoring timelines and deliverables to ensure timely completion and adherence to requirements for a moderately-sized project or initiative. - Efficiently delegates, monitors, and prioritizes work across multiple projects, providing technical oversight and adjusting plans to address shifts in resources or timelines. Collaboration & Partnership: - Collaborates across the organization to align on expectations and achieve shared objectives. - Leverages understanding of business leaders, stakeholders, and/or customers to ensure proposed solutions meet their needs. - Supports inclusivity by actively seeking and listening to diverse perspectives, ensuring others feel heard and respected. Problem Solving: - Identifies and addresses moderately complex issues by analyzing a wide range of data and/or information to identify solutions in accordance with standard practices. - Proactively escalates unresolved or critical issues with a thorough assessment and suggests potential solutions. - Reviews, contributes to, and documents problem solving strategies. Continuous Learning: - Pursues learning opportunities to expand knowledge and skills and/or tools in new areas and stays abreast of the latest industry trends and best practices. - Proactively seeks and leverages ongoing feedback and training to improve skills. - Coaches and mentors junior team members, fostering continuous learning and knowledge sharing within and across teams. Continuous Improvement: - Develops ideas, recommends updates, and/or collaborates on the implementation of process improvements to increase the efficiency and effectiveness of processes, protocols, and workflows across teams, and evaluates the impact on key stakeholders. - Solicits feedback from others on ideas for alternative approaches and methods for continued improvement. Performance and Development: - Contributes to the talent development pipeline by participating in candidate interviews, assessing candidates, and providing hiring recommendations. We need to ensure no duplicate bullet points. Some may overlap but we keep as is. Now Qualifications section: after "QUALIFICATIONS" we have disclaimer (to remove), then salary range, benefits, etc. Actually the qualifications section includes disclaimer, salary range, benefits, etc. But we need separate sections for Pay and Benefits. So we need to extract qualifications content: maybe just the disclaimer? But we removed disclaimer. So qualifications may be empty? However there may be explicit qualifications like education, experience etc not present. The posting didn't list specific qualifications like degree, years experience. So we may not have a Qualifications section with substantive content. The instruction: include a section ONLY when the posting has real, specific content for it. So we should not create Qualifications heading if no specific qualifications beyond disclaimer (which we removed). So we omit Qualifications. But we still have Pay and Benefits sections. Pay: we have salary range and bonus/equity info. Benefits: list of benefits. We also might have "About the role" section? Not present; we could maybe use first paragraph after job title? There's no explicit "About the role". So we omit. Thus final HTML will have sections: Responsibilities, Pay, Benefits. Possibly also "Requirements"? Not present. We need to use

        for each section heading. Inside each section, we need
        • for lists. For Pay, it's not a list but prose; we can use

          . For Benefits, it's a list; use

          • . For Responsibilities, it's a list; use
            • . We need to preserve all substantive information: include all bullet points exactly as given. We must not add extra formatting like unless it's part of original? The original headings like "White Space and Infrastructure Design:" are not list items but headings; we can keep them as part of the list item text. Should we keep the colon? Yes. We need to ensure we don't duplicate any bullet points. Let's compile list.

Similar jobs

Senior Data Hall Designer

OracleNashville, TN· 4 wk ago
Information Technology$102k–$210k/yrapply on eeho.fa.us2.oraclecloud.com

Senior Data Hall Designer I

OracleUnited States· 3 mo ago
RemoteInformation Technology$115k–$235k/yrapply on eeho.fa.us2.oraclecloud.com