Software Engineer II
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real specific content. The posting includes responsibilities (What You Will Be Doing), requirements (Skills & Experience, Nice to haves), qualifications (maybe Success Criteria?), Benefits. No Pay or Schedule mentioned, so we omit those sections.
We need to map content: "About Us" could be considered "About the role"? Actually "About the role" is not present; we have company description. Could we use "About the role" heading for company overview? The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., not limited to those. So we can use those headings if appropriate. We have content about company (About Us) and team (Our Team). Could combine into "About the role" maybe not ideal but acceptable. However we could also create a custom heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we could also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those exact headings when applicable. So we need to decide which sections map.
We have:
- About Us (company description) -> could be "About the role"? Not exactly but maybe we treat as "About the role". However "About the role" would be about the job itself, not company. But we have "Our Team" describing team. Could be part of "About the role". Might be okay.
- Responsibilities: "What You Will Be Doing In The Role" -> map to Responsibilities.
- Requirements: "Skills & Experience We're Seeking" and "Nice to haves" -> map to Requirements (maybe split into Skills and Requirements?). But we can combine.
- Qualifications: maybe "Success Criteria" (Own Getting Things Done etc.) could be Qualifications.
- Benefits: "Benefits" section.
We should not include Pay or Schedule.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the bullet points etc.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus we need to parse the content into prose paragraphs and lists.
Let's extract sections:
About Us paragraph: "TeleTracking began with a simple but powerful belief that no one should wait for the care they need. More than a slogan, it’s a promise to continually improve healthcare. TeleTracking builds groundbreaking technology incorporating deep clinical expertise. Our solutions are used in the nation’s largest healthcare systems and around the world to positively impact patients, families and communities. What’s your contribution to the TeleTracking story? When you chose to bring your passion and skills to helping achieve our purpose, you’ll be part of a team that understands that there’s a human life behind every data point. Your skills, curiosity, and compassion—will help fuel our innovation and achieve the TeleTracking promise of revolutionizing modern healthcare."
Our Team paragraph: "TeleTracking is an integrated healthcare operations platform provider that is Expanding the Capacity to Care™ by helping health systems optimize access to care, streamline care delivery, and connect transitions of care. We are passionate about saving the lives of the patients, giving time back to the caregivers and improving throughput across health systems. Our Team The Logistics Engineering teams design, build and operate the applications and services that serve the evolving needs of caregivers. As we expand our capabilities to effectively manage patient flows across and within hospital systems, we seek the best and brightest engineering talent to be part of our growth. Our team is looking for a Senior Software Engineer to drive the expansion of features to our customers through services that the team owns and operates on our event based microservice platform."
Note: The text repeats "Our Team" twice? Actually after first paragraph there is "Our Team". We'll combine.
What You Will Be Doing In The Role: list of duties:
- Understanding and solving business needs at scale with high-quality solutions
- Building and operating resilient services and infrastructure
- Developing fluency in using coding agents throughout the software development lifecycle
- Creating metrics, dashboards and alerts to measure and meet SLOs for service performance, errors and availability and reacting to resolve issues in an on-call rotation
- Build on AWS services such as Lambda, EKS, S3, EC2, RDS, DynamoDB
These are bullet points.
Skills & Experience We're Seeking: list:
- 2-5 years of expertise in Java, Go, or similar object-oriented languages
- Fluency in using coding agents
- Experience debugging in Production
- Ability to design, build and operate highly scalable, secure, and fault-tolerant services
- Experience in contributing to architectural decisions
- Motivated to dive deep to understand problems and customer pain points, and solve them using appropriate engineering principles
- Working understanding of event driven architecture and microservices
Nice to haves: list:
- Interest in underlying cloud infrastructure
- General understanding of hospital operations
- Development experience with Spring
Success Criteria: list (these are bullet points but each preceded by a label):
- Own Getting Things Done: Given an objective, you plan out how to get there and see it through
- Grow in Knowledge and Skill: There are things you need to learn to tackle tasks at hand, but expanding your learning beyond that is something you do habitually
- Communicate Clearly, Concisely and Effectively: Connecting with people is important to you and you work to become successful
- Deliver Frequently and Incrementally: Breaking down problems into smaller chunks, testing them and getting feedback is a discipline you hold yourself to
- Solve Problems Effectively and Efficiently: Weighing the options and picking the one most likely to fit best, is a strength that you build on
- Share Knowledge and Ideas: You jump in to contribute to the pool of ideas and provide guidance
Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future. This is a requirement; could be part of Requirements or Qualifications. We'll include as a paragraph under Requirements maybe.
Benefits: list:
- Employee Medical/dental/vision premiums paid 100% - family members without coverage
- Medical 100% - small cost for dependents on dental and vision, which start from day one!
- Life and AD&D
- Flexible Spending Accounts: Medical, Dependent Care, and Transportation
- 401 (k) Retirement Savings
- Tuition Reimbursement
- Military Paid Leave (up to 6 months of base salary while on military leave)
- Paid Time Off
- Paid parental leave
We need to output HTML fragment with headings
and content.
We need to decide which headings to use.
We have:
- About the role: could contain About Us + Our Team (company description and team). We'll put that as prose paragraphs.
- Responsibilities: the duties list.
- Requirements: could combine Skills & Experience We're Seeking, Nice to haves, and authorization statement.
- Qualifications: Success Criteria.
- Benefits: benefits list.
We should not include Pay or Schedule.
We must not repeat job title as heading; we aren't.
We must not put Job ID/requisition numbers as headings; none present.
We must remove boilerplate: Disclaimer, EEO, etc. Already removed.
Now produce HTML.
We need to ensure we use - for any list of duties/requirements/benefits. For prose, use
.
Thus:
About the role
TeleTracking began with a simple but powerful belief that no one should wait for the care they need. More than a slogan, it’s a promise to continually improve healthcare. TeleTracking builds groundbreaking technology incorporating deep clinical expertise. Our solutions are used in the nation’s largest healthcare systems and around the world to positively impact patients, families and communities. What’s your contribution to the TeleTracking story? When you chose to bring your passion and skills to helping achieve our purpose, you’ll be part of a team that understands that there’s a human life behind every data point. Your skills, curiosity, and compassion—will help fuel our innovation and achieve the TeleTracking promise of revolutionizing modern healthcare.
TeleTracking is an integrated healthcare operations platform provider that is Expanding the Capacity to Care™ by helping health systems optimize access to care, streamline care delivery, and connect transitions of care. We are passionate about saving the lives of the patients, giving time back to the caregivers and improving throughput across health systems. The Logistics Engineering teams design, build and operate the applications and services that serve the evolving needs of caregivers. As we expand our capabilities to effectively manage patient flows across and within hospital systems, we seek the best and brightest engineering talent to be part of our growth. Our team is looking for a Senior Software Engineer to drive the expansion of features to our customers through services that the team owns and operates on our event based microservice platform.
Responsibilities
- Understanding and solving business needs at scale with high-quality solutions
- Building and operating resilient services and infrastructure
- Developing fluency in using coding agents throughout the software development lifecycle
- Creating metrics, dashboards and alerts to measure and meet SLOs for service performance, errors and availability and reacting to resolve issues in an on-call rotation
- Build on AWS services such as Lambda, EKS, S3, EC2, RDS, DynamoDB
Requirements
- 2-5 years of expertise in Java, Go, or similar object-oriented languages
- Fluency in using coding agents
- Experience debugging in Production
- Ability to design, build and operate highly scalable, secure, and fault-tolerant services
- Experience in contributing to architectural decisions
- Motivated to dive deep to understand problems and customer pain points, and solve them using appropriate engineering principles
- Working understanding of event driven architecture and microservices
- Interest in underlying cloud infrastructure
- General understanding of hospital operations
- Development experience with Spring
- Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future.
Qualifications
- Own Getting Things Done: Given an objective, you plan out how to get there and see it through
- Grow in Knowledge and Skill: There are things you need to learn to tackle tasks at hand, but expanding your learning beyond that is something you do habitually
- Communicate Clearly, Concisely and Effectively: Connecting with people is important to you and you work to become successful
- Deliver Frequently and Incrementally: Breaking down problems into smaller chunks, testing them and getting feedback is a discipline you hold yourself to
- Solve Problems Effectively and Efficiently: Weighing the options and picking the one most likely to fit best, is a strength that you build on
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It suggests those are examples; we could also use other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those exact headings when applicable. So we need to decide which sections map.
We have:
- About Us (company description) -> could be "About the role"? Not exactly but maybe we treat as "About the role". However "About the role" would be about the job itself, not company. But we have "Our Team" describing team. Could be part of "About the role". Might be okay.
- Responsibilities: "What You Will Be Doing In The Role" -> map to Responsibilities.
- Requirements: "Skills & Experience We're Seeking" and "Nice to haves" -> map to Requirements (maybe split into Skills and Requirements?). But we can combine.
- Qualifications: maybe "Success Criteria" (Own Getting Things Done etc.) could be Qualifications.
- Benefits: "Benefits" section.
We should not include Pay or Schedule.
We need to preserve all substantive information, not invent or summarize away detail. So we need to keep the bullet points etc.
We need to use - for any list of duties/requirements/benefits, and
for prose.
Thus we need to parse the content into prose paragraphs and lists.
Let's extract sections:
About Us paragraph: "TeleTracking began with a simple but powerful belief that no one should wait for the care they need. More than a slogan, it’s a promise to continually improve healthcare. TeleTracking builds groundbreaking technology incorporating deep clinical expertise. Our solutions are used in the nation’s largest healthcare systems and around the world to positively impact patients, families and communities. What’s your contribution to the TeleTracking story? When you chose to bring your passion and skills to helping achieve our purpose, you’ll be part of a team that understands that there’s a human life behind every data point. Your skills, curiosity, and compassion—will help fuel our innovation and achieve the TeleTracking promise of revolutionizing modern healthcare."
Our Team paragraph: "TeleTracking is an integrated healthcare operations platform provider that is Expanding the Capacity to Care™ by helping health systems optimize access to care, streamline care delivery, and connect transitions of care. We are passionate about saving the lives of the patients, giving time back to the caregivers and improving throughput across health systems. Our Team The Logistics Engineering teams design, build and operate the applications and services that serve the evolving needs of caregivers. As we expand our capabilities to effectively manage patient flows across and within hospital systems, we seek the best and brightest engineering talent to be part of our growth. Our team is looking for a Senior Software Engineer to drive the expansion of features to our customers through services that the team owns and operates on our event based microservice platform."
Note: The text repeats "Our Team" twice? Actually after first paragraph there is "Our Team". We'll combine.
What You Will Be Doing In The Role: list of duties:
- Understanding and solving business needs at scale with high-quality solutions
- Building and operating resilient services and infrastructure
- Developing fluency in using coding agents throughout the software development lifecycle
- Creating metrics, dashboards and alerts to measure and meet SLOs for service performance, errors and availability and reacting to resolve issues in an on-call rotation
- Build on AWS services such as Lambda, EKS, S3, EC2, RDS, DynamoDB
These are bullet points.
Skills & Experience We're Seeking: list:
- 2-5 years of expertise in Java, Go, or similar object-oriented languages
- Fluency in using coding agents
- Experience debugging in Production
- Ability to design, build and operate highly scalable, secure, and fault-tolerant services
- Experience in contributing to architectural decisions
- Motivated to dive deep to understand problems and customer pain points, and solve them using appropriate engineering principles
- Working understanding of event driven architecture and microservices
Nice to haves: list:
- Interest in underlying cloud infrastructure
- General understanding of hospital operations
- Development experience with Spring
Success Criteria: list (these are bullet points but each preceded by a label):
- Own Getting Things Done: Given an objective, you plan out how to get there and see it through
- Grow in Knowledge and Skill: There are things you need to learn to tackle tasks at hand, but expanding your learning beyond that is something you do habitually
- Communicate Clearly, Concisely and Effectively: Connecting with people is important to you and you work to become successful
- Deliver Frequently and Incrementally: Breaking down problems into smaller chunks, testing them and getting feedback is a discipline you hold yourself to
- Solve Problems Effectively and Efficiently: Weighing the options and picking the one most likely to fit best, is a strength that you build on
- Share Knowledge and Ideas: You jump in to contribute to the pool of ideas and provide guidance
Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future. This is a requirement; could be part of Requirements or Qualifications. We'll include as a paragraph under Requirements maybe.
Benefits: list:
- Employee Medical/dental/vision premiums paid 100% - family members without coverage
- Medical 100% - small cost for dependents on dental and vision, which start from day one!
- Life and AD&D
- Flexible Spending Accounts: Medical, Dependent Care, and Transportation
- 401 (k) Retirement Savings
- Tuition Reimbursement
- Military Paid Leave (up to 6 months of base salary while on military leave)
- Paid Time Off
- Paid parental leave
We need to output HTML fragment with headings
and content.
We need to decide which headings to use.
We have:
- About the role: could contain About Us + Our Team (company description and team). We'll put that as prose paragraphs.
- Responsibilities: the duties list.
- Requirements: could combine Skills & Experience We're Seeking, Nice to haves, and authorization statement.
- Qualifications: Success Criteria.
- Benefits: benefits list.
We should not include Pay or Schedule.
We must not repeat job title as heading; we aren't.
We must not put Job ID/requisition numbers as headings; none present.
We must remove boilerplate: Disclaimer, EEO, etc. Already removed.
Now produce HTML.
We need to ensure we use - for any list of duties/requirements/benefits. For prose, use
.
Thus:
About the role
TeleTracking began with a simple but powerful belief that no one should wait for the care they need. More than a slogan, it’s a promise to continually improve healthcare. TeleTracking builds groundbreaking technology incorporating deep clinical expertise. Our solutions are used in the nation’s largest healthcare systems and around the world to positively impact patients, families and communities. What’s your contribution to the TeleTracking story? When you chose to bring your passion and skills to helping achieve our purpose, you’ll be part of a team that understands that there’s a human life behind every data point. Your skills, curiosity, and compassion—will help fuel our innovation and achieve the TeleTracking promise of revolutionizing modern healthcare.
TeleTracking is an integrated healthcare operations platform provider that is Expanding the Capacity to Care™ by helping health systems optimize access to care, streamline care delivery, and connect transitions of care. We are passionate about saving the lives of the patients, giving time back to the caregivers and improving throughput across health systems. The Logistics Engineering teams design, build and operate the applications and services that serve the evolving needs of caregivers. As we expand our capabilities to effectively manage patient flows across and within hospital systems, we seek the best and brightest engineering talent to be part of our growth. Our team is looking for a Senior Software Engineer to drive the expansion of features to our customers through services that the team owns and operates on our event based microservice platform.
Responsibilities
- Understanding and solving business needs at scale with high-quality solutions
- Building and operating resilient services and infrastructure
- Developing fluency in using coding agents throughout the software development lifecycle
- Creating metrics, dashboards and alerts to measure and meet SLOs for service performance, errors and availability and reacting to resolve issues in an on-call rotation
- Build on AWS services such as Lambda, EKS, S3, EC2, RDS, DynamoDB
Requirements
- 2-5 years of expertise in Java, Go, or similar object-oriented languages
- Fluency in using coding agents
- Experience debugging in Production
- Ability to design, build and operate highly scalable, secure, and fault-tolerant services
- Experience in contributing to architectural decisions
- Motivated to dive deep to understand problems and customer pain points, and solve them using appropriate engineering principles
- Working understanding of event driven architecture and microservices
- Interest in underlying cloud infrastructure
- General understanding of hospital operations
- Development experience with Spring
- Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future.
Qualifications
- Own Getting Things Done: Given an objective, you plan out how to get there and see it through
- Grow in Knowledge and Skill: There are things you need to learn to tackle tasks at hand, but expanding your learning beyond that is something you do habitually
- Communicate Clearly, Concisely and Effectively: Connecting with people is important to you and you work to become successful
- Deliver Frequently and Incrementally: Breaking down problems into smaller chunks, testing them and getting feedback is a discipline you hold yourself to
- Solve Problems Effectively and Efficiently: Weighing the options and picking the one most likely to fit best, is a strength that you build on
- for any list of duties/requirements/benefits, and
for prose. Thus we need to parse the content into prose paragraphs and lists. Let's extract sections: About Us paragraph: "TeleTracking began with a simple but powerful belief that no one should wait for the care they need. More than a slogan, it’s a promise to continually improve healthcare. TeleTracking builds groundbreaking technology incorporating deep clinical expertise. Our solutions are used in the nation’s largest healthcare systems and around the world to positively impact patients, families and communities. What’s your contribution to the TeleTracking story? When you chose to bring your passion and skills to helping achieve our purpose, you’ll be part of a team that understands that there’s a human life behind every data point. Your skills, curiosity, and compassion—will help fuel our innovation and achieve the TeleTracking promise of revolutionizing modern healthcare." Our Team paragraph: "TeleTracking is an integrated healthcare operations platform provider that is Expanding the Capacity to Care™ by helping health systems optimize access to care, streamline care delivery, and connect transitions of care. We are passionate about saving the lives of the patients, giving time back to the caregivers and improving throughput across health systems. Our Team The Logistics Engineering teams design, build and operate the applications and services that serve the evolving needs of caregivers. As we expand our capabilities to effectively manage patient flows across and within hospital systems, we seek the best and brightest engineering talent to be part of our growth. Our team is looking for a Senior Software Engineer to drive the expansion of features to our customers through services that the team owns and operates on our event based microservice platform." Note: The text repeats "Our Team" twice? Actually after first paragraph there is "Our Team". We'll combine. What You Will Be Doing In The Role: list of duties: - Understanding and solving business needs at scale with high-quality solutions - Building and operating resilient services and infrastructure - Developing fluency in using coding agents throughout the software development lifecycle - Creating metrics, dashboards and alerts to measure and meet SLOs for service performance, errors and availability and reacting to resolve issues in an on-call rotation - Build on AWS services such as Lambda, EKS, S3, EC2, RDS, DynamoDB These are bullet points. Skills & Experience We're Seeking: list: - 2-5 years of expertise in Java, Go, or similar object-oriented languages - Fluency in using coding agents - Experience debugging in Production - Ability to design, build and operate highly scalable, secure, and fault-tolerant services - Experience in contributing to architectural decisions - Motivated to dive deep to understand problems and customer pain points, and solve them using appropriate engineering principles - Working understanding of event driven architecture and microservices Nice to haves: list: - Interest in underlying cloud infrastructure - General understanding of hospital operations - Development experience with Spring Success Criteria: list (these are bullet points but each preceded by a label): - Own Getting Things Done: Given an objective, you plan out how to get there and see it through - Grow in Knowledge and Skill: There are things you need to learn to tackle tasks at hand, but expanding your learning beyond that is something you do habitually - Communicate Clearly, Concisely and Effectively: Connecting with people is important to you and you work to become successful - Deliver Frequently and Incrementally: Breaking down problems into smaller chunks, testing them and getting feedback is a discipline you hold yourself to - Solve Problems Effectively and Efficiently: Weighing the options and picking the one most likely to fit best, is a strength that you build on - Share Knowledge and Ideas: You jump in to contribute to the pool of ideas and provide guidance Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future. This is a requirement; could be part of Requirements or Qualifications. We'll include as a paragraph under Requirements maybe. Benefits: list: - Employee Medical/dental/vision premiums paid 100% - family members without coverage - Medical 100% - small cost for dependents on dental and vision, which start from day one! - Life and AD&D - Flexible Spending Accounts: Medical, Dependent Care, and Transportation - 401 (k) Retirement Savings - Tuition Reimbursement - Military Paid Leave (up to 6 months of base salary while on military leave) - Paid Time Off - Paid parental leave We need to output HTML fragment with headings
and content. We need to decide which headings to use. We have: - About the role: could contain About Us + Our Team (company description and team). We'll put that as prose paragraphs. - Responsibilities: the duties list. - Requirements: could combine Skills & Experience We're Seeking, Nice to haves, and authorization statement. - Qualifications: Success Criteria. - Benefits: benefits list. We should not include Pay or Schedule. We must not repeat job title as heading; we aren't. We must not put Job ID/requisition numbers as headings; none present. We must remove boilerplate: Disclaimer, EEO, etc. Already removed. Now produce HTML. We need to ensure we use
- for any list of duties/requirements/benefits. For prose, use
. Thus:
About the role
TeleTracking began with a simple but powerful belief that no one should wait for the care they need. More than a slogan, it’s a promise to continually improve healthcare. TeleTracking builds groundbreaking technology incorporating deep clinical expertise. Our solutions are used in the nation’s largest healthcare systems and around the world to positively impact patients, families and communities. What’s your contribution to the TeleTracking story? When you chose to bring your passion and skills to helping achieve our purpose, you’ll be part of a team that understands that there’s a human life behind every data point. Your skills, curiosity, and compassion—will help fuel our innovation and achieve the TeleTracking promise of revolutionizing modern healthcare.
TeleTracking is an integrated healthcare operations platform provider that is Expanding the Capacity to Care™ by helping health systems optimize access to care, streamline care delivery, and connect transitions of care. We are passionate about saving the lives of the patients, giving time back to the caregivers and improving throughput across health systems. The Logistics Engineering teams design, build and operate the applications and services that serve the evolving needs of caregivers. As we expand our capabilities to effectively manage patient flows across and within hospital systems, we seek the best and brightest engineering talent to be part of our growth. Our team is looking for a Senior Software Engineer to drive the expansion of features to our customers through services that the team owns and operates on our event based microservice platform.
Responsibilities
- Understanding and solving business needs at scale with high-quality solutions
- Building and operating resilient services and infrastructure
- Developing fluency in using coding agents throughout the software development lifecycle
- Creating metrics, dashboards and alerts to measure and meet SLOs for service performance, errors and availability and reacting to resolve issues in an on-call rotation
- Build on AWS services such as Lambda, EKS, S3, EC2, RDS, DynamoDB
Requirements
- 2-5 years of expertise in Java, Go, or similar object-oriented languages
- Fluency in using coding agents
- Experience debugging in Production
- Ability to design, build and operate highly scalable, secure, and fault-tolerant services
- Experience in contributing to architectural decisions
- Motivated to dive deep to understand problems and customer pain points, and solve them using appropriate engineering principles
- Working understanding of event driven architecture and microservices
- Interest in underlying cloud infrastructure
- General understanding of hospital operations
- Development experience with Spring
- Applicants must be authorized to work in the U.S. without the need for employment-based visa sponsorship now or in the future.
Qualifications
- Own Getting Things Done: Given an objective, you plan out how to get there and see it through
- Grow in Knowledge and Skill: There are things you need to learn to tackle tasks at hand, but expanding your learning beyond that is something you do habitually
- Communicate Clearly, Concisely and Effectively: Connecting with people is important to you and you work to become successful
- Deliver Frequently and Incrementally: Breaking down problems into smaller chunks, testing them and getting feedback is a discipline you hold yourself to
- Solve Problems Effectively and Efficiently: Weighing the options and picking the one most likely to fit best, is a strength that you build on
- for any list of duties/requirements/benefits. For prose, use