Software Engineer - REST API Development, Officer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID as heading. Remove boilerplate, navigation, legal, EEO, scam warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay section only if posting states salary range. It does: Salary Range $70,000 - $118,750 Annual. So include Pay section. Benefits: they list benefits: retirement savings plan (401K) with company match; insurance coverage including basic life, medical, dental, vision, long-term disability, and other optional additional coverages; paid-time off including vacation, sick leave, short term disability, and family care responsibilities; access to Employee Assistance Program; incentive compensation including eligibility for annual performance-based awards; eligibility for certain tax advantaged savings plans. So include Benefits section. Schedule: not mentioned. So omit Schedule. Also maybe include "About the role" section (the initial paragraph). Then "Responsibilities" (list). Then "Qualifications" maybe combine Required Qualifications and Preferred Qualifications? The instruction says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They separate Requirements and Qualifications. We need to decide what goes where. Typically "Requirements" could be Required Qualifications, and "Qualifications" could be Preferred Qualifications. Or "Skills" could be Technical Skills. Let's map: - About the role: the introductory paragraph(s) about role. - Responsibilities: list of responsibilities (Key Responsibilities subpoints). Use

  • . - Requirements: Required Qualifications (education, experience, maybe some baseline). Could be a list. - Qualifications: Preferred Qualifications (coursework, certifications, etc.) maybe also a list. - Skills: Technical Skills (maybe list of core technologies, nice to have). Could be a list. - Benefits: list of benefits. - Pay: salary range. We must not include filler like "commensurate with experience". Not present. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as lists. We need to be careful not to duplicate content. Let's extract sections. Original text: About The Role We are seeking an enthusiastic and motivated Junior Software Engineer to join our API Engineering team. In this role, you will help design, develop, test, document, and support REST APIs that power business applications, partner integrations, and client-facing services. You will work closely with senior engineers, architects, product managers, quality engineers, and platform teams to learn and apply modern software engineering practices while contributing to secure, scalable, and reliable APIs. This position is ideal for an early-career engineer who is eager to grow in backend development, systems integration, and API design, and who enjoys solving technical problems in a collaborative, mentorship-driven environment. Key Responsibilities API Development Assist in designing, developing, and maintaining RESTful APIs and backend services under the guidance of senior engineers. Build and maintain reusable components, libraries, and integration services. Help ensure APIs meet performance, reliability, and security requirements. Learn and apply API versioning and lifecycle management practices. Troubleshoot and help resolve API and integration issues across development and testing environments, escalating complex issues as needed. Documentation & Knowledge Sharing Create and maintain clear API and integration documentation, including API specifications, developer guides, and usage examples. Document technical work, implementation notes, and lessons learned. Contribute to team knowledge repositories and engineering best practices. Integration & Architecture Support the development of integrations between internal systems, external partners, and cloud services. Follow enterprise architecture standards when implementing API solutions. Learn and contribute to microservices and event-driven integration patterns. Assist with API gateway onboarding and basic policy implementation tasks. Quality Engineering Write unit, integration, and automated API tests with guidance from senior team members. Participate in peer code reviews and design reviews to learn team standards. Support CI/CD pipeline usage and basic deployment automation tasks. Help identify reliability, performance, and maintainability issues. Security & Compliance Learn and apply secure authentication and authorization mechanisms such as OAuth 2.0 and JWT. Follow secure coding practices and enterprise security requirements. Support vulnerability remediation activities as directed. Help ensure appropriate logging and monitoring is implemented in the services you build. Collaboration Actively participate in Agile/Scrum ceremonies and engineering planning activities. Collaborate with product, architecture, security, and operations teams. Communicate progress, questions, and technical ideas clearly to teammates and mentors. Seek feedback and apply it to continuously improve technical skills. Required Qualifications Education Bachelor's degree in Computer Science, Software Engineering, Information Technology, or a related field (or equivalent practical experience, including internships, bootcamps, or personal projects). Experience 0-2 years of professional software development experience (internships, co-ops, and academic projects are valued). Some exposure to building or consuming REST APIs, through coursework, internships, or personal projects. Familiarity with at least one backend language/framework such as Java, C#, .NET, or Spring Boot. Basic experience with Git-based source control. Technical Skills Basic understanding of REST API principles and HTTP protocols. Familiarity with JSON and API integration concepts. Basic understanding of relational databases and SQL. Foundational knowledge of software design patterns and object-oriented programming. Willingness to learn API security concepts, including OAuth 2.0 and JWT. Exposure to automated testing frameworks (unit testing) is a plus. Interest in or coursework experience with cloud platforms such as Microsoft Azure. Curiosity about containerization technologies such as Docker and Kubernetes. Eagerness to learn CI/CD pipelines and DevOps practices. Preferred Qualifications Coursework, certifications, or personal projects involving Microsoft Azure. Exposure to messaging or event-driven concepts (e.g., Kafka, RabbitMQ, Azure Service Bus). Experience writing basic technical documentation. Familiarity with monitoring/logging concepts. Internship or academic experience in financial services, fintech, or other regulated industries. What We Value Strong desire to learn and grow as a software engineer. Analytical and problem-solving mindset. Attention to detail and commitment to writing quality code. Strong written and verbal communication skills. Ability to collaborate effectively and accept mentorship in a team environment. Growth mindset and willingness to adopt new technologies. Ownership mindset with the ability to drive assigned tasks to completion with support. Core Technologies REST APIs (foundational) Java, Spring Boot, C#, or .NET Git SQL Databases Basic OAuth 2.0 / JWT concepts Nice to Have Technologies Microsoft Azure Docker / Kubernetes (exposure) CI/CD Pipelines Kafka or similar messaging platforms Desired Traits Strong foundational engineering skills Eagerness to learn cloud-native development Security-aware mindset Good communication and documentation habits Ability to work effectively in Agile teams with mentorship Passion for building reliable software and growing into a stronger engineer Role Summary This job description is aligned for an entry-level/junior engineer joining an Azure-based REST API platform team. The role emphasizes hands-on learning, mentorship, and gradual ownership of API development, integrations, testing, documentation, and cloud-native application delivery under the guidance of senior engineers. Salary Range $70,000 - $118,750 Annual The range quoted above applies to the role in the primary location specified. If the candidate would ultimately work outside of the primary location above, the applicable range could differ. Employees are eligible to participate in State Street’s comprehensive benefits program, which includes: our retirement savings plan (401K) with company match; insurance coverage including basic life, medical, dental, vision, long-term disability, and other optional additional coverages; paid-time off including vacation, sick leave, short term disability, and family care responsibilities; access to our Employee Assistance Program; incentive compensation including eligibility for annual performance-based awards (excluding certain sales roles subject to sales incentive plans); and, eligibility for certain tax advantaged savings plans. For a full overview, visit https://hrportal.ehr.com/statestreet/Home. About State Street [...] As an Equal Opportunity Employer, we consider all qualified applicants for all positions without regard to race, creed, color, religion, national origin, ancestry, ethnicity, age, disability, genetic information, sex, sexual orientation, gender identity or expression, citizenship, marital status, domestic partnership or civil union status, familial status, military and veteran status, and other characteristics protected by applicable law. Discover more information on jobs at StateStreet.com/careers Read our CEO Statement Job Application Disclosure It is unlawful in Massachusetts to require or administer a lie detector test as a condition of employment or continued employment. An employer who violates this law shall be subject to criminal penalties and civil liability. Job ID: R-798140 We need to remove boilerplate: EEO, legal, scam warning, application instructions, navigation, cookie, duplicated lines. Also remove "About State Street" etc. Also remove "Discover more information on jobs at StateStreet.com/careers", "Read our CEO Statement", "Job Application Disclosure", "Job ID". Also remove "For a full overview, visit ..." maybe considered boilerplate? It's a link to benefits overview; could be considered part of benefits but it's a reference; maybe we can keep as part of benefits? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The link to benefits overview is not exactly those; but it's a reference; we could keep it as part of benefits description? Might be okay to keep but it's a URL; not required. Safer to keep benefits description but maybe drop the URL as it's not substantive? The instruction says preserve ALL substantive information; the URL is not substantive but could be considered a reference. I'd drop it. Now we need to structure. We'll produce:

    About the role

    We are seeking an enthusiastic and motivated Junior Software Engineer to join our API Engineering team. In this role, you will help design, develop, test, document, and support REST APIs that power business applications, partner integrations, and client-facing services. You will work closely with senior engineers, architects, product managers, quality engineers, and platform teams to learn and apply modern software engineering practices while contributing to secure, scalable, and reliable APIs. This position is ideal for an early-career engineer who is eager to grow in backend development, systems integration, and API design, and who enjoys solving technical problems in a collaborative, mentorship-driven environment.

    Responsibilities

    • Assist in designing, developing, and maintaining RESTful APIs and backend services under the guidance of senior engineers.
    • Build and maintain reusable components, libraries, and integration services.
    • Help ensure APIs meet performance, reliability, and security requirements.
    • Learn and apply API versioning and lifecycle management practices.
    • Troubleshoot and help resolve API and integration issues across development and testing environments, escalating complex issues as needed.
    • Create and maintain clear API and integration documentation, including API specifications, developer guides, and usage examples.
    • Document technical work, implementation notes, and lessons learned.
    • Contribute to team knowledge repositories and engineering best practices.
    • Support the development of integrations between internal systems, external partners, and cloud services.
    • Follow enterprise architecture standards when implementing API solutions.
    • Learn and contribute to microservices and event-driven integration patterns.
    • Assist with API gateway onboarding and basic policy implementation tasks.
    • Write unit, integration, and automated API tests with guidance from senior team members.
    • Participate in peer code reviews and design reviews to learn team standards.