2

Remote Cadence Design Jobs (NOW HIRING)

Expect a zero-to-one cadence. Design an API contract in the morning, ship a Postgres migration ... Remote state in Azure Storage with locking, drift detection in pipelines. Qualifications:

Cadence is building a remote care delivery system that keeps older people healthy and out of the hospital. They are seeking a Staff IT Systems Engineer to design, automate, and scale the core ...

Expect a zero-to-one cadence. Design an API contract in the morning, ship a Postgres migration ... Remote state in Azure Storage with locking, drift detection in pipelines. Qualifications:

We offer flexible remote working policy. What you'll own Operating cadence Design and run the executive operating rhythm across a distributed leadership team. This includes C-suite meeting design ...

PartsBase offers a FULLY remote environment where one can work at the forefront of where the ... sales cadence design. • Track record of driving cross-functional alignment, holding sales ...

Be Seen First

Remote Required: * 5 - 7 years of experience in DFT. * Scan-Insertion, ATPG, GLS, Pattern ... Mentor Tessent, Cadence Modus & Synopsys Tetramax * Pattern Simulation: * Without timing, with ...

US - Remote Job Title: Core Engineering - Design Engineer V PCB Layout Engineer, AR Product Team As ... Must-Have Skills 1. Senior-level experience with Cadence Allegro (v21). 2. Rigid-flex and flexible ...

next page

Showing results 1-20

Remote Cadence Design information

See salary details

$70.5K

$134.6K

$195K

How much do remote cadence design jobs pay per year?

As of Jun 29, 2026, the average yearly pay for remote cadence design in the United States is $134,577.00, according to ZipRecruiter salary data. Most workers in this role earn between $107,500.00 and $157,500.00 per year, depending on experience, location, and employer.

How does a remote Cadence Design engineer typically collaborate with distributed teams on complex projects?

Remote Cadence Design engineers often rely on collaborative tools such as version control systems, cloud-based design platforms, and regular video meetings to stay aligned with distributed teams. Effective communication is essential, as team members may work across different time zones and need to provide timely updates on project milestones, resolve technical issues, and review each other's designs. Sharing detailed documentation and maintaining clear project records are standard practices to ensure smooth handoffs and continuity. By leveraging these tools and maintaining proactive communication, remote engineers can efficiently contribute to complex electronic design automation projects.

What are the key skills and qualifications needed to thrive as a Remote Cadence Design Engineer, and why are they important?

To excel as a Remote Cadence Design Engineer, you need a strong background in electrical engineering, digital/analog circuit design, and experience with semiconductor processes, typically supported by a relevant degree. Proficiency in Cadence EDA tools (such as Virtuoso, Allegro, and OrCAD), as well as knowledge of industry standards and scripting languages, is critical. Excellent problem-solving abilities, attention to detail, and effective remote communication skills help you collaborate and deliver high-quality designs. These skills ensure accurate, efficient design workflows and successful project outcomes in distributed work environments.

What is a Remote Cadence Design job?

A Remote Cadence Design job involves working with Cadence Design Systems' electronic design automation (EDA) tools to design and verify integrated circuits, printed circuit boards, or other electronic systems from a location outside of a traditional office setting. Professionals in this role typically collaborate with engineering teams, create schematics, run simulations, and ensure that digital or analog designs meet specific requirements. Remote Cadence Design engineers leverage software such as Cadence Virtuoso, Allegro, or OrCAD for their projects and communicate with colleagues via digital platforms. This setup allows for flexibility while still contributing to complex hardware development.
More about Remote Cadence Design jobs
What cities are hiring for Remote Cadence Design jobs? Cities with the most Remote Cadence Design job openings:
What are the most commonly searched types of Cadence Design jobs? The most popular types of Cadence Design jobs are:
What states have the most Remote Cadence Design jobs? States with the most job openings for Remote Cadence Design jobs include:
Infographic showing various Remote Cadence Design job openings in the United States as of June 2026, with employment types broken down into 96% Full Time, and 4% Contract. Highlights an 37% Physical, 3% Hybrid, and 60% Remote job distribution, with an average salary of $134,577 per year, or $64.7 per hour.
Full Stack Developer

Full Stack Developer

Hillpointe

Winter Park, FL • Remote

Other

Posted 8 days ago


Job description

Full Stack Engineer


Hillpointe is hiring a Full Stack Engineer to help build HPOS, the property management platform for our vertically integrated multifamily real estate business, from scratch. This is a greenfield engineering role. You will help establish the architecture, design the data model, ship the first services, and set the patterns the rest of the platform will inherit. 
Expect a zero-to-one cadence. Design an API contract in the morning, ship a Postgres migration before lunch, push a Bicep change to staging by end of day. We optimize for engineers who can hold the full stack in their head, make sound architectural decisions, and ship working software at pace.

The Role at a Glance:

  • Scope: Schema to UI: Database design, API contracts, frontend components, infrastructure. No tier is off-limits.
  • Surface: Greenfield build: Property management platform built from scratch. Multi-tenant from day one. Operator tooling, leasing, accounting, capital markets.
  • Cadence: Zero to one: Trunk-based development, short-lived branches, feature flags, working software in staging on a daily rhythm.
  • Impact: Foundational: What you ship in the first year becomes how the platform works for the next ten.

Key Responsibilities:

  • React surfaces: First-generation operator and resident-facing applications. React 18 with TypeScript, Vite, TanStack Query v5, React Hook Form, Zod. Component composition against the PDS Foundation design system. The patterns set here will be inherited by every surface that follows.
  • Service layer: TypeScript services on Node 20 LTS with NestJS or Express. OpenAPI contracts shared with the front end through code generation. JWT and OAuth flows, RBAC enforcement, structured audit logs, request-scoped tracing. The shared libraries that every future service will depend on.
  • Postgres data model: Multi-tenant schema design on Azure Database for PostgreSQL Flexible Server. Tenant isolation strategy, normalization tradeoffs, index strategy from day one, audit trails baked into the data model. Migrations through Prisma or Knex.
  • Warehouse integration: Stand up change data capture from Postgres into the Bronze layer of Enzo, our medallion warehouse. Establish read models surfaced from Gold-layer views back into product. Contract-first design with the data team.
  • Event-driven backbone: Asynchronous workflows over Azure Service Bus. Idempotent consumers, dead-letter handling, exactly-once where the business requires it. The async patterns the rest of the platform will adopt.
  • Infrastructure and Observability: Bicep modules for App Service, Functions, Container Apps, Service Bus, Key Vault, and managed identities. Multi-stage Azure DevOps pipelines. Structured logs, OpenTelemetry, and SLO definitions in place before we ever take production traffic.
  • Stack
    • Front End: React 18 + TypeScript 5
      • React 18 with Suspense and concurrent features, TypeScript 5.x strict, Vite, TanStack Query v5, React Hook Form with Zod, the PDS Foundation design system through Figma MCP.
    • Back End: Node 20 + NestJS
      • Node 20 LTS, NestJS or Express, TypeScript strict mode, Prisma against Postgres, BullMQ on Redis for background work, OpenAPI 3.x contracts generated for both sides.
    • Data: Azure Postgres + Fabric
      • Azure Database for PostgreSQL Flexible Server, Azure Data Factory for orchestration, Microsoft Fabric lakehouse with Bronze/Silver/Gold layers, Power BI Premium, Python and PySpark on the data team.
    • Cloud: Microsoft Azure
      • App Service Premium, Function Apps, Container Apps, Service Bus with sessions, Key Vault with managed identities, Application Insights, Front Door Premium, private endpoints throughout.
    • Devops: GitHub + Azure DevOps
      • GitHub for source and PR review, Azure DevOps multi-stage YAML pipelines for CI/CD. Trunk-based development, required reviews, automated test gates, environment promotion via parameters.
    • Infrastructure: Bicep + Terraform
      • Bicep modules for first-party Azure, Terraform for cross-cloud and third-party providers. Remote state in Azure Storage with locking, drift detection in pipelines.

Qualifications: 

  • Required:
    • Five-plus years in production: building web applications. You have taken a system from greenfield to production, or rebuilt the foundations of one that needed it.
    • TypeScript depth: generics, conditional types, discriminated unions, branded types. You know when to reach for them and when to stop.
    • React expertise: hooks, render optimization, error boundaries, Suspense. You can diagnose a re-render storm and you've written a custom hook that earned its keep.
    • Production Node.js: event loop awareness, streaming and backpressure, memory profiling, graceful shutdown, structured logging.
    • Relational data modeling: schema design, normalization tradeoffs, index strategy, partitioning, query plan analysis. You catch N+1 in code review.
    • API design: REST conventions, idempotency, versioning, pagination, OpenAPI specifications, authentication patterns (OAuth 2.0, JWT, session).
    • Azure or equivalent: production experience with App Service, Functions, identity, networking, observability. AWS or GCP at the same depth is fine.
    • CI/CD and IaC discipline: pipeline-as-code, environment promotion, automated test gates, infrastructure as reviewed artifacts, no clicks in the portal.
  • Preferred:
    • Postgres extensions in production: pg_stat_statements, pgvector, pgcrypto, PostGIS, logical replication.
    • Lakehouse and BI tooling at production scale: Microsoft Fabric, Power BI Premium with DAX, Python and PySpark on the data plane.
    • Event-sourced architectures, CQRS, sagas, or domain-driven design applied to a real codebase.
    • LLM-assisted engineering: Claude Code, Cursor, or retrieval-augmented internal tooling shipped to other engineers.
    • Real estate, property management, financial services, or other regulated-industry domain experience.