Senior Data Scientist
Nex · United States · 1 mo ago
RemoteRemoteEngineering$140k–$165k/yrFull-time
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. We need to extract content from posting.
First, identify sections:
- About the role: The paragraph after "About this Role" maybe. The posting includes: "Nex’s user base is growing quickly, and the amount of data we’re working with is growing even faster. We are seeking an experienced Senior Data Scientist to upgrade our analytics department, and help us understand our customer’s needs better than ever before as we launch in several new countries around the world. The ideal candidate for this role is fundamentally curious about the world, and wants to learn as much as possible about how our customers behave. We want Nex to exist at the forefront of subscription-based gaming, and give our customers the best gaming experiences for their age ranges, and the person in this role will have the opportunity to design & carry out the studies that get us there. If you want to work on a small team, for a growing company, and spend your time learning how best to provide value for our customers, we want to hear from you!"
That's about the role.
- Responsibilities: The "What You'll Do" section includes bullet points: Dive deep into customer data..., Transform questions into actions..., Design studies & automate their upkeep..., Write documentation and white papers...
We need to put each as under
- .
- Requirements: The "Qualifications" section includes required qualifications: 7+ years of experience as a Data Scientist or 9+ years of experience as a Business Analyst. Proficiency in SQL to retrieve data from a Redshift database. Proven ability to work independently, without constant guidance. Comfortable working in ambiguous environments that require iteration & investigation. Strong written communication skills. Bachelor’s degree in a quantitative field.
We can treat these as requirements.
- Preferred Qualifications: Could be under "Qualifications" or "Skills"? The instruction says we have sections: Qualifications, Skills. We could put required qualifications under "Qualifications" and preferred under "Skills"? Or we could combine. The instruction: "Use
- Dive deep into customer data: With over a million devices sold, hundreds of thousands of active subscribers and many more on the way, we’ve barely scratched the surface on how to understand our customers. We have terabytes of data, 10s of billions of rows and counting, for you to play around in.
- Transform questions into actions: We’re curious about our customers at all levels of the company, and any given question from any given team can potentially be a worthy avenue of study. Take initiative and spend your time working on taking those questions and running with them.
- Design studies & automate their upkeep: We don’t just want to learn things once—work with other members of the analytics team to make sure that the existing frameworks you come up with keep running as we move onto new ones.
- Write documentation and white papers: Communicate what matters in a manner that is clear, shareable, and can be understood at all levels of the company. Tell us what you’ve discovered, how you got there, and how we can use it.
- 7+ years of experience as a Data Scientist or 9+ years of experience as a Business Analyst.
- Proficiency in SQL to retrieve data from a Redshift database.
- Proven ability to work independently, without constant guidance.
- Comfortable working in ambiguous environments that require iteration & investigation.
- Strong written communication skills.
- Bachelor’s degree in a quantitative field.
- Proficiency in Python or R, in addition to SQL.
- Experience with machine learning tools and/or large data processing frameworks (i.e. Apache Spark).
- Experience with A/B methodology testing.
- Ability to work in cross-functional environments.
- Ability to thrive and create without the use of AI tools as a baseline.
- Creative solutions to complex problems.
- Proactive approach to projects.
- Ability to thrive in a fast-paced environment.
- Experience working with teams from different cultures and backgrounds.
- You’re an expert on your own work & can back up your results.
- Good-natured and easy to work with.
- Competitive compensation package
- Flexible working hours and vacation policy
- Product-driven culture that treasures talents and individual growth
- Front-row seat and hands-on experience with cutting edge technologies in the evolving gaming field
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Qualifications and Skills sections. We need to decide what goes where. Qualifications: likely the required qualifications. Skills: maybe the preferred qualifications and other skill sets like proficiency in Python/R, machine learning tools, A/B testing, cross-functional, ability to thrive without AI tools, etc. Also "What Sets You Apart" could be skills or personal attributes. We need to preserve all substantive information. So we need to include all bullet points. Let's extract: Required Qualifications (under Qualifications): - 7+ years of experience as a Data Scientist or 9+ years of experience as a Business Analyst. - Proficiency in SQL to retrieve data from a Redshift database. - Proven ability to work independently, without constant guidance. - Comfortable working in ambiguous environments that require iteration & investigation. - Strong written communication skills. - Bachelor’s degree in a quantitative field. Preferred Qualifications (maybe under Skills): - Proficiency in Python or R, in addition to SQL. - Experience with machine learning tools and/or large data processing frameworks (i.e. Apache Spark). - Experience with A/B methodology testing. - Ability to work in cross-functional environments. - Ability to thrive and create without the use of AI tools as a baseline. What Sets You Apart (maybe also under Skills or a separate section? Not in list but we could include under Skills as personal attributes): - Creative solutions to complex problems. - Proactive approach to projects. - Ability to thrive in a fast-paced environment. - Experience working with teams from different cultures and backgrounds. - You’re an expert on your own work & can back up your results. - Good-natured and easy to work with. We could put these under Skills as well. Benefits: The posting includes "We Offer Competitive compensation package.Flexible working hours and vacation policy.Product-driven culture that treasures talents and individual growth.Front-row seat and hands-on experience with cutting edge technologies in the evolving gaming field". Also earlier: "Location: Seattle, WA or Remote US Annual salary: $140,000 - $165,000 USD (Final base salary within this range will be determined based on job-related factors, including the candidate’s experience, skills, qualifications, and geographic location)". So we have Pay and Benefits. Pay: The salary range. Benefits: Competitive compensation package (but that's pay), flexible working hours and vacation policy, product-driven culture, front-row seat and hands-on experience with cutting edge technologies. Schedule: Not explicitly mentioned besides flexible working hours. Could be under Benefits? There's no explicit schedule. The instruction says only create Schedule section if posting actually states them. It mentions flexible working hours, which is schedule-related. Could we create a Schedule section with "Flexible working hours"? Might be okay. But we also have flexible working hours already in Benefits. Might be redundant. Better to put flexible working hours under Benefits, and not create a separate Schedule section unless there is explicit schedule like "Full-Time". The posting says Type: Full-Time. That's schedule type. Could be considered schedule. But we need to see if we should create Schedule section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." The posting states Type: Full-Time, and also mentions flexible working hours. So we could create Schedule section with "Full-Time" and maybe "Flexible working hours". However flexible working hours is more of a benefit. But we can include both. Pay: we have salary range. Benefits: we have competitive compensation package (maybe redundant with pay), product-driven culture, front-row seat and hands-on experience with cutting edge technologies, maybe also "Learn more about us at https://www.nexplayground.com/about." but that's not a benefit. We need to avoid boilerplate like EEO etc. Remove that. Also remove location? Location is metadata; we can fold into a short p or drop. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." Location is minor metadata; we could include a short p at top maybe. But we should not create a heading for location. We can include a
with location and maybe type. We need to output only HTML fragment, no /. So we can start with maybe a
for location and type, then sections. Let's structure:
Location: Seattle, WA or Remote US • Type: Full-Time
Then sections:About the role
... (the paragraph)
Responsibilities
Qualifications
Skills
Pay
Annual salary: $140,000 - $165,000 USD (Final base salary within this range will be determined based on job-related factors, including the candidate’s experience, skills, qualifications, and geographic location)