Senior Software Development Engineer, Audible Fintech
Audible · Newark, NJ · 3 wk ago
ConsultingFull-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.
We need to parse the description.
First, we have description: "At Audible, we believe stories have the power to transform lives..." That's prose.
Then "About This Role" heading: we need for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map headings accordingly.
We need to extract content under each heading.
Let's parse the posting:
- "Description At Audible, we believe stories have the power to transform lives. It’s why we work with some of the world’s leading creators to produce and share audio storytelling with our millions of global listeners. We are dreamers and inventors who come from a wide range of backgrounds and experiences to empower and inspire each other. Imagine your future with us."
That's likely a general description; could be placed under "About the role"? Actually "About This Role" follows after that. So maybe the first paragraph is generic company description; could be part of "About the role"? But we need to follow the instruction: Use
About the role
(they said use for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map headings accordingly.
We need to extract content under each heading.
Let's parse the posting:
- "Description At Audible, we believe stories have the power to transform lives. It’s why we work with some of the world’s leading creators to produce and share audio storytelling with our millions of global listeners. We are dreamers and inventors who come from a wide range of backgrounds and experiences to empower and inspire each other. Imagine your future with us."
That's likely a general description; could be placed under "About the role"? Actually "About This Role" follows after that. So maybe the first paragraph is generic company description; could be part of "About the role"? But we need to follow the instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections exist.
Let's see sections present:
- About This Role: content: "As a Senior Software Development Engineer, it’s up to you to define, design and refine the tech that keeps us one step ahead of listeners. Anticipate. Innovate. Bring challenging ideas and we’ll support you with the latest tech, tools and systems that you need to succeed. You’ll drive the team forward, guiding them over every obstacle and leading the way to develop exciting, original and effective solutions. Leading the way, you’ll bring our team together to build and maintain our platform to bring thousands of stories to millions of listeners and unleash the power of the human voice."
- About The Team: content: "The Audible Fintech (PaymenTech) team owns the systems that power royalty payments, recoupable advances, and financial reporting across all of Audible's marketplaces. We build and operate the full payment pipeline — from ingesting royalty transactions, to orchestrating disbursements, to creating vendor invoices and payments in Workday — giving us end-to-end accountability for every dollar Audible pays its content partners. We are migrating Audible's financial systems onto Amazon's Digital Acceleration (DA) platform, unifying contract management, royalty payments, advances, and reporting into a single, scalable, and auditable ecosystem. We are building next-generation, no-touch payment and accounting systems with compliance and auditability built in by default, so Audible's finance teams can focus on driving the business forward rather than managing operational friction."
- About You: content: "You’re in your element when you’re being challenged, and you’re always eager to share your ideas, take on responsibility and keep developing at an exciting pace. We look for people who show initiative, set their standards high and see every failure as an opportunity to learn. You’re looking for an environment where you can thrive and help your team reach their potential. With opportunities to challenge yourself and lead a talented team to success, you’ll find what you’re looking for at Audible. As a Senior Software Development Engineer, you will... [list]"
Then after that: bullet list of responsibilities? Actually "As a Senior Software Development Engineer, you will..." then a list of items:
- Design, develop, and test software components and applications for a leading global provider of audiobooks
- Collaborate on an agile engineering team, writing scalable and maintainable code and influencing team decisions
- Collaborate with stakeholders to envision, design, develop, test, and launch customer-centric software solutions
- Utilize technology to tackle challenging problems and deliver high-quality code on schedule
- Demonstrate proficiency in a wide range of data structures and algorithms, applying them effectively
- Independently clarify technical requirements, assess development estimates, and employ diverse design approaches
- Conduct code reviews and provide constructive feedback to team members
- Foster continuous improvement in software quality, customer experience, and product maintainability
- Mentor and lead developers, fostering curiosity and deep technical understanding
These are responsibilities/duties.
Then "About Audible": description of company.
Then "Basic Qualifications": list:
- Experience with AWS technologies
- Bachelor's degree or above in Computer Science
- 3+ years’ experience of software development and deployment of distributed multi-tier applications
Then "Preferred Qualifications": list:
- Experience delivering large, cross-functional, customer facing products
- Experience taking a leading role in building complex software or computing infrastructure that has been successfully delivered to customers
- Strong problem-solving skills with the ability to navigate complex and ambiguous situations
- Full stack proficiency (e.g., Java, NoSQL, HTML5, CSS3, JavaScript, node.js, React)
- Competency at delegating work in parallel to accelerate delivery
- Enthusiasm for promoting high-quality standard in others across: documentation, unit testing, code reviews, test automation, continuous integration and deployment
Then "Amazon is an equal opportunity employer..." (EEO boilerplate) to be removed.
Then "If you have a disability..." (accommodation) to be removed.
Then "If the country/region you’re applying in isn’t listed, please contact your Recruiting Partner." (application instruction) to be removed.
Then "The base salary range for this position is listed below. Your Amazon package will include sign-on payments and restricted stock units (RSUs). Final compensation will be determined based on factors including experience, qualifications, and location. Amazon also offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave. Learn more about our benefits at https://amazon.jobs/en/benefits."
Then location: "USA, NJ, Newark - 158,100.00 - 213,800.00 USD annually"
Then "Company - Audible, Inc. - B13 Job ID: A10535237"
We need to include Pay and Benefits sections if they have specific content. Pay: we have salary range: 158,100 - 213,800 USD annually. Also mention sign-on payments and RSUs. That's specific enough. Benefits: they list health insurance etc. That's specific. So we should include Benefits and Pay sections.
Schedule: not mentioned. So omit Schedule.
Now we need to map sections:
- About the role: combine the initial description? Actually "About This Role" is a section. We'll put that content under About the role
. Also maybe include the initial paragraph? The initial paragraph is more about Audible mission; could be part of "About Audible" but we don't have that as a section heading (we could include under "About the role" or maybe we could create a separate "About Audible" but not in allowed headings. The instruction says use those headings; we can also include other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings.
Thus:
- About the role: include the "About This Role" paragraph(s). Possibly also the initial description? But that is more about Audible mission; could be considered part of "About the role"? Might be okay.
- Responsibilities: the list after "As a Senior Software Development Engineer, you will..."
- Requirements: maybe Basic Qualifications? Or Requirements could be Basic Qualifications. Usually "Requirements" = basic qualifications. We'll put Basic Qualifications under Requirements.
- Qualifications: Preferred Qualifications.
- Skills: maybe we can extract from Preferred Qualifications like full stack proficiency etc. But we already have Qualifications; maybe Skills separate? Could combine. But we need to avoid thin sections. We could put Skills as a subsection under Qualifications? But instruction: Use - for any list of duties/requirements/benefits, and
for prose. So we can have multiple sections.
We have:
- About the role (prose)
- Responsibilities (list)
- Requirements (list) = Basic Qualifications
- Qualifications (list) = Preferred Qualifications
- Skills (maybe we could list specific skills like AWS, Java, etc.) but we already have those in qualifications. Could create Skills section from the list of technologies: "Experience with AWS technologies", "Full stack proficiency (e.g., Java, NoSQL, HTML5, CSS3, JavaScript, node.js, React)". But that's duplication.
Better to follow typical job posting: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Skills maybe not needed if covered.
But we need to decide: The instruction says "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. So we can combine Skills into Qualifications or Requirements.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if we have content for each:
- About the role: we have the initial description + About This Role paragraph. We'll combine into prose.
- Responsibilities: the bullet list.
- Requirements: Basic Qualifications list.
- Qualifications: Preferred Qualifications list.
- Benefits: the benefits description (health insurance, 401k matching, PTO, parental leave). Also mention learning more link? We can keep prose.
- Pay: salary range and sign-on payments/RSUs.
We must not include boilerplate like EEO, accommodation, application instructions, Job ID, etc.
We must not repeat job title as heading.
We must not include navigation etc.
Now produce HTML fragment.
Structure:
About the role
...combined prose...
Responsibilities
- ...
...
Requirements
- Experience with AWS technologies
- Bachelor's degree or above in Computer Science
- 3+ years’ experience of software development and deployment of distributed multi-tier applications
Qualifications
- Experience delivering large, cross-functional, customer facing products
- Experience taking a leading role in building complex software or computing infrastructure that has been successfully delivered to customers
- Strong problem-solving skills with the ability to navigate complex and ambiguous situations
- Full stack proficiency (e.g., Java, NoSQL, HTML5, CSS3, JavaScript, node.js, React)
- Competency at delegating work in parallel to accelerate delivery
- Enthusiasm for promoting high-quality standard in others across: documentation, unit testing, code reviews, test automation, continuous integration and deployment
Benefits
Amazon offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave.
Pay
The base salary range for this position is $158,100.00 - $
About the role
. Also maybe include the initial paragraph? The initial paragraph is more about Audible mission; could be part of "About Audible" but we don't have that as a section heading (we could include under "About the role" or maybe we could create a separate "About Audible" but not in allowed headings. The instruction says use those headings; we can also include other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should map content to those headings.
Thus:
- About the role: include the "About This Role" paragraph(s). Possibly also the initial description? But that is more about Audible mission; could be considered part of "About the role"? Might be okay.
- Responsibilities: the list after "As a Senior Software Development Engineer, you will..."
- Requirements: maybe Basic Qualifications? Or Requirements could be Basic Qualifications. Usually "Requirements" = basic qualifications. We'll put Basic Qualifications under Requirements.
- Qualifications: Preferred Qualifications.
- Skills: maybe we can extract from Preferred Qualifications like full stack proficiency etc. But we already have Qualifications; maybe Skills separate? Could combine. But we need to avoid thin sections. We could put Skills as a subsection under Qualifications? But instruction: Use - for any list of duties/requirements/benefits, and
for prose. So we can have multiple sections.
We have:
- About the role (prose)
- Responsibilities (list)
- Requirements (list) = Basic Qualifications
- Qualifications (list) = Preferred Qualifications
- Skills (maybe we could list specific skills like AWS, Java, etc.) but we already have those in qualifications. Could create Skills section from the list of technologies: "Experience with AWS technologies", "Full stack proficiency (e.g., Java, NoSQL, HTML5, CSS3, JavaScript, node.js, React)". But that's duplication.
Better to follow typical job posting: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Skills maybe not needed if covered.
But we need to decide: The instruction says "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. So we can combine Skills into Qualifications or Requirements.
Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check if we have content for each:
- About the role: we have the initial description + About This Role paragraph. We'll combine into prose.
- Responsibilities: the bullet list.
- Requirements: Basic Qualifications list.
- Qualifications: Preferred Qualifications list.
- Benefits: the benefits description (health insurance, 401k matching, PTO, parental leave). Also mention learning more link? We can keep prose.
- Pay: salary range and sign-on payments/RSUs.
We must not include boilerplate like EEO, accommodation, application instructions, Job ID, etc.
We must not repeat job title as heading.
We must not include navigation etc.
Now produce HTML fragment.
Structure:
About the role
...combined prose...
Responsibilities
- ...
...
Requirements
- Experience with AWS technologies
- Bachelor's degree or above in Computer Science
- 3+ years’ experience of software development and deployment of distributed multi-tier applications
Qualifications
- Experience delivering large, cross-functional, customer facing products
- Experience taking a leading role in building complex software or computing infrastructure that has been successfully delivered to customers
- Strong problem-solving skills with the ability to navigate complex and ambiguous situations
- Full stack proficiency (e.g., Java, NoSQL, HTML5, CSS3, JavaScript, node.js, React)
- Competency at delegating work in parallel to accelerate delivery
- Enthusiasm for promoting high-quality standard in others across: documentation, unit testing, code reviews, test automation, continuous integration and deployment
Benefits
Amazon offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave.
Pay
The base salary range for this position is $158,100.00 - $
- for any list of duties/requirements/benefits, and
for prose. So we can have multiple sections. We have: - About the role (prose) - Responsibilities (list) - Requirements (list) = Basic Qualifications - Qualifications (list) = Preferred Qualifications - Skills (maybe we could list specific skills like AWS, Java, etc.) but we already have those in qualifications. Could create Skills section from the list of technologies: "Experience with AWS technologies", "Full stack proficiency (e.g., Java, NoSQL, HTML5, CSS3, JavaScript, node.js, React)". But that's duplication. Better to follow typical job posting: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Skills maybe not needed if covered. But we need to decide: The instruction says "Prefer a few substantive sections over many thin ones." So we should avoid creating many thin sections. So we can combine Skills into Qualifications or Requirements. Thus we will have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check if we have content for each: - About the role: we have the initial description + About This Role paragraph. We'll combine into prose. - Responsibilities: the bullet list. - Requirements: Basic Qualifications list. - Qualifications: Preferred Qualifications list. - Benefits: the benefits description (health insurance, 401k matching, PTO, parental leave). Also mention learning more link? We can keep prose. - Pay: salary range and sign-on payments/RSUs. We must not include boilerplate like EEO, accommodation, application instructions, Job ID, etc. We must not repeat job title as heading. We must not include navigation etc. Now produce HTML fragment. Structure:
About the role
...combined prose...
Responsibilities
- ... ...
Requirements
- Experience with AWS technologies
- Bachelor's degree or above in Computer Science
- 3+ years’ experience of software development and deployment of distributed multi-tier applications
Qualifications
- Experience delivering large, cross-functional, customer facing products
- Experience taking a leading role in building complex software or computing infrastructure that has been successfully delivered to customers
- Strong problem-solving skills with the ability to navigate complex and ambiguous situations
- Full stack proficiency (e.g., Java, NoSQL, HTML5, CSS3, JavaScript, node.js, React)
- Competency at delegating work in parallel to accelerate delivery
- Enthusiasm for promoting high-quality standard in others across: documentation, unit testing, code reviews, test automation, continuous integration and deployment
Benefits
Amazon offers comprehensive benefits including health insurance (medical, dental, vision, prescription, Basic Life & AD&D insurance and option for Supplemental life plans, EAP, Mental Health Support, Medical Advice Line, Flexible Spending Accounts, Adoption and Surrogacy Reimbursement coverage), 401(k) matching, paid time off, and parental leave.
Pay
The base salary range for this position is $158,100.00 - $