Senior Software Engineer - Java/Microservices

We need to output HTML fragment with sections: About the role? Actually the posting includes "Who is Tenable?" and "What makes Tenable such a great place to work?" but we need to use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections when posting has real specific content. We have content about role: description of responsibilities, opportunities, etc. We have qualifications/requirements: list of needed experience. We have benefits: list of benefits. We have pay: US Pay Range $131,500—$175,500 USD. No schedule info. So we should include sections: About the role (maybe combine role description), Responsibilities (maybe from "Your Opportunity" bullet list), Requirements (maybe from "What You'll Need"), Qualifications (maybe overlapping but we can combine?), Skills (maybe from list of technologies), Benefits, Pay. We must not repeat job title as heading. Also we must not include boilerplate like EEO, etc. Also we must not include application instructions. We need to preserve all substantive information. So we need to extract details. Let's parse the posting: - Intro about Tenable: description of company, mission, culture. Could be "About the role"? Actually "About the role" is for role description. But we could put company description under "About the role"? Might be better to have "About the role" include role description and maybe company overview. However guidelines: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can decide which sections to include. We have: - Role description: "Your Role Tenable is looking for a Senior Software Engineer to join our core product engineering team. Focused on designing, developing, and maintaining cloud-based, state-of-the-art search solutions on top of our customers' ever-evolving landscape of infrastructure in a scalable way. As a Senior Software Engineer on the team, you will have the opportunity to be part of implementing and maintaining a highly scalable, highly reliable cloud-native user interface and underlying microservices which utilize modern technologies and programming languages." - Opportunity bullet list: "Building the Backbone, not just Processing Data: ..." then several bullet-like sentences: Data Management, Leadership, Innovate, Learn new things, Raise the bar, Collaborate. We can treat those as responsibilities. - Requirements/Qualifications: "What You'll Need" list: many bullet points. - Benefits: list after "Tenable also offers a variety of comprehensive and competitive benefits which include: medical, dental, vision, disability and life insurance; 401(k) retirement savings with company match; an employee stock purchase plan; an employee referral program; flexible spending accounts; an Employee Assistance Program (EAP); education assistance; parental leave; paid time off (PTO); company-paid holidays; health and wellness events; and community programs." - Pay: "US Pay Range $131,500—$175,500 USD" - No schedule. We must not include boilerplate like EEO, data consent, etc. We must not repeat job title as heading. We must not include duplicated lines. We must output only HTML fragment. Let's craft sections:

About the role

Tenable® is the Exposure Management company. Over 40,000 organizations around the globe rely on Tenable to understand and reduce cyber risk. Our global employees support 65 percent of the Fortune 500, 50 percent of the Global 2000, and large government agencies. Come be part of our journey! We work together to build and innovate best-in-class cybersecurity solutions for our customers; all while creating a culture of belonging, respect, and excellence where we can be our best selves. When you’re part of our #OneTenable team, you can expect to partner with some of the most talented and passionate people in the industry, and have the support and resources you need to do work that truly matters. We deliver results that exceed expectations and we win together!

But maybe that's too much company info; but it's substantive. Could be okay. Alternatively, we could put company description under About the role, and responsibilities under Responsibilities. Let's do:

About the role

Tenable® is the Exposure Management company. Over 40,000 organizations around the globe rely on Tenable to understand and reduce cyber risk. Our global employees support 65 percent of the Fortune 500, 50 percent of the Global 2000, and large government agencies. Come be part of our journey! We work together to build and innovate best-in-class cybersecurity solutions for our customers; all while creating a culture of belonging, respect, and excellence where we can be our best selves. When you’re part of our #OneTenable team, you can expect to partner with some of the most talented and passionate people in the industry, and have the support and resources you need to do work that truly matters. We deliver results that exceed expectations and we win together!

Responsibilities

• Designing, developing, and maintaining cloud-based, state-of-the-art search solutions on top of customers' ever-evolving infrastructure in a scalable way.
• Implementing and maintaining a highly scalable, highly reliable cloud-native user interface and underlying microservices utilizing modern technologies and programming languages.
• Building the services that enable data ingestion, storage, querying, and retrieval at scale (the reliable and efficient 'plumbing' that powers the entire data ecosystem).
• Managing the ingestion, storage, and retrieval of data within the platform, ensuring robustness and efficiency.
• Architecting, designing and implementing features to help drive the overall architecture of the platform.
• Driving ongoing innovation of the global cloud architecture and distributed systems serving the broad customer base with the latest cybersecurity technologies.
• Participating in a training budget to attend conferences or workshops.
• Continuously improving the tech stack, product features, and personal performance.
• Collaborating closely with Product Managers, other engineers, designers, and stakeholders to iterate on products and drive consensus; supporting and mentoring peers inside and outside the team.

Requirements

• 4+ years of software development experience in enterprise development and a desire to lead.
• Experience in software development, particularly within a distributed, microservice architecture.
• Experience in database performance tuning, schema design, query optimization in a distributed microservice architecture.
• B.S. degree in Computer Science or a directly related field, or equivalent work experience.
• Experience developing in Java or Kotlin, and a willingness to learn new languages as needed.
• Experience working in containerized microservice architecture in Kubernetes.
• Experience developing core libraries, infrastructure, and search engines.
• Cross-platform development is a big plus.
• Accountability for the behavior of your software in production.
• Experience coaching and leading mid-level and junior staff in the design, implementation, and execution of highly technical development projects.
• Experience working in an Agile team, and enthusiasm for working collaboratively within and across product teams.
• Ability to work independently and as part of a team, and to lead/drive projects as necessary.
• Experience with databases (SQL or NoSQL such as PostgreSQL, DynamoDB, Elasticsearch).
• Experience with event-driven systems (Kafka, SQS, RabbitMQ or similar).
• Desire to continuously learn and be exposed to new technologies.

We could also have Qualifications section but it's overlapping. The instruction says prefer a few substantive sections over many thin ones. So we might combine Requirements and Qualifications into one section, maybe "Requirements". Or we could have "Qualifications" for degree and experience, and "Skills" for tech stack. But we need to avoid thin sections. Let's think: we have many bullet points; we could split into Requirements (experience, leadership, Agile) and Skills (technologies). But we need to decide. Given the instruction: "Prefer a few substantive sections over many thin ones." So maybe we keep Requirements as one big list covering all needed qualifications and skills. That's fine. Then Benefits section:

Benefits

• Medical, dental, vision, disability and life insurance
• 401(k) retirement savings with company match
• Employee stock purchase plan
• Employee referral program
• Flexible spending accounts
• Employee Assistance Program (EAP)
• Education assistance
• Parental leave
• Paid time off (PTO)
• Company-paid holidays
• Health and wellness events
• Community programs

Pay section:

Pay

US Pay Range $131,500—$175,500 USD

We should not include Schedule. We must not include any markdown fences. Just raw HTML. Check for any duplicated lines: we have not repeated. Check for boilerplate removed: we removed EEO, data consent, visa sponsorship, etc. Check for any placeholder like "commensurate with experience": none. Check for any invented info: we only used what's present. Check for any missing substantive info: we included company description, role description, responsibilities, requirements, benefits, pay. Did we include the "Applicants must be authorized to work for any employer in the U.S. without sponsorship."? That's a requirement about work authorization. Should we include? It's substantive. It's under the "Applicants must be authorized to work for any employer in the U.S. without sponsorship. We are unable to provide sponsorship for work visas of any kind at the time of hire, or at any point during employment." This is a requirement. We should include it maybe under Requirements. Let's add a bullet: "Must be authorized to work for any employer in the U.S. without sponsorship; Tenable does not provide sponsorship for work visas." Also we included "Applicants must be authorized to work for any employer in the U.S. without sponsorship." That is a requirement. We also included "Your Opportunity" bullet list items like "Learn new things: We provide a training budget for you to attend conferences or workshops" we captured as training budget bullet. We also included "Raise the bar: We are always looking for ways to improve ourselves, our tech stack, and our product features. Bring your ideas and experiences to the table and help make a lasting impact" we captured as continuous improvement bullet. We also included "Collaborate: Work closely with Product Managers, other engineers, designers, and stakeholders to continuously iterate on our products and drive consensus. You will have the opportunity to support and mentor your peers inside and outside your team" we captured. We also included "Leadership: As a senior member of the team, you will have the opportunity to architect, design and implement features to help drive the overall architecture of our platform" we captured. We also included "Innovate: Become a member of senior engineering teams driving on-going innovation of our global cloud architecture and distributed systems that serves our broad customer base with the latest cyber security technologies" we captured. We also included "Data Management: This role will be responsible for managing the ingestion, storage, and retrieval of data within the platform. This includes ensuring the robustness and efficiency of these processes" we captured. We also included "Building the Backbone, not just Processing Data: This role centers on crafting the services that enable data ingestion, storage, querying, and retrieval at scale. It's about building the reliable and efficient 'plumbing' that powers the entire data ecosystem." we captured. We also included "As a Senior Software Engineer on the team, you will have the opportunity to be part of