Responsibilities
- Own end-to-end technical execution for ROOM42 deliverables — websites, microsites, interactive apps, conference kiosk and panel experiences, and real-world evidence platforms
- Write and review production-quality code across the full stack; maintain a target of 50% direct hands-on contribution alongside leadership responsibilities
- Architect solutions that balance speed-to-market with long-term maintainability, security, and accessibility compliance
- Lead technical solutioning on new engagements — translating UX wireframes and creative briefs into clearly scoped, achievable builds
- Own Git workflows, branching strategy, and code review standards across all active ROOM42 builds
- Maintain CI/CD pipelines for ROOM42's primary hosting environments (WP Engine, Pantheon, Acquia, Netlify/Vercel for JAMstack); make deployments repeatable and low-risk
- Manage staging, UAT, and production environment configurations; provision and document access for all ROOM42 developers
- Identify and implement automation opportunities across the DevOps lifecycle — from scaffolding new projects to post-deploy validation
- Operate Figma MCP server integration to accelerate design handoff — extracting tokens, components, and layout specs directly into code-ready outputs; eliminating manual interpretation cycles
- Leverage AI code generation tools (GitHub Copilot, Claude Code, Cursor AI) as daily build accelerators — not novelties — across front-end, back-end, and configuration work
- Define and document ROOM42's AI-augmented build workflows for each deliverable type so the approach scales beyond a single practitioner
- Stay ahead of emerging agentic tooling (MCP servers, AI browser agents, generative UI frameworks) and evaluate when adoption creates genuine delivery leverage
- Implement AI-assisted QA automation across ROOM42 project types — visual regression testing, accessibility scanning, cross-browser checks, and functional testing pipelines
- Establish a QA automation baseline for repeatable deliverable types (CMS sites, kiosk apps, email builds) so that human QA effort concentrates on edge cases and client-specific requirements
- Triage technical defects surfaced by QA — classify root cause, assign or resolve remediation, verify fix integrity before re-advancing to UAT
- Define and maintain ROOM42's technical standards across deliverable types — coding conventions, repo structure, accessibility requirements, security baselines, deployment protocols
- Conduct code reviews for all ROOM42 developers before deliverables advance to QA; enforce standards consistently and use reviews as teaching moments
- Partner with RC's VP of Technology on standards alignment, tooling strategy, and team architecture as the practice scales
- Lead technical onboarding for new ROOM42 hires — tool access, standards orientation, and first-week productivity within two weeks of start date
- Serve as primary technical escalation point when blockers threaten delivery; resolve environment, integration, and access issues within 24 hours of identification
- Partner with Producers and TDMs on SOW scoping — translate creative and functional requirements into accurate technical estimates for hours, stack decisions, and phased rollout
- Own the technical delivery lifecycle for key ROOM42 engagement from kickoff through post-launch, work with technical delivery managers to ensure timeline integrity, milestone readiness, and handoff completeness
- Maintain a live view of technical progress across all active projects; proactively flag risks to Delivery Managers before they surface in status calls
- Drive milestone gates: work closely with QA lead to ensure that what moves from development to QA to UAT to production is actually ready — not optimistically ready
- Manage technical dependencies across concurrent projects (shared environments, overlapping APIs, licensing constraints) and surface conflicts before they collide
- Own technical documentation throughout each engagement: architecture decisions, environment setup, API integration specs, deployment runbooks — so no knowledge lives only in one person's head
- Participate in client-facing conversations where technical credibility matters — scoping sessions, risk discussions, demo walkthroughs — presenting clearly and without jargon
- Define 'done' for every deliverable type — not just 'it works' but that it is performant, accessible, secure, cross-browser validated, and visually faithful to approved design
- Own quality accountability end-to-end: if something ships broken, looks wrong, or fails an MLR technical review, this role is accountable for the root cause and the remediation
- Work with QA lead to establish and maintain a ROOM42 quality checklist for each deliverable type — covering functional, visual, performance, accessibility, and security checks — so quality is structural, not ad hoc
- Review developer output not only for code correctness but for UX implementation fidelity: does the built experience actually look and behave like the approved design?
- Lead post-launch quality reviews on major engagements; document defect patterns and translate them into upstream process improvements
- Champion performance as a quality dimension: page load, animation smoothness, kiosk responsiveness, and interactive load times are quality metrics, not afterthoughts
- Maintain zero tolerance for preventable defects reaching client UAT — own the internal quality bar so clients aren't the ones finding the obvious problems
- Speak UX fluently — understand information architecture, user flows, interaction patterns, and content hierarchy well enough to actively contribute to UX decisions, not just receive them
- Evaluate wireframes and prototypes through both a user experience lens and a technical feasibility lens simultaneously: identify where a flow creates friction before it's built, and where a design pattern creates technical debt before it ships
- Read a Figma file not just for spec values but for design intent — understand what the designer was solving for and protect that intent through every build decision, especially when specs have gaps or edge cases aren't covered
- Catch UX implementation drift before QA does: spot when a multi-step interaction is off-sequence, a loading state is missing, an error condition is unhandled, or a component is pixel-perfect in isolation but contextually broken in the live layout
- Catch visual implementation drift with the same discipline: notice when padding is off, a typeface is rendering incorrectly, a hover state feels wrong, or a component is pixel-perfect in isolation but contextually broken in the live layout
- Participating actively in UX and design reviews as a technical partner — able to say 'that interaction pattern will feel laggy on kiosk hardware' or 'here's how we can get the same UX outcome with a lighter implementation' or 'this flow needs an empty state that the design doesn't account for'
- Understand foundational UX/UI principles — user task flow design, progressive disclosure, feedback and affordance, responsive and adaptive layout, motion and timing — well enough to make confident decisions when the design file doesn't cover every scenario
- Bridge the gap between design and engineering vocabulary; translate UX intent and creative direction into precise technical implementation notes that developers can execute without ambiguity or interpretation risk
- Push back constructively when a UX or design spec is technically infeasible at the required timeline or budget — and always bring an alternative that preserves the experience intent, not just a 'no'
- Appreciate that in healthcare and pharma, the human story being told is someone's life — and that the quality of the experience we build, how it feels to use, how clearly it communicates, how gracefully it handles errors, is not separate from the mission
Requirements
- 7+ years of hands-on development experience, with at least 3 years in a technical lead, staff engineer, or architect role
- Demonstrable full-stack proficiency — not a generalist who dabbles; someone who can build, review, and unblock at every layer
- A genuine design eye with UX/UI depth: able to evaluate user flows and interaction patterns for experience quality, read a Figma file for intent, catch UX and visual implementation drift, and make confident decisions at the design-code boundary without designer supervision
- Technical delivery experience: has owned milestone tracking, risk communication, and deployment readiness across concurrent projects — not just individual coding output
- Demonstrated accountability for quality outcomes: has owned defect triage, post-launch quality reviews, and upstream process improvements when things go wrong
- Active, daily practitioner of AI code generation tools (GitHub Copilot, Cursor AI, Claude Code) — able to define team-wide workflows around them
- Hands-on experience with Figma MCP server or comparable design-to-code AI tooling; familiar with design token standards and component handoff patterns
- QA automation experience: visual regression, accessibility automation, or AI-assisted test generation in a production environment
Work Arrangement
Hybrid — New York City, Boston, Chicago, Carmel, Lambertville, San Francisco
