СШАFront End JavaScript / TypeScript Engineer
13 ч. назад
80k–120k USD / годСШАRemote
javascripttypescriptwebflowjqueryes5apianalyticspayments
Develop and maintain frontend JavaScript/TypeScript code for Webflow pages enabling services like registration, payments, and API interactions for a platform aiding older adults in independent living.
О компании
- ’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.
Условия
- Fully remote position
- $80k – $120k (based on location, experience and seniority)
- Paid holidays
- Personal Time-off of 15 days at start
- Engineering team retreat
- US Employees Healthcare Insurance (Medical, Dental, Vision)
- 401k Plan
Другое
- * Must be able to work US timezones or 4+ hours overlap with mainland US
- 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.
- 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.
- 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 TypeScript. App code does not.
- API
- Large TypeScript Node service. Registration and billing are not a tiny CRUD layer; controllers have real business rules.
- Auth is typically bearer tokens; some flows differ (partner vs consumer).
- Error responses are not always uniform. You have to read the handler.
- JavaScript and TypeScript in the browser (DOM, events, fetch/XHR, cookies, localStorage, CORS).
- Reading 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.
- Mapping a form to a real endpoint: required vs optional fields, nested payloads, auth headers, 4xx handling.
- Incremental migration: JS → TS, globals → modules, without freezing feature work.
- Build tooling: bundlers, source maps, minify, watch, CI.
- Working with a designer who does not write JS: explicit contracts (element IDs, data attributes).
- Playwright or similar for user flows.
- Nice to Have: Stripe.js, Webflow custom code, analytics pixels, GraphQL, having changed a small backend endpoint yourself.
- Mid to Senior level. You should be able to:
- Take a new landing flow, find the right backend endpoints, wire the page, test it, ship it — without someone translating the API for you.
- Propose a TS + bundler plan and execute it in slices.
- Push back when Webflow structure will break the JS, or when the API cannot support the page as designed.
- You own our Webflow flows end-to-end: page contract, JS, correct API usage (from reading backend code), Playwright, ship.
- You can explain, from the backend source, why a given page calls the endpoints it calls.
- App source is being migrated to TypeScript (or a clear majority, with a path for the rest).
- Build is a real pipeline: typed, module-aware, minified, source maps, documented deploy.
- https://www.gogograndparent.com/whyworkatgogoengineering
- Meaningful work: Build technology that helps older adults and people with disabilities live more independently.
- Real-world impact: Your work directly affects customers’ daily lives, from arranging transportation to accessing meals, groceries, and other essential services.
- Strong ownership: Engineers are trusted to influence solutions from initial design through deployment and production monitoring.
- Visible contribution: GoGo has a relatively small engineering team, so individual contributions have a meaningful impact on the product and company.
- Build across multiple domains: Engineers have opportunities to work across different products, services, and technical challenges rather than being confined to a single feature area.
- Direct collaboration: Work closely with product, operations, customer support, and company leadership rather than being separated by layers of management.
- Technical influence: Engineers can help shape architecture, development processes, reliability practices, and engineering standards.
- Remote-first environment: Work with an international team while maintaining meaningful collaboration and ownership.
- Growing Startup: GoGo is profitable, generates significant revenue, and continues to expand its products and customer base.
- Continuous improvement: The company invests in better testing, observability, infrastructure, security, compliance, and engineering processes.
- Experienced teammates: Work alongside senior engineers who can provide thoughtful code reviews, technical discussions, and mentorship.
- Yearly engineering retreats: The engineering team meets in person each year to strengthen relationships, collaborate, plan, and spend time together outside the usual remote environment.
- Learning budget: Receive reimbursement for any courses (Udemy, Pluralsight, etc), books, or other resources related to engineering or your work at GoGo
- If you're passionate about improving the lives of older adults and people with disabilities, we would love for you to apply!