Senior Software Developer

We need to output HTML fragment with sections: About the role (maybe from POSITION OVERVIEW?), Responsibilities, Qualifications, Benefits, Pay, Schedule? The posting includes compensation and benefits. Schedule: remote primarily, occasional onsite. So we can include Schedule section. Also maybe "About NBME" is not required as a heading? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should include headings that match content. We have "POSITION OVERVIEW" which is about the role. So we can use

About the role

. Then responsibilities list. Then qualifications: we have QUALIFICATIONS section with Skills and Abilities, Experience, Education. Could combine into Qualifications. Also maybe separate Skills? But instruction says prefer few substantive sections over many thin ones. So we can have Qualifications covering skills, experience, education. Benefits: we have "Excellent Benefits include: ..." plus mention of competitive salaries etc. So Benefits section. Pay: compensation range. Schedule: remote primarily, occasional onsite. Also mention location radius. Could be part of Schedule or maybe a note. We'll include Schedule. We must not repeat job title as heading. No Job ID. Remove boilerplate: EEO, etc. Also remove navigation/legal etc. Also remove duplicated lines. Also remove application instructions (none). Also remove cookie/navigation/legal/EEO etc. We must preserve all substantive information. So include details about responsibilities, qualifications, benefits, pay, schedule, location radius, remote friendly, occasional onsite, 50-mile radius, Philadelphia office, onsite interviews maybe. We must not include placeholder text like "commensurate with experience". Not present. We must not invent or summarize away detail. So keep specifics. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. Thus:

  About the role

  ... (the overview paragraph(s) )

  Then

  Responsibilities

  • ... each responsibility line
  Then

  Qualifications

  We could break into sub-lists? But we can just list items. Qualifications includes Skills and Abilities (list), Experience, Education. We can make a single
  with all qualification items. But we might want to separate Skills vs Experience vs Education? The instruction says prefer few substantive sections over many thin ones. So one Qualifications section is fine. Thus

  Qualifications

  • In-depth understanding of serverless computing concepts, event-driven architectures, and design patterns for serverless applications.
  • Strong hands-on experience with AWS serverless technologies, including Lambda, API Gateway, SQS, SNS, EventBridge, Step Functions, and AppSync.
  • Deep knowledge of Python, AWS SDKs, and the boto3 library for AWS services integration.
  • Strong experience with AWS database and storage technologies, including DynamoDB, DocumentDB, Aurora, RDS, and S3.
  • Knowledge of Infrastructure as Code and modern DevOps practices, including CloudFormation, CDK or SAM, CI/CD pipelines, and serverless testing frameworks.
  • Knowledge of serverless monitoring, debugging, security, and compliance considerations, including tools such as AWS X-Ray or CloudTrail.
  • Ability to work effectively across cloud-native and legacy application environments, including PL/SQL, Java, and Oracle.
  • Strong communication, collaboration, and technical leadership skills, with experience working in Agile or Scrum-based environments.
  • AWS certification related to serverless computing, such as AWS Certified Developer - Associate or AWS Certified Solutions Architect, is a plus but not required.
  • 10+ years of experience in Information Technology, with expertise in designing and building large-scale applications, security, or infrastructure solutions.
  • Bachelor's degree in a related field or equivalent work experience.
  Then

  Benefits

  • Healthcare, Dental, Prescription, and Vision plans
  • 401(k) w/match
  • Tuition Reimbursement Plan
  • Commuter Benefit: Public Transit or Parking options
  • Remote Friendly Workplace
  Then

  Pay

  Compensation range: $135,600 - $170,000 per year. The offered rate typically aligns with the minimum to midrange of this grade, but can vary based on qualifications, experience, department budget, and internal equity review.

  Then

  Schedule

  Primarily remote position with occasional onsite work for team collaboration or meetings. Applicants are prioritized within a 50‑mile radius of the Philadelphia office; onsite interviews and onboarding may be required.

  We should also include maybe a brief about NBME? The instruction says include section only when posting has real specific content. The "About NBME" paragraph is substantive. Could be a section "About NBME". But the allowed headings list includes "About the role", not "About NBME". However we could still include a heading like "About NBME" if we want, but the instruction says use headings for section headings (e.g. About the role, Responsibilities...). It doesn't forbid other headings, but says use those for section headings. Probably better to include "About NBME" as a section? The instruction: "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, not exclusive. But they also say "Prefer a few substantive sections over many thin ones." So we could add an "About NBME" section if it's substantive. However the "About NBME" paragraph is descriptive of the organization, not directly about the role. Might be considered boilerplate? It's not navigation/legal/EEO. It's substantive about the organization. I'd include it as a section maybe "About NBME". But the instruction says "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it." It doesn't forbid other headings. Given the examples, they likely expect sections like About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. The "About NBME" could be considered part of About the role? But the overview already includes NBME mission etc. Actually the POSITION OVERVIEW includes NBME mission and description. The later "About NBME" repeats some of that. Might be redundant. To avoid duplication, we could incorporate NBME description into About the role section. The overview already mentions NBME's mission etc. So we can keep About the role as is, which includes that content. The later "About NBME" is somewhat repetitive; we could drop it to avoid duplication. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we drop the repeated paragraph, we might lose some detail that is not already in overview. Let's compare: Overview includes: "At NBME, we continue to innovate and improve how we fulfill the evolving needs of the health care community. This commitment starts and ends with the people at NBME. By recruiting and empowering talented individuals from various disciplines and backgrounds, which includes professionals with diverse life experiences, abilities, and perspectives, NBME can take a well-informed, robust approach to advancing medical education and assessment for years to come." That's about NBME's commitment. The later "About NBME" includes: "NBME is a not-for-profit organization that specializes in the creation of assessments and learning tools for physicians and health professionals. Our mission is to advance assessment of these professionals to achieve optimal care for all, supporting the development of a highly effective, diverse and compassionate health care workforce. Founded in 1915, NBME develops and manages the United States Medical Licensing Examination® with the Federation of State Medical Boards. We offer a comprehensive portfolio of assessment products for every stage of the medical school journey and provide assessment services to various health profession organizations. We are dedicated to advancing innovative assessment approaches through research, collaboration and contributions to the medical education and assessment communities. In 2024, we expanded our assessment capabilities to include simulation through the acquisition of MedVR Education. Learn more on NBME's website." That's more detailed about NBME. So we should preserve that. It's not in overview. So we need a section for that. Could be "About NBME". Since it's substantive, we should include. Thus we will have sections: About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule, About NBME. But the instruction says prefer a few substantive sections over many thin ones. Adding another section increases count but it's substantive. Could we fold About NBME into About the role? The overview already has some NBME content but not the detailed history. We could combine them into About the role section, making it longer but still one section. That would reduce number of sections. The instruction: "Prefer a few substantive sections over many thin ones." So better to combine. Let's merge the NBME description into About the role section. That way we have About the role, Responsibilities, Qualifications, Benefits, Pay, Schedule. That's six sections. We need to ensure we preserve all substantive info from the NBME description. So we will add that paragraph(s) to About the role. Thus About the role will contain two paragraphs: first from POSITION OVERVIEW, second from About NBME. Let's craft:

  About the role

  NBME is seeking an experienced Senior Software Developer with deep AWS and serverless expertise to join the Product Engineering unit as a key member of the Scoring team. In this role, you will lead the architecture, development, testing, and implementation of a new scoring system, designing scalable serverless and event-driven solutions within the AWS environment. You will partner with engineers, Product Owners, Solution Architects, the Enterprise Application and Infrastructure teams, and business stakeholders while providing technical leadership and mentorship across internal and offshore team members. Your work will have a direct impact on NBME's future growth and innovation in a highly collaborative, digitally driven environment. This role has been designated as a primarily remote position, though it may require occasional onsite work for team collaboration or meetings. We are currently prioritizing applicants within a 50-mile radius of our Philadelphia office. Please note that onsite interviews and onboarding at our Philadelphia office may be required for this role. If applicable, advance notice will be provided to support planning.

  At NBME, we continue to innovate and improve how we fulfill the evolving needs of the health care community. This commitment starts and ends with the people at NBME. By recruiting and empowering talented individuals from various disciplines and backgrounds, which includes professionals with diverse life experiences, abilities, and perspectives, NBME can take a well-informed, robust approach to advancing medical education and assessment for years to come.

  NBME is a not-for-profit organization that specializes in the creation of assessments and learning tools for physicians and health professionals. Our mission is to advance assessment of these professionals to achieve optimal care for all, supporting the development of a highly effective, diverse and compassionate health care workforce. Founded in 1915, NBME develops and manages the United States Medical Licensing Examination® with the Federation of State Medical Boards. We offer a comprehensive portfolio of assessment products for every stage of the medical school journey and provide assessment services to various health profession organizations. We are dedicated to advancing innovative assessment approaches through research, collaboration and contributions to the medical education and assessment communities. In 2024, we expanded our assessment capabilities to include simulation through the acquisition of MedVR Education. Learn more on NBME's website.

  That seems to capture all.