Senior Fullstack Software Engineer at LVT
American Fork, UT
—
Jul 2, 2026
American Fork, UT
Jul 21, 2026
What this job asks for AI summary
A senior full-stack engineering role focused on building and maintaining both the frontend React/Next.js interfaces and the Node.js backend services — including federated GraphQL subgraphs and real-time WebSocket data flows — that enterprise customers use to interact with IoT data. The position involves end-to-end feature ownership, cross-service debugging, API design, and mentoring junior engineers. Onsite work at the American Fork, UT office is required.
Senior level · 5+ years · Provo-Orem, UT · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 2 times — it's one opening, so apply once.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 55 people in the Provo-Orem, UT area plausibly meet what this posting asks for (software developers). range 25–80
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
Most people in this occupation already list these. Still required — just not what gets you shortlisted.
What the occupation pays Median $134,095 (middle half $101,688–$168,179).
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (6)
Role is explicitly onsite at the American Fork, UT office — remote is not available. American Fork falls within the Provo-Orem, UT CBSA.
NestJS is listed as 'preferred' within the backend requirements ('NestJS preferred'), so it is marked as a preferred skill.
Knex is introduced with 'like Knex', functioning as an illustrative example of a query builder/ORM rather than a hard gate; marked preferred with common ORM alternatives listed.
Apollo Server is listed with 'or similar GraphQL ecosystems' — marked required (the GraphQL schema/resolver capability is clearly gated) with alternatives populated for the specific tool.
MySQL is listed as 'preferred' within the relational database requirement ('MySQL preferred'); however, relational database proficiency itself is a hard gate — MySQL is marked required with alternatives, consistent with the substitution-qualifier rule.
No compensation figures were provided in the posting.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.