{"schemaVersion":"jobsearcher.job.v1","id":"0df2aa62e3d2f98d6f0afc7f","url":"https://jobsearcher.com/jobs/0df2aa62e3d2f98d6f0afc7f","canonicalUrl":"https://jobsearcher.com/jobs/0df2aa62e3d2f98d6f0afc7f","title":"Front End JavaScript / TypeScript Engineer","description":"About the role\nAbout the Company\n\nGoGoGrandparent’s (GoGo’s) mission is to help older adults live independently in their home for as long as possible. We do that by tailoring existing on demand apps to the needs of people living with mobility, visual, cognitive and dexterity impairments and letting older adults use them by making a phone call. After ordering, our service becomes a virtual caregiver that monitors the instrumental activities of daily living (mobility, meals, groceries, medication delivery & home management) for tens of thousands of older adults around the United States. We’re profitable, have been around since 2016 & haven’t raised any venture capital financing to date. The company was inspired by the cofounder’s grandmother, who still uses us to this day (she’s turning 95 in March)!\n\nOur engineering team is fully remote, tight-knit, and moves fast. You’ll work closely with founders, ship meaningful features weekly, and have real ownership over architecture, reliability, and product direction.\n\n* This is a fully remote position\n* Must be able to work US timezones or 4+ hours overlap with mainland US\n\nJob Summary\n\nWe have a Webflow designer who owns layout and CMS. He does not write JavaScript.\n\nYou will own everything that makes our Webflow pages work: registration, payments, service checks, analytics, cookies, and talking to our APIs.\n\nYou will also take the code from concatenated ES5/jQuery to TypeScript with a real build pipeline, without breaking production landing pages.\n\nYou are not a backend hire. You are expected to read our Node/TypeScript/GraphQL/REST API well enough to decide which endpoint to call, what to send, what comes back, and what happens when it fails. We do not have complete, trustworthy API documentation for this. The source, and its tests, is the documentation.\n\nYou need to be comfortable communicating and working directly with our marketing team and other company stakeholders.\n\nWhat you will actually do\n\nProduct / integration\n\nWire Webflow forms and pages to existing REST and GraphQL endpoints: callers, loved ones, membership, Stripe payment, service-area checks, grocery/home-services leads, error logging.\nOwn multi-step registration: validation, session persistence, step navigation, auth tokens, 401 handling, partner vs consumer flows.\nKeep Stripe Elements, phone inputs, cookies, and tracking working across many landing-page variants.\nCoordinate with the Webflow person on DOM IDs, required attributes, and page structure. Our form reader is DOM-driven; a wrong ID on a Webflow page is a production bug.\nTake responsibility for our Playwright test coverage and add more tests as needed.\n\nReading the backend (required, not optional)\n\nOpen the relevant route/controller in our backend (TypeScript, Express-style routes, controllers, some GraphQL) and extract: HTTP method, path, auth, request body/query, success payload, error codes and shapes.\nUse existing route tests as a second source of truth when the handler is messy.\nChoose the right endpoint for the page (create vs patch, REST vs GraphQL, payment intent vs caller update). Calling the wrong one, or omitting a field the controller actually requires, is a failed task.\nWhen the API cannot do what the page needs, write a clear request for backend (expected input/output, current behavior, what's missing). You will not be expected to own large backend changes.\n\nEngineering\n\nOver time, migrate the codebase from JS IIFE modules to TypeScript.\nReplace concat + Terser with a real bundler (esbuild/Vite/Rollup).\nUntangle globals, jQuery, and implicit script order without a rewrite that takes the site down.\nWhat the systems look like\n\nClient\n\nWe use Webflow: a visual web design and development platform that lets you create, build, and host custom websites without writing manual production code, while also supporting custom HTML, CSS, and JavaScript for advanced functionality and customization.\nVanilla JS + jQuery, IIFEs, concatenated in a fixed file order.\nPlaywright tests already use TypeScript. App code does not.\n\nAPI\n\nLarge TypeScript Node service. Registration and billing are not a tiny CRUD layer; controllers have real business rules.\nAuth is typically bearer tokens; some flows differ (partner vs consumer).\nError responses are not always uniform. You have to read the handler.\nYou Should Be Strong At\nJavaScript and TypeScript in the browser (DOM, events, fetch/XHR, cookies, localStorage, CORS).\nReading other people's TypeScript: routes, controllers, types, tests. You do not need to write production backend, but you cannot treat the API as a black box or wait for a spec.\nMapping a form to a real endpoint: required vs optional fields, nested payloads, auth headers, 4xx handling.\nIncremental migration: JS TS, globals modules, without freezing feature work.\nBuild tooling: bundlers, source maps, minify, watch, CI.\nWorking with a designer who does not write JS: explicit contracts (element IDs, data attributes).\nPlaywright or similar for user flows.\nNice to Have: Stripe.js, Webflow custom code, analytics pixels, GraphQL, having changed a small backend endpoint yourself.\nSeniority\n\nMid to Senior level. You should be able to:\n\nTake a new landing flow, find the right backend endpoints, wire the page, test it, ship it — without someone translating the API for you.\nPropose a TS + bundler plan and execute it in slices.\nPush back when Webflow structure will break the JS, or when the API cannot support the page as designed.\nHow We Will Measure Success (first 6–12 months)\nYou own our Webflow flows end-to-end: page contract, JS, correct API usage (from reading backend code), Playwright, ship.\nYou can explain, from the backend source, why a given page calls the endpoints it calls.\nApp source is being migrated to TypeScript (or a clear majority, with a path for the rest).\nBuild is a real pipeline: typed, module-aware, minified, source maps, documented deploy.\nBenefits\nFully remote position\n$80k – $120k (based on location, experience and seniority)\nPaid holidays\nPersonal Time-off of 15 days at start\nEngineering team retreat\nUS Employees\nHealthcare Insurance (Medical, Dental, Vision)\n401k Plan\nAbout the interview\n\n2-stage interview process\n\nShow more","company":"Gogograndparent","rawCompany":"gogograndparent","city":"Wilmington","state":"DE","isRemote":false,"isActive":false,"createdAt":"2026-10-16T11:33:04.527Z","occupations":[{"code":"15-1254.00","title":"Web Developers","slug":"web-developers"},{"code":"15-1252.00","title":"Software Developers","slug":"software-developers"},{"code":"15-1255.00","title":"Web and Digital Interface Designers","slug":"web-and-digital-interface-designers"}],"industries":[{"code":"541511","title":"Custom Computer Programming Services","slug":"custom-computer-programming-services"},{"code":"513210","title":"Software Publishers","slug":"software-publishers"},{"code":"541512","title":"Computer Systems Design Services","slug":"computer-systems-design-services"}],"jobPosting":{"@context":"https://schema.org","@type":"JobPosting","title":"Front End JavaScript / TypeScript Engineer","description":"About the role\nAbout the Company\n\nGoGoGrandparent’s (GoGo’s) mission is to help older adults live independently in their home for as long as possible. We do that by tailoring existing on demand apps to the needs of people living with mobility, visual, cognitive and dexterity impairments and letting older adults use them by making a phone call. After ordering, our service becomes a virtual caregiver that monitors the instrumental activities of daily living (mobility, meals, groceries, medication delivery & home management) for tens of thousands of older adults around the United States. We’re profitable, have been around since 2016 & haven’t raised any venture capital financing to date. The company was inspired by the cofounder’s grandmother, who still uses us to this day (she’s turning 95 in March)!\n\nOur engineering team is fully remote, tight-knit, and moves fast. You’ll work closely with founders, ship meaningful features weekly, and have real ownership over architecture, reliability, and product direction.\n\n* This is a fully remote position\n* Must be able to work US timezones or 4+ hours overlap with mainland US\n\nJob Summary\n\nWe have a Webflow designer who owns layout and CMS. He does not write JavaScript.\n\nYou will own everything that makes our Webflow pages work: registration, payments, service checks, analytics, cookies, and talking to our APIs.\n\nYou will also take the code from concatenated ES5/jQuery to TypeScript with a real build pipeline, without breaking production landing pages.\n\nYou are not a backend hire. You are expected to read our Node/TypeScript/GraphQL/REST API well enough to decide which endpoint to call, what to send, what comes back, and what happens when it fails. We do not have complete, trustworthy API documentation for this. The source, and its tests, is the documentation.\n\nYou need to be comfortable communicating and working directly with our marketing team and other company stakeholders.\n\nWhat you will actually do\n\nProduct / integration\n\nWire Webflow forms and pages to existing REST and GraphQL endpoints: callers, loved ones, membership, Stripe payment, service-area checks, grocery/home-services leads, error logging.\nOwn multi-step registration: validation, session persistence, step navigation, auth tokens, 401 handling, partner vs consumer flows.\nKeep Stripe Elements, phone inputs, cookies, and tracking working across many landing-page variants.\nCoordinate with the Webflow person on DOM IDs, required attributes, and page structure. Our form reader is DOM-driven; a wrong ID on a Webflow page is a production bug.\nTake responsibility for our Playwright test coverage and add more tests as needed.\n\nReading the backend (required, not optional)\n\nOpen the relevant route/controller in our backend (TypeScript, Express-style routes, controllers, some GraphQL) and extract: HTTP method, path, auth, request body/query, success payload, error codes and shapes.\nUse existing route tests as a second source of truth when the handler is messy.\nChoose the right endpoint for the page (create vs patch, REST vs GraphQL, payment intent vs caller update). Calling the wrong one, or omitting a field the controller actually requires, is a failed task.\nWhen the API cannot do what the page needs, write a clear request for backend (expected input/output, current behavior, what's missing). You will not be expected to own large backend changes.\n\nEngineering\n\nOver time, migrate the codebase from JS IIFE modules to TypeScript.\nReplace concat + Terser with a real bundler (esbuild/Vite/Rollup).\nUntangle globals, jQuery, and implicit script order without a rewrite that takes the site down.\nWhat the systems look like\n\nClient\n\nWe use Webflow: a visual web design and development platform that lets you create, build, and host custom websites without writing manual production code, while also supporting custom HTML, CSS, and JavaScript for advanced functionality and customization.\nVanilla JS + jQuery, IIFEs, concatenated in a fixed file order.\nPlaywright tests already use TypeScript. App code does not.\n\nAPI\n\nLarge TypeScript Node service. Registration and billing are not a tiny CRUD layer; controllers have real business rules.\nAuth is typically bearer tokens; some flows differ (partner vs consumer).\nError responses are not always uniform. You have to read the handler.\nYou Should Be Strong At\nJavaScript and TypeScript in the browser (DOM, events, fetch/XHR, cookies, localStorage, CORS).\nReading other people's TypeScript: routes, controllers, types, tests. You do not need to write production backend, but you cannot treat the API as a black box or wait for a spec.\nMapping a form to a real endpoint: required vs optional fields, nested payloads, auth headers, 4xx handling.\nIncremental migration: JS TS, globals modules, without freezing feature work.\nBuild tooling: bundlers, source maps, minify, watch, CI.\nWorking with a designer who does not write JS: explicit contracts (element IDs, data attributes).\nPlaywright or similar for user flows.\nNice to Have: Stripe.js, Webflow custom code, analytics pixels, GraphQL, having changed a small backend endpoint yourself.\nSeniority\n\nMid to Senior level. You should be able to:\n\nTake a new landing flow, find the right backend endpoints, wire the page, test it, ship it — without someone translating the API for you.\nPropose a TS + bundler plan and execute it in slices.\nPush back when Webflow structure will break the JS, or when the API cannot support the page as designed.\nHow We Will Measure Success (first 6–12 months)\nYou own our Webflow flows end-to-end: page contract, JS, correct API usage (from reading backend code), Playwright, ship.\nYou can explain, from the backend source, why a given page calls the endpoints it calls.\nApp source is being migrated to TypeScript (or a clear majority, with a path for the rest).\nBuild is a real pipeline: typed, module-aware, minified, source maps, documented deploy.\nBenefits\nFully remote position\n$80k – $120k (based on location, experience and seniority)\nPaid holidays\nPersonal Time-off of 15 days at start\nEngineering team retreat\nUS Employees\nHealthcare Insurance (Medical, Dental, Vision)\n401k Plan\nAbout the interview\n\n2-stage interview process\n\nShow more","datePosted":"2026-10-16T11:33:04.527Z","dateModified":"2026-10-16T11:33:04.527Z","hiringOrganization":{"@type":"Organization","name":"Gogograndparent","sameAs":"https://jobsearcher.com"},"jobLocation":{"@type":"Place","address":{"@type":"PostalAddress","addressLocality":"Wilmington","addressRegion":"DE","addressCountry":"US"}},"identifier":{"@type":"PropertyValue","name":"JobSearcher","value":"0df2aa62e3d2f98d6f0afc7f"},"url":"https://jobsearcher.com/jobs/0df2aa62e3d2f98d6f0afc7f"}}