Careers

Client Application Development

• Perform requirements analysis and technical design for new features, translating client and internal requirements into a build-ready plan prior to implementation
• Build custom web applications on .NET 8backends with React 19 / Next.js 15 frontends
• Design and implement Azure SQLdatabase schemas, RESTful API layers, and integration endpoints
• Build structured approval workflows, document generation pipelines, and real-time analytics dashboards
• Integrate with third-party platforms via REST APIs (CRM systems, DocuSign, payment processors)
• Implement Azure AD B2Cauthentication, role-based access control, and security best practices

Cloud Infrastructure & DevOps

• Deploy and manage containerized applications using Docker, Docker Compose, and Azure Container Instances
• Write and maintain Azure BicepIaC templates for provisioning cloud resources (ACR, Key Vault, Storage Accounts, ACI)
• Build and maintain Azure DevOps CI/CD pipelinesfor automated builds, testing, and deployments
• Configure nginxreverse proxies with path-based routing, WebSocket support, and streaming/SSE passthrough
• Manage CloudflareDNS, SSL/TLS, and edge security configurations

AI & Automation Platform

• Build and maintain MCP (Model Context Protocol) serversthat enable AI agents to interact with authenticated external services
• Design and build n8n workflowsthat orchestrate multi-step business processes, API integrations, and AI agent pipelines
• Develop AI-powered chat interfaces and agent systems using LLM APIs
• Contribute to internal tooling that accelerates team productivity through intelligent automation

Integration Engineering

• Build bidirectional API integrations (e.g., CRM sync, webhook listeners, retry logic with exponential backoff)
• Implement OAuth 2.0authentication flows for third-party service connections
• Design data synchronization strategies with conflict resolution and audit trails
• Work with platforms including Atlassian (Jira/Confluence), Zoho CRM, ClientSpace, and DocuSign

What We’re Looking For

Required

• Bachelor’s Degree required for this position.
• 3+ yearsof professional software engineering experience
• Strong proficiency in TypeScript/JavaScriptand js
• Experience with Reactand modern frontend frameworks (Next.js preferred)
• Backend development experience with .NET (C#)and NestJS — you should be comfortable working across both ecosystems for API development, service architecture, and integration layers
• Working knowledge of SQL databases(schema design, query optimization, migrations)
• Experience with Dockerand containerized application deployment
• Familiarity with Gitversion control and pull request workflows
• Comfort with REST APIdesign, implementation, and integration
• Firm understanding of Sequential Script Automation vs. Reasoning-Based Automation— you should know when a workflow calls for deterministic, step-by-step scripted execution versus when to leverage LLM-driven agents that reason through decisions, evaluate context, and dynamically select tools or actions. Knowing which approach fits the problem is as important as knowing how to build either one.

AI Tooling & Workflow (Critical)

• Active, daily useof AI-assisted development tools such as Cursor, Windsurf, Claude Code, GitHub Copilot, or similar
• Applied understanding of LLMs and thinking models— not just prompting, but knowing when to use which model, how to structure context, and how to critically evaluate AI-generated output
• Ability to use AI tools for architecture exploration, code generation, debugging, test writing, and documentation— while maintaining ownership of quality and correctness
• Experience or strong interest in agentic AI workflows— multi-step processes where AI agents interact with tools, APIs, and data sources autonomously
• Working knowledge of the Model Context Protocol (MCP)— understanding how MCP servers expose tools, resources, and prompts to AI agents. Ability to author custom MCP servers that wrap third-party APIs and services, enabling AI agents to interact with authenticated external systems as structured tool interfaces
• Familiarity with OpenAPI / Swagger specifications— ability to read, write, and leverage OpenAPI definitions for rapid API integration, client generation, and as a foundation for building MCP server tool schemas
• Critical thinking about AI output: you know when to trust it, when to verify, and when to throw it away and think for yourself

Cloud & Infrastructure

• Experience with Microsoft Azureservices (or equivalent cloud platform with willingness to learn Azure)
• Familiarity with Infrastructure as Codeconcepts (Bicep, Terraform, ARM templates, or similar)
• Understanding of CI/CD pipelinesand automated deployment workflows
• Basic understanding of networking(reverse proxies, DNS, SSL/TLS, CORS)

Strong Plus

• Experience with n8n, Make (Integromat), Zapier, or similar workflow automation platforms
• Experience building or consuming MCP serversor similar protocol-based tool interfaces
• Experience with Playwrightor other browser automation frameworks
• Familiarity with the Atlassian ecosystem(Jira, Confluence APIs)
• Experience with Azure DevOps(Pipelines, Repos, Boards)
• Knowledge of Rediscaching, SendGrid email services, or Cloudflare configuration
• Experience with document generation(PDF rendering, template engines, e-signature APIs)
• Background in consulting, agency, or client-facing delivery environments
• Exposure to the healthcare or skilled nursing facility (SNF) domain — EHR/EMR systems, clinical or billing workflows. Not required; domain context will be provided.

How You’ll Work

• AI-First Development:You’ll be expected to use AI tools daily — not as a crutch, but as a lever. We care about output quality and velocity, and we expect you to use every tool at your disposal to maximize both.
• Ownership & Follow-Through: You own your tickets end-to-end — from understanding the requirement to shipping and supporting it. When something is hard or ambiguous, you push through and see it to completion rather than passing it off. We value engineers who take full accountability for their work and don’t give up when problems get difficult.
• Client-Facing Delivery:You’ll contribute to projects with real stakeholders, real deadlines, and real business impact. Clear communication and professional delivery matter.
• Documentation Culture:We maintain living documentation in Confluence, inline code comments for complex logic, and comprehensive READMEs. You’ll be expected to contribute.

Branching Strategy & Release Management

We follow a trunk-based Git branching strategy with an atomic pull request workflow. You should be comfortable with this approach and understand why it matters for velocity and code quality.

• Trunk-Based Development:Short-lived feature branches merged frequently into main. You’ll keep branches small, focused, and conflict-free — no long-running feature branches that drift from trunk.
• Atomic Pull Requests:Each PR represents a single, self-contained unit of change — reviewable, testable, and deployable on its own. You should be comfortable writing clear PR descriptions, responding to code review feedback, and reviewing your peers’ work with the same rigor.
• Environment Progression:You’ll work across Local, SIT, UAT, and occasionally Production You should understand the purpose of each stage, how configuration and secrets differ between them, and how to troubleshoot environment-specific issues without disrupting upstream.

Testing

You’ll be expected to write and maintain tests — not just run them. Quality is a shared responsibility, not something handed off to QA.

• Unit Testing:Write meaningful unit tests for business logic, services, and utility functions. You should understand mocking, test isolation, and how to write tests that catch real defects rather than just inflate coverage numbers.
• End-to-End Testing:Build and maintain E2E test suites using Playwright (or similar frameworks). You should be comfortable authoring test scenarios that validate critical user flows across the full application stack, and integrating those tests into CI/CD pipelines.

You’ll operate within a structured Agile/Scrum framework and are expected to be a fluent participant — not someone learning the basics on the job.

• Sprint Cadence:Work is organized into time-boxed sprints with sprint planning, daily standups, sprint demos, and retrospectives. You’ll be expected to commit to sprint goals and communicate early when scope or capacity shifts.
• Story Point Estimation:You’ll participate in estimation sessions using story points on the Fibonacci sequence (1, 2, 3, 5, 8, 13, 21). You should understand that story points measure relative complexity and effort — not hours — and be comfortable defending your estimates, flagging unknowns, and recalibrating as work evolves.
• Epics, Features &** User Stories:You’ll contribute to the decomposition of business requirements into well-structured work items. This means writing and refining Epics that capture large initiatives, breaking them into Features that represent deliverable capabilities, and authoring User Stories** with clear acceptance criteria that are testable and sprint-ready. You should be comfortable working with the format: “As a [persona], I want [capability], so that [business value]” — and know when a story is too large and needs to be split.
• Backlog Ownership:You’ll work closely with the Lead Developer and BA to groom and prioritize the backlog, ensuring stories are refined, estimated, and ready for sprint commitment. Proactive communication about blockers, dependencies, and technical debt is expected.
• Visibility &** Accountability:You’ll maintain accurate status on your assigned work items in Jira**, move tickets through workflow states in real-time, and ensure sprint boards reflect the true state of progress — not a retroactive update at the end of the week.

On-Call & After-Hours Availability

This role includes participation in an on-call rotation for production support. While after-hours work is infrequent, you should be prepared for:

• Hotfix &** Outage Support:** Responding to critical production issues that require immediate investigation and resolution outside of standard business hours.
• Evening Build Releases:Occasional evening deployment windows for coordinated releases to Production or UAT environments, particularly when client-facing downtime must be minimized.

Tech Stack Overviews