Jobs · Information Technology · Illinois

Senior Front End Product Engineer

Hyatt · Chicago, IL · 3 wk ago
Information Technology$117k–$145k/yrFull-time
We need to output HTML fragment with sections: headings

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use
  • for any list of duties/requirements/benefits, and

    for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text (e.g., "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless posting actually states them. Prefer few substantive sections over many thin ones. We need to parse the posting. Key parts: - Organization- Hyatt Corporate Office Summary The Opportunity Hyatt Hotels Corporation seeks an enthusiastic Senior Front End Product Engineer to join our Digital team. ... (some intro) - Who We Are (description of Hyatt culture) - could be "About the role"? Actually "Who We Are" is about company, not role. But we can treat as "About the role"? The instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. We have: - The Role: description of responsibilities, etc. That's responsibilities. - Qualifications: Experience Required, Experience Preferred. - Benefits: listed under "We’re proud to offer exceptional corporate benefits which include: ..." then list. - Pay: "The salary range for this position is $117,000 - $145,000" plus note about final pay rate depending on experience etc. So we have pay info. - Schedule: Not explicitly mentioned. There's "Flexible work schedule" under benefits. That's a benefit, not schedule. No explicit schedule like full-time, part-time, remote. So we should not create a Schedule section unless posting actually states them. It does mention flexible work schedule as benefit, but not a dedicated schedule. So we skip Schedule. - Skills: Could be derived from qualifications? But we have Qualifications section already. Could also have Skills separate but we can combine. The instruction: prefer few substantive sections over many thin ones. So we can have sections: About the role (maybe company overview), Responsibilities, Qualifications, Benefits, Pay. Possibly also Skills? But we can embed skills in Qualifications. We need to avoid repeating job title as heading. So no heading for "Senior Front End Product Engineer". Use headings as per list. We need to output only HTML fragment, no /, no markdown fences. We need to use

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

      for prose. We must preserve ALL substantive information; do NOT invent or summarize away detail. Remove boilerplate etc. Let's extract substantive content. First, intro: "Organization- Hyatt Corporate Office Summary The Opportunity Hyatt Hotels Corporation seeks an enthusiastic Senior Front End Product Engineer to join our Digital team. In this role, you will be collaborating closely with the broader digital product, design and platform operations team, where you’ll be instrumental in continuing to make Hyatt a leading hospitality company. You will be part of a team that is passionate about our purpose, committed to nurturing curiosity and new skills, and building connections across the organization with colleagues, customers, and guests." That's about the role/opportunity. Could be "About the role". We'll put that in a

      . Next "Who We Are" section: description of Hyatt culture, purpose, etc. That's also about company. Could be part of About the role or separate? Since we have limited headings, we could combine into About the role (or maybe "About the company"? Not in list). The instruction says headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put company description under About the role as well. Next "Why Now?" - maybe not needed. Next "How We Care For Our People" - includes benefits list. That's benefits. Next "Who You Are" - describes ideal candidate values. Could be part of Qualifications or Requirements? Might be "Requirements" (soft skills). We'll treat as Requirements. Next "The Role" - detailed responsibilities. That's Responsibilities. Next "Qualifications" - Experience Required and Experience Preferred. That's Qualifications. Next "The position responsibilities outlined above are in no way to be construed as all-encompassing..." - boilerplate, can drop. Next "We welcome you: Research shows that individuals tend to apply..." - encouraging to apply, maybe drop as application instruction? It's not exactly instruction but encouraging. Might be considered boilerplate; we can drop. Next "The salary range for this position is $117,000 - $145,000 The final pay rate/salary offered to the successful candidate will depend on experience, skill level and other qualifications for the role, as well as the location of the performance of work. Pay for the successful candidate will meet local requirements, including the local minimum wage rate." That's Pay. Next "We value our relationships with recruitment partners and require that agencies contact us first before submitting any candidates. Hyatt will not be responsible for any fees and obligations associated with unsolicited submissions unless a formal agreement is in place." That's boilerplate about recruitment agencies; drop. Now we need to format. We'll have sections: - About the role (combining intro, Who We Are, Why Now? maybe). We'll keep substantive paragraphs. - Responsibilities (from The Role). - Requirements (from Who You Are, maybe also some from Qualifications? But Qualifications separate.) - Qualifications (Experience Required and Preferred). - Benefits (list from How We Care For Our People). - Pay (salary range). We should not create Schedule. Now we need to ensure we use

      • for any list of duties/requirements/benefits. Thus: Responsibilities: list of duties from The Role bullet-like sentences. We'll extract each responsibility sentence and put as
      • . Requirements: list from Who You Are (values) maybe as
      • . Also maybe include "You enjoy working with others, are results-driven, and are looking for a variety of opportunities to develop personally and professionally." That's a requirement. Qualifications: two lists: Experience Required and Experience Preferred. We'll make
        • for each. Benefits: list from "We’re proud to offer exceptional corporate benefits which include:" then items. Pay: just a

          with salary range and note. Now we need to preserve all substantive information; do not invent or summarize away detail. So we must keep each piece exactly as in text, but we can rephrase? The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. It doesn't forbid rephrasing, but we should keep the meaning. Safer to keep the original sentences. We'll need to extract each bullet. Let's parse The Role paragraph: "The Senior Product Engineer is instrumental in architecting and delivering scalable, maintainable, and high-performance digital solutions for Hyatt’s global platforms. This position demands advanced technical skills, exceptional problem-solving abilities, and the capacity to influence technical strategies across multiple teams. Key responsibilities include mentoring engineering colleagues, collaborating with cross-functional partners, and driving enhancements in engineering practices and system architecture. Senior Engineers ensure Hyatt’s technology solutions remain reliable, secure, and strategically aligned with long-term business objectives. Lead the development of complex features and services throughout the technology stack. Design, implement, and optimize scalable software architectures. Provide mentorship and technical guidance to mid-level engineers through code reviews and best practice adoption. Define and uphold standards in coding, testing, and deployment processes. Collaborate with Product Managers and Designers to translate requirements into effective technical implementations. Enhance the observability, reliability, and performance of production systems. Promote the adoption of modern tools, frameworks, and cloud technologies. Serve as a technical lead on designated projects or initiatives. Work closely with Product Managers, Designers, Backend Engineers, and QA teams to convert business requirements into intuitive digital experiences. Mentor team members in front-end engineering best practices. Drive improvements in application performance, accessibility, reliability, observability, and production support." We can break into separate sentences for

        • . Ensure we keep each distinct responsibility. Now Requirements from Who You Are: "As our ideal candidate, you understand the power and purpose of our culture of care, and embody our core values of Empathy, Inclusion, Integrity, Experimentation, Respect, and Wellbeing. You enjoy working with others, are results-driven, and are looking for a variety of opportunities to develop personally and professionally." We can make two
        • items: one about embodying core values, another about enjoying working with others, results-driven, looking for development opportunities. Now Qualifications: Experience Required: list: - 5+ years of experience in front-end software engineering or an equivalent software development role. - Strong experience with React, Next.js, TypeScript, JavaScript, HTML5, CSS3, and responsive web design. - Experience integrating REST APIs, microservices, authentication providers, and third-party services. - Experience with automated testing tools such as React Testing Library, Cypress, or Playwright. - Experience with Git, code reviews, CI/CD pipelines, Agile development, and production troubleshooting. Experience Preferred: - Bachelor’s degree in Computer Science, Engineering, or STEM field, or equivalent practical experience. - Experience with Hyatt Privé application technologies, including React Query, OAuth/OpenID Connect, JWT, and role-based access control. - Experience improving front-end performance for applications dependent on multiple backend or external services. - Experience with accessibility standards such as Docker, Kubernetes, and observability tools. (Note: this sentence seems odd: "Experience with accessibility standards such as Docker, Kubernetes, and observability tools." Probably a mistake but we keep as is.) Now Benefits list: From "We’re proud to offer exceptional corporate benefits which include: Annual allotment of free hotel stays at Hyatt hotels globally Flexible work schedule Work-life benefits including wellbeing initiatives such as a complimentary Headspace subscription, and a discount at the on-site fitness center A global family assistance policy with paid time off following the birth or adoption of a child as well as financial assistance for adoption Paid Time Off, Medical, Dental, Vision, 401K with company match" We need to split into items. The text is a bit run-on. We'll parse: - Annual allotment of free hotel stays at Hyatt hotels globally - Flexible work schedule - Work-life benefits including wellbeing initiatives such as a complimentary Headspace subscription, and a discount at the on-site fitness center - A global family assistance policy with paid time off following the birth or adoption of a child as well as financial assistance for adoption - Paid Time Off, Medical, Dental, Vision, 401K with company match We'll keep each as
        • . Now Pay: "The salary range for this position is $117,000 - $145,000 The final pay rate/salary offered to the successful candidate will depend on experience, skill level and other qualifications for the role, as well as the location of the performance of work. Pay for the successful candidate will meet local requirements, including the local minimum wage rate." We'll put as

          maybe multiple sentences. Now About the role: we need to combine intro and Who We Are and Why Now? and How We Care For Our People? Actually benefits separate. So About the role includes: - Organization- Hyatt Corporate Office Summary The Opportunity Hyatt Hotels Corporation seeks an enthusiastic Senior Front End Product Engineer to join our Digital team. In this role, you will be collaborating closely with the broader digital product, design and platform operations team, where you’ll be instrumental in continuing to make Hyatt a leading hospitality company. You will be part of a team that is passionate about our purpose, committed to nurturing curiosity

Similar jobs

Senior Front End Engineer

TrendAIAustin, Texas Metropolitan Area· 3 wk ago
Engineeringapply on trendmicro.wd3.myworkdayjobs.com