JavaScript/Typescript P3 Dev
3B Staffing LLC, New York, NY, United States
This position is Hybrid in New York City, Glendale, CA, Seattle, WA, or Bristol, CT. No Remote work allowed - must work Hybrid at a Disney Hub
This is a critical project, and workers must commit to the duration of the assignment and the potential to extend it. This is working on the ESPN Flagship Project and is part of the Media Engineering Group.
Please review manager notes below. Look at the level of expectation on TypeScript. Very important.
***This is backend, not a front-end developer with extremely strong TypeScript experience, writing typescript from scratch, building/creating APIs,
familiar with REST and knows how to create REST services, the HTTP methods.
Work location: New York
INTERNAL NOTES:
Title: JavaScript/Typescript P3 Dev
Ideal Start Date: ASAP
Duration of Assignment: 8+ months
Top 3 skillsets needed: REST in Typescript, TDD, APIs
Interview Schedule/Availability: Telephone followed by zoom
Misc. Info: Must give last four SSN, Birth mm/dd and email address
Make sure to answer these questions:
Please add the candidate's Middle Initial.
IF it says above that the role has OT, please put in the OT (1.5) rate and DT (2) rates next to the regular rate.
Has this candidate been submitted by us to Disney in the past?
If so, is the attached resume new or the same one we used last submittal?
Have they interviewed for Disney in the past:
Have they worked for Disney in the past:
As a Contractor or as a FTE?
When and who was their manager?
Manager Notes:
A lot of resumes on prior similar roles came in as Front-End Engineers.
However, what their team is doing are very API-driven TypeScript-driven projects.
Looking for someone with STRONG TypeScript knowledge, and familiarity with API development, not front-end, as the majority of the work they are doing is very API-driven.
They are a TypeScript team, and they are a Sr TypeScript team, so the expectation is anyone coming in, even at the P2 level, would understand TypeScript, not just JavaScript, but understand what makes TypeScript different, and how to use the power of what TypeScript brings in.
The manager said a lot of people say they know TypeScript because it's a subset of JavaScript, but they just know JavaScript. So a lot of resumes he looked at had listed a lot of TypeScript, but when he looked at the ones that had public repos, when he would click to go look for TypeScript project examples, they either would have a starter version that they pulled from some class or something like that, or they forged some code. He didn't get a sense that any of the candidates actually had strong TypeScript experience by example.
In the resumes he reviewed, they showed this TypeScript experience, but they didn't show up in any of their public repos.
While a Front-End Engineer or a FS Engineer would be valuable for some of the stuff in the future, the majority of the work is someone who knows how to create APIs. Not that they integrated APIs, but know how to build APIs, since their team is on the side that is creating the APIs for integration. So the expectation is that they are familiar with REST and know how to create REST services, the HTTP methods.
It would be a bonus to have the HLS for these roles. If a candidate has both, it will probably shoot them to the top of the list, but this one he's looking for someone with tech savviness, .and problem-solving capabilities that would come with an engineering role, more than a Playlist specialist.
At the end of the day, he's looking for a strong problem solver.
Candidates for these two roles, don't have to be from big name companies, as long as they have some skills that are better, although candidates from enterprise companies would more likely have these types of skills.
Candidates should have Unit Testing experience, should be standard, and that's more of a skillset that can be taught.
The mocking is less standard, but very valuable. So, if they have familiarity with it, and created a Mock, or understands what it takes to Mock data, that would definitely be a highlight. He also mentioned that if we get the sense that the candidate is a lean in problem solver, that Trumps everything. He can teach someone how to write unit tests. It's a lot harder to teach someone how to be a problem solver, where they're hungry to jump in. His team is like that. They have a lot of internal stakeholders, and the people that really stand out are the folks that don't need him to tell them every step of the way. They can solve problems on their own and come back and have the personal skills to be able to communicate their ideas. Problem Solver Mentality.
He has some visuals which he would share with candidates on the interview, and will ask them how they will solve it, trying to get a sense of how they think and how they can pivot. Technically, they would not need to know anything about what he's talking about, if you're a problem solver, they should be able to add their take on it. This gives the manager a sense of candidate's ability to problem solve.
Day to Day: If for example there is a bottleneck somewhere. This team should be involved to solve it. Let's work as a team to figure out a solution. And then he would tell his team, "Take this now, and I want you to be able to expand on it." An example: So, the day to day would be "I'm problem solving with the idea." "I'm communicating with my team." And someone who feels comfortable be able to speak up and provide their ideas. And then they would take it, and either execute against that in an API or Prototype. By execution, he means they are running a TypeScript API, and either expanding on it, adding new endpoints, perhaps mock a new service because they need it to test scenario X. They should feel comfortable to talk to stakeholders, and then they execute against that by expanding upon the API.
More specifically: Right now, their gateway is a single service API, so they would be pulling against that. It's all TypeScript, so they would be writing TypeScript, so the expectation is that they are writing TRUE TYPESCRIPT in this project, and it's not JavaScript with some "sugar" on top, and are expanding upon the code base that way. And then they would most likely send the PR, which most likely would be reviewed by Leandro or another Sr team member. They have daily syncs where they problem solve together and talk about future things.
While you might be working on Project A which is needed right now, you might also be supporting the person on the HLS playback side with some technical things. So, they are juggling some tasks on their sprint, which is writing code in TypeScript for this application, and then at the same time having the ability to juggle about future objectives and think about it, as problem solving is very valuable to the team. Candidates may sit on any Disney Hub and should be local to a Disney Hub. Work is hybrid, so candidates must live near a hub.
EXTERNAL JOB DESCRIPTION:
The Early Playback Enablement team mission is to enable media player engineers and QA partners to validate video and audio playback across our player stack by creating and managing test-streams, mocking relevant services, and removing related impediments. We help support new platforms, accelerate the development of our in-house media player, and improve playback quality across the Disney media ecosystem.
Our team is seeking someone to help us further support media playback across brands and to expand our capabilities to serve video and audio test content.
Your primary initiative will be to ensure our deliverables help provide a foundation for media playback innovation.
You are an opinionated optimist who always leaves the code that you are working on better than you found it. You foster trust, approach problems with empathy and respect, and embrace creativity. You see yourself as a partner who excels in problem solving, puts users first, and cares deeply about quality.
Responsibilities:
• Develop and maintain an internal REST service written in Typescript
• Design systems and procedures to best expand and scale our services
• Automate processes around our deliverables
• Use Test Driven Development practices and functional paradigms
• Determine creative ways to surface test content and mock services across our ecosystem
• Deliver test content to unblock our partners and/or expose new media features
• Own the end-to-end fulfillment of test content requests
• Support partner needs as they pertain to media playback
• Share ownership of our playback support channels and threads
• Create documentation around test content and relevant services
• Understand the intricacies of playback across our brands
• Track and execute against product and project requirements
• Maintain of our test-stream and mock-service catalogs
Basic Qualifications:
• 5+ years' experience in JavaScript
• 3+ years' experience with advanced TypeScript (Please see manager notes as to the level of experience required)
• 2+ years' experience leading a project
• 2+ years' experience working in a cross-functional capacity
• 2+ years' experience building APIs
• Experience mocking data and services
• Experience writing unit tests
• Experience with authentication, authorization, and access management
• Experience manipulating/proxying data to augment application state
• Experience managing collections/catalogs
• Understanding of agile methodologies and git source control
Preferred Qualifications:
• 2+ years' experience working with functional paradigms
• 5+ years' experience leading a project
• 5+ years' experience working in a cross-functional capacity
• Experience with AWS
• Experience with SQL
• Interest in the HLS video space
Required Education Bachelor's Degree or work exp
This is a critical project, and workers must commit to the duration of the assignment and the potential to extend it. This is working on the ESPN Flagship Project and is part of the Media Engineering Group.
Please review manager notes below. Look at the level of expectation on TypeScript. Very important.
***This is backend, not a front-end developer with extremely strong TypeScript experience, writing typescript from scratch, building/creating APIs,
familiar with REST and knows how to create REST services, the HTTP methods.
Work location: New York
INTERNAL NOTES:
Title: JavaScript/Typescript P3 Dev
Ideal Start Date: ASAP
Duration of Assignment: 8+ months
Top 3 skillsets needed: REST in Typescript, TDD, APIs
Interview Schedule/Availability: Telephone followed by zoom
Misc. Info: Must give last four SSN, Birth mm/dd and email address
Make sure to answer these questions:
Please add the candidate's Middle Initial.
IF it says above that the role has OT, please put in the OT (1.5) rate and DT (2) rates next to the regular rate.
Has this candidate been submitted by us to Disney in the past?
If so, is the attached resume new or the same one we used last submittal?
Have they interviewed for Disney in the past:
Have they worked for Disney in the past:
As a Contractor or as a FTE?
When and who was their manager?
Manager Notes:
A lot of resumes on prior similar roles came in as Front-End Engineers.
However, what their team is doing are very API-driven TypeScript-driven projects.
Looking for someone with STRONG TypeScript knowledge, and familiarity with API development, not front-end, as the majority of the work they are doing is very API-driven.
They are a TypeScript team, and they are a Sr TypeScript team, so the expectation is anyone coming in, even at the P2 level, would understand TypeScript, not just JavaScript, but understand what makes TypeScript different, and how to use the power of what TypeScript brings in.
The manager said a lot of people say they know TypeScript because it's a subset of JavaScript, but they just know JavaScript. So a lot of resumes he looked at had listed a lot of TypeScript, but when he looked at the ones that had public repos, when he would click to go look for TypeScript project examples, they either would have a starter version that they pulled from some class or something like that, or they forged some code. He didn't get a sense that any of the candidates actually had strong TypeScript experience by example.
In the resumes he reviewed, they showed this TypeScript experience, but they didn't show up in any of their public repos.
While a Front-End Engineer or a FS Engineer would be valuable for some of the stuff in the future, the majority of the work is someone who knows how to create APIs. Not that they integrated APIs, but know how to build APIs, since their team is on the side that is creating the APIs for integration. So the expectation is that they are familiar with REST and know how to create REST services, the HTTP methods.
It would be a bonus to have the HLS for these roles. If a candidate has both, it will probably shoot them to the top of the list, but this one he's looking for someone with tech savviness, .and problem-solving capabilities that would come with an engineering role, more than a Playlist specialist.
At the end of the day, he's looking for a strong problem solver.
Candidates for these two roles, don't have to be from big name companies, as long as they have some skills that are better, although candidates from enterprise companies would more likely have these types of skills.
Candidates should have Unit Testing experience, should be standard, and that's more of a skillset that can be taught.
The mocking is less standard, but very valuable. So, if they have familiarity with it, and created a Mock, or understands what it takes to Mock data, that would definitely be a highlight. He also mentioned that if we get the sense that the candidate is a lean in problem solver, that Trumps everything. He can teach someone how to write unit tests. It's a lot harder to teach someone how to be a problem solver, where they're hungry to jump in. His team is like that. They have a lot of internal stakeholders, and the people that really stand out are the folks that don't need him to tell them every step of the way. They can solve problems on their own and come back and have the personal skills to be able to communicate their ideas. Problem Solver Mentality.
He has some visuals which he would share with candidates on the interview, and will ask them how they will solve it, trying to get a sense of how they think and how they can pivot. Technically, they would not need to know anything about what he's talking about, if you're a problem solver, they should be able to add their take on it. This gives the manager a sense of candidate's ability to problem solve.
Day to Day: If for example there is a bottleneck somewhere. This team should be involved to solve it. Let's work as a team to figure out a solution. And then he would tell his team, "Take this now, and I want you to be able to expand on it." An example: So, the day to day would be "I'm problem solving with the idea." "I'm communicating with my team." And someone who feels comfortable be able to speak up and provide their ideas. And then they would take it, and either execute against that in an API or Prototype. By execution, he means they are running a TypeScript API, and either expanding on it, adding new endpoints, perhaps mock a new service because they need it to test scenario X. They should feel comfortable to talk to stakeholders, and then they execute against that by expanding upon the API.
More specifically: Right now, their gateway is a single service API, so they would be pulling against that. It's all TypeScript, so they would be writing TypeScript, so the expectation is that they are writing TRUE TYPESCRIPT in this project, and it's not JavaScript with some "sugar" on top, and are expanding upon the code base that way. And then they would most likely send the PR, which most likely would be reviewed by Leandro or another Sr team member. They have daily syncs where they problem solve together and talk about future things.
While you might be working on Project A which is needed right now, you might also be supporting the person on the HLS playback side with some technical things. So, they are juggling some tasks on their sprint, which is writing code in TypeScript for this application, and then at the same time having the ability to juggle about future objectives and think about it, as problem solving is very valuable to the team. Candidates may sit on any Disney Hub and should be local to a Disney Hub. Work is hybrid, so candidates must live near a hub.
EXTERNAL JOB DESCRIPTION:
The Early Playback Enablement team mission is to enable media player engineers and QA partners to validate video and audio playback across our player stack by creating and managing test-streams, mocking relevant services, and removing related impediments. We help support new platforms, accelerate the development of our in-house media player, and improve playback quality across the Disney media ecosystem.
Our team is seeking someone to help us further support media playback across brands and to expand our capabilities to serve video and audio test content.
Your primary initiative will be to ensure our deliverables help provide a foundation for media playback innovation.
You are an opinionated optimist who always leaves the code that you are working on better than you found it. You foster trust, approach problems with empathy and respect, and embrace creativity. You see yourself as a partner who excels in problem solving, puts users first, and cares deeply about quality.
Responsibilities:
• Develop and maintain an internal REST service written in Typescript
• Design systems and procedures to best expand and scale our services
• Automate processes around our deliverables
• Use Test Driven Development practices and functional paradigms
• Determine creative ways to surface test content and mock services across our ecosystem
• Deliver test content to unblock our partners and/or expose new media features
• Own the end-to-end fulfillment of test content requests
• Support partner needs as they pertain to media playback
• Share ownership of our playback support channels and threads
• Create documentation around test content and relevant services
• Understand the intricacies of playback across our brands
• Track and execute against product and project requirements
• Maintain of our test-stream and mock-service catalogs
Basic Qualifications:
• 5+ years' experience in JavaScript
• 3+ years' experience with advanced TypeScript (Please see manager notes as to the level of experience required)
• 2+ years' experience leading a project
• 2+ years' experience working in a cross-functional capacity
• 2+ years' experience building APIs
• Experience mocking data and services
• Experience writing unit tests
• Experience with authentication, authorization, and access management
• Experience manipulating/proxying data to augment application state
• Experience managing collections/catalogs
• Understanding of agile methodologies and git source control
Preferred Qualifications:
• 2+ years' experience working with functional paradigms
• 5+ years' experience leading a project
• 5+ years' experience working in a cross-functional capacity
• Experience with AWS
• Experience with SQL
• Interest in the HLS video space
Required Education Bachelor's Degree or work exp