Typescript Software Engineer
Lucas James Talent Partners · Chicago, IL · 1 mo ago
RemoteRemoteInformation Technology$125k/yrFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. The posting includes: "THE OPPORTUNITY" description (maybe About the role). Then "About Us". Then "Responsibilities" (but note the responsibilities section actually starts with a list that includes many bullet points, but the first bullet is "Bachelor’s degree...". Actually the responsibilities list includes qualifications etc. Then later there is a duplicate "Requirements" heading with marketing-focused requirements (seems mismatched). Then "Tech Stack". Then "Benefits" with details. Also there is mention of salary range: "Competitive Salary and Annual Bonus The salary range for this role is $100,000 to $125,000". So we need a Pay section. Schedule? Not mentioned. So we should not include Schedule.
We need to preserve all substantive info, not invent. Remove boilerplate like cookie/navigation/legal/EEO etc. There's none.
We need to use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real content. The posting includes: "THE OPPORTUNITY" description (maybe About the role). Then "About Us". Then "Responsibilities" (but note the responsibilities section actually starts with a list that includes many bullet points, but the first bullet is "Bachelor’s degree...". Actually the responsibilities list includes qualifications etc. Then later there is a duplicate "Requirements" heading with marketing-focused requirements (seems mismatched). Then "Tech Stack". Then "Benefits" with details. Also there is mention of salary range: "Competitive Salary and Annual Bonus The salary range for this role is $100,000 to $125,000". So we need a Pay section. Schedule? Not mentioned. So we should not include Schedule.
We need to preserve all substantive info, not invent. Remove boilerplate like cookie/navigation/legal/EEO etc. There's none.
We need to use for section headings. Use - for any list of duties/requirements/benefits. Use
for prose.
We must not repeat job title as heading. Not include Job ID.
We need to decide sections: About the role (maybe from THE OPPORTUNITY and About Us). Responsibilities (list). Requirements (list). Qualifications? Could combine with Requirements? But we have both Responsibilities and Requirements sections. The posting has a "Responsibilities" list that actually includes many items (some are qualifications). Then later a "Requirements" heading with marketing-focused requirements (maybe mis-placed). We need to preserve all substantive info; we should not invent or summarize away detail. So we need to include both sections as they appear, but we need to ensure they are not filler. The Responsibilities section includes bullet points like "Bachelor’s degree in Computer Science..." etc. That's substantive. The Requirements section includes bullet points like "5-8+ years of experience in B2B SaaS growth marketing..." etc. That's also substantive (though seems mismatched). We'll keep both.
We also have "Tech Stack" maybe could be Skills? Could be a section "Skills" or "Tech Stack". The instruction says use headings like Skills, Benefits, Pay, Schedule. We could put Tech Stack under Skills. But we must not invent headings not listed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we can use those headings. Probably we should map content to those headings. Tech Stack could go under Skills. But we could also create a Skills heading and list the tech stack there. However we must not invent headings that are not in the list unless needed? The instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings; we can use them. It doesn't forbid other headings, but better to stick to those. So we can have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay.
We need to avoid empty sections.
Now extract content:
About the role: From THE OPPORTUNITY paragraph(s) and About Us paragraph(s). Let's combine.
THE OPPORTUNITY: "Casechek is on a mission to innovate the implant supply chain and bring greater transparency to the cost of patient care. From procurement to payment, Casechek automates workflows for vendor-supported surgical procedures. Our emergent Bill Only solution provides a comprehensive system of record for hospitals and health systems to manage the complexity of surgical cases involving implantable medical devices, expose hidden expenses, and surface revenue opportunities. In this role, you will design, build, and improve the technology that powers Casechek’s mobile and web products. As a Software Engineer, you will develop scalable cloud-based solutions, contribute to technical architecture and design decisions, and help translate product goals into reliable software. You will collaborate closely with Product, Engineering, and other internal teams to deliver solutions that meet customer and business needs. You will also help strengthen our development practices, code quality, testing standards, and overall technical capabilities. Your day-to-day interactions will require strategic thinking, strong communication skills, the ability to leverage data, and comfort managing complex initiatives. You should be adept at navigating new technologies and collaborating with cross-functional teams to deliver exceptional service and support. Casechek is a highly collaborative environment, and our team is also self-motivated and works independently. We strongly believe that great ideas are not created in isolation. Our team interacts with our healthcare customers to understand their needs and ultimately deliver the best user experience possible."
About Us: "Casechek is based out of Chicago’s Fulton Market, but we’re a hybrid, remote, and in-person team. We are highly motivated and passionate about solving healthcare’s messiest problems with new technologies. We value diversity, curiosity, and a passion for learning. The team has a lot of advanced degrees and even a few professional musicians. Innovating the implant supply chain is a marathon and not a sprint. We support each other in long-term growth and value developing transferable skills."
We can combine into a prose
maybe multiple paragraphs.
Responsibilities: The list after "Responsibilities" heading: It starts with "Bachelor’s degree in Computer Science, Software Engineering, a related field, or equivalent professional experience required." then many bullet-like sentences separated by periods. We need to turn each into
- . Let's extract each distinct item:
- Bachelor’s degree in Computer Science, Software Engineering, a related field, or equivalent professional experience required.
- 5+ years of professional backend software development experience.
- Strong proficiency with TypeScript and Node.js.
- Professional experience developing applications with NestJS.
- Experience designing, developing, and integrating REST APIs.
- Experience supporting and troubleshooting an AWS-hosted SaaS product.
- Experience building scalable, performant, and reliable software solutions.
- Familiarity with relational database technologies, data modeling, and database design.
- Experience working in an Agile or Scrum software development environment.
- Strong problem-solving skills and the ability to address complex technical challenges creatively.
- Sharp attention to detail and a commitment to writing clean, maintainable, and reliable code.
- Excellent English verbal and written communication skills.
- Ability to collaborate effectively across technical and nontechnical teams.
- Ability to manage multiple priorities and adapt to changing project requirements in a fast-paced environment.
- Commitment to continuous learning and staying current with modern technologies, frameworks, and development practices.
That's the responsibilities list.
Requirements: The second "Requirements" heading list:
- 5-8+ years of experience in B2B SaaS growth marketing, demand generation, or revenue marketing.
- Demonstrated track record of generating qualified pipeline and marketing-influenced revenue in support of an enterprise sales organization.
- Strong analytical and reporting skills, with comfort owning metrics such as qualified pipeline generated, opportunities created, conversion rates, campaign performance, and ROMI.
- Hands-on expertise with CRM software and Marketing Automation (Salesforce and Pardot preferred), including lead management and attribution.
- Ability to operate strategically while remaining highly hands-on as an individual contributor.
- Experience in managing 1-3 direct reports is strongly preferred
- Experience in Healthcare strongly preferred: Healthcare Technology, Healthcare Supply Chain, Revenue Cycle, Medical Devices, or Hospital Operations.
- Comfortable with MS Excel (analyzing spreadsheets and charts) as well as Microsoft PowerPoint.
- Bachelor's degree in Marketing, Business Administration or relevant field. (MBA preferred).
We need to keep as list.
Skills: Could be Tech Stack: NestJS, Angular, TypeScript, Node.js, PostgreSQL, AWS, AWS Lambda. Also maybe other skills from responsibilities? But we can put tech stack under Skills.
Benefits: List from "Why You'll Love Working Here" bullet points:
- Competitive Salary and Annual Bonus: The salary range for this role is $100,000 to $125,000, based on experience, skills, and location.
- Opportunity for Long-Term Incentives (LTI): Be part of our success with equity or long-term incentive plans that grow with the company.
- 401(k) Match: Invest in your future with our generous matching program to help you build long-term financial security.
- Work-from-Home Flexibility: Enjoy the freedom to work where you are most productive with a supportive hybrid option in Chicago or a remote setup nationally.
- Flexible Time Off (Unlimited PTO): Recharge and focus on what matters most with unlimited paid time off tailored to your needs.
- Parental Leave: Take time to bond with and care for your growing family with fully paid parental leave options.
- Comprehensive Medical and Dental Benefits: Prioritize your health and well-being with premium plans for you and your family.
- Brand-New Pro-Level Laptop: Receive top-tier tools and technology to set you up for success from day one.
- Annual Education Budget: Expand your skills and knowledge with dedicated funding for courses, certifications, and learning resources.
We need to separate Pay maybe as its own section. The benefits list includes salary range; but we also need a Pay section per instruction: only create Pay if posting actually states them. It does state salary range. So we should have a Pay section with that info. Benefits section should exclude salary? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can have both Pay and Benefits sections; we just need to not duplicate salary in Benefits if we move it to Pay. However the benefits list includes "Competitive Salary and Annual Bonus The salary range for this role is $100,000 to $125,000, based on experience, skills, and location." We could keep that as part of Benefits but also have Pay. To avoid duplication, maybe we put salary range in Pay section, and keep other benefits in Benefits section without the salary line. Let's extract other benefits:
- Opportunity for Long-Term Incentives (LTI): Be part of our success with equity or long-term incentive plans that grow with the company.
- 401(k) Match: Invest in your future with our generous matching program to help you build long-term financial security.
- Work-from-Home Flexibility: Enjoy the freedom to work where you are most productive with a supportive hybrid option in Chicago or a remote setup nationally.
- Flexible Time Off (Unlimited PTO): Recharge and focus on what matters most with unlimited paid time off tailored to your needs.
- Parental Leave: Take time to bond with and care for your growing family with fully paid parental leave options.
- Comprehensive Medical and Dental Benefits: Prioritize your health and well-being with premium plans for you and your family.
- Brand-New Pro-Level Laptop: Receive top-tier tools and technology to set you up for success from day one.
- Annual Education Budget: Expand your skills and knowledge with dedicated funding for courses, certifications, and learning resources.
Pay section: Salary range $100,000 to $125,000 based on experience, skills, and location. Also mention Competitive Salary and Annual Bonus? Could include that phrase.
Now Skills section: list tech stack: NestJS, Angular, TypeScript, Node.js, PostgreSQL, AWS, AWS Lambda.
We might also include other skills like REST API, AWS-hosted SaaS, etc. But those are in responsibilities. We'll keep Skills as tech stack.
Now we need to output HTML fragment only, no /. Use
headings,
for prose,
- for lists.
We need to ensure we don't include any boilerplate.
Let's craft:
About the role
Casechek is on a mission to innovate the implant supply chain and bring greater transparency to the cost of patient care. From procurement to payment, Casechek automates workflows
- for any list of duties/requirements/benefits. Use
for prose. We must not repeat job title as heading. Not include Job ID. We need to decide sections: About the role (maybe from THE OPPORTUNITY and About Us). Responsibilities (list). Requirements (list). Qualifications? Could combine with Requirements? But we have both Responsibilities and Requirements sections. The posting has a "Responsibilities" list that actually includes many items (some are qualifications). Then later a "Requirements" heading with marketing-focused requirements (maybe mis-placed). We need to preserve all substantive info; we should not invent or summarize away detail. So we need to include both sections as they appear, but we need to ensure they are not filler. The Responsibilities section includes bullet points like "Bachelor’s degree in Computer Science..." etc. That's substantive. The Requirements section includes bullet points like "5-8+ years of experience in B2B SaaS growth marketing..." etc. That's also substantive (though seems mismatched). We'll keep both. We also have "Tech Stack" maybe could be Skills? Could be a section "Skills" or "Tech Stack". The instruction says use headings like Skills, Benefits, Pay, Schedule. We could put Tech Stack under Skills. But we must not invent headings not listed? It says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exhaustive; we can use those headings. Probably we should map content to those headings. Tech Stack could go under Skills. But we could also create a Skills heading and list the tech stack there. However we must not invent headings that are not in the list unless needed? The instruction: "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests those are typical headings; we can use them. It doesn't forbid other headings, but better to stick to those. So we can have sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. We need to avoid empty sections. Now extract content: About the role: From THE OPPORTUNITY paragraph(s) and About Us paragraph(s). Let's combine. THE OPPORTUNITY: "Casechek is on a mission to innovate the implant supply chain and bring greater transparency to the cost of patient care. From procurement to payment, Casechek automates workflows for vendor-supported surgical procedures. Our emergent Bill Only solution provides a comprehensive system of record for hospitals and health systems to manage the complexity of surgical cases involving implantable medical devices, expose hidden expenses, and surface revenue opportunities. In this role, you will design, build, and improve the technology that powers Casechek’s mobile and web products. As a Software Engineer, you will develop scalable cloud-based solutions, contribute to technical architecture and design decisions, and help translate product goals into reliable software. You will collaborate closely with Product, Engineering, and other internal teams to deliver solutions that meet customer and business needs. You will also help strengthen our development practices, code quality, testing standards, and overall technical capabilities. Your day-to-day interactions will require strategic thinking, strong communication skills, the ability to leverage data, and comfort managing complex initiatives. You should be adept at navigating new technologies and collaborating with cross-functional teams to deliver exceptional service and support. Casechek is a highly collaborative environment, and our team is also self-motivated and works independently. We strongly believe that great ideas are not created in isolation. Our team interacts with our healthcare customers to understand their needs and ultimately deliver the best user experience possible." About Us: "Casechek is based out of Chicago’s Fulton Market, but we’re a hybrid, remote, and in-person team. We are highly motivated and passionate about solving healthcare’s messiest problems with new technologies. We value diversity, curiosity, and a passion for learning. The team has a lot of advanced degrees and even a few professional musicians. Innovating the implant supply chain is a marathon and not a sprint. We support each other in long-term growth and value developing transferable skills." We can combine into a prose
maybe multiple paragraphs. Responsibilities: The list after "Responsibilities" heading: It starts with "Bachelor’s degree in Computer Science, Software Engineering, a related field, or equivalent professional experience required." then many bullet-like sentences separated by periods. We need to turn each into
- . Let's extract each distinct item:
- Bachelor’s degree in Computer Science, Software Engineering, a related field, or equivalent professional experience required.
- 5+ years of professional backend software development experience.
- Strong proficiency with TypeScript and Node.js.
- Professional experience developing applications with NestJS.
- Experience designing, developing, and integrating REST APIs.
- Experience supporting and troubleshooting an AWS-hosted SaaS product.
- Experience building scalable, performant, and reliable software solutions.
- Familiarity with relational database technologies, data modeling, and database design.
- Experience working in an Agile or Scrum software development environment.
- Strong problem-solving skills and the ability to address complex technical challenges creatively.
- Sharp attention to detail and a commitment to writing clean, maintainable, and reliable code.
- Excellent English verbal and written communication skills.
- Ability to collaborate effectively across technical and nontechnical teams.
- Ability to manage multiple priorities and adapt to changing project requirements in a fast-paced environment.
- Commitment to continuous learning and staying current with modern technologies, frameworks, and development practices.
That's the responsibilities list.
Requirements: The second "Requirements" heading list:
- 5-8+ years of experience in B2B SaaS growth marketing, demand generation, or revenue marketing.
- Demonstrated track record of generating qualified pipeline and marketing-influenced revenue in support of an enterprise sales organization.
- Strong analytical and reporting skills, with comfort owning metrics such as qualified pipeline generated, opportunities created, conversion rates, campaign performance, and ROMI.
- Hands-on expertise with CRM software and Marketing Automation (Salesforce and Pardot preferred), including lead management and attribution.
- Ability to operate strategically while remaining highly hands-on as an individual contributor.
- Experience in managing 1-3 direct reports is strongly preferred
- Experience in Healthcare strongly preferred: Healthcare Technology, Healthcare Supply Chain, Revenue Cycle, Medical Devices, or Hospital Operations.
- Comfortable with MS Excel (analyzing spreadsheets and charts) as well as Microsoft PowerPoint.
- Bachelor's degree in Marketing, Business Administration or relevant field. (MBA preferred).
We need to keep as list.
Skills: Could be Tech Stack: NestJS, Angular, TypeScript, Node.js, PostgreSQL, AWS, AWS Lambda. Also maybe other skills from responsibilities? But we can put tech stack under Skills.
Benefits: List from "Why You'll Love Working Here" bullet points:
- Competitive Salary and Annual Bonus: The salary range for this role is $100,000 to $125,000, based on experience, skills, and location.
- Opportunity for Long-Term Incentives (LTI): Be part of our success with equity or long-term incentive plans that grow with the company.
- 401(k) Match: Invest in your future with our generous matching program to help you build long-term financial security.
- Work-from-Home Flexibility: Enjoy the freedom to work where you are most productive with a supportive hybrid option in Chicago or a remote setup nationally.
- Flexible Time Off (Unlimited PTO): Recharge and focus on what matters most with unlimited paid time off tailored to your needs.
- Parental Leave: Take time to bond with and care for your growing family with fully paid parental leave options.
- Comprehensive Medical and Dental Benefits: Prioritize your health and well-being with premium plans for you and your family.
- Brand-New Pro-Level Laptop: Receive top-tier tools and technology to set you up for success from day one.
- Annual Education Budget: Expand your skills and knowledge with dedicated funding for courses, certifications, and learning resources.
We need to separate Pay maybe as its own section. The benefits list includes salary range; but we also need a Pay section per instruction: only create Pay if posting actually states them. It does state salary range. So we should have a Pay section with that info. Benefits section should exclude salary? The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can have both Pay and Benefits sections; we just need to not duplicate salary in Benefits if we move it to Pay. However the benefits list includes "Competitive Salary and Annual Bonus The salary range for this role is $100,000 to $125,000, based on experience, skills, and location." We could keep that as part of Benefits but also have Pay. To avoid duplication, maybe we put salary range in Pay section, and keep other benefits in Benefits section without the salary line. Let's extract other benefits:
- Opportunity for Long-Term Incentives (LTI): Be part of our success with equity or long-term incentive plans that grow with the company.
- 401(k) Match: Invest in your future with our generous matching program to help you build long-term financial security.
- Work-from-Home Flexibility: Enjoy the freedom to work where you are most productive with a supportive hybrid option in Chicago or a remote setup nationally.
- Flexible Time Off (Unlimited PTO): Recharge and focus on what matters most with unlimited paid time off tailored to your needs.
- Parental Leave: Take time to bond with and care for your growing family with fully paid parental leave options.
- Comprehensive Medical and Dental Benefits: Prioritize your health and well-being with premium plans for you and your family.
- Brand-New Pro-Level Laptop: Receive top-tier tools and technology to set you up for success from day one.
- Annual Education Budget: Expand your skills and knowledge with dedicated funding for courses, certifications, and learning resources.
Pay section: Salary range $100,000 to $125,000 based on experience, skills, and location. Also mention Competitive Salary and Annual Bonus? Could include that phrase.
Now Skills section: list tech stack: NestJS, Angular, TypeScript, Node.js, PostgreSQL, AWS, AWS Lambda.
We might also include other skills like REST API, AWS-hosted SaaS, etc. But those are in responsibilities. We'll keep Skills as tech stack.
Now we need to output HTML fragment only, no /. Use
headings,
for prose,
- for lists.
We need to ensure we don't include any boilerplate.
Let's craft:
About the role
Casechek is on a mission to innovate the implant supply chain and bring greater transparency to the cost of patient care. From procurement to payment, Casechek automates workflows
- for lists.
We need to ensure we don't include any boilerplate.
Let's craft: