1

Contract Next Js Developer Jobs in Austin, TX (NOW HIRING)

React + Next Program Manager

Austin, TX · On-site

$127K - $165K/yr

... Next.js application layers. Translate business and content requirements into structured technical initiatives with clear milestones and measurable outcomes. Coordinate across engineering, design ...

Front End Developer

Austin, TX · On-site

$120 - $160/hr

What You'll DoDesign, build, and maintain storefront features using Next.js 16 (App Router, Server ... practicesMentor junior developers and contribute to technical documentation and coding ...

New

Senior Software Engineer

Austin, TX · On-site

$121K - $160K/yr

  • PTO

... Next.js, TypeScript, Tailwind, and shadcn/ui. * Build backend services and APIs using NestJS, TypeScript, PostgreSQL, Drizzle ORM, and shared Zod contracts. * Model complex operational domains ...

... and developer ergonomics. Qualifications : Required : • Meaningful experience building production web apps with TypeScript / React / Next.js and Postgres (impact > exact years). • Ability to ...

... and developer ergonomics. Qualifications : Required : • Meaningful experience building production web apps with TypeScript / React / Next.js and Postgres (impact > exact years) • Ability to ...

This is a US-based, remote-friendly contract-to-hire opportunity for high-performing engineers. WHAT YOU WILL DO - Build and maintain full-stack features across the frontend using React, Next.js, and ...

This is a US-based, remote-friendly contract-to-hire opportunity for high-performing engineers. WHAT YOU WILL DO - Build and maintain full-stack features across the frontend using React, Next.js, and ...

We have an established technical direction and a modern stack (including Next.js), and we need a seasoned developer who can jump in, contribute high-quality code, and offer smart perspectives on how ...

next page

Showing results 1-20

Contract Next Js Developer information

See Austin, TX salary details

$10

$57

$82

How much do contract next js developer jobs pay per hour?

As of Aug 20, 2026, the average hourly pay for contract next js developer in Austin, TX is $57.72, according to ZipRecruiter salary data. Most workers in this role earn between $48.85 and $63.12 per hour, depending on experience, location, and employer.

What is the difference between Contract Next Js Developer vs Contract React Developer?

AspectContract Next Js DeveloperContract React Developer
Required SkillsNext.js, React, JavaScript, SSR, SEO optimizationReact, JavaScript, SPA development, UI/UX design
Work EnvironmentWeb development projects, server-side rendering, full-stack rolesFront-end development, client-side applications, UI focus
Industry UsageTech companies, startups, agencies requiring SEO-friendly sitesWeb apps, SaaS, dashboards, client-facing interfaces

Contract Next Js Developers specialize in server-side rendering and SEO optimization using Next.js, while Contract React Developers focus on building interactive, client-side React applications. Both roles require strong JavaScript skills, but Next.js developers often work on full-stack projects with SSR, whereas React developers typically focus on front-end UI development.

What are popular job titles related to Contract Next Js Developer jobs in Austin, TX?

For Contract Next Js Developer jobs in Austin, TX, the most frequently searched job titles are:

What job categories do people searching Contract Next Js Developer jobs in Austin, TX look for?

The top searched job categories for Contract Next Js Developer jobs in Austin, TX are:

What cities near Austin, TX are hiring for Contract Next Js Developer jobs?

Cities near Austin, TX with the most Contract Next Js Developer job openings:

React + Next Program Manager

1 point system

Austin, TX • On-site

$127K - $165K/yr

Contractor

Re-posted yesterday


Job description

What you’ll do:
Program leadership for web experience delivery
Drive end‑to‑end execution of initiatives that span the CMS, design system, and Next.js application layers.
Translate business and content requirements into structured technical initiatives with clear milestones and measurable outcomes.
Coordinate across engineering, design, content strategy, SEO, and marketing to ensure cohesive delivery.
Manage dependencies across CMS schema changes, API integrations, front‑end components, and deployment workflows.
Identify risks related to content migrations, breaking API changes, caching strategies, and release timing.
Technical partnership in a Next.js + headless CMS environment
Participate in architectural discussions involving rendering strategies (SSR, SSG, ISR), routing, caching, and performance optimization.
Understand CMS content modeling, API querying models (REST/GROG/GraphQL), and integration patterns well enough to challenge assumptions and unblock teams.
Collaborate with engineering leads to ensure front‑end and CMS changes align with long‑term platform direction.
Use analytics, Core Web Vitals, A/B testing data, and telemetry to guide prioritization and measure success.
Support teams in adopting best practices for accessibility, SEO, and performance.
Communication and stakeholder alignment
Produce clear written communication: program briefs, status updates, migration plans, and decision records.
Ability to translate business and product requirements into structured delivery plans, epics, and tickets in Jira.
Simplify complex technical issues—such as rendering tradeoffs or CMS schema impacts—for non‑technical stakeholders.
Align engineering, design, and content teams around timelines, expectations, and quality standards.
Facilitate decision‑making around content workflows, release processes, and cross‑team dependencies.
Operational excellence for web platforms
Coordinate postmortems for production issues, including rendering failures, broken content, or CMS outages, and drive long‑term fixes.
Improve processes around content publishing, preview environments, QA workflows, and deployment pipelines.
Champion performance, reliability, and accessibility as core pillars of the web experience.
Promote consistent use of design systems, component libraries, and CMS governance.