You'll own how Firecrawl explains itself to developers , across docs, API reference, SDK guides, quickstarts, tutorials, cookbooks, and the technical content that lives between marketing and engineering.
\nThis role sits at the intersection of product and growth: the docs are the product surface developers hit first, and the technical content is how they discover us in the first place. You'll work closely with the growth marketing team, who owns growth and content strategy, while you own the writing itself , turning shipped features into clear documentation, and turning real product capabilities into tutorials and cookbooks that show developers what's actually possible.
\n$160,000 to $200,000/year (Range shown is for U.S.-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living.)
\nUp to 0.05%
\nFull-Time
\n4+ years writing for a technical or developer-facing product
\nUS Citizenship/Visa required
\nYou'll own everything that builds Firecrawl's authority off our own site , backlinks, digital PR, brand mentions, and the newer game of getting cited inside ChatGPT, Perplexity, Claude, and the other LLMs developers now use to discover tools. Traditional off-page SEO and GEO (generative engine optimization) are converging fast, and we want one person who can run both. You'll work closely with Eric, who owns growth strategy, while you own the off-page function end to end: outreach, partnerships, mentions, citations, and the measurement that proves it's working.
\nResponsibilities
\nRequirements
\nBenefits & Perks
\nYou'll own Firecrawl's flagship product , the scrape endpoint that turns any URL into clean, LLM-ready data with a single API call. It's the product 100k+ developers know us for, the one that put Firecrawl on the map, and the one every new AI app reaches for when it needs the web as input. Your job is to make it unbeatable: faster, more reliable, better formatted, and more delightful to integrate than anything else on the market.
\nThis isn't a maintenance role. Scrape is the front door , and the front door has to be the best part of the house. At a 26-person company, the gap between 'the scraper works' and 'developers can't imagine using anything else' is exactly one person. You're that person.
\nYou'll make calls about what gets stripped, what gets preserved, how tables and code blocks are handled, when to flatten vs. when to keep structure. These are product decisions disguised as engineering ones.
\nYou'll iterate on the extraction surface until developers stop writing their own post-processing.
\nYou'll run fast product experiments. Form a hypothesis about what would make scrape better, instrument it, ship it, measure it, decide quickly. You're comfortable making calls with imperfect data because waiting for perfect data means shipping nothing , and the competition isn't waiting.
\nYou'll raise the bar on developer experience. Firecrawl's users are technical. They notice when response formats drift, when error codes are unhelpful, when docs lag behind behavior. You notice too , and you fix it before they have to ask.
\nYou'll obsess over the output, not just the fetch. Pulling the HTML is table stakes. The product is the markdown , its structure, cleanliness, fidelity to the source, and how well it drops into an LLM prompt.
\nYou'll ship structured extraction that developers trust. Schema-based extraction, JSON mode, prompt-based extraction , developers use these to skip the LLM call entirely. They have to be reliable enough to build on.
\nYou'll dogfood relentlessly. You build with the API before you ship changes to it. You feel the friction first. You read every GitHub issue, every Discord thread, every support ticket that touches scrape , not because someone asked you to, but because that's where the product signal lives.
\nYou'll own the scrape product end-to-end. Scrape is the endpoint developers integrate first and the one they depend on most. You own how it feels , response format, latency, reliability, error messages, the markdown quality, structured extraction, every parameter, every edge case.
\nYou'll make 'just works' actually true. The web is messy. JavaScript-heavy SPAs, anti-bot walls, dynamic content, infinite scrolls, weird charsets, broken HTML. Developers don't want to know about any of it , they want clean markdown. Your job is to push the 'just works' rate from great to unbeatable, one long-tail failure mode at a time.
","enriched_at":1779318637137},{"id":"job_a7e9e080-f0a","title":"Research Engineer – Evals","source_url":"https://jobs.ashbyhq.com/firecrawl/25092c0e-9a32-4191-af79-050738213704","location":"San Francisco, CA (Hybrid) OR Remote (Americas, UTC-3 to UTC-10)","job_type":"Full time","experience_level":"senior","work_arrangement":"hybrid","category":"Engineering","description":"You'll build the evaluation systems that tell us whether Firecrawl actually works. That sounds simple. It isn't. Our core promise , convert any URL into clean, structured, LLM-ready data reliably , is hard to measure rigorously across millions of different websites, formats, and edge cases. As we layer in models and agent workflows, the question 'did that work?' gets harder, not easier.
\nThis isn't an eval role where you inherit a framework and run benchmarks. You'll design the metrics, build the pipelines, generate the datasets, and own the feedback loop from output quality back to model and product decisions. If you care about what 'good' actually means and have the engineering depth to measure it, this is the role.
\nYou'll build the eval stack from scratch. Design and own the systems that measure whether Firecrawl's outputs are actually good , across scrape, crawl, extract, and map. That means defining metrics, building pipelines, curating datasets, and integrating evals into CI/CD so regressions get caught before they ship. You build the infra yourself because you're the one who needs it to work.
\nDesign benchmarks that reflect reality. Our outputs need to hold up across millions of websites , SPAs, paywalled content, dynamic rendering, structured and unstructured formats. You'll build benchmark datasets that cover the real distribution of what our customers send us, including the edge cases that break naive approaches. Ground truth doesn't come for free , you'll design the collection and labeling systems too.
\nOwn LLM-as-judge pipelines. You'll design and validate automated judges that score extraction quality at scale, know the failure modes of LLM-based evaluation, and build the human review tooling needed when automation isn't enough. You understand the difference between an eval that measures something real and one that just flatters the system.
\nClose the loop with models and RL. Evals here aren't a reporting layer , they're a training signal. You'll work closely with the RL and Search/IR research engineers to turn quality measurements into reward signals and feedback loops that make models meaningfully better. Your benchmarks directly influence what gets trained next.
\nRun fast experiments and communicate clearly. You design experiments that test meaningful hypotheses, run them quickly, and make decisions based on results. When you have findings, anyone on the team can understand what they mean , no decoder ring required.
\nWe're looking for someone who builds their own eval infrastructure. You don't wait for tooling to appear. You write the pipelines, curate the datasets, design the rubrics, and validate the judges yourself , because you understand that infra choices directly affect what you're actually measuring. You've run evals at scale and debugged the places where they lie.
\nYou know what 'good' means for unstructured web data. You've worked with messy, real-world data before. You understand why markdown quality is hard to define, why structured extraction fidelity varies by schema, and why naive string-match metrics miss the point. You have strong opinions about what a useful benchmark actually looks like , and the rigor to validate them.
\nYou're fluent in LLM evaluation methodology. You understand LLM-as-judge systems, their correlation with human judgment, and where they break down. You've designed rubrics that hold up under adversarial inputs, built human review pipelines that scale, and know how to measure inter-rater agreement. You're not fooled by evals that only look good in aggregate.
\nYou're production-minded. You care about whether your evals reflect real production behavior, not just offline benchmarks. You've worked on systems serving real traffic and made hard tradeoffs between evaluation depth, coverage, and cost. A benchmark that doesn't represent what customers actually send isn't a benchmark worth maintaining.
\nYou'd rather run three rough experiments this week than one polished one next month. When you have results, anyone on the team can understand what they mean , and what to do next.
\nBackgrounds that tend to do well: ML engineers who've built eval or data quality systems at AI labs or applied teams. Engineers who've worked on LLM fine-tuning or RLHF pipelines and understand how feedback quality drives model improvement. People who've worked at the intersection of data infrastructure and model development. Anyone who's been the person on the team asking 'but how do we know this actually works?'
\nWe're not looking for benchmark runners. If your eval experience is running existing frameworks on existing benchmarks and reporting numbers, this isn't the right fit. We need someone who builds the frameworks and defines the benchmarks.
\nWe're not looking for people who treat evals as an afterthought. If your default workflow is to build first and evaluate later , or to treat pass rates as a proxy for actual quality , you'll struggle here. Evals are a first-class product, not a QA gate.
\nWe're not looking for researchers who need a platform team. If you expect pipelines, datasets, and labeling infrastructure to exist before you can be productive, you'll be frustrated. You build the tools you need.
\nWe're not looking for slow iterators. If your standard experiment cycle is measured in weeks, not days, you'll struggle with the pace. We need someone who can design, run, and interpret a meaningful experiment within a day or two.
\nBonus points: Any other niche expertise and skills. Previous experience at a scraping, automation, or security-focused startup. Ex-founder.
","enriched_at":1778699573696},{"id":"job_77521408-8a7","title":"Technical BDR","source_url":"https://jobs.ashbyhq.com/firecrawl/4d095906-803f-4987-a5a4-941e3f1a1600","location":"San Francisco, CA (Hybrid) OR Remote (Americas, UTC-3 to UTC-10)","job_type":"Full time","experience_level":"mid","work_arrangement":"remote","category":"Engineering","description":"You'll be the tip of the spear for Firecrawl's outbound motion , identifying, engaging, and qualifying technical buyers (engineers, data scientists, AI/ML leads) who need to turn messy web data into structured, LLM-ready output.
\nThis isn't a dial-and-smile BDR seat. You'll combine technical fluency with relentless outbound execution to open doors that only someone who speaks the buyer's language can open.
\nSalary Range: $120,000–$220,000/year OTE (Range shown is for U.S.-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living.)
\nEquity Range: Up to 0.10%
\nJob Type: Full-Time or Contract
\nExperience: 3+ years or equivalent shipped systems
\nVisa: N/A (Remote)
\nAbout Firecrawl
\nFirecrawl is the easiest way to extract data from the web. Developers use us to reliably convert URLs into LLM-ready markdown or structured data with a single API call.
\nWhat You'll Do
\nWhat We're Looking For
\nEngineer-first, BDR-second. We can teach you sales. We can't fast-track deep technical intuition. The ideal candidate has a technical background , maybe you've shipped code, built side projects, contributed to open source, or studied CS/engineering , and you're drawn to the commercial side of technology.
\nTechnically fluent. You can read code, use APIs, talk about web scraping, and understand what LLM-ready data means. You've built things , even if they're small.
\nUrgency is your default setting. You don't wait for permission, process, or perfect information. You move. You follow up. You close the loop same-day.
\nBias for action over analysis. You'd rather send 10 imperfect outbounds and learn than spend a week crafting the perfect email. Speed compounds.
\nThrives in complexity and ambiguity. You don't need a playbook to get started. You can navigate a messy prospect landscape and figure out who to talk to, what to say, and when to say it.
\nCurious and relentless. You dig into a prospect's GitHub, read their blog, understand their stack. You earn the right to their time.
\nClear communicator. You write crisp emails and run tight calls. You know when to go technical and when to zoom out.
\n_Backgrounds that often do well: Engineers who want to move into a commercial role. CS students who've done hackathons and side projects. Technical founders who've done their own outbound. Developer advocates looking for a more direct revenue path._
","enriched_at":1777033099175},{"id":"job_08821b4f-0e8","title":"Growth Operations Lead","source_url":"https://jobs.ashbyhq.com/firecrawl/0d7a5f64-4da7-4f68-844f-7c4748c5f847","location":"San Francisco, CA (Hybrid) OR Remote (Americas, UTC-3 to UTC-10)","job_type":"Full time","experience_level":"mid","work_arrangement":"remote","category":"Operations","description":"We're looking for a Growth Operations Lead to join our team. As a key member of our product growth and success department, you will be responsible for owning the operational backbone of our growth motion. This includes managing the billing lifecycle, revenue dashboards, procurement, collections, and compliance workflows. You will also be responsible for supporting enterprise deal operations and using AI to automate reporting and repetitive ops work.
\nThe ideal candidate will have 3+ years of experience in revenue operations, billing operations, or growth ops at a SaaS or usage-based company. They will be operationally relentless, comfortable owning the billing lifecycle, and able to build dashboards from raw data. They will also have experience with usage-based pricing and enterprise deal support.
\nIn this role, you will have the opportunity to work with a small, fast-moving, technical team building essential infrastructure kakapo will use to gather data on the web. You will be responsible for keeping the engine running and making it run faster. If you're the person who finds the thing that's broken before anyone notices, builds a dashboard no one asked for but everyone needs, and quietly saves the company $50K by catching a bad contract , this is your role.
\nThis is a hands-on role that requires someone who is comfortable with process docs, but also lives in the numbers and can build the reporting infrastructure. The ideal candidate will be able to own billing, dashboards, compliance, and procurement themselves, and will not need a direct report for each function. They will also be able to treat compliance as someone else's problem, and will not be intimidated by new tools.
\nWe offer a competitive salary of $90,000–$160,000/year, up to 0.05% equity, and a generous PTO policy. We also offer parental leave, wellness stipends, learning and development opportunities, and team offsites.
","enriched_at":1777033086516},{"id":"job_161e6f4d-1a5","title":"Product Researcher","source_url":"https://jobs.ashbyhq.com/firecrawl/86a64caf-f5b7-4be9-9ed0-b59fd2c1e076","location":"San Francisco, CA (Hybrid) OR Remote (Americas, UTC-3 to UTC-10)","job_type":"Full time","experience_level":"senior","work_arrangement":"remote","category":"Engineering","description":"You'll be the person who figures out what Firecrawl should build next , and why. Right now, our engineers are shipping great infrastructure, and our support and sales teams are handling inbound well. But the bigger product bets , the ones that turn a good tool into a dominant platform , are stalling because nobody has the bandwidth to do real customer discovery.
\nThis isn't a PM role where you write tickets and manage a backlog. You're in the field. You talk to customers , a lot of them. You find the patterns, source the insights, and bring them back to the team in a way that changes what we prioritize. You're the bridge between what developers are actually trying to do and what we're building.
\nTalk to customers constantly. This is the job. You're running 15-25 customer conversations a week , discovery calls, user interviews, onboarding sessions, churn conversations. You're not surveying people. You're having real conversations that uncover what they're building, where they're stuck, and what would make Firecrawl indispensable to their workflow. You develop a sixth sense for what customers say versus what they actually need.
\nFind the insights that change priorities. You don't just report what customers said , you synthesize it. You spot the patterns across dozens of conversations and turn them into clear, actionable product recommendations. "Here's the use case we're missing, here's how big it is, here's what we'd need to build, here's why it matters now." You bring receipts.
\nOwn customer discovery for new product surfaces. When the team is exploring a new direction , a new endpoint, a new pricing model, a new market segment , you're the person who goes deep. You map the landscape, talk to the right people, and come back with a clear picture of whether it's worth pursuing and how to win. You've done this at the 0-to-1 stage and you've done it at scale. You know the difference.
\nBe the voice of the customer in every product conversation. You're in the room when product and engineering decisions are being made. Not to slow things down , to make them sharper. You bring real user context that prevents the team from building technically impressive things nobody asked for.
\nClose the feedback loop. When the team ships something based on your research, you go back to the customers who informed it. You validate. You measure. You learn. Discovery isn't a one-time phase , it's a continuous cycle that compounds the more you do it.
\nCreate content from customer conversations. The best product research doubles as marketing. Customer stories, use case write-ups, product positioning insights , you naturally produce content that helps the team sell and market, not just build.
","enriched_at":1777033069165},{"id":"job_cd7e255f-1f5","title":"Dev Rel (Docs & YouTube)","source_url":"https://jobs.ashbyhq.com/firecrawl/ea5a3aa0-0ef9-4301-91b5-8322a72af775","location":"San Francisco, CA (Hybrid) OR Remote (Americas, UTC-3 to UTC-10)","job_type":"Full time","experience_level":"mid","work_arrangement":"remote","category":"Engineering","description":"You'll be the person developers learn Firecrawl from , through docs that actually help them build, YouTube tutorials they watch start to finish, and community presence that makes them feel like they're building alongside us, not just consuming our API. We have the product. We need the person who makes it impossible to not understand.
\nSalary Range: $150,000–$200,000/year (Range shown is for U.S.-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living.)
\nEquity Range: Up to 0.1%
\nLocation: San Francisco, CA or Remote (Americas, UTC-3 to UTC-10)
\nJob Type: Full-Time
\nExperience: 3+ years in developer relations, technical content, or software engineering with a content track record
\nVisa: US Citizenship/Visa required for SF; open for Remote
\nFirecrawl is the easiest way to extract data from the web. Developers use us to reliably convert URLs into LLM-ready markdown or structured data with a single API call. In just over a year, we've hit 8 figures in ARR and 100k+ GitHub stars by building the fastest way for developers to get clean, structured web data.
\nWe're a small, fast-moving, technical team building essential infrastructure for the AI era. We ship fast and deep.
\nAn engineer who can teach. You have a software engineering background and have built with APIs, SDKs, or developer tools. You know what it feels like to hit a wall in someone else's docs , and you know how to fix it.
\nA YouTube operator. You've owned a technical YouTube channel before , not just appeared in videos. You know the full workflow: scripting for retention, filming efficiently, editing for technical audiences, and building a publishing cadence that doesn't collapse under pressure.
\nFluent in the AI/ML developer ecosystem. Agents, LLM tooling, orchestration frameworks, RAG pipelines , you speak this language and you've built in it. You understand where Firecrawl fits and why developers reach for it.
\nThinks about docs as infrastructure. You understand that in an agent-first world, documentation needs to be structured for machines as much as humans. You have opinions about how to do that.
\nCommunity-connected. You have real relationships in the AI engineering or open source world , not just followers. You can open doors for Firecrawl that cold outreach can't.
\nBackgrounds that often do well: DevRel at an API-first or developer tools company, software engineer who started a technical YouTube channel, open source contributor with a content track record.
\nWe're a small team doing a lot. Roles here are loosely defined on purpose , you'll own things that don't have a clear owner yet, and that's a feature, not a bug. If you need your scope fully defined before you can move, this probably isn't the right fit. If you want to build something that matters inside one of the fastest-growing AI infrastructure companies in the world, let's talk.
\nSalary that makes sense , $150,000–$200,000/year (SF, U.S.-based), based on impact, not tenure
\nOwn a piece , Up to 0.1% equity in what you're helping build
\nGenerous PTO , 15 days mandatory, anything after 24 days, just ask (holidays excluded); take the time you need to recharge
\nParental leave , 12 weeks fully paid, for moms and dads
\nWellness stipend , $100/month for the gym, therapy, massages, or whatever keeps you human
\nLearning & Development , Expense up to $1,000/year toward anything that helps you grow professionally
\nTeam offsites , A change of scenery, minus the trust falls
\nSabbatical , 3 paid months off after 4 years, do something fun and new
\nFull coverage, no red tape , Medical, dental, and vision (100% for employees, 50% for spouse/kids) , no weird loopholes, just care that works
\nLife & Disability insurance , Employer-paid short-term disability, long-term disability, and life insurance , coverage for life's curveballs
\nSupplemental options , Optional accident, critical illness, hospital indemnity, and voluntary life insurance for extra peace of mind
\nDoctegrity telehealth , Talk to a doctor from your couch
\n401(k) plan , Retirement might be a ways off, but future-you will thank you
\nPre-tax benefits , Access to FSAs and commuter benefits (US-only) to help your wallet out a bit
\nPet insurance , Because fur babies are family too
\nSF HQ perks , Snacks, drinks, team lunches, intense ping pong, and peak startup energy
\nE-Bike transportation , A loaner electric bike to get you around the city, on us
\nApplication Review , Send us your work: a YouTube channel you've grown, docs you've owned, or technical content you've created. A quick note on what you'd fix about Firecrawl's docs or content today.
\nIntro Chat (~20 min) , Quick alignment call. We'll talk about what you've built, how you think about developer education, and what you'd tackle first.
\nDeep Dive Chat (~45 min) , Walk us through a real example: a piece of content or docs work that measurably grew developer adoption. Then a live scenario , how would you approach rewriting Firecrawl's docs for an agent-first world?
\nFounder Chat (~30 min) , Culture, pace, ownership, and how you like to work. Time for your questions too.
\nPaid Work Trial (1–2 weeks) , Build something real: a tutorial, a doc rewrite, or a short-form video. We evaluate on technical accuracy, clarity, and whether a developer would actually use it.
\nDecision , We move fast after the trial.
\nIf you want to be the voice developers learn Firecrawl from , and you have the engineering chops and content track record to back it up , this is your shot.
","enriched_at":1777033058089},{"id":"job_b490d457-f6f","title":"Product Growth Engineer","source_url":"https://jobs.ashbyhq.com/firecrawl/fe6ab2c9-0528-4751-a6dd-67467e90fc0e","location":"Remote (Americas, UTC-3 to UTC-10)","job_type":"Full time","experience_level":"senior","work_arrangement":"remote","category":"Engineering","description":"$120K – $220K • 0.01% – 0.1%
\nFirecrawl's Product Growth team runs like an engineering org. Every initiative we take on (activation flows, conversion landing pages, in-product surfaces, internal tooling) is shipped as real software by the people on this team. The backlog is long and most of it is bottlenecked on engineering capacity, not ideas.
\nWe need a senior full-stack engineer who can take on growth projects end-to-end: scope the work, build the frontend and backend, ship it to production, and iterate. Someone who can work across the stack at speed and own ambitious projects without needing a PM to break them down. This is a high-output IC role. You'll work directly with the Head of Product Growth on priorities, build alongside the team's data and growth engineers, and have direct access to core engineering for anything that needs coordination.
\nScope note: top-of-funnel work (brand, SEO content, broad marketing site) lives with the Marketing team. Your work lives closer to conversion: the pages, flows, and in-product surfaces where interested users turn into active, paying customers.
\n120,000 to 200,000/year OTE (Range shown is for U.S.-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living. You can explore how we calculate this here: https://www.firecrawl.dev/careers/compensation)
\n0.01 to 0.10%
\nFull-Time (SF) or Contract (Remote)
\n5+ years
\nUS Citizenship/Visa required for SF; N/A for Remote
\nFirecrawl is the easiest way to extract data from the web. Developers use us to reliably convert URLs into LLM-ready markdown or structured data with a single API call. In just a year, we've hit 8 figures in ARR and 90k+ GitHub stars by building the fastest way for developers to get LLM-ready data.
\nWe're a small, fast-moving, technical team building essential infrastructure super-intelligence will use to gather data on the web. We ship fast and deep.
\nStrong full-stack engineer. You ship production code across React, TypeScript, Next.js, and Node. You're comfortable in Python and SQL too. You've owned real features end-to-end, not just frontends or just APIs.
\nProduct-minded with taste. You can look at a flow or a page and tell what's broken before the data does. You care about the details, and you can shape what you're building without needing a spec handed to you.
\nGrowth-oriented. You think in funnels, activation curves, and conversion rates. You want to know how your work moved the number, not just whether it shipped. You instrument everything.
\nAI-native. You already use AI tools daily as core work infrastructure. You've pushed Claude, Copilot, or similar tools far enough to know where they help and where they don't. You use them to ship more, faster.
\nFast and scrappy. You ship working versions, not perfect plans. You know when a one-off script is better than a framework and when a quick fix is better than an abstraction. You'd rather ship four experiments this week than one polished feature next month.
\nClear communicator. You can explain what you built and why to non-technical teammates. You write good PR descriptions and document what's worth documenting.
\nYou'll own the look, feel, and experience of Firecrawl across our entire platform , from the core product UI to docs, playgrounds, and marketing pages. You take ideas from rough sketches to production-ready pages, and you ship them fast. If you care about motion, precision, and performance, you'll thrive here.
\nSalary Range: $160,000–$240,000/year (Range shown is for U.S.-based employees in San Francisco, CA. Compensation outside the U.S. is adjusted fairly based on your country's cost of living.)
\nEquity Range: Up to 0.15%
\nLocation: San Francisco, CA or Remote (Americas, UTC-3 to UTC-10)
\nJob Type: Full-Time
\nExperience: 3+ years
\nVisa: US Citizenship/Visa required
\nYou go from concept to finished product independently. You don't wait for a spec to be perfect , you ship, iterate, and make things better every day. You've worked in fast environments before and you like it that way.
\nStrong with Next.js, Tailwind, and Framer Motion. These are our core stack. You don't need to be an expert in all three on day one, but you should be dangerous in at least two and excited to go deep on the third.
\nObsessed with developer experience. Our users are developers. You understand that great design in a dev tools context means clarity, speed, and zero friction , not flashy gimmicks.
\nYou ship live projects with real users. Portfolio pieces are fine. But we want to see things people actually use , not just Dribbble shots that never saw production.
\nBackgrounds that often do well: Design engineers at developer tools companies, frontend engineers with strong design instincts, designers who code and ship their own work, or indie builders who've launched products end-to-end.
\nWhat We're NOT Looking For:
\nA Note On Pace: We operate at an absurd level of urgency because the window for what we're building won't stay open forever. If that excites you, keep reading. If it doesn't, no hard feelings , but this role probably isn't for you.
\nBenefits & Perks:
\n