1

Revit Api Software Engineer Jobs in Florida (NOW HIRING)

Role: Software Engineer Type: Full-Time Location: Orlando, FL - Hybrid Reports to: Software ... Experience with Java/Jakarta EE technologies such as Servlet API, JPA, JMS, JAX-RS, JAX-WS ...

Lead Architectural Engineer is a technical and process leader within the Architectural engineering ... Revit 2. Hands-on experience with Autodesk Revit API ( C#, Dynamo scripting or Python) 3. ...

Revit Drafter

Orlando, FL ยท On-site

$53K - $75K/yr

We are seeking a talented and detail-oriented Revit Drafter to join our dynamic team. If you're ... Engineering, or a related field. Preferred Skills: * Familiarity with additional design software (e ...

Software Engineer Location: Jacksonville, FL / Alpharetta, GA / Berkeley Heights, NJ (Either ... API * Experience building Go applications backed by a relational database such as Postgres or ...

Revit Drafter

Orlando, FL ยท On-site

$53K - $75K/yr

We are seeking a talented and detail-oriented Revit Drafter to join our dynamic team. If you're ... Engineering, or a related field. Preferred Skills: * Familiarity with additional design software (e ...

Software Engineer

Tampa, FL ยท On-site

$110K - $125K/yr

Job brief Quest Diagnostics is looking for a Software Engineer to create well-designed, effective ... Experience developing Java Web Services with public API (e.g. REST, SOAP) * Proficient in object ...

Senior Software Engineer

Maitland, FL ยท On-site

$135K - $160K/yr

Designing scalable RESTful API architectures supporting high-concurrency workloads ... Software engineering standards and development practices improve team productivity and code quality.

About the Role As a Software Engineer at 4C, you'll design and build software systems that support ... Experience with Java/Jakarta EE technologies such as the Servlet API, JPA, JMS, JAX-RS, JAX-WS ...

We are hiring a Senior Software Engineer to join the Workflow Engineering Team to develop ... Experience with API creation and consumption in REST or GraphQL. * Experience with Software Design ...

Yes Position Summary Base-2 Solutions is seeking a Software Engineer to support USSOUTHCOM J26 ... The role involves developing, maintaining, and optimizing data integration pipelines, API services ...

New

Job Posting Title: Sr Software Engineer Req ID: 10149383 At Disney "We Power the Magic!" That's our ... Hands-on experience with API Gateways/API management (Google Apigee) * Excellent database skills in ...

Yes Position Summary Base-2 Solutions is seeking a Software Engineer to support USSOUTHCOM J26 ... The role involves developing, maintaining, and optimizing data integration pipelines, API services ...

New

The Software Engineer will be responsible for designing, implementing, and maintaining complex ... RESTful API design and implementation * Demonstrated experience with: * Geographic Information ...

The Software Engineer will be responsible for designing, implementing, and maintaining complex ... RESTful API design and implementation * Demonstrated experience with: * Geographic Information ...

next page

Showing results 1-20

Revit Api Software Engineer information

What is the difference between Revit Api Software Engineer vs Revit Developer?

AspectRevit Api Software EngineerRevit Developer
CredentialsBachelor's in Computer Science or related field; knowledge of Revit APISimilar credentials; often self-taught or with certifications in Revit and programming
Work EnvironmentSoftware development teams, architecture, engineering firmsDesign and BIM teams, architecture firms, construction companies
Industry UsageDevelops custom Revit tools, plugins, automation scriptsCreates Revit families, templates, and workflows

The Revit Api Software Engineer focuses on developing and maintaining Revit API-based software solutions, while the Revit Developer primarily creates Revit content and workflows. Both roles require programming skills and industry knowledge, but their core responsibilities differ in scope and application.

What are popular job titles related to Revit Api Software Engineer jobs in Florida? For Revit Api Software Engineer jobs in Florida, the most frequently searched job titles are:
What job categories do people searching Revit Api Software Engineer jobs in Florida look for? The top searched job categories for Revit Api Software Engineer jobs in Florida are:
What cities in Florida are hiring for Revit Api Software Engineer jobs? Cities in Florida with the most Revit Api Software Engineer job openings:
Infographic showing various Revit Api Software Engineer job openings in Florida as of August 2026, with employment types broken down into 100% Full Time. Highlights an 100% In-person job distribution.

Senior Software Engineer (API Integrations)

Handtevy-Pediatric Emergency Standards

Davie, FL โ€ข On-site

$112K - $148K/yr

Full-time

Medical, Dental, Vision

Re-posted 22 days ago


Job description

About Us

Handtevy is a leading provider of pediatric and adult emergency care solutions. Our SaaS platform is used by hospitals, EMS agencies, and fire departments to deliver evidence-based medication dosing, standardized clinical protocols, and real-time coordination tools for emergency medical services. Our software is used in ambulances and emergency departments every day, in moments where clarity, speed, and reliability are not optional.


Position Overview

We are hiring a Senior Software Engineer focused on Enterprise API Integrations to lead the design and delivery of our growing integration ecosystem, with a near-term focus on ePCR, narcotic (controlled substance) tracking and blood product tracking platforms used by EMS agencies and hospitals.

This role is the technical owner of how Handtevy talks to the rest of the healthcare operations stack. You will both:

  • Integrate Handtevy as a client with partner systems that already expose APIs, and
  • Expose Handtevy's APIs as the system of record for partners who need to consume our data.

You will work directly with our CTO, engineering leads, product, and partner engineering counterparts at integration partners. You will own the integration platform end-to-end: contracts, security, reliability, observability, and the partner-facing surface area.


What You'll Own

Integration architecture and delivery

  • Architect and build bidirectional integrations between Handtevy and third-party platforms.
  • Design integration patterns that fit the partner: REST, webhooks, polling with cursors, HL7 v2 (MLLP), and FHIR R4 resources where the partner supports it.
  • Build resilient sync engines: idempotent writes, retry with exponential backoff and jitter, dead-letter queues, reconciliation jobs, and replay tooling. Assume partner APIs will go down, rate-limit, change schemas without warning, or send malformed data and design accordingly.
  • Define and own the canonical internal data model that integration adapters map into and out of, so a new partner is an adapter, not a rewrite.

Handtevy's outbound API platform

  • Evolve our public-facing API into a partner platform.
  • Own API authentication and authorization for partners: OAuth 2.0 client credentials, JWT, scoped API keys, and per-tenant rate limiting.
  • Drive developer experience for partners: OpenAPI specs as the source of truth, generated client examples, Postman collections, sandbox data, and partner-facing documentation.

Reliability, security, and compliance

  • Contribute to SOC 2 controls in integration code paths: change management, access reviews, secret rotation, evidence collection.
  • Build observability into every integration: structured logs, correlation IDs that follow a record across systems, metrics on partner latency and error rates, and alerting on silent failures (a partner that stops sending data is not a healthy partner).
  • Champion test coverage, contract tests against partner sandboxes, and integration-specific chaos testing.

Cross-functional leadership

  • Partner with Product and Engineering Leads to scope integrations, define success metrics, and prioritize the integration roadmap.
  • Partner with Clinical, Customer Success, and Implementation teams on customer-specific deployment and configuration.
  • Lead technical conversations with partner engineering teams. You will be the engineer on the call when their API doesn't behave as documented.
  • Participate in architecture discussions, code reviews, sprint planning, and mentorship of other engineers.


Required Qualifications

Engineering foundation

  • Bachelor's degree in Computer Science, Engineering, or related field.
  • 5+ years of backend development, with meaningful time spent on integrations, API platforms, or partner-facing systems.
  • Strong production experience with Node.js and NestJS (or a comparable typed, modular backend framework you can demonstrate transfers cleanly).
  • Strong proficiency designing and consuming RESTful APIs, including pagination, idempotency, error contracts, and versioning strategy.
  • Deep understanding of authentication and authorization: OAuth 2.0 (authorization code, client credentials, refresh flows), JWT (signing, validation, key rotation), SSO/SAML, API keys, and mTLS.

Integration-specific depth

  • Hands-on experience designing resilient integration patterns: idempotency keys, retry strategies, dead-letter queues, circuit breakers, backpressure, eventual consistency, and reconciliation.
  • Experience with webhooks as both producer and consumer: signing, verification, replay, and at-least-once delivery semantics.
  • Experience with OpenAPI/Swagger as a contract, not just documentation.
  • Comfort reading vendor API docs critically and finding the gaps before they bite you in production.

Data, infrastructure, and tooling

  • Proficiency with relational and NoSQL databases:
    • SQL: MySQL (optional: PostgreSQL, MSSQL)
    • NoSQL: MongoDB / DocumentDB (optional: Redis, DynamoDB)
    • ORMs: TypeORM (optional: Sequelize, Prisma)
  • Experience with AWS services relevant to integrations: Aurora, SQS / SNS / EventBridge, Lambda, Secrets Manager, API Gateway, CloudWatch, S3, SES, CloudFront.
  • Hands-on with Docker, Git, and CI/CD pipelines (GitHub Actions, Bitbucket Pipelines).
  • Strong grasp of software design patterns, security best practices, and distributed system tradeoffs.
  • Excellent collaboration and written communication. You will write integration specs and partner-facing docs, not just code.


Nice to Have

  • Familiarity with healthcare interoperability standards: HL7 v2 message structures and FHIR R4 resources.
  • Awareness of HIPAA requirements as they apply to engineering.
  • Direct experience integrating with narcotic / controlled substance tracking platforms
  • Direct experience integrating with blood product tracking systems and familiarity with ISBT 128 labeling and AABB standards.
  • Familiarity with DEA controlled substance recordkeeping requirements, CSOS, and state-level PDMP concepts.
  • Integration experience with ePCR platforms (ESO, ImageTrend, Zoll, etc) or hospital EHRs (Epic, Cerner / Oracle Health, Meditech) via HL7, FHIR, or proprietary APIs.
  • Experience standing up a partner / developer portal or public API documentation site.
  • Familiarity with PHP and Laravel
  • Event-driven architecture experience: Kafka, Kinesis, EventBridge, or similar.
  • Expertise with AI-assisted development tools 
  • Observability platforms: Datadog, New Relic, or similar.
  • Prior experience in healthcare tech or another regulated industry.


Our Engineering Culture

  • We use NestJS, TypeORM, Aurora MySQL, DocumentDB, and Angular with Tailwind in production.
  • We leverage AI-assisted development (Claude Code, GitHub Copilot) and expect engineers to use these tools thoughtfully and well.
  • We invest in observability, testing, and clean architecture — not just speed.
  • Engineers have real input into tooling, architectural decisions, and technical direction.
  • We are small, mission-driven, and ship code that runs in ambulances and emergency departments. We take that seriously.


Benefits

  • Competitive salary commensurate with experience.
  • Comprehensive health, dental, and vision coverage.


How to Apply

Submit your resume and a short note about an integration you're proud of. What made it hard, what you'd do differently, and how you knew it was working in production.