Product Solutions Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title. Must not include Job ID etc. Must remove boilerplate like EEO etc. Must preserve all substantive info. We need to parse the posting. Content: Location: Hawaii (Any Island) Ready is seeking a passionate and innovative Product Solutions Engineer to support our state customers as we rapidly expand. This person will force-multiply our ability to deliver results for key customers and drive expansion into future opportunities. You will translate customer requests into impactful features, navigate development complexities, and bridge the gap between technical feasibility and user-centric design, ensuring our customers' needs don’t fall through the cracks. This person will also contribute to Ready’s Center of Excellence through AI technology and automation. This is a fully remote position; however, candidates must be based in and reside in Hawaii. About Your Role At Ready ⚡️ Collaborate with product managers and engineers (PED) to define and prioritize product requirements, ensuring technical feasibility and alignment with user needs. Capture, document, and communicate client requirements with the core team while adhering to the agreed upon format to convey priority. Proactively identify and manage risks and dependencies across cross-functional teams, advocating for solutions and driving efficient execution. Develop, utilize, and perform effective test strategies to ensure quality and performance of implemented features. Document technical specifications and maintain clear communication with stakeholders throughout the development process. Contribute to the continuous improvement of our development processes and tools, promoting a culture of innovation and agility. Stay abreast of emerging technologies and industry trends, proactively suggesting opportunities for product enhancement. Technical Support and Troubleshooting. Client Training and Education on Ready Software tools. Work closely with engineering, product, and operations teams to optimize AI utilization, flag risks/blockers, and drive continuous improvement in workflows. A Bit About You 🥇 Bachelor's degree with an emphasis on computer science, engineering, or similar technical field. 2-3 years experience working in an engineering role. Strong understanding of Agile development methodologies and experience working in cross-functional teams. Excellent communication, collaboration, and problem-solving skills. Passion for building user-friendly and impactful products. Ability to independently manage multiple tasks and prioritize effectively under pressure. Builder mentality with proven experience in customer facing roles. Ability to write clean, maintainable, and efficient code in at least one relevant programming language (e.g., React, Python etc). Demonstrated understanding of user experience (UX) principles and practices. Strong analytical and data-driven approach to problem-solving. Basic understanding of web technologies such as HTML5, CSS3, and web APIs. Proficiency in AI model monitoring, data validation, and automation tooling. Ability to thrive in a fast-paced, agile environment and manage multiple priorities. Excellent written and verbal communication skills. A passion for user-centered design and clean coding practice. Ability to operate independently and thrive in an ambiguous environment. Experience with AWS Bedrock, Python (including SQL knowledge), CI/CD (Docker, AWS), MLflow + Airflow (good to have), and Langchain or Pydantic-AI. Knowledge of LLM model evaluation, RAG architectures, LLM MCP servers, and LLM prompt engineering & function calls. About Ready 🚀 Creative problem solvers approaching a legacy industry with a new point of viewHumble but ambitious, knowledgeable but curious, persistent but not obnoxiousConcise and effective in written and spoken communicationComfortable working hybridOne team, one dream About What You Get… Competitive salary plus meaningful equity upside; salary range is $125,000-$140,000Competitive (and ever expanding) benefits for employees and dependentsOpportunities to learn and grow – all things startupsMajority remote (WFH) with frequent travel requirements and flexibility to commute to the office as neededA chance to play a role in defining the roadmap as we pursue a bold vision and and a big goalTo get away - we all convene 1-2x / year for [optional, encouraged] retreatsWe’re actively shaping our benefits program: have a say in which benefits matter to youThe charter to realize a market that is set to receive $65 billion in grant funding across the United States Then EEO boilerplate. We need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. - About the role: Could be the introductory paragraph about the role? The posting has "About Your Role At Ready" which is a list of responsibilities. Could treat that as Responsibilities section. The initial paragraph before that could be About the role (overview). Let's decide: Use "About the role" for overview description: "Location: Hawaii (Any Island) Ready is seeking a passionate and innovative Product Solutions Engineer to support our state customers as we rapidly expand. This person will force-multiply our ability to deliver results for key customers and drive expansion into future opportunities. You will translate customer requests into impactful features, navigate development complexities, and bridge the gap between technical feasibility and user-centric design, ensuring our customers' needs don’t fall through the cracks. This person will also contribute to Ready’s Center of Excellence through AI technology and automation. This is a fully remote position; however, candidates must be based in and reside in Hawaii." - Responsibilities: The bullet list after "About Your Role At Ready ⚡️". That includes many items. We'll put them as

• . - Requirements: Could be the "A Bit About You" list (education, experience, etc). That's qualifications/requirements. We'll treat as Requirements. - Qualifications: Might be overlapping; but we need to avoid duplicate thin sections. Perhaps combine Requirements and Qualifications? But we need to follow instruction: include a section only when posting has real specific content. We have content for both Requirements and Qualifications? The "A Bit About You" includes education, experience, skills, etc. Could split: Requirements (education, experience) and Qualifications (technical skills). But risk of thin sections. Let's see if we can make substantive sections: Requirements: education, years experience, Agile understanding, communication skills, etc. Qualifications: specific technical proficiencies (AWS Bedrock, Python, CI/CD, MLflow+Airflow, Langchain/Pydantic-AI, LLM model evaluation, RAG, etc). Skills: maybe soft skills? But we already have communication etc. Could treat Skills as technical skills list. However we need to avoid filler. Better: Use sections: About the role, Responsibilities, Requirements (education/experience), Skills (technical proficiencies), Benefits, Pay. Schedule: we have schedule info: "Majority remote (WFH) with frequent travel requirements and flexibility to commute to the office as needed". Also "This is a fully remote position; however, candidates must be based in and reside in Hawaii." That's location not schedule. Schedule: remote, travel. So we can include Schedule. Benefits: "Competitive (and ever expanding) benefits for employees and dependents", "Opportunities to learn and grow – all things startups", "To get away - we all convene 1-2x / year for [optional, encouraged] retreats", "We’re actively shaping our benefits program: have a say in which benefits matter to you". Also "Competitive salary plus meaningful equity upside; salary range is $125,000-$140,000" is Pay. Thus we have Benefits and Pay. We need to avoid boilerplate like EEO, About Ready (company culture) maybe not needed. The "About Ready 🚀 Creative problem solvers..." is fluff; could be omitted as not substantive? It's about company culture but maybe not required. We can drop as it's not specific to role. The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. The "About Ready" fluff is maybe not substantive for the role; but it's still part of posting. However we can consider it boilerplate? It's not legal/EEO but it's generic marketing. Might be okay to drop? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This is not those. It's company description. Might be considered substantive? It's vague. I'd keep it maybe as a short paragraph under "About the company"? But we don't have a section for that. Could include as part of About the role? Might be okay to omit as not directly about role. Safer to keep it? The instruction: "Prefer a few substantive sections over many thin ones." If we add a section for company overview, that might be thin. I'd omit. Thus final HTML:

  About the role

  Location: Hawaii (Any Island) Ready is seeking a passionate and innovative Product Solutions Engineer to support our state customers as we rapidly expand. This person will force-multiply our ability to deliver results for key customers and drive expansion into future opportunities. You will translate customer requests into impactful features, navigate development complexities, and bridge the gap between technical feasibility and user-centric design, ensuring our customers' needs don’t fall through the cracks. This person will also contribute to Ready’s Center of Excellence through AI technology and automation. This is a fully remote position; however, candidates must be based in and reside in Hawaii.

  Responsibilities

  • Collaborate with product managers and engineers (PED) to define and prioritize product requirements, ensuring technical feasibility and alignment with user needs.
  • Capture, document, and communicate client requirements with the core team while adhering to the agreed upon format to convey priority.
  • Proactively identify and manage risks and dependencies across cross-functional teams, advocating for solutions and driving efficient execution.
  • Develop, utilize, and perform effective test strategies to ensure quality and performance of implemented features.
  • Document technical specifications and maintain clear communication with stakeholders throughout the development process.
  • Contribute to the continuous improvement of our development processes and tools, promoting a culture of innovation and agility.
  • Stay abreast of emerging technologies and industry trends, proactively suggesting opportunities for product enhancement.
  • Provide technical support and troubleshooting.
  • Conduct client training and education on Ready Software tools.
  • Work closely with engineering, product, and operations teams to optimize AI utilization, flag risks/blockers, and drive continuous improvement in workflows.

  Requirements

  • Bachelor's degree with an emphasis on computer science, engineering, or similar technical field.
  • 2-3 years experience working in an engineering role.
  • Strong understanding of Agile development methodologies and experience working in cross-functional teams.
  • Excellent communication, collaboration, and problem-solving skills.
  • Passion for building user-friendly and impactful products.
  • Ability to independently manage multiple tasks and prioritize effectively under pressure.
  • Builder mentality with proven experience in customer‑facing roles.

  Skills

  • Ability to write clean, maintainable, and efficient code in at least one relevant programming language (e.g., React, Python).
  • Demonstrated understanding of user experience (UX) principles and practices.
  • Strong analytical and data‑driven approach to problem‑solving.
  • Basic understanding of web technologies such as HTML5, CSS3, and web APIs.
  • Proficiency in AI model monitoring, data validation, and automation tooling.
  • Ability to thrive in a fast‑paced, agile environment and manage multiple priorities.
  • Excellent written and verbal communication skills.
  • Passion for user‑centered design and clean coding practice.
  • Ability to operate independently and thrive in an ambiguous environment.
  • Experience with AWS Bedrock, Python (including SQL knowledge), CI/CD (D