Job description

About this role HubSync builds the platform the largest CPA and advisory firms in the country run on. The domain is unforgiving in the best way: a tax return is either right or it is not, deadlines are statutory, and our customers' busiest weeks are the ones where the software absolutely has to hold. Engineering here is AI-native as a working style, AI code review, AI-driven QA, and Claude-class coding agents are part of how software gets built, and we expect engineers to use that leverage rather than admire it. This role is a senior, full-stack product engineer who ships. You will work in a small pod, an engineering lead, a product owner who is a deep tax-domain expert, and two or three engineers, and you will own features end to end: sharpening the requirement, building it across the stack, testing it, shipping it, and standing behind it in production. What you'll do • Own features end to end. From an ambiguous requirement to shipped, tested, and monitored. Not "my part of it": the feature. • Sharpen requirements before you build. Our product owners are genuine tax experts, and part of the job is meeting them halfway: asking the question that turns domain knowledge into a spec, writing the acceptance criteria, and pushing back on a ticket that is not buildable yet. Engineers who need a perfect ticket to start will not enjoy this; engineers who make tickets better will thrive. • Build across the stack. React frontends, TypeScript/Node services, PostgreSQL, event-driven backend work on AWS. You will move to where the feature needs you. • Ship with the tests attached. Unit tests and Playwright end-to-end coverage are part of the definition of done here, not a phase that happens to your code later. • Use AI tooling aggressively. AI coding agents, AI code review, AI-assisted QA. We care about the output: engineers here ship multiples of what the same person shipped three years ago, and we hire for people who want that. • Operate what you ship. Monitoring, incident follow-through, and the fix after the fix. What success looks like We judge the first 90 days on shipped software. • By 30 days: your first feature through the full loop, requirement to production, in one module. • By 60 days: you own a feature area, and tickets you touch come out the other side clearer than they went in. • By 90 days: you are the person your pod points to when someone asks "will this ship on time," and the answer is usually yes with evidence. What makes you a fit • 5+ years building and shipping production web software, with real depth on both sides of the stack and several years operating what you built. • A delivery track record you can narrate. You have been the person who made a sprint land: you can tell the story of a specific release, what threatened it, and what you personally did about it. • TypeScript/Node and React, or near equivalents with clear evidence you cross over fast. Solid relational-database instincts (PostgreSQL or equivalent). AWS or comparable cloud experience. • Testing as a habit, not a chore. You write the tests, end-to-end included, because you have been burned by the alternative. • Daily AI-tool leverage. You use AI coding tools as a core part of how you work and can show the difference it makes. • Comfort with a dense domain. Tax, accounting, fintech, legal, or another regulated space is a plus. Curiosity about how the customer's work actually works is mandatory. • You write things down. Decisions, acceptance criteria, the reason the estimate moved. Your teammates should never have to reconstruct your reasoning from the diff. What this role is not • Not a single-layer slot. Pure-frontend or pure-backend specialists who do not want to cross the boundary will be fighting the role. • Not a maintenance queue. You will fix what you ship, but the mandate is building. Level and growth Senior individual contributor. The pods are small and the accountability is real, and engineers who show they can carry a pod's delivery have a direct path to leading one. If you want to be running a team inside a year, that path is open here and not required. Technologies TypeScript and Node.js 20 (Fastify and Express), React 18 with module federation, PostgreSQL (Aurora), AWS (Lambda, SQS, S3, ECS), event-driven distributed processing, Playwright for end-to-end testing, and an AI toolchain (Bedrock-hosted models, AI code review, agentic QA) woven through the development loop. We are an equal opportunity employer. All applicants will be considered for employment without attention to race, color, religion, sex, sexual orientation, gender identity, national origin, veteran or disability status.

Requirements

Must-haves

What you'll do • Own features end to end. From an ambiguous requirement to shipped, tested, and monitored. Not "my part of it": the feature.
Build across the stack. React frontends, TypeScript/Node services, PostgreSQL, event-driven backend work on AWS. You will move to where the feature needs you.
Ship with the tests attached. Unit tests and Playwright end-to-end coverage are part of the definition of done here, not a phase that happens to your code later.
Operate what you ship. Monitoring, incident follow-through, and the fix after the fix.
What success looks like
We judge the first 90 days on shipped software. • By 30 days: your first feature through the full loop, requirement to production, in one module.
By 60 days: you own a feature area, and tickets you touch come out the other side clearer than they went in.
By 90 days: you are the person your pod points to when someone asks "will this ship on time," and the answer is usually yes with evidence.
What makes you a fit • 5+ years building and shipping production web software, with real depth on both sides of the stack and several years operating what you built.
A delivery track record you can narrate. You have been the person who made a sprint land: you can tell the story of a specific release, what threatened it, and what you personally did about it.
TypeScript/Node and React, or near equivalents with clear evidence you cross over fast. Solid relational-database instincts (PostgreSQL or equivalent). AWS or comparable cloud experience.
Testing as a habit, not a chore. You write the tests, end-to-end included, because you have been burned by the alternative.
Daily AI-tool leverage. You use AI coding tools as a core part of how you work and can show the difference it makes.
You write things down. Decisions, acceptance criteria, the reason the estimate moved. Your teammates should never have to reconstruct your reasoning from the diff.
What this role is not • Not a single-layer slot. Pure-frontend or pure-backend specialists who do not want to cross the boundary will be fighting the role.
Not a maintenance queue. You will fix what you ship, but the mandate is building.
Level and growth
Technologies
We are an equal opportunity employer. All applicants will be considered for employment without attention to race, color, religion, sex, sexual orientation, gender identity, national origin, veteran or disability status.

Nice-to-haves

Comfort with a dense domain. Tax, accounting, fintech, legal, or another regulated space is a plus. Curiosity about how the customer's work actually works is mandatory.

Application prep

Use the role’s language and application details while tailoring your materials.

Keywords to mirror

aireacttypescriptawsnode.js

Platform: jazzhr
Effort: medium