Enterprise - Software Engineer - Java, AI, REST
Erias Ventures · San Antonio, TX · 1 mo ago
Information Technology$150k/yrFull-time
We need to output HTML fragment with sections: About the role? The posting includes description, responsibilities, qualifications, skills, benefits, pay, schedule maybe. Let's parse.
We must not repeat job title as heading. Use for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We include only sections with real specific content.
We need to preserve all substantive info, no boilerplate.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We must not include Pay/Schedule/Benefits unless posting actually states them. It does state Benefits and Pay (salary range). Schedule? It mentions partial telework, hybrid environment, average 2 days per week at San Antonio office, flexibility to adapt schedule changes. That's schedule info. So we can include Schedule section.
We need to include About the role? The description includes role description. Could be "About the role" or maybe "Description". We'll use "About the role". Provide paragraph(s) summarizing role.
Responsibilities: list of duties: designing, developing, implementing complex software capabilities; work closely with other engineers; stay up-to-date; dynamic collaborative team; self-motivated; etc. Also additional duties as assigned.
Requirements/Qualifications: The posting has Experience, Required Skills, Desired Skills, Clearance, etc. We need to separate Requirements vs Qualifications? Usually Requirements = mandatory, Qualifications = preferred? But we can put mandatory in Requirements, desired in Qualifications or Skills. However we have separate Skills section. The instruction: Use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to allocate content accordingly.
We need to decide what goes where.
- About the role: overview paragraph.
- Responsibilities: bullet list of duties.
- Requirements: mandatory items: Experience (9 years etc), Clearance (must obtain and maintain US Govt Security Clearance, US Citizenship required), Required Skills list (strong working knowledge Java, Next-Gen Coding Agents, etc), maybe also "Must be able to work in a hybrid environment..."? That's schedule but could be requirement. We'll put schedule separate.
- Qualifications: maybe education alternatives? Actually experience includes education alternatives; could be considered qualifications. But we already used experience in Requirements. Could put education alternatives in Qualifications. Also Desired Skills could go under Qualifications or Skills. Since we have Skills heading, we can put all skills (required and desired) under Skills. Then Requirements could be experience and clearance. Qualifications could be education alternatives? But we need to avoid duplication.
Let's think: The posting lists:
Experience: Nine (9) years experience in Software Engineering, Modern Java Frameworks and Libraries (e.g. Spring, Guava) and a Bachelors in related field; seven (7) years relevant experience with Masters in related field; or High School Diploma or equivalent and thirteen (13) years relevant experience.
That's a mix of experience and education. Could be considered Requirements.
Required Skills: list of many items.
Desired Skills: list.
Clearance: Must obtain and maintain a U.S. Government Security Clearance, but not required on day one; U.S. Citizenship required.
Additional: partial telework, hybrid environment 2 days/week at San Antonio office.
Thus:
- About the role: paragraph from first paragraphs.
- Responsibilities: bullet list from "Will work closely..." etc.
- Requirements: Experience (years + education alternatives) + Clearance + Citizenship.
- Qualifications: maybe "Must be able to work in a hybrid environment..."? That's more schedule. Could be under Schedule.
- Skills: combine Required Skills and Desired Skills (maybe separate subheadings? but we only have Skills heading; we can list all skills as bullet list, maybe mark required vs desired? But we must preserve all info; we can list them all.
- Benefits: list benefits.
- Pay: salary range.
- Schedule: partial telework, hybrid environment 2 days/week at San Antonio office, flexibility.
We must not include boilerplate like EEO, referrals, etc.
Now produce HTML.
We need to use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We include only sections with real specific content.
We need to preserve all substantive info, no boilerplate.
We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions.
We must not include Pay/Schedule/Benefits unless posting actually states them. It does state Benefits and Pay (salary range). Schedule? It mentions partial telework, hybrid environment, average 2 days per week at San Antonio office, flexibility to adapt schedule changes. That's schedule info. So we can include Schedule section.
We need to include About the role? The description includes role description. Could be "About the role" or maybe "Description". We'll use "About the role". Provide paragraph(s) summarizing role.
Responsibilities: list of duties: designing, developing, implementing complex software capabilities; work closely with other engineers; stay up-to-date; dynamic collaborative team; self-motivated; etc. Also additional duties as assigned.
Requirements/Qualifications: The posting has Experience, Required Skills, Desired Skills, Clearance, etc. We need to separate Requirements vs Qualifications? Usually Requirements = mandatory, Qualifications = preferred? But we can put mandatory in Requirements, desired in Qualifications or Skills. However we have separate Skills section. The instruction: Use headings for About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to allocate content accordingly.
We need to decide what goes where.
- About the role: overview paragraph.
- Responsibilities: bullet list of duties.
- Requirements: mandatory items: Experience (9 years etc), Clearance (must obtain and maintain US Govt Security Clearance, US Citizenship required), Required Skills list (strong working knowledge Java, Next-Gen Coding Agents, etc), maybe also "Must be able to work in a hybrid environment..."? That's schedule but could be requirement. We'll put schedule separate.
- Qualifications: maybe education alternatives? Actually experience includes education alternatives; could be considered qualifications. But we already used experience in Requirements. Could put education alternatives in Qualifications. Also Desired Skills could go under Qualifications or Skills. Since we have Skills heading, we can put all skills (required and desired) under Skills. Then Requirements could be experience and clearance. Qualifications could be education alternatives? But we need to avoid duplication.
Let's think: The posting lists:
Experience: Nine (9) years experience in Software Engineering, Modern Java Frameworks and Libraries (e.g. Spring, Guava) and a Bachelors in related field; seven (7) years relevant experience with Masters in related field; or High School Diploma or equivalent and thirteen (13) years relevant experience.
That's a mix of experience and education. Could be considered Requirements.
Required Skills: list of many items.
Desired Skills: list.
Clearance: Must obtain and maintain a U.S. Government Security Clearance, but not required on day one; U.S. Citizenship required.
Additional: partial telework, hybrid environment 2 days/week at San Antonio office.
Thus:
- About the role: paragraph from first paragraphs.
- Responsibilities: bullet list from "Will work closely..." etc.
- Requirements: Experience (years + education alternatives) + Clearance + Citizenship.
- Qualifications: maybe "Must be able to work in a hybrid environment..."? That's more schedule. Could be under Schedule.
- Skills: combine Required Skills and Desired Skills (maybe separate subheadings? but we only have Skills heading; we can list all skills as bullet list, maybe mark required vs desired? But we must preserve all info; we can list them all.
- Benefits: list benefits.
- Pay: salary range.
- Schedule: partial telework, hybrid environment 2 days/week at San Antonio office, flexibility.
We must not include boilerplate like EEO, referrals, etc.
Now produce HTML.
We need to use for each section heading, then content:
for prose,
- for lists.
We must not include any extra text outside HTML fragment.
Let's craft.
About the role: combine first paragraphs: "Erias Ventures was founded to serve its customers with an entrepreneurial mindset. We value creative problem-solving, open communication, and empowering our employees to make decisions and put forth new ideas. Our staff includes technical experts working across multiple disciplines, bringing diverse perspectives to every project. We are seeking engineers who wish to grow their careers and want to become part of a technically strong and growth-oriented company focused on bringing innovative solutions to the difficult mission problems facing our customers." Then description: "We are seeking a Software [Engineer?] who will be responsible for designing, developing, and implementing complex software capabilities for computer-based systems. Will work closely with other talented engineers to create software solutions that meet the needs of our clients. In this role, you will have the opportunity to work with modern tools and technologies, and you will be encouraged to stay up-to-date with the latest developments in the field. You will be part of a dynamic and collaborative team that is committed to delivering high-quality software solutions to our clients. If you are a self-motivated, creative, and detail-oriented software engineer who is passionate about developing innovative software solutions, we would love to hear from you." Also mention "Should have an inquisitive nature, responsiveness, and excellent testing skills Must also possess strong troubleshooting skills and the ability to work under pressure with multiple deadlines Keep up-to-date with emerging trends and technologies in software development Seamlessly transition between hands-on execution and team guidance, treating mentorship and team leadership as inherent components of senior-level impact Will work in a fast-paced, small business environment with our talented team Additional duties as assigned". That's responsibilities.
We'll separate.
Now produce HTML.
Let's draft:
About the role
Erias Ventures was founded to serve its customers with an entrepreneurial mindset. We value creative problem-solving, open communication, and empowering our employees to make decisions and put forth new ideas. Our staff includes technical experts working across multiple disciplines, bringing diverse perspectives to every project. We are seeking engineers who wish to grow their careers and want to become part of a technically strong and growth-oriented company focused on bringing innovative solutions to the difficult mission problems facing our customers.
We are seeking a Software Engineer who will be responsible for designing, developing, and implementing complex software capabilities for computer-based systems. You will work closely with other talented engineers to create software solutions that meet client needs, have the opportunity to work with modern tools and technologies, stay up-to-date with the latest developments, and be part of a dynamic and collaborative team committed to delivering high-quality software solutions. If you are a self‑motivated, creative, and detail‑oriented software engineer passionate about developing innovative software solutions, we would love to hear from you.
That's about. Responsibilities: bullet list. We need to capture: Should have an inquisitive nature, responsiveness, and excellent testing skills; Must also possess strong troubleshooting skills and the ability to work under pressure with multiple deadlines; Keep up-to-date with emerging trends and technologies in software development; Seamlessly transition between hands-on execution and team guidance, treating mentorship and team leadership as inherent components of senior-level impact; Will work in a fast-paced, small business environment with our talented team; Additional duties as assigned. Also earlier: designing, developing, implementing complex software capabilities; work closely with other engineers; stay up-to-date; etc. But those are already in about; we can still list responsibilities. Let's list:- Design, develop, and implement complex software capabilities for computer‑based systems
- Work closely with other engineers to create software solutions that meet client needs
- Stay up‑to‑date with modern tools, technologies, and emerging trends
- Demonstrate an inquisitive nature, responsiveness, and excellent testing skills
- Possess strong troubleshooting skills and the ability to work under pressure with multiple deadlines
- Seamlessly transition between hands‑on execution and team guidance, providing mentorship and team leadership
- Operate in a fast‑paced, small‑business environment alongside a talented team
- Perform additional duties as assigned
Requirements
- Nine (9) years of experience in Software Engineering with Modern Java Frameworks and Libraries (e.g., Spring, Guava) and a Bachelor’s degree in a related field; OR
- Seven (7) years of relevant experience with a Master’s degree in a related field; OR
- High School Diploma or equivalent and thirteen (13) years of relevant experience
- Ability to obtain and maintain a U.S. Government Security Clearance (not required on day one)
- U.S. Citizenship required
Qualifications
- Active Secret or Top Secret security clearance (strong plus)
- Proven ability to serve as a tech lead, mentor, or manager for engineering teams
- Experience with cloud‑based technologies (AWS, Azure)
- Experience with distributed databases, NoSQL, full‑text search engines (e.g., Elasticsearch, MongoDB, Solr)
- Scripting experience
- Familiarity with Data Lakes or Warehouses
- Understanding of AGILE methodologies and standard tool suites (JIRA, Confluence, GitHub Enterprise, etc.)