Cape
Web Developer
About this role
Cape, a privacy-focused mobile carrier, is seeking a contract Web Developer to oversee their marketing website. The role involves managing updates and enhancements, collaborating with various teams, and implementing security-minded practices for web analytics.
What you'll do
- Manage production releases and monitor builds
- Update website content through the CMS
- Implement design updates from Figma designs
- Maintain web checkout flow and handle integrations
- Optimize site performance and implement SEO best practices
- Address security vulnerabilities promptly
What they're looking for
- Proficiency in JavaScript/TypeScript and Next.js
- Experience with Vercel and CI/CD pipelines
- Hands-on with headless CMS platforms
- Familiarity with web security fundamentals
- Knowledge of marketing analytics tools
- Proficiency in translating Figma designs to code
- Attention to design and UX detail
Benefits
- Flexible working hours
- Opportunity to work on cutting-edge privacy technology
- Collaborative and innovative team environment
- Participation in a mission-driven company focused on privacy
- Exposure to a wide range of projects and stakeholders
- [unknown]
Opens the official application on the employer’s site. No login required.
Cape
Cape builds privacy-focused mobile network infrastructure and telecommunications systems designed to protect user communications across devices and networks. The company is hiring software engineers, security engineers, forward-deployed engineers embedded with federal customers, web developers, and technical specialists to develop secure infrastructure, drive product improvements based on field needs, and ensure reliable deployment of privacy-centric mobile solutions.
View all jobs at CapeLikely interview questions
- Walk us through your experience with Next.js and Vercel deployments. How have you optimized build pipelines or diagnosed deployment failures in production?
- Tell us about a time you implemented privacy-first web analytics or attribution tracking. How did you minimize third-party data exposure while still capturing meaningful conversion data?