• Build the tool surface an agent acts through, the retrieval and context layer that grounds it in the right clinical and operational data, the serving path product teams call to reach a model, and the evaluation that catches a regression before a customer does. • Take over shared components that every team depends on, providing interfaces worth depending on, and clarify the seams between the legacy platform and the newer services. • Enhance the messaging backbone; take the event bus the rest of the way, adding contract testing for service verification.

Role Description We're looking for a Senior Platform Engineer who sits at the intersection of software development and infrastructure. You'll design and build the foundation our engineering teams ship on — codifying AWS infrastructure with Terraform and Pulumi, running workloads across ECS, EKS, and EC2, and playing a central role in our migration from monolithic services to a microservices architecture. This is a hands-on role for someone who writes production-quality code, thinks in systems, and raises the bar for the engineers around them. What You’ll Do - Design, build, and maintain AWS infrastructure as code using Terraform and Pulumi, with an emphasis on reusable modules, safe change management, and multi-account/multi-environment patterns. - Operate and evolve container platforms across ECS and EC2, including cluster architecture, autoscaling, networking, and cost optimization. - Drive our migration to microservices: decompose existing services, establish golden paths for service scaffolding, CI/CD, and deployment, and partner with product engineering teams through the transition. - Build internal tooling and automation in a general-purpose language (Python, Go, or TypeScript) — this role writes real software, not just configuration. - Own and advance our observability practice in Datadog: SLOs, dashboards, alerting strategy, distributed tracing, and driving down noise so on-call is humane. - Lead incident response and post-incident reviews; turn findings into durable platform improvements. - Mentor engineers, review designs and code, and set technical direction for platform standards across teams. - Champion security, compliance, and reliability best practices appropriate to a healthcare environment. Qualifications - 10+ years in platform, infrastructure, DevOps, or SRE roles, with a strong software development background — you're comfortable being evaluated on both your code and your architecture. - Deep, production experience with Terraform and hands-on experience with Pulumi (or strong Terraform plus a compelling reason we should trust you to ramp fast). - Expert-level AWS knowledge: compute (ECS, Serverless, EC2), networking (VPC, load balancing, DNS), IAM, and the surrounding ecosystem. - Proficiency in at least one of Python, Go, or TypeScript, including testing and CI practices. - Direct experience decomposing monoliths or migrating platforms to microservices, and the scars to prove it — service boundaries, data migration, traffic cutover, rollback strategy. - Strong observability chops: metrics, logging, tracing, SLO design (Datadog experience is a plus). - Demonstrated leadership: mentoring engineers, leading cross-team initiatives, communicating clearly with both engineers and non-technical stakeholders. Requirements - Experience in regulated environments (HIPAA, SOC 2). - GitHub Actions or similar CI/CD platform experience at org scale. - Experience with release management, deployment gates, and progressive delivery (canary, blue/green). Benefits - Annual Salary up to $170,000. - Health Care Plan (Medical, Dental & Vision). - Retirement Plan (Roth 401k). - Life Insurance (Basic, Voluntary & AD&D). - Flexible PTO Policy. - Paid Holidays. - Short Term Disability. - Training & Development.

Role Description We are seeking an experienced Integration Platform Developer to design, build, and operate enterprise integrations using the Boomi AtomSphere platform. In this role you will own the full integration lifecycle — from analysis and design through development, deployment, monitoring, and ongoing support — and will partner with application teams, enterprise architects, and integration partners. The ideal candidate will combine strong hands-on Boomi expertise with broad knowledge of enterprise integration patterns, API management, and event-driven architectures. In this role you will work closely with cross-functional partners — product, design, engineering, operations, and business stakeholders — to translate ambiguous requirements into well-engineered solutions, and will be expected to raise the bar through code review, design review, and mentorship of more junior engineers. The successful candidate brings strong engineering discipline, a clear communication style, and a track record of shipping meaningful work that holds up well in production. Key Responsibilities - Design and develop Boomi integration processes, including connectors, data maps, decisions, branches, and exception handling. - Apply Boomi’s low-code patterns alongside custom scripting (Groovy, JavaScript) for complex transformations. - Build connectors and use the Boomi Connector SDK where required. - Configure and manage Atom and Molecule runtimes appropriate to workload needs. - Design and operate API management strategies using Boomi API Management. - Implement secure authentication patterns including OAuth2, mTLS, and certificate-based authentication. - Build event-driven and pub/sub patterns using Boomi Flow, Event Streams, and external messaging platforms. - Develop CI/CD pipelines for Boomi processes using Boomi’s deployment APIs, GitHub Actions, or Jenkins. - Lead migration efforts to retire legacy integrations from other middleware platforms to Boomi, planning phased cutovers, building backward-compatibility shims where needed, and ensuring each migration step is reversible and well-monitored. - Implement comprehensive monitoring, alerting, and operational dashboards, applying disciplined engineering practices and partnering closely with stakeholders to ensure outcomes are durable, well-documented, and aligned with broader team and platform standards. - Profile and optimize performance of high-volume Boomi integrations, applying systematic measurement, targeted improvements, and data-driven validation to deliver quantifiable gains in throughput, latency, or resource efficiency. - Maintain comprehensive, current technical documentation — including architecture diagrams, design decisions, configuration references, runbooks, and operational procedures — so that the system remains supportable, auditable, and easy to onboard new engineers onto over time. - Mentor junior developers and contribute to internal integration patterns and standards. Qualifications - Bachelor’s degree in Computer Science, Engineering, or a related technical discipline. - Five or more years of integration experience with strong focus on Dell Boomi AtomSphere. - Hands-on experience with Boomi processes, connectors, and Atom/Molecule runtimes. - Solid scripting skills (Groovy, JavaScript) for Boomi customization. - Working knowledge of Boomi API Management. - Experience with API security standards (OAuth2, mTLS, certificate-based). - Familiarity with event-driven integration patterns. - Hands-on experience integrating SAP, Salesforce, Workday, NetSuite, or similar SaaS platforms. - Experience with CI/CD tooling for Boomi. - Excellent troubleshooting, communication, and documentation skills. Preferred Qualifications - Boomi Professional or Architect certifications. - Exposure to Boomi Flow and Boomi DataHub. - Familiarity with multi-tenant integration patterns. - Experience with related platforms (MuleSoft, OIC, SAP CPI). - Working knowledge of FinOps and integration cost management. How to Apply Would you like to know more about this opportunity? For immediate consideration, please send your resume to [email protected] or contact us at (908) 505-3545. Learn more about Bright Vision Technologies at www.bvteck.com . Equal Employment Opportunity (EEO) Statement Bright Vision Technologies (BV Teck) is committed to equal employment opportunity (EEO) for all employees and applicants without regard to race, color, religion, sex, sexual orientation, gender identity or expression, national origin, age, genetic information, disability, veteran status, or any other protected status as defined by applicable federal, state, or local laws. This commitment extends to all aspects of employment, including recruitment, hiring, training, compensation, promotion, transfer, leaves of absence, termination, layoffs, and recall. BV Teck expressly prohibits any form of workplace harassment or discrimination. Any improper interference with employees' ability to perform their job duties may result in disciplinary action up to and including termination of employment.

Role Description Every delivery team at ECP depends on a set of shared components that none of them own. The authentication and identity layer every user passes through, the shared data services at the core of the product, and the messaging infrastructure connecting the platform are three of them, and they are not the only ones. When any of these has undocumented behavior, a reliability gap, or needs a coordinated change, the work falls to whichever team happens to be closest to it that sprint. We're standing up a platform organization to close that gap, and you'd be one of its first engineers. ECP Intelligence sits here too. It's a set of role-based agents meant to get our users out of the software and back to their communities. Today it's a strategy. Nothing has been designed or written yet. Our data warehouse, which this team also owns, will give an agent what it can see. You own what it can do. An agent that only reads is a demo. One that acts has to act as a specific user, inside that user's permissions, through the same identity and domain services every other client of the platform goes through. That is your first mandate. This is a builder role on a team of four senior engineers, reporting to the VP of Platform Engineering. You'll write the code these capabilities are made of, with a loud voice in how they get designed. The stack: - New code is Node and TypeScript. - We're migrating off a ColdFusion legacy platform, and the two will coexist for a while. - SQL Server and PostgreSQL, a mix of monolith and services, adopting domain-driven design and an event-driven architecture, all on AWS. - This is a multi-tenant HIPAA product. You won't write ColdFusion, but you will design against it, because what you write has to serve both platforms at once. What You'll Build - ECP Intelligence: You'll build the tool surface an agent acts through, the retrieval and context layer that grounds it in the right clinical and operational data, the serving path product teams call to reach a model, and the evaluation that catches a regression before a customer does. You'll also build the first agent workflows that run on it. - The shared components: Which ones we take on first is an open question, and you'd help answer it. These are systems already in production that every team depends on, with behavior nobody wrote down and boundaries nobody drew on purpose. You'll take them over, give them interfaces worth depending on, and make the seams between the legacy platform and the newer services explicit. - The messaging backbone: The event bus works, but it's only partly adopted and nobody owns it. You'd take it the rest of the way, add contract testing so a service can be verified on its own, and support it as something the other teams can build on. Qualifications - You've built shared components or platform services that other teams depended on, and you stayed accountable for them afterward. This is not a first platform role. - Real depth in domain-driven design and event-driven architecture. You can explain why a bounded context sits where it does, what an anti-corruption layer bought you, and which flavor of event-driven you were actually doing. - You've built the production systems behind an AI feature, against data that was messy, governed, and inconveniently shaped. The model itself is someone else's problem. - You've carried a pager for a system other teams depended on. - Breadth across more than one language and paradigm, with real depth in at least one. Tell us about a time you had to get productive in an unfamiliar stack fast, and what that took. - Data modeling and query performance under real load. Some of our shared components sit on the hot path for every request. - AI-augmented development is already how you work, and you know where it holds up and where it needs a human check. Preferred - Experience shipping meaningful customer-facing AI features (more than just a chatbot). - PHI or other regulated data in an AI or analytics path. - Multi-tenant SaaS at scale, with tenant isolation as a data-layer concern. - Node and TypeScript, SQL Server, PostgreSQL, AWS. - Building alongside a legacy platform mid-migration, without the luxury of waiting for it to finish. - Contract testing or service virtualization in an event-driven system. - Mentoring engineers, or wanting to grow into it. What Success Looks Like - At six months, the AI foundation is real and at least one ECP Intelligence agent workflow is running in front of customers, taking work off a caregiver's plate that they used to do by hand. - The shared components and the messaging backbone are a longer job, and that work starts once the agent foundation is in place. The measure there is that teams build on these components without having to think about them, and spend their time on their own roadmaps instead.