Senior Frontend Software Engineer, Consumer Engineering
GigFinder.ai · Indiana, United States · 4 wk ago
$191k/yrFull-time
We need to extract sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use for each heading only if content present. Remove boilerplate, navigation, EEO, etc. Also remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. Also remove mention of "Originally posted on Himalayas". Also remove "For more information, visit ." etc. Also remove "Reddit is a community of communities..." maybe that's part of description but could be considered "About the role"? Actually that's generic company description; maybe we can include under "About the role". The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have an "About the role" section with description of role and team.
We need to preserve all substantive information. Let's parse the posting.
First paragraph: "Reddit is a community of communities..." That's generic about Reddit. Might be considered company overview, not role-specific. Could be included under "About the role" maybe. But we need to decide if it's substantive. It's about the company, not the role. Might be considered filler but still could be part of "About the role". However instruction: "Prefer a few substantive sections over many thin ones." We could include a short paragraph about Reddit under About the role.
Next: "The Reddit Consumer Engineering organization builds and scales the products that Reddit ors use directly to discover content, participate in communities, and connect with others. Sitting at the intersection of large-scale distributed systems and core user journeys, Product Engineers in Consumer Engineering partner directly with Product Managers, Designers, Data Scientists, ML Engineers, and Frontend Engineers to build, experiment with, and scale features that power how hundreds of millions of users discover, join, navigate, and engage with Reddit . This centralized role hires across several high-impact consumer teams, including: Core Product & Feeds: Home Experience, Recommendations & Content Discovery, Content Contribution Community & Presence: Reddit Pro, Youth Experience & Teen Safety, Creator Tools Growth & Engagement: Authentication, Notifications, Social Sharing, SEO, Onboarding. Monetization & Conversion: Paid User Acquisition, Conversion Funnel Optimization Identity & Security: Account Management, Trust & Safety"
That's role description. Good.
Then "What You'll Do" bullet list: Cross-Functional Product Architecture..., End-to-End Delivery..., Metrics & Experimentation-Led Engineering..., API & System Performance..., Technical Rigor & Modern Tooling...
That's responsibilities.
Then "Who You Are": bullet list: User-Centric Mindset..., Data-Informed & Hypothesis-Driven..., Technical Rigor at Scale..., Bias for Action..., Collaborative Communicator...
That's qualifications/skills.
Then "Technical Qualifications": bullet list: 6+ years of software development experience in one or more front end focused programming languages; Javascript, Typescript, ES6 Experience with one or more front-end web frameworks such as LIT, Polymer, React, Vue, or Angular with experience with CSS Experience with GraphQL, REST, HTTP, Thrift basics, and the ability to design and implement maintainable APIs is a plus. Modern Workflows: Experience or interest in using AI-assisted engineering tools to accelerate development workflows.
That's more specific qualifications/skills.
Then "Benefits": list: Comprehensive Healthcare Benefits and Income Replacement Programs 401k with Employer Match Global Benefit programs that fit your lifestyle, from workspace to professional development to caregiving support Family Planning Support Gender-Affirming Care Mental Health & Coaching Benefits Flexible Vacation & Paid Volunteer Time Off Generous Paid Parental Leave Pay Transparency
Then after that: "This job posting may span more than one career level. In addition to base salary, this job is eligible to receive equity in the form of restricted stock units, and depending on the position offered, it may also be eligible to receive a commission. Additionally, Reddit offers a wide range of benefits to U.S.-based employees, including medical, dental, and vision insurance, 401(k) program with employer match, generous time off for vacation, and parental leave. To learn more, please visit . To provide greater transparency to candidates, we share base salary ranges for all US-based job postings regardless of state. We set standard base pay ranges for all roles based on function, level, and country location, benchmarked against similar stage growth companies. Final offer amounts are determined by multiple factors including, skills, depth of work experience and relevant licenses/credentials, and may vary from the amounts listed below. The Base Salary Range For This Position Is $190,800$267,100 USD"
Note there is a missing comma between numbers: $190,800$267,100. Should be $190,800 - $267,100 maybe. We'll preserve as given? Probably we should keep the text exactly: "$190,800$267,100 USD". Might be a typo but we must preserve.
Then there is interview recording info, privacy policy, EEO statement, etc. Those are boilerplate to remove.
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements?, Qualifications?, Skills?, Benefits, Pay, Schedule. We have no schedule info. So we omit Schedule.
We have Benefits present. Pay present (salary range). Requirements? Could be "Technical Qualifications" maybe as Requirements. Qualifications maybe "Who You Are" or "Technical Qualifications". Skills maybe overlapped. We need to decide which sections to include based on content.
We have:
- About the role: description of team and role.
- Responsibilities: "What You'll Do" bullet list.
- Requirements: maybe "Technical Qualifications" (6+ years experience etc.) Could be considered requirements.
- Qualifications: "Who You Are" (user-centric mindset etc.) Could be qualifications.
- Skills: maybe combine with qualifications? But we have also "Technical Qualifications" includes specific tech skills. Could be Skills.
We need to avoid thin sections. Perhaps combine "Who You Are" and "Technical Qualifications" into a single "Qualifications" section, but we need to follow instruction: use headings only when posting has real, specific content for it. We have both; we could make separate sections if they are substantive.
Let's see content:
Who You Are: bullet points about mindset, data-informed, technical rigor, bias for action, collaborative communicator. That's substantive.
Technical Qualifications: bullet points about 6+ years experience, front-end languages, frameworks, GraphQL etc., AI-assisted tools. Also substantive.
Thus we can have both sections: "Qualifications" for Who You Are, and "Skills" for Technical Qualifications (or vice versa). Or we could label "Requirements" for Technical Qualifications (experience requirements) and "Skills" for specific tech skills. But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map:
- About the role: description.
- Responsibilities: What You'll Do.
- Requirements: maybe the 6+ years experience etc. (Technical Qualifications) as requirements.
- Qualifications: Who You Are (soft skills, mindset).
- Skills: maybe the specific tech skills (languages, frameworks, APIs) but that overlaps with requirements. Could combine.
Better: Requirements: 6+ years experience etc. Qualifications: Who You Are. Skills: Experience with front-end languages/frameworks, GraphQL etc. But that seems redundant.
Given we have limited time, I'll produce sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We can omit Skills if we incorporate into Requirements/Qualifications.
But we need to preserve all substantive information. If we omit Skills heading, we still need to include the content somewhere. We could put the technical skill details under Requirements or Qualifications.
Let's assign:
- About the role: includes company description and team description.
- Responsibilities: What You'll Do.
- Requirements: 6+ years experience, front-end languages, frameworks, GraphQL etc., AI-assisted tools.
- Qualifications: Who You Are (user-centric mindset, data-informed, technical rigor, bias for action, collaborative communicator).
- Benefits: list.
- Pay: base salary range.
We'll omit Schedule.
Now we need to strip boilerplate: remove "For more information, visit ." etc. Also remove "Originally posted on Himalayas". Remove EEO statements, privacy policy, interview recording, etc.
Also remove duplicated lines: The benefits list appears twice? There's a benefits list earlier and later a sentence about benefits. We'll keep the benefits list (the bullet list) and maybe not repeat the later sentence.
We need to format as HTML: use
for each heading only if content present. Remove boilerplate, navigation, EEO, etc. Also remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, application instructions. Also remove mention of "Originally posted on Himalayas". Also remove "For more information, visit ." etc. Also remove "Reddit is a community of communities..." maybe that's part of description but could be considered "About the role"? Actually that's generic company description; maybe we can include under "About the role". The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". So we can have an "About the role" section with description of role and team.
We need to preserve all substantive information. Let's parse the posting.
First paragraph: "Reddit is a community of communities..." That's generic about Reddit. Might be considered company overview, not role-specific. Could be included under "About the role" maybe. But we need to decide if it's substantive. It's about the company, not the role. Might be considered filler but still could be part of "About the role". However instruction: "Prefer a few substantive sections over many thin ones." We could include a short paragraph about Reddit under About the role.
Next: "The Reddit Consumer Engineering organization builds and scales the products that Reddit ors use directly to discover content, participate in communities, and connect with others. Sitting at the intersection of large-scale distributed systems and core user journeys, Product Engineers in Consumer Engineering partner directly with Product Managers, Designers, Data Scientists, ML Engineers, and Frontend Engineers to build, experiment with, and scale features that power how hundreds of millions of users discover, join, navigate, and engage with Reddit . This centralized role hires across several high-impact consumer teams, including: Core Product & Feeds: Home Experience, Recommendations & Content Discovery, Content Contribution Community & Presence: Reddit Pro, Youth Experience & Teen Safety, Creator Tools Growth & Engagement: Authentication, Notifications, Social Sharing, SEO, Onboarding. Monetization & Conversion: Paid User Acquisition, Conversion Funnel Optimization Identity & Security: Account Management, Trust & Safety"
That's role description. Good.
Then "What You'll Do" bullet list: Cross-Functional Product Architecture..., End-to-End Delivery..., Metrics & Experimentation-Led Engineering..., API & System Performance..., Technical Rigor & Modern Tooling...
That's responsibilities.
Then "Who You Are": bullet list: User-Centric Mindset..., Data-Informed & Hypothesis-Driven..., Technical Rigor at Scale..., Bias for Action..., Collaborative Communicator...
That's qualifications/skills.
Then "Technical Qualifications": bullet list: 6+ years of software development experience in one or more front end focused programming languages; Javascript, Typescript, ES6 Experience with one or more front-end web frameworks such as LIT, Polymer, React, Vue, or Angular with experience with CSS Experience with GraphQL, REST, HTTP, Thrift basics, and the ability to design and implement maintainable APIs is a plus. Modern Workflows: Experience or interest in using AI-assisted engineering tools to accelerate development workflows.
That's more specific qualifications/skills.
Then "Benefits": list: Comprehensive Healthcare Benefits and Income Replacement Programs 401k with Employer Match Global Benefit programs that fit your lifestyle, from workspace to professional development to caregiving support Family Planning Support Gender-Affirming Care Mental Health & Coaching Benefits Flexible Vacation & Paid Volunteer Time Off Generous Paid Parental Leave Pay Transparency
Then after that: "This job posting may span more than one career level. In addition to base salary, this job is eligible to receive equity in the form of restricted stock units, and depending on the position offered, it may also be eligible to receive a commission. Additionally, Reddit offers a wide range of benefits to U.S.-based employees, including medical, dental, and vision insurance, 401(k) program with employer match, generous time off for vacation, and parental leave. To learn more, please visit . To provide greater transparency to candidates, we share base salary ranges for all US-based job postings regardless of state. We set standard base pay ranges for all roles based on function, level, and country location, benchmarked against similar stage growth companies. Final offer amounts are determined by multiple factors including, skills, depth of work experience and relevant licenses/credentials, and may vary from the amounts listed below. The Base Salary Range For This Position Is $190,800$267,100 USD"
Note there is a missing comma between numbers: $190,800$267,100. Should be $190,800 - $267,100 maybe. We'll preserve as given? Probably we should keep the text exactly: "$190,800$267,100 USD". Might be a typo but we must preserve.
Then there is interview recording info, privacy policy, EEO statement, etc. Those are boilerplate to remove.
We need to output HTML fragment with sections: About the role, Responsibilities, Requirements?, Qualifications?, Skills?, Benefits, Pay, Schedule. We have no schedule info. So we omit Schedule.
We have Benefits present. Pay present (salary range). Requirements? Could be "Technical Qualifications" maybe as Requirements. Qualifications maybe "Who You Are" or "Technical Qualifications". Skills maybe overlapped. We need to decide which sections to include based on content.
We have:
- About the role: description of team and role.
- Responsibilities: "What You'll Do" bullet list.
- Requirements: maybe "Technical Qualifications" (6+ years experience etc.) Could be considered requirements.
- Qualifications: "Who You Are" (user-centric mindset etc.) Could be qualifications.
- Skills: maybe combine with qualifications? But we have also "Technical Qualifications" includes specific tech skills. Could be Skills.
We need to avoid thin sections. Perhaps combine "Who You Are" and "Technical Qualifications" into a single "Qualifications" section, but we need to follow instruction: use headings only when posting has real, specific content for it. We have both; we could make separate sections if they are substantive.
Let's see content:
Who You Are: bullet points about mindset, data-informed, technical rigor, bias for action, collaborative communicator. That's substantive.
Technical Qualifications: bullet points about 6+ years experience, front-end languages, frameworks, GraphQL etc., AI-assisted tools. Also substantive.
Thus we can have both sections: "Qualifications" for Who You Are, and "Skills" for Technical Qualifications (or vice versa). Or we could label "Requirements" for Technical Qualifications (experience requirements) and "Skills" for specific tech skills. But the instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can map:
- About the role: description.
- Responsibilities: What You'll Do.
- Requirements: maybe the 6+ years experience etc. (Technical Qualifications) as requirements.
- Qualifications: Who You Are (soft skills, mindset).
- Skills: maybe the specific tech skills (languages, frameworks, APIs) but that overlaps with requirements. Could combine.
Better: Requirements: 6+ years experience etc. Qualifications: Who You Are. Skills: Experience with front-end languages/frameworks, GraphQL etc. But that seems redundant.
Given we have limited time, I'll produce sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
We can omit Skills if we incorporate into Requirements/Qualifications.
But we need to preserve all substantive information. If we omit Skills heading, we still need to include the content somewhere. We could put the technical skill details under Requirements or Qualifications.
Let's assign:
- About the role: includes company description and team description.
- Responsibilities: What You'll Do.
- Requirements: 6+ years experience, front-end languages, frameworks, GraphQL etc., AI-assisted tools.
- Qualifications: Who You Are (user-centric mindset, data-informed, technical rigor, bias for action, collaborative communicator).
- Benefits: list.
- Pay: base salary range.
We'll omit Schedule.
Now we need to strip boilerplate: remove "For more information, visit ." etc. Also remove "Originally posted on Himalayas". Remove EEO statements, privacy policy, interview recording, etc.
Also remove duplicated lines: The benefits list appears twice? There's a benefits list earlier and later a sentence about benefits. We'll keep the benefits list (the bullet list) and maybe not repeat the later sentence.
We need to format as HTML: use for each heading, then content: either
for prose or
- for lists. We need to preserve all substantive information: ensure we keep all bullet points. Let's extract bullet points. Responsibilities (What You'll Do): - Cross-Functional Product Architecture: Partner closely with Product Management, Product Design, Data Science, and Client Engineers (iOS/Android/Web) to translate business and user needs into reliable, low-latency technical solutions. - End-to-End Delivery: Own the full software lifecycle for major product initiatives from technical design docs and API contracts to development, testing, rollout, and observability. - Metrics & Experimentation-Led Engineering: Design, build, and evaluate A/B experiments. Work with tools like BigQuery, HEX, or Firebase to analyze user behavior, conversion funnels, and retention loops to make data-backed engineering decisions. - API & System Performance: Build and maintain scalable APIs (GraphQL, REST, gRPC) and distributed backend services optimized for client consumption and consumer UI performance. - Technical Rigor & Modern Tooling: Establish engineering best practices, improve developer workflows, mentor teammates, and use modern, AI-integrated tools to ship high-quality products efficiently. Who You Are (Qualifications): - User-Centric Mindset: An advocate for the user with an intuitive feel for product usability, interaction design, social dynamics, and user growth loops. You care deeply about why a feature is being built and its impact on the end user. - Data-Informed & Hypothesis-Driven: Comfortable working alongside Data Scientists and PMs to design experiments, establish core performance metrics, and iterate quickly based on real-time feedback. - Technical Rigor at Scale: 5+ years of hands-on backend development experience building and operating large-scale distributed serving systems in high-concurrency environments. - Bias for Action: Self-directed, innovative, and comfortable navigating ambiguity in fast-paced product environments where balancing velocity with system reliability is essential. - Collaborative Communicator: Outstanding communication skills with a track record of driving cross-functional alignment in fully remote or hybrid team environments. Technical Qualifications (Requirements): - 6+ years of software development experience in one or more front end focused programming languages; Javascript, Typescript, ES6 - Experience with one or more front-end web frameworks such as LIT, Polymer, React, Vue, or Angular with experience with CSS - Experience with GraphQL, REST, HTTP, Thrift basics, and the ability to design and implement maintainable APIs is a plus. - Modern Workflows: Experience or interest in using AI-assisted engineering tools to accelerate development workflows. Note: The first bullet has a semicolon then list. We'll keep as is. Benefits: - Comprehensive Healthcare Benefits and Income Replacement Programs - 401k with Employer Match - Global Benefit programs that fit your lifestyle, from workspace to professional development to caregiving support - Family Planning Support - Gender-Affirming Care - Mental Health & Coaching Benefits - Flexible Vacation & Paid Volunteer Time Off - Generous Paid Parental Leave - Pay Transparency We could also include the later sentence about medical/dental/vision etc but it's duplicate; we can ignore. Pay: - The Base