

Developer
β - Featured Role | Apply direct with Data Freelance Hub
This role includes multiple hybrid openings in Jersey City, NJ: Mulesoft Developer (with Informatica experience), Fullstack .Net Developer (10+ years in finance, strong Angular, Agile), and Release Manager/Market Risk (financial services knowledge, release management methodologies). Pay rate and contract length unspecified.
π - Country
United States
π± - Currency
$ USD
-
π° - Day rate
-
ποΈ - Date discovered
June 3, 2025
π - Project duration
Unknown
-
ποΈ - Location type
Hybrid
-
π - Contract type
W2 Contractor
-
π - Security clearance
Unknown
-
π - Location detailed
Jersey City, NJ
-
π§ - Skills detailed
#Jira #Oracle #SQL Server #Strategy #Stories #JavaScript #Informatica #Base #Project Management #BI (Business Intelligence) #.Net #Containers #Angular #Scrum #SQL (Structured Query Language) #Agile #GIT #Deployment #Compliance #Jenkins #Ansible #Scala
Role description
MULTIPLE HYBRID JOBS OPENINGS IN JERSEY CITY, NJ - ONLY W2
1. Mulesoft Developer with some Informatica
1. Fullstack .Net Developer
1. Release Manager/Market Risk
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’ Mulesoft Developer with some Informatica
Would like to get someone who has actively worked on both those technologies, While the work on informatica is not too extensive post August, would like them to be able to support the team till August when they transition to Mulesoft.
Experience with Mulesoft development
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’ Fullstack .Net Developer
Requirements:
β’ Senior Full Stack Developer with at least 10 years of experience with prior exposure to working in the financial sector
β’ Strong communications and delivery skills
β’ Working knowledge of GIT or any similar source code repositories
β’ Working knowledge of Continuous build and deployment strategy using Jenkins and Ansible
β’ Experience with Agile and scrum
β’ Strong experience with Angular framework
β’ Experience with all or some of the following technologies: JavaScript, Relational DBs (Oracle/SQL Server), ASP MVC, Net Core, WCF
β’ Experience building distributed and scalable complex services as well as robust micro services
β’ Experience with Multi-threading, low latency, high performance components & applications (including GC tuning)
β’ Good grasp of modern web application development approaches
β’ Experience in maintaining a focus on testing and acceptance, particularly with respect to regulatory and compliance requirements
β’ Experience in breaking down larger problems and detail user stories
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’ Release Manager/Market Risk
Day-to-Day Responsibilities
Application Access:
β’ ITSM Remedy (CRQs)-- Technical change requests (CRQs) are the official record of a technical change being released to the production environment.
β’ Horizon (JIRA)- an issue tracking software--Technology teams use Horizon Jira to capture all work (Base and Initiative)
β’ Release Manager - Captures key information and evidence from Horizon JIRA, ITSM Remedy and PPRT (when applicable) to create a change release.
β’ Agile-- robust and highly customizable project management tool (rollout pending).
Creation of a Release
β’ Run a weekly release call, attended by Dev, QA and Delivery Management to gather all pertinent information to create a CRQ.
β’ Review EPICs (resides within JIRA and contains the Design Details, Acceptance Criteria and Release Notes for a body of work) to ensure it represents a logical summation of the work being released.
β’ ERFT QA is a group outside of MRT but within BAC that reviews our deployments. Any part of a release that will not pass an audit will be flagged as βfailedβ. Itβs the responsibility of release management to work with dev to fix /edit the fails.
β’ Obtain Dev Lead approval known as OTA for all components prior to release.
β’ After release, responsible for Closing CRQs/JIRAs and Release Containers as well as uploading supporting docs for audit.
β’ Follow up on any post release issues. This includes creation and tracking of PIRs (Post Implementation Review) and PKEs (Problem Known Error).
β’ Off Cycle Release---unscheduled releases that follow the above steps
β’ Attend bi-weekly MRT office hours to stay abreast of latest changes to the release process.
β’ Be available to process Latent and/or Emergency releases.
Required Qualifications:
β’ Business Acumen--Understanding of the financial services industry and the impact of technology on business operations.
β’ Strong written and oral communication skills, presentation to senior leaders
β’ Collaborates; builds relationships across workgroups to deliver consistent quality results
β’ Highly organized with strong project/time management skills
β’ Ability to balance priorities and to work independently with minimal supervision.
β’ Ability to think critically and offer solutions when roadblocks arise
β’ Familiarity with release management methodologies, such as Agile, Horizon (JIRA) or similar frameworks.
Interpersonal Skills:
β’ The ability to build relationships, coach, and mentor others is crucial for supporting employees through change.
β’ Supporting project teams in managing the implementation of changes, ensuring they stay on track and meet deadlines.
β’ Identifies upstream and downstream impacts associated with project related changes and/or decisions.
MULTIPLE HYBRID JOBS OPENINGS IN JERSEY CITY, NJ - ONLY W2
1. Mulesoft Developer with some Informatica
1. Fullstack .Net Developer
1. Release Manager/Market Risk
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’ Mulesoft Developer with some Informatica
Would like to get someone who has actively worked on both those technologies, While the work on informatica is not too extensive post August, would like them to be able to support the team till August when they transition to Mulesoft.
Experience with Mulesoft development
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’ Fullstack .Net Developer
Requirements:
β’ Senior Full Stack Developer with at least 10 years of experience with prior exposure to working in the financial sector
β’ Strong communications and delivery skills
β’ Working knowledge of GIT or any similar source code repositories
β’ Working knowledge of Continuous build and deployment strategy using Jenkins and Ansible
β’ Experience with Agile and scrum
β’ Strong experience with Angular framework
β’ Experience with all or some of the following technologies: JavaScript, Relational DBs (Oracle/SQL Server), ASP MVC, Net Core, WCF
β’ Experience building distributed and scalable complex services as well as robust micro services
β’ Experience with Multi-threading, low latency, high performance components & applications (including GC tuning)
β’ Good grasp of modern web application development approaches
β’ Experience in maintaining a focus on testing and acceptance, particularly with respect to regulatory and compliance requirements
β’ Experience in breaking down larger problems and detail user stories
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’
β’ Release Manager/Market Risk
Day-to-Day Responsibilities
Application Access:
β’ ITSM Remedy (CRQs)-- Technical change requests (CRQs) are the official record of a technical change being released to the production environment.
β’ Horizon (JIRA)- an issue tracking software--Technology teams use Horizon Jira to capture all work (Base and Initiative)
β’ Release Manager - Captures key information and evidence from Horizon JIRA, ITSM Remedy and PPRT (when applicable) to create a change release.
β’ Agile-- robust and highly customizable project management tool (rollout pending).
Creation of a Release
β’ Run a weekly release call, attended by Dev, QA and Delivery Management to gather all pertinent information to create a CRQ.
β’ Review EPICs (resides within JIRA and contains the Design Details, Acceptance Criteria and Release Notes for a body of work) to ensure it represents a logical summation of the work being released.
β’ ERFT QA is a group outside of MRT but within BAC that reviews our deployments. Any part of a release that will not pass an audit will be flagged as βfailedβ. Itβs the responsibility of release management to work with dev to fix /edit the fails.
β’ Obtain Dev Lead approval known as OTA for all components prior to release.
β’ After release, responsible for Closing CRQs/JIRAs and Release Containers as well as uploading supporting docs for audit.
β’ Follow up on any post release issues. This includes creation and tracking of PIRs (Post Implementation Review) and PKEs (Problem Known Error).
β’ Off Cycle Release---unscheduled releases that follow the above steps
β’ Attend bi-weekly MRT office hours to stay abreast of latest changes to the release process.
β’ Be available to process Latent and/or Emergency releases.
Required Qualifications:
β’ Business Acumen--Understanding of the financial services industry and the impact of technology on business operations.
β’ Strong written and oral communication skills, presentation to senior leaders
β’ Collaborates; builds relationships across workgroups to deliver consistent quality results
β’ Highly organized with strong project/time management skills
β’ Ability to balance priorities and to work independently with minimal supervision.
β’ Ability to think critically and offer solutions when roadblocks arise
β’ Familiarity with release management methodologies, such as Agile, Horizon (JIRA) or similar frameworks.
Interpersonal Skills:
β’ The ability to build relationships, coach, and mentor others is crucial for supporting employees through change.
β’ Supporting project teams in managing the implementation of changes, ensuring they stay on track and meet deadlines.
β’ Identifies upstream and downstream impacts associated with project related changes and/or decisions.