ZipRecruiter

Log In

1

Nanny Authority Jobs (NOW HIRING)

Discord

Security Analyst

San Francisco, CA · On-site

$144K - $162K/yr

... than babysit it. We care about the right level of compliance for Discord, our users, and our ... Ability to work across teams and influence without authority in a fast-moving environment with ...

previous page

Showing results 41-43

All JobsPersonal Care JobsHome Child Care JobsNanny JobsNanny Authority Jobs

Nanny Authority information

See salary details

$11

$23

$36

How much do nanny authority jobs pay per hour?

As of Aug 21, 2026, the average hourly pay for nanny authority in the United States is $23.57, according to ZipRecruiter salary data. Most workers in this role earn between $18.03 and $26.92 per hour, depending on experience, location, and employer.

What is a Nanny Authority?

A Nanny Authority is a professional agency or organization that specializes in recruiting, vetting, and placing highly qualified nannies and childcare professionals with families. They often provide personalized services to match families with nannies who meet their specific needs, whether for live-in, live-out, full-time, or part-time care. The Nanny Authority ensures that candidates are thoroughly screened, experienced, and have verified references, giving families peace of mind about the quality and safety of their childcare provider.

What are the key skills and qualifications needed to thrive as a nanny, and why are they important?

To thrive as a Nanny, you need a background in child development, first aid/CPR certification, and experience caring for children of various ages. Familiarity with scheduling apps, baby monitors, and household management tools is often required. Patience, strong communication, and reliability help build trust and foster healthy relationships with both children and parents. These skills ensure a safe, nurturing, and organized environment that supports children's growth and family well-being.

How does a nanny working with an agency like Nanny Authority typically collaborate with families to establish routines and expectations?

When working through an agency such as Nanny Authority, nannies often begin by meeting with families to discuss household values, children's routines, and specific needs. Clear communication is key, and the agency usually helps facilitate these initial conversations to ensure alignment. Nannies are expected to be proactive in suggesting activities, maintaining daily schedules, and providing regular updates to parents. Building trust and establishing boundaries early on helps foster a positive, collaborative environment where both the family and the nanny can thrive.

What is the difference between Nanny Authority vs Nanny?

AspectNanny AuthorityNanny
CredentialsChildcare certifications, background checks, CPR/First AidOften similar, but may not require formal certifications
Work EnvironmentPrivate homes, family settingsPrivate homes, family settings
Employer & Industry UsageAgency or direct family hiring, focus on childcare expertiseFamily-employed, focus on daily childcare tasks
Search & Comparison IntentLooking for qualified, certified childcare providersSeeking general childcare services

In summary, Nanny Authority typically refers to highly qualified, certified childcare providers with specific credentials, whereas Nanny may refer to general childcare providers without formal certifications. Both work in private homes but differ in credentials and industry usage.

More about Nanny Authority jobs

What cities are hiring for Nanny Authority jobs?

Cities with the most Nanny Authority job openings:

What states have the most Nanny Authority jobs?

States with the most job openings for Nanny Authority jobs include:

What job categories do people searching Nanny Authority jobs look for?

The top searched job categories for Nanny Authority jobs are:

Nanny Authority jobs near you
Infographic showing various Nanny Authority job openings in the United States as of August 2026, with employment types broken down into 1% As Needed, 88% Full Time, 10% Part Time, and 1% Contract. Highlights an 87% Physical, 4% Hybrid, and 9% Remote job distribution, with an average salary of $49,027 per year, or $23.6 per hour.

Senior Principal Hardware Emulation Engineer

SambaNova

San Jose, CA • On-site

$129K - $172K/yr

Full-time

Posted 3 days ago

New

Job description

About the team

The emulation team builds the pre-silicon model of SambaNova's RDU that the software, architecture, and verification teams depend on.

About the role

SambaNova is looking for a Senior Principal Engineer to build and own the hardware emulation models for our next-generation Reconfigurable Dataflow Unit - the silicon behind our AI workload acceleration systems.

Emulation is a development platform here, not a checkbox. Our software teams bring up drivers, runtime, and compiler against the emulation model months before silicon. Our architects measure performance on it. Our verification team runs on it to get through scenarios that simulation cannot reach in useful time. When the model is fast, accurate, and available, three organizations move faster; when it is not, they wait.

Building that model is the core of the job. You will work shoulder to shoulder with the RTL design team to keep the design emulation-compliant, decide where a vendor model will do and where you need to write a custom one, and own the automation that keeps the platform running tests continuously rather than by hand. This is a senior individual-contributor role, and much of its leverage comes through other teams: you will be the person design, verification, and software engineers consult on what emulation can and should do, and the one who holds our emulator vendors to account.

Responsibilities

Build the models

  • Develop the emulation model for each new RDU generation: high-performance transactors, behavioral models, and memory models in SystemVerilog and C/C++
  • Partner with the RTL design team to keep the design emulation-compliant: review RTL and IP for constructs that will not map cleanly to the emulator, and close the gaps by substituting vendor emulation models or hand-coding custom models where no vendor model exists
  • Own model fidelity: make sure substituted and custom models track design intent closely enough that software, performance, and verification results can be trusted
  • Influence design decisions upstream so emulation-readiness is designed in rather than worked around

Own the platform, flows, and automation

  • Own the emulation environment architecture: build and runtime flows, partitioning, compile strategy, clocking, and memory configuration for each chip generation
  • Build and own the workflows that automate emulation testing on the hardware: job scheduling, regression launch, failure triage, and results reporting, so the platform runs continuously without manual babysitting
  • Own throughput and capacity: profile and remove bottlenecks in models, transactors, and testbench collateral so turnaround stays fast as the design grows
  • Own the emulator vendor relationship: drive blocking tool issues to resolution, hold the vendor accountable to our program schedule, and advise on platform selection and capacity investment

Serve the three primary use cases

  • Software and hardware co-development: deliver and sustain the platform software teams depend on for pre-silicon bring-up of drivers, runtime, and compiler, and debug hardware/software integration failures alongside them
  • Performance verification: enable workload bring-up, measurement methodology, and reproducible results, and work with architecture to correlate emulated performance against architectural models
  • Verification acceleration: partner with design verification to move long-running and full-chip regressions onto emulation reliably, including system-level and gate-level scenarios that are impractical in simulation
  • Silicon debug, secondary to the above: reproduce post-silicon issues on emulation when lab debug needs a controllable, fully visible model

Technical Leadership

  • Own the emulation methodology and mentor engineers on it, and act as the authority design, verification, and software teams consult when deciding what belongs on emulation

Required Qualifications

  • BS or MS in EE, CE, or CS with 10+ years (or equivalent) of industry experience, including deep hands-on emulation work
  • Hands-on expertise bringing up and sustaining designs on an industry-standard emulation platform such as Palladium, Veloce, or Zebu: compile flows, partitioning, debug capabilities, and performance tuning
  • Strong SystemVerilog together with C/C++, applied to building transactors, behavioral models, memory models, and co-emulation infrastructure
  • Experience making a design emulation-ready: identifying RTL and IP that will not map to the emulator, and resolving it by substituting vendor emulation models or coding custom models
  • Track record owning an emulation platform across at least one full chip program, from bring-up through tape-out, including enabling software teams to run a real stack against the pre-silicon model
  • Track record owning an emulator vendor relationship: driving blocking tool issues to resolution and evaluating and landing new platform capabilities
  • Experience applying emulation to performance analysis, to accelerating functional verification regressions, or both
  • Deep debug ability across the hardware/software boundary: able to localize a failure that could be RTL, model, transactor, flow, or software
  • Scripting and automation in Python and shell: building the regression, scheduling, and triage workflows that keep an emulation platform continuously utilized
  • Demonstrated technical leadership without formal authority: setting methodology direction across design, verification, and software teams

Preferred Qualifications

  • MS or PhD in EE, CE, or CS with 12+ years of experience
  • Depth on Cadence Palladium
  • Hands-on experience on more than one emulation platform, with judgment about the trade-offs between them
  • Machine learning accelerators, dataflow architectures, or reconfigurable silicon
  • High-speed interconnect and memory modeling: PCIe, Ethernet, HBM/DDR
  • Virtual or hybrid platforms combining emulation with instruction-accurate models
  • FPGA prototyping platforms and design partitioning for prototyping
  • Post-silicon debug, reproducing lab failures on a pre-silicon platform
  • Compiler or runtime software background, or experience embedded on a software team
  • Fluency with Claude or other AI tools applied to flow development and automation

Apply