Principal Core Infrastructure Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections that have real specific content. The posting includes a job description with many details. We need to extract sections: About the role (maybe from first paragraph?), Responsibilities (the "Key Responsibilities" and "Core Responsibilities" sections), Qualifications (the "Qualifications" section includes disclaimer and maybe requirements?), Benefits (the benefits details), Pay (the hiring range), Schedule (maybe not present). There's no explicit schedule info. So we should not create Schedule section.
We need to preserve all substantive information, not invent or summarize away detail. Use - for any list of duties/requirements/benefits, and
for prose.
We must not repeat job title as heading (not given). Do not put Job ID etc.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should strip the EEO statement, the "About Us" maybe? The "About Us" might be considered boilerplate? It's not exactly EEO but it's generic marketing. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" might be considered not boilerplate but could be kept? It's not specifically listed to remove, but it's generic marketing. However we need to preserve ALL substantive information; the "About Us" is substantive? It's marketing fluff but maybe considered not essential. The instruction says remove EEO/equal-opportunity boilerplate. Not about us. But we could keep it as part of "About the role"? Might be better to include a short paragraph about the role from the first paragraph: "Leads development and begins architecting components of scalable, elastic distributed systems..." That's the job description. Then we have responsibilities etc.
We need to decide sections: About the role (maybe a brief summary), Responsibilities (detailed), Qualifications (maybe includes disclaimer and maybe requirements?), Benefits, Pay.
We must not create sections with filler like "commensurate with experience". The posting includes Pay: "Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." That's specific, so we can include Pay section.
Benefits: they list many benefits, specific. So Benefits section.
Qualifications: The posting includes a "Qualifications Disclaimer" and then some text about US hiring range etc. Actually the qualifications section includes disclaimer and then the range and benefit info. But we already extracted Pay and Benefits. The qualifications may also include any specific requirements? There's no explicit list of qualifications like degree, years experience. The posting only includes disclaimer and then range/benefit. So maybe we shouldn't create a Qualifications section if it's just disclaimer and range/benefit (which we already placed elsewhere). However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine Qualifications and Pay/Benefits? But they said use headings for those categories if content exists. Since we have Pay and Benefits specific, we should make those sections. For Qualifications, there is minimal content (just disclaimer). Might be considered not substantive enough to warrant a section. Could we include it as a
under Responsibilities? Probably not. Better to omit Qualifications section if no specific qualifications listed.
Skills: Not explicitly listed. Could infer from responsibilities but not explicit. So omit.
Schedule: Not present.
Thus sections: About the role (maybe from first paragraph), Responsibilities (combining Key Responsibilities and Core Responsibilities), Benefits, Pay.
We need to format using
for each section heading. Use - for lists. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, benefits, pay.
We must not duplicate lines. Ensure we don't repeat same bullet.
Let's extract responsibilities bullets:
From "Key Responsibilities" and "Core Responsibilities". Let's parse.
Key Responsibilities bullet list (with sub-bullets):
System Design & Architecture - System Scalability:
- Lead the development and implementation, and begin to architect, components of scalable distributed systems that support horizontal and vertical scaling to meet system demands, including leveraging distributed state management tools.
- Optimize code and/or systems for large-scale data processing and high-throughput requirements to support hyper-scale systems.
- Define scalability requirements for owned components and ensure design and implementation requirements are met.
- Design systems to scale with elasticity (e.g., effectively scaling both up and down).
- Leverage data plane platforms to effectively handle large-scale data retrieval, storage, and processing.
- Design performance and load testing.
System Design & Architecture - System Reliability Design:
- Build and design fault-tolerant components and systems capable of withstanding in-service updates by implementing redundancy, replication, and automatic failover mechanisms.
- Design systems to effectively handle service disruptions (e.g., network partitions) by prioritizing consistency, availability, or partition tolerance.
- Implement and optimize approaches to handle network unreliability, including load-shedding, throttling, and rate-limiting.
- Design components and systems that are durable and adhere to service level objectives (SLOs), setting expectations for availability and durability of other computing services within the department.
System Design & Architecture - System Reliability Performance:
- Define key performance indicators (KPIs) and telemetry to identify gaps or issues in running systems.
- Build and customize moderately complex dashboards, telemetry systems, and alerting mechanisms to proactively monitor components and system health.
System Design & Architecture - Correctness / Availability:
- Design and implement functional and correctness requirements for feature sets and/or systems in new or existing systems.
- Design complex test scenarios (e.g., fault-injection, brown-out) to evaluate system correctness.
- Implement data replication and synchronization techniques to maintain data integrity and availability.
Operational Troubleshooting & Incident Management:
- Take a proactive role in diagnosing, debugging, and resolving issues in active components and systems to support ongoing operation, and mentor others in these processes.
- Implement strategies to prevent interruptions, ensuring no maintenance windows are required for customers and users when resolving issues.
- Maintain expertise in owned components and systems to ensure effective troubleshooting and performance.
- Meet operational readiness expectations through design and implementation.
- Serve in operational support rotations, providing guidance in incident response and root cause investigations.
Compliance & Security:
- Implement robust security measures to protect data and applications in multi-tenant environments, including encryption techniques and access controls.
- Execute remediation plans to address identified security gaps.
- Ensure cloud infrastructure is in compliance with industry standards and regulations and that documentation is up to date.
Automation & Change Management:
- Develop and maintain automation scripts and tools (e.g., Infrastructure as Code (IaC)) to manage cloud infrastructure.
- Create and adhere to change management plans for patching, updating, and rolling back applications, and begin designing systems and components to allow for automation of these processes.
Core Responsibilities:
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 include all these as list items under Responsibilities. Could group them under subheadings? The instruction only says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid inner headings, but we should likely just make a single Responsibilities section with a containing all bullets. However that would be a huge list; still okay.
We must not lose any detail. So we need to include each bullet as - . Ensure we preserve the exact wording.
Now Benefits: list from posting:
- Medical, dental, and vision insurance, including expert medical opinion
- Short term disability and long term disability
- Life insurance and AD&D
- Supplemental life insurance (Employee/Spouse/Child)
- Health care and dependent care Flexible Spending Accounts
- Pre-tax commuter and parking benefits
- 401(k) Savings and Investment Plan with company match
- Paid time off: Flexible Vacation is provided to all eligible employees assigned to a salaried (non-overtime eligible) position. Accrued Vacation is provided to all other employees eligible for vacation benefits. For employees working at least 35 hours per week, the vacation accrual rate is 13 days annually for the first three years of employment and 18 days annually for subsequent years of employment. Vacation accrual is prorated for employees working between 20 and 34 hours per week. Employees working fewer than 20 hours per week are not eligible for vacation.
- 11 paid holidays
- Paid sick leave: 72 hours of paid sick leave upon date of hire. Refreshes each calendar year. Unused balance will carry over each year up to a maximum cap of 112 hours.
- Paid parental leave
- Adoption assistance
- Employee Stock Purchase Plan
- Financial planning and group legal
- Voluntary benefits including auto, homeowner and pet insurance
We need to keep each as list item. Some are sentences; we can keep as is.
Pay: "Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." Also note about Oracle maintains broad salary ranges etc. That's also part of the posting but maybe considered boilerplate? It's explanatory about range. Might be considered substantive? It's describing the range. Could include as paragraph.
We also have a disclaimer about qualifications: "Qualifications Disclaimer: Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements." That's a qualification disclaimer; maybe we should include it under Qualifications? But we decided not to create Qualifications section due to lack of specifics. However this disclaimer is substantive; maybe we should include it as a
under Responsibilities? Not appropriate. Could create a Qualifications section with just that disclaimer. The instruction: "Prefer a few substantive sections over many thin ones." This is a thin section but it's the only qualification info. Might be better to include Qualifications section with that disclaimer. Also there is the line about "Range
for prose. We must not repeat job title as heading (not given). Do not put Job ID etc. We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. So we should strip the EEO statement, the "About Us" maybe? The "About Us" might be considered boilerplate? It's not exactly EEO but it's generic marketing. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Us" might be considered not boilerplate but could be kept? It's not specifically listed to remove, but it's generic marketing. However we need to preserve ALL substantive information; the "About Us" is substantive? It's marketing fluff but maybe considered not essential. The instruction says remove EEO/equal-opportunity boilerplate. Not about us. But we could keep it as part of "About the role"? Might be better to include a short paragraph about the role from the first paragraph: "Leads development and begins architecting components of scalable, elastic distributed systems..." That's the job description. Then we have responsibilities etc. We need to decide sections: About the role (maybe a brief summary), Responsibilities (detailed), Qualifications (maybe includes disclaimer and maybe requirements?), Benefits, Pay. We must not create sections with filler like "commensurate with experience". The posting includes Pay: "Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." That's specific, so we can include Pay section. Benefits: they list many benefits, specific. So Benefits section. Qualifications: The posting includes a "Qualifications Disclaimer" and then some text about US hiring range etc. Actually the qualifications section includes disclaimer and then the range and benefit info. But we already extracted Pay and Benefits. The qualifications may also include any specific requirements? There's no explicit list of qualifications like degree, years experience. The posting only includes disclaimer and then range/benefit. So maybe we shouldn't create a Qualifications section if it's just disclaimer and range/benefit (which we already placed elsewhere). However the instruction: "Prefer a few substantive sections over many thin ones." So we could combine Qualifications and Pay/Benefits? But they said use headings for those categories if content exists. Since we have Pay and Benefits specific, we should make those sections. For Qualifications, there is minimal content (just disclaimer). Might be considered not substantive enough to warrant a section. Could we include it as a
under Responsibilities? Probably not. Better to omit Qualifications section if no specific qualifications listed. Skills: Not explicitly listed. Could infer from responsibilities but not explicit. So omit. Schedule: Not present. Thus sections: About the role (maybe from first paragraph), Responsibilities (combining Key Responsibilities and Core Responsibilities), Benefits, Pay. We need to format using
for each section heading. Use - for lists. Use
for prose.
We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, benefits, pay.
We must not duplicate lines. Ensure we don't repeat same bullet.
Let's extract responsibilities bullets:
From "Key Responsibilities" and "Core Responsibilities". Let's parse.
Key Responsibilities bullet list (with sub-bullets):
System Design & Architecture - System Scalability:
- Lead the development and implementation, and begin to architect, components of scalable distributed systems that support horizontal and vertical scaling to meet system demands, including leveraging distributed state management tools.
- Optimize code and/or systems for large-scale data processing and high-throughput requirements to support hyper-scale systems.
- Define scalability requirements for owned components and ensure design and implementation requirements are met.
- Design systems to scale with elasticity (e.g., effectively scaling both up and down).
- Leverage data plane platforms to effectively handle large-scale data retrieval, storage, and processing.
- Design performance and load testing.
System Design & Architecture - System Reliability Design:
- Build and design fault-tolerant components and systems capable of withstanding in-service updates by implementing redundancy, replication, and automatic failover mechanisms.
- Design systems to effectively handle service disruptions (e.g., network partitions) by prioritizing consistency, availability, or partition tolerance.
- Implement and optimize approaches to handle network unreliability, including load-shedding, throttling, and rate-limiting.
- Design components and systems that are durable and adhere to service level objectives (SLOs), setting expectations for availability and durability of other computing services within the department.
System Design & Architecture - System Reliability Performance:
- Define key performance indicators (KPIs) and telemetry to identify gaps or issues in running systems.
- Build and customize moderately complex dashboards, telemetry systems, and alerting mechanisms to proactively monitor components and system health.
System Design & Architecture - Correctness / Availability:
- Design and implement functional and correctness requirements for feature sets and/or systems in new or existing systems.
- Design complex test scenarios (e.g., fault-injection, brown-out) to evaluate system correctness.
- Implement data replication and synchronization techniques to maintain data integrity and availability.
Operational Troubleshooting & Incident Management:
- Take a proactive role in diagnosing, debugging, and resolving issues in active components and systems to support ongoing operation, and mentor others in these processes.
- Implement strategies to prevent interruptions, ensuring no maintenance windows are required for customers and users when resolving issues.
- Maintain expertise in owned components and systems to ensure effective troubleshooting and performance.
- Meet operational readiness expectations through design and implementation.
- Serve in operational support rotations, providing guidance in incident response and root cause investigations.
Compliance & Security:
- Implement robust security measures to protect data and applications in multi-tenant environments, including encryption techniques and access controls.
- Execute remediation plans to address identified security gaps.
- Ensure cloud infrastructure is in compliance with industry standards and regulations and that documentation is up to date.
Automation & Change Management:
- Develop and maintain automation scripts and tools (e.g., Infrastructure as Code (IaC)) to manage cloud infrastructure.
- Create and adhere to change management plans for patching, updating, and rolling back applications, and begin designing systems and components to allow for automation of these processes.
Core Responsibilities:
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 include all these as list items under Responsibilities. Could group them under subheadings? The instruction only says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid inner headings, but we should likely just make a single Responsibilities section with a containing all bullets. However that would be a huge list; still okay.
We must not lose any detail. So we need to include each bullet as - . Ensure we preserve the exact wording.
Now Benefits: list from posting:
- Medical, dental, and vision insurance, including expert medical opinion
- Short term disability and long term disability
- Life insurance and AD&D
- Supplemental life insurance (Employee/Spouse/Child)
- Health care and dependent care Flexible Spending Accounts
- Pre-tax commuter and parking benefits
- 401(k) Savings and Investment Plan with company match
- Paid time off: Flexible Vacation is provided to all eligible employees assigned to a salaried (non-overtime eligible) position. Accrued Vacation is provided to all other employees eligible for vacation benefits. For employees working at least 35 hours per week, the vacation accrual rate is 13 days annually for the first three years of employment and 18 days annually for subsequent years of employment. Vacation accrual is prorated for employees working between 20 and 34 hours per week. Employees working fewer than 20 hours per week are not eligible for vacation.
- 11 paid holidays
- Paid sick leave: 72 hours of paid sick leave upon date of hire. Refreshes each calendar year. Unused balance will carry over each year up to a maximum cap of 112 hours.
- Paid parental leave
- Adoption assistance
- Employee Stock Purchase Plan
- Financial planning and group legal
- Voluntary benefits including auto, homeowner and pet insurance
We need to keep each as list item. Some are sentences; we can keep as is.
Pay: "Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." Also note about Oracle maintains broad salary ranges etc. That's also part of the posting but maybe considered boilerplate? It's explanatory about range. Might be considered substantive? It's describing the range. Could include as paragraph.
We also have a disclaimer about qualifications: "Qualifications Disclaimer: Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements." That's a qualification disclaimer; maybe we should include it under Qualifications? But we decided not to create Qualifications section due to lack of specifics. However this disclaimer is substantive; maybe we should include it as a
under Responsibilities? Not appropriate. Could create a Qualifications section with just that disclaimer. The instruction: "Prefer a few substantive sections over many thin ones." This is a thin section but it's the only qualification info. Might be better to include Qualifications section with that disclaimer. Also there is the line about "Range
for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from responsibilities, benefits, pay. We must not duplicate lines. Ensure we don't repeat same bullet. Let's extract responsibilities bullets: From "Key Responsibilities" and "Core Responsibilities". Let's parse. Key Responsibilities bullet list (with sub-bullets): System Design & Architecture - System Scalability: - Lead the development and implementation, and begin to architect, components of scalable distributed systems that support horizontal and vertical scaling to meet system demands, including leveraging distributed state management tools. - Optimize code and/or systems for large-scale data processing and high-throughput requirements to support hyper-scale systems. - Define scalability requirements for owned components and ensure design and implementation requirements are met. - Design systems to scale with elasticity (e.g., effectively scaling both up and down). - Leverage data plane platforms to effectively handle large-scale data retrieval, storage, and processing. - Design performance and load testing. System Design & Architecture - System Reliability Design: - Build and design fault-tolerant components and systems capable of withstanding in-service updates by implementing redundancy, replication, and automatic failover mechanisms. - Design systems to effectively handle service disruptions (e.g., network partitions) by prioritizing consistency, availability, or partition tolerance. - Implement and optimize approaches to handle network unreliability, including load-shedding, throttling, and rate-limiting. - Design components and systems that are durable and adhere to service level objectives (SLOs), setting expectations for availability and durability of other computing services within the department. System Design & Architecture - System Reliability Performance: - Define key performance indicators (KPIs) and telemetry to identify gaps or issues in running systems. - Build and customize moderately complex dashboards, telemetry systems, and alerting mechanisms to proactively monitor components and system health. System Design & Architecture - Correctness / Availability: - Design and implement functional and correctness requirements for feature sets and/or systems in new or existing systems. - Design complex test scenarios (e.g., fault-injection, brown-out) to evaluate system correctness. - Implement data replication and synchronization techniques to maintain data integrity and availability. Operational Troubleshooting & Incident Management: - Take a proactive role in diagnosing, debugging, and resolving issues in active components and systems to support ongoing operation, and mentor others in these processes. - Implement strategies to prevent interruptions, ensuring no maintenance windows are required for customers and users when resolving issues. - Maintain expertise in owned components and systems to ensure effective troubleshooting and performance. - Meet operational readiness expectations through design and implementation. - Serve in operational support rotations, providing guidance in incident response and root cause investigations. Compliance & Security: - Implement robust security measures to protect data and applications in multi-tenant environments, including encryption techniques and access controls. - Execute remediation plans to address identified security gaps. - Ensure cloud infrastructure is in compliance with industry standards and regulations and that documentation is up to date. Automation & Change Management: - Develop and maintain automation scripts and tools (e.g., Infrastructure as Code (IaC)) to manage cloud infrastructure. - Create and adhere to change management plans for patching, updating, and rolling back applications, and begin designing systems and components to allow for automation of these processes. Core Responsibilities: 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 include all these as list items under Responsibilities. Could group them under subheadings? The instruction only says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid inner headings, but we should likely just make a single Responsibilities section with a containing all bullets. However that would be a huge list; still okay.
We must not lose any detail. So we need to include each bullet as - . Ensure we preserve the exact wording.
Now Benefits: list from posting:
- Medical, dental, and vision insurance, including expert medical opinion
- Short term disability and long term disability
- Life insurance and AD&D
- Supplemental life insurance (Employee/Spouse/Child)
- Health care and dependent care Flexible Spending Accounts
- Pre-tax commuter and parking benefits
- 401(k) Savings and Investment Plan with company match
- Paid time off: Flexible Vacation is provided to all eligible employees assigned to a salaried (non-overtime eligible) position. Accrued Vacation is provided to all other employees eligible for vacation benefits. For employees working at least 35 hours per week, the vacation accrual rate is 13 days annually for the first three years of employment and 18 days annually for subsequent years of employment. Vacation accrual is prorated for employees working between 20 and 34 hours per week. Employees working fewer than 20 hours per week are not eligible for vacation.
- 11 paid holidays
- Paid sick leave: 72 hours of paid sick leave upon date of hire. Refreshes each calendar year. Unused balance will carry over each year up to a maximum cap of 112 hours.
- Paid parental leave
- Adoption assistance
- Employee Stock Purchase Plan
- Financial planning and group legal
- Voluntary benefits including auto, homeowner and pet insurance
We need to keep each as list item. Some are sentences; we can keep as is.
Pay: "Hiring Range in USD from: $114,600 - $234,600 per year. May be eligible for bonus, equity, and compensation deferral." Also note about Oracle maintains broad salary ranges etc. That's also part of the posting but maybe considered boilerplate? It's explanatory about range. Might be considered substantive? It's describing the range. Could include as paragraph.
We also have a disclaimer about qualifications: "Qualifications Disclaimer: Certain U.S. based or U.S. customer or client-facing roles may be required to comply with applicable requirements, such as immunization/occupational health mandates, and/or drug testing requirements." That's a qualification disclaimer; maybe we should include it under Qualifications? But we decided not to create Qualifications section due to lack of specifics. However this disclaimer is substantive; maybe we should include it as a
under Responsibilities? Not appropriate. Could create a Qualifications section with just that disclaimer. The instruction: "Prefer a few substantive sections over many thin ones." This is a thin section but it's the only qualification info. Might be better to include Qualifications section with that disclaimer. Also there is the line about "Range
under Responsibilities? Not appropriate. Could create a Qualifications section with just that disclaimer. The instruction: "Prefer a few substantive sections over many thin ones." This is a thin section but it's the only qualification info. Might be better to include Qualifications section with that disclaimer. Also there is the line about "Range