Senior Software Engineer
Vertical Relevance · New York, NY · 4 wk ago
EngineeringFull-time
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO, equal opportunity, etc. Must preserve all substantive info.
We need to parse the posting.
Let's extract sections:
- Role Summary: "Vertical Relevance is seeking a Senior Software Engineer with deep experience in TypeScript, workflow orchestration, distributed systems, and cloud-native platforms who can lead technically while remaining hands-on in code."
That's about the role. Could be "About the role" section.
- Key Responsibilities: list bullet points.
- Required Qualifications: list bullet points.
- Preferred Qualifications: list bullet points.
- Technical Environment: list of technologies.
- Ideal Candidate Profile: description.
- Sample Activities: many bullet points (some seem like tasks). Might be considered responsibilities? Could be separate "Sample Activities" but not required heading; we can incorporate into Responsibilities or maybe a separate "Activities" but not in allowed headings. We have only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these.
"Requirements" could be Required Qualifications. "Qualifications" could be Preferred Qualifications. "Skills" could be Technical Environment / Ideal Candidate Profile / maybe list of skills.
We must not create sections with filler. Must include only sections with real content.
We have no explicit Benefits, Pay, Schedule info in posting. So we should NOT include those sections.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Skills.
Check each for content.
About the role: we have the role summary sentence.
Responsibilities: from "Key Responsibilities" bullet list.
Requirements: from "Required Qualifications" bullet list.
Qualifications: from "Preferred Qualifications" bullet list.
Skills: from "Technical Environment" and maybe "Ideal Candidate Profile" and "Sample Activities"? But we need to ensure we don't duplicate. Could combine technical environment list as skills.
We must preserve all substantive info; not invent or summarize away detail. So we need to include all bullet points exactly as given (maybe rephrase? but must preserve info). We'll output as
- each bullet.
We need to remove boilerplate: EEO statement, "Powered by JazzHR", maybe also "Vertical Relevance was founded..." paragraph about company? That's substantive? It's about the company; could be considered part of About the role? Might be considered extra but not required headings. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The company description may be considered not boilerplate but maybe part of About the role? It's not explicitly a heading. Could be included in About the role paragraph? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the company description as part of About the role? It's substantive. However the About the role heading is for role summary; we could add more paragraphs under About the role that include company description. That seems okay.
We also have "Ideal Candidate Profile" and "Sample Activities". Those are substantive; we need to place them somewhere. Could be under Skills or maybe under Responsibilities? But they are not responsibilities exactly; they are activities. Could be under Responsibilities as they are tasks. But the "Key Responsibilities" already list some; the Sample Activities are more detailed tasks. Might be appropriate to include under Responsibilities as additional bullet points. However we must not invent headings; we can add them under Responsibilities as
- . That would preserve info.
Similarly Ideal Candidate Profile could be under Skills or maybe under Qualifications? It's more about profile; could be under Skills as a paragraph.
We need to decide structure.
Let's extract all bullet points:
Key Responsibilities:
- Design and implement enterprise workflow orchestration capabilities.
- Build durable workflows using Temporal, Dapr, AWS Step Functions, or similar technologies.
- Architect event-driven systems using Kafka and messaging technologies.
- Deploy and operate containerized applications in Kubernetes or OpenShift environments.
- Evaluate platform and infrastructure choices and provide architectural recommendations.
Required Qualifications:
- 8+ years software engineering experience.
- Expert-level TypeScript and Node.js skills.
- Hands-on workflow orchestration experience.
- Strong distributed systems background including Kafka, pub/sub, retries, and idempotency.
- Kubernetes or OpenShift experience.
- Enterprise architecture and technical leadership experience.
Preferred Qualifications:
- AI agent platforms and orchestration frameworks.
- Financial services or regulated-industry experience.
- Build-versus-buy evaluation experience.
- Platform engineering background.
Technical Environment:
- TypeScript, Node.js, Temporal, Kubernetes, OpenShift, Kafka, AWS, Containerized Microservices, Distributed Systems, AI-enabled Workflows
Ideal Candidate Profile:
- A builder, architect, and technical leader capable of defining technical direction while writing production-quality code and operating effectively in ambiguous environments.
Sample Activities: many bullet points (some seem repetitive). Let's list them:
- Creating a Self-Service Pipeline Framework
- Assist Customers in defining Customer’s Framework capabilities based on Customer’s identified business outcomes.
- Assist Customer with reviewing the Framework architecture against Customer’s identified business outcomes, to include providing general recommendations to help Customer close any observed gaps.
- Provide Customer with AWS general best practices that may help Customer refine identified deployments.
- Assist Customer with defining the first iteration of minimum viable product (MVP) for the DevOps Framework.
- Deploying Java web apps and building new Amazon Elastic Compute Cloud (Amazon EC2) instances
- Deploying Python on AWS Lambda
- Deploying Java on AWS Lambda
- Blue/green deployments on Amazon Elastic Container Service (Amazon ECS)
- Deploying to existing Amazon EC2 instances (Windows operating system)
- Provisioning dashboards to monitor deployments.
- Assist Customer in developing and implementing the first iteration of MVP in a non-production environment, under Customer’s direction and using AWS general best practices
- Assist Customer with identifying next steps and proposing activities for a future follow-on engagement.
- Creating a Self-Service Environment Framework
- Assist in selecting tools for building Infrastructure-as-Code.
- Assist Customer in the development of referenceable playbooks, supported by relevant code examples for application infrastructure code.
- Assist Customer in the development of sample runbooks to automate the implementation of application infrastructure code:
- Infrastructure-as-Code - Development of Infrastructure-as-Code specific to each application that can be used to automate the delivery of configured AWS resources specific to the requirements of the application being deployed.
- Configuration Management - The development of configuration management modules specific to each application used to automate the configuration of servers including software installation and configuration.
- Service Catalog Pipeline - Development of a framework for orchestrating build, test, deployment, and validation of infrastructure automation code.
- Service Catalog - Management of Service Catalog portfolios to connect products based on selected applications.
- Assist Customer with the development of a report and supporting sample code addressing the application infrastructure code as part of the playbook.
That's a lot. We'll include them under Responsibilities as additional bullet points (maybe under a subheading? but we can't add new headings). We'll just continue the same
- list.
Now About the role: we have the role summary sentence plus company description paragraph(s). Let's extract company description:
"The Company Vertical Relevance was founded to help business leaders drive value through the design and delivery of effective transformation programs across people, processes, and systems. Our mission is to help firms at any stage of their journey develop custom solutions for success and growth. We provide a full range of services from strategy and design through to implementation and training. Our collective industry expertise is our greatest asset - our professionals have an average of 20+ years’ experience within Financial Services, across Wealth Management, Asset Management, Insurance, and Banking. Within our Customer Experience practice, we add complementary industry expertise (technology and media) synergizing the most relevant and successful customer trends. We focus wholly on your success by first rigorously assessing your business and technology challenges, and then right-sizing solutions that provide a meaningful ROI. With our industry experts hitting the ground running and focusing on nimble, quality delivery, we can see rapid, tangible improvements with our clients in productivity and effectiveness. When it makes sense for your company, we leverage our product partnerships in the areas of CRM, Sales Acceleration, Predictive Analytics, Digital Knowledge Management, and Cloud Transformation."
We should keep that as paragraph(s) under About the role.
Now Skills: we could include Technical Environment list and Ideal Candidate Profile as a paragraph.
We must not create sections with filler. Ensure we don't include Benefits, Pay, Schedule.
Now produce HTML fragment:
About the role
Vertical Relevance is seeking a Senior Software Engineer with deep experience in TypeScript, workflow orchestration, distributed systems, and cloud-native platforms who can lead technically while remaining hands-on in code.
[company description paragraph(s)]
Responsibilities
- Design and implement enterprise workflow orchestration capabilities.
- Build durable workflows using Temporal, Dapr, AWS Step Functions, or similar technologies.
- Architect event-driven systems using Kafka and messaging technologies.
- Deploy and operate containerized applications in Kubernetes or OpenShift environments.
- Evaluate platform and infrastructure choices and provide architectural recommendations.
- Creating a Self-Service Pipeline Framework
- Assist Customers in defining Customer’s Framework capabilities based on Customer’s identified business outcomes.
- Assist Customer with reviewing the Framework architecture against Customer’s identified business outcomes, to include providing general recommendations to help Customer close any observed gaps.
- Provide Customer with AWS general best practices that may help Customer refine identified deployments.
- Assist Customer with defining the first iteration of minimum viable product (MVP) for the DevOps Framework.
- Deploying Java web apps and building new Amazon Elastic Compute Cloud (Amazon EC2) instances
- Deploying Python on AWS Lambda
- Deploying Java on AWS Lambda
- Blue/green deployments on Amazon Elastic Container Service (Amazon ECS)
- Deploying to existing Amazon EC2 instances (Windows operating system)
- Provisioning dashboards to monitor deployments.
- Assist Customer in developing and implementing the first iteration of MVP in a non-production environment, under Customer’s direction and using AWS general best practices
- Assist Customer with identifying next steps and proposing activities for a future follow-on engagement.
- Creating a Self-Service Environment Framework
- Assist in selecting tools for building Infrastructure-as-Code.
- Assist Customer in the development of referenceable playbooks, supported by relevant code examples for application infrastructure code.
- Assist Customer in the development of sample runbooks to automate the implementation of application infrastructure code:
- Infrastructure-as-Code - Development of Infrastructure-as-Code specific to each application that can be used to automate the delivery of configured AWS resources specific to the requirements of the application being deployed.
- Configuration Management - The development of configuration management modules specific to each application used to automate the configuration of servers including software installation and configuration.
- Service Catalog Pipeline - Development of a framework for orchestrating build, test, deployment, and validation of infrastructure automation code.
- Service Catalog - Management of Service Catalog portfolios to connect products based on selected applications.
- Assist Customer with the development of a report and supporting sample code addressing the application infrastructure code as part of the playbook.
Requirements
- 8+ years software engineering experience.
- Expert-level TypeScript and Node.js skills.
- Hands-on workflow orchestration experience.
- Strong distributed systems background including Kafka, pub/sub, retries, and idempotency.
- Kubernetes or OpenShift
- list.
Now About the role: we have the role summary sentence plus company description paragraph(s). Let's extract company description:
"The Company Vertical Relevance was founded to help business leaders drive value through the design and delivery of effective transformation programs across people, processes, and systems. Our mission is to help firms at any stage of their journey develop custom solutions for success and growth. We provide a full range of services from strategy and design through to implementation and training. Our collective industry expertise is our greatest asset - our professionals have an average of 20+ years’ experience within Financial Services, across Wealth Management, Asset Management, Insurance, and Banking. Within our Customer Experience practice, we add complementary industry expertise (technology and media) synergizing the most relevant and successful customer trends. We focus wholly on your success by first rigorously assessing your business and technology challenges, and then right-sizing solutions that provide a meaningful ROI. With our industry experts hitting the ground running and focusing on nimble, quality delivery, we can see rapid, tangible improvements with our clients in productivity and effectiveness. When it makes sense for your company, we leverage our product partnerships in the areas of CRM, Sales Acceleration, Predictive Analytics, Digital Knowledge Management, and Cloud Transformation."
We should keep that as paragraph(s) under About the role.
Now Skills: we could include Technical Environment list and Ideal Candidate Profile as a paragraph.
We must not create sections with filler. Ensure we don't include Benefits, Pay, Schedule.
Now produce HTML fragment:
- . That would preserve info.
Similarly Ideal Candidate Profile could be under Skills or maybe under Qualifications? It's more about profile; could be under Skills as a paragraph.
We need to decide structure.
Let's extract all bullet points:
Key Responsibilities:
- Design and implement enterprise workflow orchestration capabilities.
- Build durable workflows using Temporal, Dapr, AWS Step Functions, or similar technologies.
- Architect event-driven systems using Kafka and messaging technologies.
- Deploy and operate containerized applications in Kubernetes or OpenShift environments.
- Evaluate platform and infrastructure choices and provide architectural recommendations.
Required Qualifications:
- 8+ years software engineering experience.
- Expert-level TypeScript and Node.js skills.
- Hands-on workflow orchestration experience.
- Strong distributed systems background including Kafka, pub/sub, retries, and idempotency.
- Kubernetes or OpenShift experience.
- Enterprise architecture and technical leadership experience.
Preferred Qualifications:
- AI agent platforms and orchestration frameworks.
- Financial services or regulated-industry experience.
- Build-versus-buy evaluation experience.
- Platform engineering background.
Technical Environment:
- TypeScript, Node.js, Temporal, Kubernetes, OpenShift, Kafka, AWS, Containerized Microservices, Distributed Systems, AI-enabled Workflows
Ideal Candidate Profile:
- A builder, architect, and technical leader capable of defining technical direction while writing production-quality code and operating effectively in ambiguous environments.
Sample Activities: many bullet points (some seem repetitive). Let's list them:
- Creating a Self-Service Pipeline Framework
- Assist Customers in defining Customer’s Framework capabilities based on Customer’s identified business outcomes.
- Assist Customer with reviewing the Framework architecture against Customer’s identified business outcomes, to include providing general recommendations to help Customer close any observed gaps.
- Provide Customer with AWS general best practices that may help Customer refine identified deployments.
- Assist Customer with defining the first iteration of minimum viable product (MVP) for the DevOps Framework.
- Deploying Java web apps and building new Amazon Elastic Compute Cloud (Amazon EC2) instances
- Deploying Python on AWS Lambda
- Deploying Java on AWS Lambda
- Blue/green deployments on Amazon Elastic Container Service (Amazon ECS)
- Deploying to existing Amazon EC2 instances (Windows operating system)
- Provisioning dashboards to monitor deployments.
- Assist Customer in developing and implementing the first iteration of MVP in a non-production environment, under Customer’s direction and using AWS general best practices
- Assist Customer with identifying next steps and proposing activities for a future follow-on engagement.
- Creating a Self-Service Environment Framework
- Assist in selecting tools for building Infrastructure-as-Code.
- Assist Customer in the development of referenceable playbooks, supported by relevant code examples for application infrastructure code.
- Assist Customer in the development of sample runbooks to automate the implementation of application infrastructure code:
- Infrastructure-as-Code - Development of Infrastructure-as-Code specific to each application that can be used to automate the delivery of configured AWS resources specific to the requirements of the application being deployed.
- Configuration Management - The development of configuration management modules specific to each application used to automate the configuration of servers including software installation and configuration.
- Service Catalog Pipeline - Development of a framework for orchestrating build, test, deployment, and validation of infrastructure automation code.
- Service Catalog - Management of Service Catalog portfolios to connect products based on selected applications.
- Assist Customer with the development of a report and supporting sample code addressing the application infrastructure code as part of the playbook.
That's a lot. We'll include them under Responsibilities as additional bullet points (maybe under a subheading? but we can't add new headings). We'll just continue the same