Senior Software Engineer
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like cookie/navigation/legal/EEO etc. Must preserve all substantive info. We need to parse the posting. Job Summary: description about client, role, responsibilities, etc. We'll need to create sections. We have: - Job Summary (maybe "About the role"): includes description of client, role, responsibilities, etc. Could be "About the role". We'll include that. - Core Responsibilities: list of duties. - Required Skills/Experience (Must-Haves): qualifications. - Preferred Skills/Experience (Nice-to-Haves): maybe "Preferred Qualifications" or "Skills". Could be "Preferred Skills". - Key Competencies & Behaviors: maybe "Key Competencies". Could be "Skills" or "Qualities". We'll treat as "Key Competencies". - Work Environment: Location, Work Model. - Compensation & Benefits: Pay Range, Benefits (Medical, Dental, Vision, Employee Stock Ownership Plan, 401K). Also note "We comply with local wage minimums." - About KellyMitchell: maybe not needed? It's about the staffing firm; could be considered boilerplate? It's not required but maybe we can include as "About the Company"? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "About KellyMitchell" is not boilerplate but is about the staffing agency. Might be considered part of posting; but we can keep as "About the Company". However they said "Prefer a few substantive sections over many thin ones." Might combine. We also have "Marketing Disclosure" which is boilerplate (legal) - remove. Also "Contract Details": Contract type: Contract, Length: 4 months. This is metadata; we can fold into a short
maybe under "Contract Details" but they said do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can include a paragraph about contract type and length. We must not repeat job title as heading. So no heading for "Senior Software Engineer". Good. We must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is stated: Pay Range: $39.00-$56.00. Benefits: Medical, Dental, Vision, Employee Stock Ownership Plan, 401K. Schedule? Not mentioned. So we should not create Schedule section. We need to use
for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail.
Thus we need to include all bullet points from responsibilities, required skills, preferred skills, key competencies, benefits, etc.
Let's extract.
Job Summary paragraph: "Our client, a leading airline company, is seeking a Senior Software Engineer to join a high-performing technology team focused on building reliable, scalable, and secure digital products that support the airline's business. This role will design, develop, test, deploy, and maintain large-scale software solutions using Java, Spring Boot, Microservices, Kafka, cloud platforms, and MongoDB. The ideal candidate will bring strong software engineering fundamentals, a focus on reliability and performance, and the ability to mentor other engineers while helping the team adopt modern engineering practices. This position is W-2 only. We do not work with third-party firms or C2C arrangements for this role."
We can put that as
under About the role.
Contract Details: "Contract type: ContractLength: 4 months". Actually there is no space: "Contract type: ContractLength: 4 months". Probably it's "Contract type: Contract" then newline "Length: 4 months". We'll combine: "Contract type: Contract, Length: 4 months". We'll put as a short
.
Core Responsibilities list: each bullet starts with a verb. We'll list as
- .
Required Skills/Experience (Must-Haves): list.
Preferred Skills/Experience (Nice-to-Haves): list.
Key Competencies & Behaviors: list.
Work Environment: Location: Fort Worth, TX; Work Model: Hybrid.
Compensation & Benefits: Pay Range: The approximate pay range for this position is between $39.00 and $56.00. Please note that the pay range provided is a good faith estimate. Final compensation may vary based on factors including but not limited to background, knowledge, skills, and location. We comply with local wage minimums. Medical, Dental, & Vision Insurance Plans Employee Stock Ownership Plan 401K offered
We need to format benefits as list.
Also note "About KellyMitchell" paragraph: we could include as "About the Company" maybe. It's substantive but not required. Might be okay to include. However they said remove boilerplate; this is not boilerplate but it's about the staffing firm. I'd include as a section "About KellyMitchell". But they said prefer few substantive sections over many thin ones. Could combine with About the role? Might be redundant. I'd include as a separate section "About the Company". But we need to decide.
Given the instruction: "Prefer a few substantive sections over many thin ones." So we should aim for maybe 5-6 sections: About the role, Responsibilities, Requirements (must-haves), Preferred qualifications, Benefits & Pay, Work Environment. Could also include Key Competencies as part of Requirements or Skills. But we could merge Key Competencies into Skills section.
Better: Have sections:
- About the role (summary)
- Responsibilities
- Required Qualifications
- Preferred Qualifications
- Key Competencies (maybe as part of Required? but we can keep)
- Compensation & Benefits
- Work Environment
That's 7 sections. Might be okay.
But we need to avoid thin sections: each should have substantive content.
Let's craft.
We'll output only HTML fragment, no or . Use
for each heading.
We'll not include any extra markup like unless needed.
We'll ensure lists are - .
Now craft content.
About the role: combine the job summary paragraph plus maybe contract details? Could separate.
I'll put About the role paragraph as the summary (excluding contract details). Then a separate short paragraph for Contract type and length maybe under "Contract Details" but we could fold into About the role as a sentence. But they said fold minor metadata into a short
or drop it. So we can add a
after the summary: "Contract type: Contract, Length: 4 months."
Now Responsibilities: list each bullet.
Required Qualifications: list each bullet from Required Skills/Experience.
Preferred Qualifications: list each bullet from Preferred Skills/Experience.
Key Competencies: list each bullet from Key Competencies & Behaviors.
Compensation & Benefits: we need to include Pay range paragraph and benefits list.
Work Environment: paragraph with Location and Work Model.
We should not include About KellyMitchell unless we decide. I'd omit to keep sections fewer. The posting includes that but it's about the staffing firm; maybe it's considered boilerplate? Not exactly, but it's promotional. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. However they also said "Prefer a few substantive sections over many thin ones." Including About KellyMitchell adds another section. Might be okay but could be considered thin? It's a paragraph about the company. Could be included as "About the Company". I'd include it to preserve all substantive information. The instruction says preserve ALL substantive information. So we must include that paragraph. So we need a section for it.
Thus we add "About KellyMitchell" section.
Now we have many sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Key Competencies, Compensation & Benefits, Work Environment, About KellyMitchell. That's 8 sections. Might be okay.
But we could combine About KellyMitchell with About the role? Not really.
Let's keep.
Now ensure we don't include any boilerplate like "Marketing Disclosure". Remove.
Now craft HTML.
We'll need to escape any special characters? Not needed.
Let's write.
About the role
Our client, a leading airline company, is seeking a Senior Software Engineer to join a high-performing technology team focused on building reliable, scalable, and secure digital products that support the airline's business. This role will design, develop, test, deploy, and maintain large-scale software solutions using Java, Spring Boot, Microservices, Kafka, cloud platforms, and MongoDB. The ideal candidate will bring strong software engineering fundamentals, a focus on reliability and performance, and the ability to mentor other engineers while helping the team adopt modern engineering practices. This position is W-2 only. We do not work with third-party firms or C2C arrangements for this role.
Contract type: Contract, Length: 4 months
Responsibilities
- Design, develop, test, document, and implement large-scale software solutions in production environments
- Develop and maintain Java/Spring Boot microservices and event-driven applications using Kafka
- Design and implement solutions using MongoDB and other persistent storage technologies
- Build and integrate applications with REST and other APIs
- Deploy and support applications across AWS and/or Azure cloud environments
- Conduct root cause analysis and develop solutions to improve system reliability, resiliency, security, and performance
- Design self-contained services and lead the implementation of significant capabilities within existing systems
- Break down complex technical designs into maintainable solutions that can be implemented by engineers across different experience levels
- Develop test strategies, automated tests, and system instrumentation to monitor application availability, latency, and overall production health
- Identify potential security vulnerabilities and attack surfaces and implement appropriate mitigation strategies
- Proactively address vulnerabilities and follow security and compliance best practices throughout the development lifecycle
- Promote small, incremental releases that deliver business value quickly while reducing deployment risk
- Identify opportunities to improve existing systems, processes, architecture, and engineering practices
- Promote code and solution reusability across the organization
- Participate in Agile/Scrum ceremonies, design discussions, code reviews, and technical planning
- Mentor and coach other engineers and help develop technical skills across the team
- Collaborate with cross-functional teams to communicate technical concepts through documentation, diagrams, code, and presentations
Required Qualifications
- Bachelor's degree in Computer Science, Computer Engineering, Information Systems, Engineering, or a related technical field, or equivalent experience/training
- 7+ years of professional software engineering experience designing, developing, and implementing large-scale production solutions
- Strong hands-on experience with Java
- Strong experience with Spring Boot and Microservices architecture
- Hands-on experience with Apache Kafka and event-driven architectures
- Experience with MongoDB or other persistent storage technologies
- Experience developing and supporting applications in AWS and/or Azure cloud environments
- Airline industry experience
Preferred Qualifications
- Master's degree in Computer Science, Computer Engineering, Information Systems, Engineering, or a related technical field
- Front-end development experience with Angular or React
- Experience with Kubernetes and Docker
- Experience with GitHub and Azure DevOps
- Experience with Git
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. Thus we need to include all bullet points from responsibilities, required skills, preferred skills, key competencies, benefits, etc. Let's extract. Job Summary paragraph: "Our client, a leading airline company, is seeking a Senior Software Engineer to join a high-performing technology team focused on building reliable, scalable, and secure digital products that support the airline's business. This role will design, develop, test, deploy, and maintain large-scale software solutions using Java, Spring Boot, Microservices, Kafka, cloud platforms, and MongoDB. The ideal candidate will bring strong software engineering fundamentals, a focus on reliability and performance, and the ability to mentor other engineers while helping the team adopt modern engineering practices. This position is W-2 only. We do not work with third-party firms or C2C arrangements for this role." We can put that as
under About the role. Contract Details: "Contract type: ContractLength: 4 months". Actually there is no space: "Contract type: ContractLength: 4 months". Probably it's "Contract type: Contract" then newline "Length: 4 months". We'll combine: "Contract type: Contract, Length: 4 months". We'll put as a short
. Core Responsibilities list: each bullet starts with a verb. We'll list as
- .
Required Skills/Experience (Must-Haves): list.
Preferred Skills/Experience (Nice-to-Haves): list.
Key Competencies & Behaviors: list.
Work Environment: Location: Fort Worth, TX; Work Model: Hybrid.
Compensation & Benefits: Pay Range: The approximate pay range for this position is between $39.00 and $56.00. Please note that the pay range provided is a good faith estimate. Final compensation may vary based on factors including but not limited to background, knowledge, skills, and location. We comply with local wage minimums. Medical, Dental, & Vision Insurance Plans Employee Stock Ownership Plan 401K offered
We need to format benefits as list.
Also note "About KellyMitchell" paragraph: we could include as "About the Company" maybe. It's substantive but not required. Might be okay to include. However they said remove boilerplate; this is not boilerplate but it's about the staffing firm. I'd include as a section "About KellyMitchell". But they said prefer few substantive sections over many thin ones. Could combine with About the role? Might be redundant. I'd include as a separate section "About the Company". But we need to decide.
Given the instruction: "Prefer a few substantive sections over many thin ones." So we should aim for maybe 5-6 sections: About the role, Responsibilities, Requirements (must-haves), Preferred qualifications, Benefits & Pay, Work Environment. Could also include Key Competencies as part of Requirements or Skills. But we could merge Key Competencies into Skills section.
Better: Have sections:
- About the role (summary)
- Responsibilities
- Required Qualifications
- Preferred Qualifications
- Key Competencies (maybe as part of Required? but we can keep)
- Compensation & Benefits
- Work Environment
That's 7 sections. Might be okay.
But we need to avoid thin sections: each should have substantive content.
Let's craft.
We'll output only HTML fragment, no or . Use
for each heading. We'll not include any extra markup like unless needed. We'll ensure lists are
- .
Now craft content.
About the role: combine the job summary paragraph plus maybe contract details? Could separate.
I'll put About the role paragraph as the summary (excluding contract details). Then a separate short paragraph for Contract type and length maybe under "Contract Details" but we could fold into About the role as a sentence. But they said fold minor metadata into a short
or drop it. So we can add a
after the summary: "Contract type: Contract, Length: 4 months." Now Responsibilities: list each bullet. Required Qualifications: list each bullet from Required Skills/Experience. Preferred Qualifications: list each bullet from Preferred Skills/Experience. Key Competencies: list each bullet from Key Competencies & Behaviors. Compensation & Benefits: we need to include Pay range paragraph and benefits list. Work Environment: paragraph with Location and Work Model. We should not include About KellyMitchell unless we decide. I'd omit to keep sections fewer. The posting includes that but it's about the staffing firm; maybe it's considered boilerplate? Not exactly, but it's promotional. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. However they also said "Prefer a few substantive sections over many thin ones." Including About KellyMitchell adds another section. Might be okay but could be considered thin? It's a paragraph about the company. Could be included as "About the Company". I'd include it to preserve all substantive information. The instruction says preserve ALL substantive information. So we must include that paragraph. So we need a section for it. Thus we add "About KellyMitchell" section. Now we have many sections: About the role, Responsibilities, Required Qualifications, Preferred Qualifications, Key Competencies, Compensation & Benefits, Work Environment, About KellyMitchell. That's 8 sections. Might be okay. But we could combine About KellyMitchell with About the role? Not really. Let's keep. Now ensure we don't include any boilerplate like "Marketing Disclosure". Remove. Now craft HTML. We'll need to escape any special characters? Not needed. Let's write.
About the role
Our client, a leading airline company, is seeking a Senior Software Engineer to join a high-performing technology team focused on building reliable, scalable, and secure digital products that support the airline's business. This role will design, develop, test, deploy, and maintain large-scale software solutions using Java, Spring Boot, Microservices, Kafka, cloud platforms, and MongoDB. The ideal candidate will bring strong software engineering fundamentals, a focus on reliability and performance, and the ability to mentor other engineers while helping the team adopt modern engineering practices. This position is W-2 only. We do not work with third-party firms or C2C arrangements for this role.
Contract type: Contract, Length: 4 months
Responsibilities
- Design, develop, test, document, and implement large-scale software solutions in production environments
- Develop and maintain Java/Spring Boot microservices and event-driven applications using Kafka
- Design and implement solutions using MongoDB and other persistent storage technologies
- Build and integrate applications with REST and other APIs
- Deploy and support applications across AWS and/or Azure cloud environments
- Conduct root cause analysis and develop solutions to improve system reliability, resiliency, security, and performance
- Design self-contained services and lead the implementation of significant capabilities within existing systems
- Break down complex technical designs into maintainable solutions that can be implemented by engineers across different experience levels
- Develop test strategies, automated tests, and system instrumentation to monitor application availability, latency, and overall production health
- Identify potential security vulnerabilities and attack surfaces and implement appropriate mitigation strategies
- Proactively address vulnerabilities and follow security and compliance best practices throughout the development lifecycle
- Promote small, incremental releases that deliver business value quickly while reducing deployment risk
- Identify opportunities to improve existing systems, processes, architecture, and engineering practices
- Promote code and solution reusability across the organization
- Participate in Agile/Scrum ceremonies, design discussions, code reviews, and technical planning
- Mentor and coach other engineers and help develop technical skills across the team
- Collaborate with cross-functional teams to communicate technical concepts through documentation, diagrams, code, and presentations
Required Qualifications
- Bachelor's degree in Computer Science, Computer Engineering, Information Systems, Engineering, or a related technical field, or equivalent experience/training
- 7+ years of professional software engineering experience designing, developing, and implementing large-scale production solutions
- Strong hands-on experience with Java
- Strong experience with Spring Boot and Microservices architecture
- Hands-on experience with Apache Kafka and event-driven architectures
- Experience with MongoDB or other persistent storage technologies
- Experience developing and supporting applications in AWS and/or Azure cloud environments
- Airline industry experience
Preferred Qualifications
- Master's degree in Computer Science, Computer Engineering, Information Systems, Engineering, or a related technical field
- Front-end development experience with Angular or React
- Experience with Kubernetes and Docker
- Experience with GitHub and Azure DevOps
- Experience with Git
- .
Now craft content.
About the role: combine the job summary paragraph plus maybe contract details? Could separate.
I'll put About the role paragraph as the summary (excluding contract details). Then a separate short paragraph for Contract type and length maybe under "Contract Details" but we could fold into About the role as a sentence. But they said fold minor metadata into a short