Platform and Developer Experience Engineer

About Workweek

Workweek is revolutionizing how business leaders connect, learn, and operate by integrating distinct personalities, unparalleled expertise, and a vibrant community into a one-of-a-kind professional networking platform.

Our Approach

At Workweek, we build brands and audiences in specialized B2B sectors by providing expert content crafted by industry practitioners who have actually done the job. Once credibility and a sizable audience are established through our unique content, we further support these sectors by offering exclusive professional memberships. These memberships provide category-leading value, enabling leaders to connect with peers, access a comprehensive library of educational content, and utilize tools and services that streamline daily operations.

About the role

Most platform roles hand you a backlog of tickets. This one hands you a mandate.

We're moving to a model where small, autonomous teams — including non-engineers using Claude Code and Cursor — ship experiments fast. That only works if the infrastructure underneath is safe: if anyone on the team can build and ship without accidentally corrupting data, breaking the design system, or losing the ability to roll things back.

This role exists to build that infrastructure. You are not building features. You are building the system that makes it safe for everyone else to build features fast. This is a high-leverage, low-visibility role. The best outcome is that the team never notices you exist — because nothing breaks. You'll work closely with our engineering lead and report to our Director of Engineering.

What you'll do

• Own the AI context layer — write and maintain CLAUDE.md and skill files with the same rigor you'd apply to a CI/CD pipeline. These are the primary guardrail for non-engineers using Claude Code. If Claude writes something wrong and no one can catch it, it ships.
• Own the CI/CD layer — feature flag enforcement, automated PR review, Playwright smoke tests, Cloudwatch alerts. The safety net that catches what Claude's context missed.
• Enforce frontend standards automatically — not through checklists, but through gates that reject non-compliant code before it merges.
• Keep observability tight — automated alerting on platform changes and key experiment metrics, so regressions surface before anyone notices.
• Contribute to dead code removal on both frontend and backend, reducing the risk surface and giving Claude a cleaner codebase to reason about.
• Automate documentation so it stays in sync with the codebase — Claude should never be working off stale context.
• Help close out the ongoing Rails to AWS migration, a dependency for the broader platform guardrails work.
• Contribute to the shared infrastructure that makes the whole team faster, not just your own work.

Qualifications