Skip to main content
Loading
loadingbar
Loading, Please wait..!!

Senior Software Engineer: Node.js/TypeScript, Kafka & AI Coding Agents | Seattle (Remote USA) | Up t

  • Senior Software Engineer: Node.js/TypeScript, Kafka & AI Coding Agents | Seattle (Remote USA) | Up t job type Posted on: Nov 03, 2026
  • Senior Software Engineer: Node.js/TypeScript, Kafka & AI Coding Agents | Seattle (Remote USA) | Up t experience level Big Wave Digital - USA
  • Senior Software Engineer: Node.js/TypeScript, Kafka & AI Coding Agents | Seattle (Remote USA) | Up t employment type Seattle, Washington
  • Senior Software Engineer: Node.js/TypeScript, Kafka & AI Coding Agents | Seattle (Remote USA) | Up t employment type Remote
  • Senior Software Engineer: Node.js/TypeScript, Kafka & AI Coding Agents | Seattle (Remote USA) | Up t salary Full-time

Point Apply Here APPLY LATER

Curious about compensation?

Explore the historical salary trends, average pay, and estimated compensation for Senior Software Engineer: Node.js/TypeScript, Kafka & AI Coding Agents | Seattle (Remote USA) | Up t roles in Washington.

View Salary Guide →

Job Title :

Senior Software Engineer: Node.js/TypeScript, Kafka & AI Coding Agents | Seattle (Remote USA) | Up t

Job Type :

Full-Time

Job Location :

Seattle Washington United States

Remote :

Yes

Jobcon Logo Job Description :

Job Description

"Houston, we have a product problem."

\n


\n

In 1970, a room full of NASA engineers got a box of spare parts, a hard deadline and one brief: make a square filter fit a round hole, or the crew doesn't come home. Nobody gave them a spec or a ticket. They defined the problem, designed the fix from a blank page and owned the outcome.

\n


\n

That's the engineer this search is for.

\n


\n

THE COMMAND MODULE (TECH DETAILS)

\n
    \n
  • Core stack: Node.js and TypeScript across the backend services you'll own and design
  • \n
  • Messaging: Kafka, RabbitMQ and event-driven architecture, carrying high-volume business transactions between companies, where ordering, idempotency, retries and replay can't go wrong
  • \n
  • Scale: hundreds of millions of transactions processed for hundreds of customers across thousands of live trading connections, so throughput and reliability are designed in from day one
  • \n
  • AI in the product: AI built into customer workflows, writing and maintaining the data rules that used to take people weeks of manual setup, and catching errors before they hit a customer's operations
  • \n
  • AI in the workflow: coding agents are standard on every engineer's desk. You direct them, review their output line by line and own what ships
  • \n
  • Architecture ownership: you'll write the technical designs for large initiatives and plan for performance, scale and reliability up front
  • \n
  • Product surface: a self-service platform and API, so customers integrate and go live themselves
  • \n
\n


\n

MISSION BRIEF

\n

Our client is a venture-backed, AI-first B2B software company modernizing the plumbing of the supply chain. Hundreds of brands, from Fortune 500 manufacturers to fast-growing consumer names, run hundreds of millions of transactions through its platform. It's growth-stage, around 100 people and remote-first.

\n


\n

THE FLIGHT PLAN

\n

You'll take major product initiatives from problem statement to production architecture. You'll decide how the system should work, direct AI agents to help build it, and review what they produce as hard as you'd review a senior colleague's pull request. Fundamentals matter more here, not less. You'll also mentor other engineers and work closely with product to make sure what ships moves the business.

\n


\n

MISSION REQUIREMENTS

\n

The hiring manager scores every applicant against these.

\n
    \n
  1. You've owned the technical design of a major system end to end. The number one filter. You took a blank page and turned it into an architecture, rather than working inside one somebody else drew.
  2. \n
  3. Real product ownership. You defined the problem, made product decisions and shipped something that changed outcomes. Your resume should say what you designed and shipped and what changed because of it.
  4. \n
  5. Expert Node.js and TypeScript, backend first. You need to be a backend product engineer.
  6. \n
  7. Distributed systems and messaging in production. Kafka, RabbitMQ or similar in high-volume, transactional settings.
  8. \n
  9. You ship production work with AI coding agents. Agent-first day to day, better still if you've built agent features or your own agent tooling. A strong bonus, but never a stand-in for design depth.
  10. \n
  11. Growth-stage background. Ideally Series C and beyond, or Series A/B with genuine enterprise traction. Large-company-only careers won't clear the bar.
  12. \n
  13. 5 to 15 years in product engineering.
  14. \n
  15. Product-minded and a strong communicator. You hold opinions, defend them, and are comfortable having them challenged.
  16. \n
  17. SaaS background is a plus. Supply chain, logistics or B2B data exchange experience is a bigger one.
  18. \n
\n


\n

Location: Seattle, remote USA, with Pacific or Mountain time strongly preferred. US citizens or Green Card holders only, as no visa sponsorship is available.

\n


\n

"Failure is not an option. Neither is a resume that only lists tools."

\n


\n

ABORT CRITERIA

\n
    \n
  • Your experience is mostly platform, devex, infrastructure or frontend rather than product engineering
  • \n
  • Your career is mostly contract, consulting or agency work, or a run of one to two year stints
  • \n
  • You're actively running a startup or side venture you plan to keep going
  • \n
  • Your resume lists tools and responsibilities without showing what you personally owned and its impact
  • \n
\n


\n

THE PAYLOAD

\n
    \n
  • Base up to $230K plus competitive equity
  • \n
  • Remote-first, with unlimited PTO and a work-from-home lifestyle benefit
  • \n
  • Reporting into a deeply technical engineering leader
  • \n
  • Multiple hires across the team
  • \n
\n


\n

REQUESTING LAUNCH CLEARANCE

\n

Apply with your resume and answer the screening questions. Big Wave Digital is recruiting this role on behalf of our client, and every application is read by a real person. A resume that shows what you owned will beat a long one every time.

Jobcon Logo Position Details

Posted:

Nov 03, 2026

Reference Number:

1500a808f141a7b9

Employment:

Full-time

City:

Seattle

Job Origin:

ziprecruiter

Share this job:

  • linkedin

Jobcon Logo
A job sourcing event
In Dallas Fort Worth
Aug 19, 2017 9am-6pm
All job seekers welcome!

Senior Software Engineer: Node.js/TypeScript, Kafka & AI Coding Agents | Seattle (Remote USA) | Up t    Apply

Click on the below icons to share this job to Linkedin, Twitter!

Job Description

"Houston, we have a product problem."

\n


\n

In 1970, a room full of NASA engineers got a box of spare parts, a hard deadline and one brief: make a square filter fit a round hole, or the crew doesn't come home. Nobody gave them a spec or a ticket. They defined the problem, designed the fix from a blank page and owned the outcome.

\n


\n

That's the engineer this search is for.

\n


\n

THE COMMAND MODULE (TECH DETAILS)

\n
    \n
  • Core stack: Node.js and TypeScript across the backend services you'll own and design
  • \n
  • Messaging: Kafka, RabbitMQ and event-driven architecture, carrying high-volume business transactions between companies, where ordering, idempotency, retries and replay can't go wrong
  • \n
  • Scale: hundreds of millions of transactions processed for hundreds of customers across thousands of live trading connections, so throughput and reliability are designed in from day one
  • \n
  • AI in the product: AI built into customer workflows, writing and maintaining the data rules that used to take people weeks of manual setup, and catching errors before they hit a customer's operations
  • \n
  • AI in the workflow: coding agents are standard on every engineer's desk. You direct them, review their output line by line and own what ships
  • \n
  • Architecture ownership: you'll write the technical designs for large initiatives and plan for performance, scale and reliability up front
  • \n
  • Product surface: a self-service platform and API, so customers integrate and go live themselves
  • \n
\n


\n

MISSION BRIEF

\n

Our client is a venture-backed, AI-first B2B software company modernizing the plumbing of the supply chain. Hundreds of brands, from Fortune 500 manufacturers to fast-growing consumer names, run hundreds of millions of transactions through its platform. It's growth-stage, around 100 people and remote-first.

\n


\n

THE FLIGHT PLAN

\n

You'll take major product initiatives from problem statement to production architecture. You'll decide how the system should work, direct AI agents to help build it, and review what they produce as hard as you'd review a senior colleague's pull request. Fundamentals matter more here, not less. You'll also mentor other engineers and work closely with product to make sure what ships moves the business.

\n


\n

MISSION REQUIREMENTS

\n

The hiring manager scores every applicant against these.

\n
    \n
  1. You've owned the technical design of a major system end to end. The number one filter. You took a blank page and turned it into an architecture, rather than working inside one somebody else drew.
  2. \n
  3. Real product ownership. You defined the problem, made product decisions and shipped something that changed outcomes. Your resume should say what you designed and shipped and what changed because of it.
  4. \n
  5. Expert Node.js and TypeScript, backend first. You need to be a backend product engineer.
  6. \n
  7. Distributed systems and messaging in production. Kafka, RabbitMQ or similar in high-volume, transactional settings.
  8. \n
  9. You ship production work with AI coding agents. Agent-first day to day, better still if you've built agent features or your own agent tooling. A strong bonus, but never a stand-in for design depth.
  10. \n
  11. Growth-stage background. Ideally Series C and beyond, or Series A/B with genuine enterprise traction. Large-company-only careers won't clear the bar.
  12. \n
  13. 5 to 15 years in product engineering.
  14. \n
  15. Product-minded and a strong communicator. You hold opinions, defend them, and are comfortable having them challenged.
  16. \n
  17. SaaS background is a plus. Supply chain, logistics or B2B data exchange experience is a bigger one.
  18. \n
\n


\n

Location: Seattle, remote USA, with Pacific or Mountain time strongly preferred. US citizens or Green Card holders only, as no visa sponsorship is available.

\n


\n

"Failure is not an option. Neither is a resume that only lists tools."

\n


\n

ABORT CRITERIA

\n
    \n
  • Your experience is mostly platform, devex, infrastructure or frontend rather than product engineering
  • \n
  • Your career is mostly contract, consulting or agency work, or a run of one to two year stints
  • \n
  • You're actively running a startup or side venture you plan to keep going
  • \n
  • Your resume lists tools and responsibilities without showing what you personally owned and its impact
  • \n
\n


\n

THE PAYLOAD

\n
    \n
  • Base up to $230K plus competitive equity
  • \n
  • Remote-first, with unlimited PTO and a work-from-home lifestyle benefit
  • \n
  • Reporting into a deeply technical engineering leader
  • \n
  • Multiple hires across the team
  • \n
\n


\n

REQUESTING LAUNCH CLEARANCE

\n

Apply with your resume and answer the screening questions. Big Wave Digital is recruiting this role on behalf of our client, and every application is read by a real person. A resume that shows what you owned will beat a long one every time.

Loading
Please wait..!!