Front End JavaScript / TypeScript Engineer at GoGoGrandparent

Job description

About the Company GoGoGrandparent’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)! Our 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. * This is a fully remote position * Must be able to work US timezones or 4+ hours overlap with mainland US Job Summary We have a Webflow designer who owns layout and CMS. He does not write JavaScript. You will own everything that makes our Webflow pages work: registration, payments, service checks, analytics, cookies, and talking to our APIs. You will also take the code from concatenated ES5/jQuery to TypeScript with a real build pipeline, without breaking production landing pages. You 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. You need to be comfortable communicating and working directly with our marketing team and other company stakeholders. What you will actually do Product / integration Wire 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. Own multi-step registration: validation, session persistence, step navigation, auth tokens, 401 handling, partner vs consumer flows. Keep Stripe Elements, phone inputs, cookies, and tracking working across many landing-page variants. Coordinate 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. Take responsibility for our Playwright test coverage and add more tests as needed. Reading the backend (required, not optional) Open 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. Use existing route tests as a second source of truth when the handler is messy. Choose 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. When 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. Engineering Over time, migrate the codebase from JS IIFE modules to TypeScript. Replace concat + Terser with a real bundler (esbuild/Vite/Rollup). Untangle globals, jQuery, and implicit script order without a rewrite that takes the site down. What the systems look like Client We 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. Vanilla JS + jQuery, IIFEs, concatenated in a fixed file order. Playwright tests already use T