Sr. Cloud Developer

for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. Include a section only when posting has real specific content for it; never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the given posting. The posting text: "Role Description JD Support Airvision Schedule Manager and ancillary processes that support the Network Planning business team. Skill and Experience Level AWS, Serverless Architecture, Java Full Stack Senior (7+ Years) Python/Shell Scripting Senior (7+ Years) AI Agentic Tools Senior (7+ Years) RDS/Oracle/Postgres/MS SQLServer Senior (7+ Years) IOS and Android Mid (3-7 Years) Responsibilities Develop solid and supportable modular designs for data streaming, Cloud transformation/migration, and API product development in support of critical applications Develop data APIs and data delivery services that support operational and analytical applications for internal business operations, customers and partners Creation and support of data-centric products that encompass multiple specializations, platforms, and technologies Analyze technical information and produce quality software Initiate collaboration with teammates Offer creative solutions to overcome obstacles Work within automated testing and CICD processes Be an expert on the products we built Document solutions in written and diagram form, and communicate across teams Leverage developer coding standards to ensure it meets design goals and business needs Identify technical issues, articulate impact and need for prioritization Proactive communication to both team and leadership Work collaboratively with vendor(s) and About Mphasis Mphasis applies next-generation technology to help enterprises transform businesses globally. Customer centricity is foundational to Mphasis and is reflected in the Mphasis’ Front2Back™ Transformation approach. Front2Back™ uses the exponential power of cloud and cognitive to provide hyper-personalized (C=X2C2TM=1) digital experience to clients and their end customers. Mphasis’ Service Transformation approach helps ‘shrink the core’ through the application of digital technologies across legacy environments within an enterprise, enabling businesses to stay ahead in a changing world. Mphasis’ core reference architectures and tools, speed and innovation with domain expertise and specialization are key to building strong relationships with marquee clients. Equal Opportunity Employer Mphasis is an equal opportunity/affirmative action employer. We provide equal employment opportunities to applicants and existing associates and evaluate qualified candidates without regard to race, gender, national origin, ancestry, age, color, religious creed, marital status, genetic information, sexual orientation, gender identity, gender expression, sex (including pregnancy, breast feeding and related medical conditions), mental or physical disability, medical conditions military and veteran status or any other status or condition protected by applicable federal, state, or local laws, governmental regulations and executive orders. Other Details Salary range $63000 to $134500" We need to extract sections: About the role (maybe from Role Description). Responsibilities (list). Requirements/Qualifications/Skills (skill and experience level). Benefits? Not present. Pay? Salary range present. Schedule? Not present. So we should include sections: About the role, Responsibilities, Skills (or Requirements), Pay. Possibly also "Qualifications" but we can combine skill list under Skills. We need to avoid filler like "commensurate with experience". Not present. We need to remove EEO boilerplate, "About Mphasis" maybe considered company description; but is that substantive? It's about the company, not role. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Should we keep the "About Mphasis" paragraph? It's not about the role but about the company. It might be considered boilerplate? It's not EEO but it's company description. Usually we might keep it under "About the company" but we only have headings for About the role, Responsibilities, etc. There's no heading for About the company. The instruction 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 those for those sections. It doesn't say we cannot add other headings, but we should follow the pattern. Probably we should include company description under "About the role"? Not exactly. Could treat as part of role description? The role description includes "Role Description JD Support Airvision Schedule Manager and ancillary processes that support the Network Planning business team." That's the role description. Then after responsibilities, there is "About Mphasis". That's company overview. Might be considered substantive but not required headings. We could include it as a

after responsibilities without a heading, or maybe under a heading "About Mphasis". But the instruction only gave examples; not strict. Safer to include it as a paragraph without a heading, or maybe under a heading "About the company". However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That implies we should use those headings for those sections; but we could also add other headings if needed? The instruction doesn't forbid other headings, but to be safe, we could incorporate the company description into a paragraph under "About the role" or just as a separate

without heading. 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." So we can have other headings if needed, but they gave examples. I'd include a section "About Mphasis" as

About Mphasis

• each skill. Possibly keep the experience level in parentheses. Responsibilities: list of bullet points. We need to split by sentences starting with verbs. The responsibilities text: "Develop solid and supportable modular designs for data streaming, Cloud transformation/migration, and API product development in support of critical applications Develop data APIs and data delivery services that support operational and analytical applications for internal business operations, customers and partners Creation and support of data-centric products that encompass multiple specializations, platforms, and technologies Analyze technical information and produce quality software Initiate collaboration with teammates Offer creative solutions to overcome obstacles Work within automated testing and CICD processes Be an expert on the products we built Document solutions in written and diagram form, and communicate across teams Leverage developer coding standards to ensure it meets design goals and business needs Identify technical issues, articulate impact and need for prioritization Proactive communication to both team and leadership Work collaboratively with vendor(s) and". There's a trailing "and". Probably incomplete but we keep as is. We need to make each responsibility a
• . We'll split at each capitalized verb at start of sentence? Let's list: 1. Develop solid and supportable modular designs for data streaming, Cloud transformation/migration, and API product development in support of critical applications 2. Develop data APIs and data delivery services that support operational and analytical applications for internal business operations, customers and partners 3. Creation and support of data-centric products that encompass multiple specializations, platforms, and technologies 4. Analyze technical information and produce quality software 5. Initiate collaboration with teammates 6. Offer creative solutions to overcome obstacles 7. Work within automated testing and CICD processes 8. Be an expert on the products we built 9. Document solutions in written and diagram form, and communicate across teams 10. Leverage developer coding standards to ensure it meets design goals and business needs 11. Identify technical issues, articulate impact and need for prioritization 12. Proactive communication to both team and leadership 13. Work collaboratively with vendor(s) and We'll keep them. Now About the role: "Role Description JD Support Airvision Schedule Manager and ancillary processes that support the Network Planning business team." That's a sentence. We'll put as

  . About Mphasis: paragraphs. Pay: Salary range $63000 to $134500. We'll put under

  Pay

  with

  Salary range: $63,000 to $134,500

  (maybe keep original formatting). Use commas? Keep as given. Schedule: not present, omit. Benefits: not present, omit. Requirements/Qualifications: we have skill list; we could put under

  Skills

  with list. We should not repeat job title. Now produce HTML fragment: no /, no markdown. We'll output:

  About the role

  Role Description JD Support Airvision Schedule Manager and ancillary processes that support the Network Planning business team.

  Responsibilities

  • Develop solid and supportable modular designs for data streaming, Cloud transformation/migration, and API product development in support of critical applications
  • Develop data APIs and data delivery services that support operational and analytical applications for internal business operations, customers and partners
  • Creation and support of data-centric products that encompass multiple specializations, platforms, and technologies
  • Analyze technical information and produce quality software
  • Initiate collaboration with teammates
  • Offer creative solutions to overcome obstacles
  • Work within automated testing and CICD processes
  • Be an expert on the products we built
  • Document solutions in written and diagram form, and communicate across teams
  • Leverage developer coding standards to ensure it meets design goals and business needs
  • Identify technical issues, articulate impact and need for prioritization
  • Proactive communication to both team and leadership
  • Work collaboratively with vendor(s) and

  Skills

  • AWS, Serverless Architecture
  • Java Full Stack Senior (7+ Years)
  • Python/Shell Scripting Senior (7+ Years)
  • AI Agentic Tools Senior (7+ Years)
  • RDS/Oracle/Postgres/MS SQLServer Senior (7+ Years)
  • IOS and Android Mid (3-7 Years)

  About Mphasis

  Mphasis applies next-generation technology to help enterprises transform businesses globally. Customer centricity is foundational to Mphasis and is reflected in the Mphasis’ Front2Back™ Transformation approach. Front2Back™ uses the exponential power of cloud and cognitive to provide hyper-personalized (C=X2C2TM=1) digital experience to clients and their end customers. Mphasis’ Service Transformation approach helps ‘shrink the core’ through the application of digital technologies across legacy environments within an enterprise, enabling businesses to stay ahead in a changing world. Mphasis’ core reference architectures and tools, speed and innovation with domain expertise and specialization are key to building strong relationships with marquee clients.

  Pay

  Salary range $63000 to $134500

  We need to ensure