Junior Full Stack Developer

We need to output HTML fragment with sections: About the role? Actually we have "Who We Are" and "You Are" etc. We need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real content. We need to preserve all substantive info, remove boilerplate, navigation, EEO, etc. Also remove duplicated lines, application instructions. We need to extract relevant content: Role description, Who We Are, You Are, The Opportunity (responsibilities), What You Need (requirements/qualifications), Data CoE Expectations, Preferred Background, Preferred Experience, Key Competencies, Visa sponsorship note, Compensation range, Benefits details, Location, etc. We need to map to headings: About the role (maybe combine Who We Are and You Are?), Responsibilities (The Opportunity), Requirements (What You Need), Qualifications (maybe Preferred Background?), Skills (list of tech), Benefits, Pay (Compensation Range), Schedule (maybe not present). The posting does not mention schedule specifics (full-time etc). It mentions full-time, regular employees etc. Could include schedule as full-time? But we should only create Schedule section if posting actually states them. It does mention full-time, regular employees etc. That could be schedule info. However the instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits and compensation, and mentions full-time etc. So we can include Benefits, Pay, and maybe Schedule (full-time). But we need to check if schedule is explicitly stated: "Full-time, regular employees accrue..." So yes schedule info present: full-time. We'll include Schedule section with that info. We must not repeat job title as heading. The job title is "Junior Full Stack Developer Developer I - Software Engineering". We'll not use that as heading. We need to avoid duplicating lines. We'll produce something like:

About the role

...

But we need to decide what goes in About the role: maybe combine Who We Are and You Are? The "Who We Are" is company description. "You Are" is about the role? Actually "You Are We are searching for a high-potential Junior Full Stack Developer..." That's role description. So we can put About the role as the company description? Or we could have two sections: About the role (company overview) and Responsibilities etc. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should follow that. Thus: About the role: company description (Who We Are) plus maybe the role summary (You Are). We'll combine. Responsibilities: The Opportunity bullet list. Requirements: What You Need (graduation year, GPA, experience, tech stacks). Could also include Data CoE Expectations as part of requirements. Qualifications: Preferred Background, Preferred Experience. Skills: list of specific technologies (Frontend, Backend, Databases, APIs, Cloud, Tools). Could also include Key Competencies as skills? But we have separate section for Skills; we can put technical skills there. Benefits: benefits description. Pay: compensation range. Schedule: full-time info. We must not include boilerplate like Equal Employment Opportunity, Visa sponsorship note? Visa sponsorship is not available for this role - that's substantive? It's a note about visa sponsorship. Should we keep? It's not boilerplate; it's a specific note. Could be placed maybe in Requirements or Qualifications? But we don't have a heading for that. Could add a short paragraph under Requirements or Qualifications. However instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that note. Where to put? Could add a

under Requirements or Qualifications. Probably under Requirements as it's a condition. Also note: "Compensation can differ depending on factors..." that's part of Pay section. We need to remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So remove the EEO statement, the "We Believe" values? That's substantive? It's company values; maybe we can include in About the role? It's not boilerplate but it's culture. Could keep. But we need to avoid too many sections; we can incorporate into About the role. We also need to remove duplicated lines like "Full-time, regular employees accrue..." appears multiple times for different employee types; we should consolidate. Let's extract content. Company description (Who We Are): "Born digital, UST transforms lives through the power of technology. We walk alongside our clients and partners, embedding innovation and agility into everything they do. We help them create transformative experiences and human-centered solutions for a better world. UST is a mission-driven group of 29,000+ practical problem solvers and creative thinkers in more than 30 countries. Our entrepreneurial teams are empowered to innovate, act nimbly, and create a lasting and sustainable impact for our clients, their customers, and the communities in which we live. With us, you’ll create a boundless impact that transforms your career—and the lives of people across the world. Visit us at UST.com." Role summary (You Are): "We are searching for a high-potential Junior Full Stack Developer to join our Data CoE, focused on building data-driven applications and platforms. This role is ideal for candidates with strong fundamentals and a passion for working at the intersection of application development and data engineering." Opportunity (Responsibilities): - Develop and maintain end-to-end full stack applications (frontend + backend) - Build scalable data-driven applications and APIs - Integrate applications with enterprise data platforms (data lakes, warehouses, APIs) - Collaborate with data engineers, data scientists, and architects - Participate in design discussions, code reviews, and debugging - Ensure code quality, testing, and adherence to modern engineering practices (CI/CD) What You Need (Requirements): - Graduation Year: 2024, 2025 or 2026 - GPA: 3.5 - Experience: 0-3 years - Frontend: React / Angular / Vue.js, HTML, CSS, JavaScript/TypeScript - Backend: Java / Python / Node.js - Databases: SQL (Postgres/MySQL) + NoSQL (MongoDB preferred) - APIs: REST / Microservices architecture - Cloud: Exposure to AWS / Azure / GCP - Tools: Git, CI/CD, Docker (good to have) - Visa sponsorship is not available for this role Data CoE Expectations (maybe part of Requirements): - Build applications leveraging enterprise data platforms and large datasets - Basic understanding of data pipelines, ETL, and data modeling concepts - Ability to work with data APIs and analytics-driven use cases - Exposure/interest in AI/ML-driven or data-centric applications (nice to have) Preferred Background (Qualifications): - Bachelor’s/Master’s in Computer Science or related field - Candidates from top-tier universities (e.g., MIT, Stanford, CMU, UC Berkeley, etc.) or equivalent strong institutions preferred - Strong foundation in data structures, algorithms, and system design Preferred Experience (Nice to Have) (Qualifications): - Internship/work experience with leading tech/product companies (e.g., Google, Microsoft, Amazon, etc.) - Exposure to data platforms, analytics, or modern data ecosystems - Contributions to open source, hackathons, or research projects Key Competencies (Skills?): - Strong problem-solving and analytical skills - Ability to work in a fast-paced, collaborative environment - Strong learning agility and ownership mindset - Good communication (technical + business stakeholders) Benefits: - Full-time, regular employees accrue a minimum of 10 days of paid vacation per year, receive 6 days of paid sick leave each year (pro-rated for new hires throughout the year), 10 paid holidays, and are eligible for paid bereavement leave and jury duty. - Eligible to participate in the Company’s 401(k) Retirement Plan with employer matching. - They and their dependents residing in the US are eligible for medical, dental, and vision insurance, as well as the following Company-paid Employee Only benefits: basic life insurance, accidental death and disability insurance, and short- and long-term disability benefits. - Regular employees may purchase additional voluntary short-term disability benefits, and participate in a Health Savings Account (HSA) as well as a Flexible Spending Account (FSA) for healthcare, dependent child care, and/or commuting expenses as allowable under IRS guidelines. - Benefits offerings vary in Puerto Rico. - Part-time employees receive 6 days of paid sick leave each year (pro-rated for new hires throughout the year) and are eligible to participate in the Company’s 401(k) Retirement Plan with employer matching. - Full-time temporary employees receive 6 days of paid sick leave each year (pro-rated for new hires throughout the year) and are eligible to participate in the Company’s 401(k) program with employer matching. They and their dependents residing in the US are eligible for medical, dental, and vision insurance. - Part-time temporary employees receive 6 days of paid sick leave each year (pro-rated for new hires throughout the year). - All US employees who work in a state or locality with more generous paid sick leave benefits than specified here will receive the benefit of those sick leave laws. Pay: - Compensation Range: $50 to $55/hr - Compensation can differ depending on factors including but not limited to the specific office location, role, skill set, education, and level of experience. - Role Location: Bellevue, Washington Schedule: - Full-time, regular employees (as indicated in benefits). Could state: Full-time position. We need to avoid duplication: The benefits text repeats for different employee types; we can consolidate but must preserve all substantive info. Could keep as is but maybe shorten? The instruction: do NOT invent or summarize away detail. Summarizing might be considered summarizing away detail. We need to preserve all substantive information; we can keep the detailed benefits as is, even if repetitive. But we can combine similar points without losing info? Might be considered summarizing. Safer to keep the original benefit paragraphs as they appear, but we can remove duplicated lines that are exactly same? The posting repeats similar sentences for different employee categories; they are not identical but similar. Removing them would lose detail about part-time etc. So we should keep all. But we can format as

• for each bullet? The benefits are prose; we can keep as

  paragraphs. We need to ensure we don't include boilerplate like "Equal Employment Opportunity Statement" etc. Remove that. Also remove "#UST #CB Skills Java, Microsoft Azure, Python" at end? That's a skills list maybe duplicate; we already have skills. Might be considered boilerplate; but it's a list of skills. However we already have skills section; we could incorporate those. But to avoid duplication, we can ignore that line. Now produce HTML. We'll need to wrap sections in

  and content in

  or

  • . For lists like responsibilities, requirements, qualifications, skills, we use
    • . For prose like About the role, Benefits, Pay, Schedule we use

      . Let's craft. About the role: combine Who We Are and You Are. We'll make two paragraphs maybe. Responsibilities: list. Requirements: list (graduation year, GPA, experience, tech stacks, visa note). Could also include Data CoE Expectations as part of requirements; but we could make a separate section? Not in allowed headings. Could incorporate into Requirements. Qualifications: Preferred Background and Preferred Experience. Skills: list of technical skills (Frontend, Backend, Databases, APIs, Cloud, Tools) plus Key Competencies? Actually Key Competencies are soft skills; could go under Skills as well. But we already have Skills heading; we can include both technical and soft skills there. Or we could put Key Competencies under Skills as well. But we have also a