Software Development Engineer, FinTech/Customer Service Tech
or drop it. So we could include company name maybe as a short paragraph? It's minor metadata; we could drop it or include in a p. Probably drop it as not essential. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Company name maybe substantive? It's not essential to role but could be considered metadata. I'd include it as a short p maybe under a generic "About the company"? But we have About Audible section already. So we can drop the duplicate. We need sections: About the role (maybe combine About This Role and About The Team and About You? Actually we have headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content: - About the role: could be the "About This Role" paragraph. - Responsibilities: the bullet list under "As a Software Development Engineer, you will..." - Requirements: maybe Basic Qualifications? Or "About You" (the candidate description) could be considered Requirements? But we have separate Requirements and Qualifications sections. Usually Requirements = basic qualifications, Qualifications = preferred qualifications. Skills maybe derived from bullet points? But we already have responsibilities. Could also put skills from preferred qualifications? However we need to avoid thin sections. Let's decide: - About the role: combine About This Role, About The Team, About You? But About You is more about candidate traits; could go under Requirements or Qualifications. Better: Use sections as they appear in posting: About This Role (-> About the role), About The Team (maybe part of About the role or separate? Not a heading we have). About You (-> Responsibilities? Actually About You includes description of candidate and then bullet list of responsibilities). Could split: About You paragraph as Requirements? Hmm. We need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we must map content to these headings. Let's decide: - About the role: include "About This Role" and "About The Team" (both describe role and team). Could combine. - Responsibilities: the bullet list of duties. - Requirements: Basic Qualifications (1+ years experience, programming language). - Qualifications: Preferred Qualifications list. - Skills: maybe we could extract skills from responsibilities or preferred qualifications? But we already have qualifications. Could skip Skills if no specific content beyond what's already covered. However we might include skills like "data structures and algorithms", "agile methodologies", "code reviews", etc. But those are already in qualifications. To avoid thin sections, maybe omit Skills if not distinct. - Benefits: from the paragraph about comprehensive benefits. - Pay: salary range. - Schedule: not mentioned; we should not include Schedule section if no specific content. Thus we will output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We must not include empty sections. Now format: Use
for each heading. Then content: For prose use
. For lists use
- .
We need to preserve all substantive information; do not invent or summarize away detail.
Let's craft:
About the role
As a 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. We pride ourselves on our ability to imagine and invent solutions to problems of the future. You’ll be essential in this forward-thinking approach to development. Together with the team, you’ll build and maintain our platform to bring thousands of stories to millions of listeners and unleash the power of the human voice.
We build the tools, AI agents, and platforms that power how Audible serves every person who interacts with us — listeners, creators, agents, and internal stakeholders alike. On the FinTech side, we build the workflows that publish content, support content providers, and deliver essential information to legal and financial stakeholders. On the Customer Service Technology side, we build the AI-powered self-service experiences, agent consoles, help centers, and policy-enforcement systems that let listeners resolve issues in a single conversation and give creators a unified support model. Across both teams, the mission is the same: guarantee the right result reaches the right person, on the right surface, every time.
That covers About This Role and About The Team. Now Responsibilities:Responsibilities
- 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
Requirements
- 1+ years of non-internship professional software development experience
- Experience programming with at least one software programming language
Qualifications
- Experience in designing and developing large-scale services
- Experience building complex software systems that have been successfully delivered to customers
- Knowledge of software engineering best practices across the development life cycle, including agile methodologies, coding standards, code reviews, source management, build processes, testing, and operations
- Experience handling ambiguous or undefined challenges through strong problem solving abilities
- Experience working in a collaborative team environment to deliver high-quality design solutions
- Basic understanding of security concepts
- Capable of