Claude CLI Vibe Coding Front-End / Full-Stack Engineering Internship

Claude CLI Vibe Coding Front-End / Full-Stack Engineering Internship Remote | Unpaid Internship | 3–6 Months | 15–20 hrs/week | Master's Degree RequiredTHIS IS NOT A SUMMER INTERNSHIP, for immediate hire only. About the Internship We are seeking a graduate-level intern specializing in front-end engineering or full-stack product development to help turn front-end product screens into real working software functionality inside an existing codebase. This role is 100% centered around using Claude CLI and MCP tools in the terminal to analyze codebases, review designs and backend documentation, create missing front-end documentation, implement features, debug issues, and refine production-ready software. This role is about building product functionality.The intern's job is to take front-end screens, flows, and product requirements and help translate them into complete working features by thinking through: • how the feature should behave • what user stories need to be defined • what the acceptance criteria should be • what happens in edge cases • what the data limitations are • what empty states, loading states, and error states need to exist • what the front end needs from the backend in order to work correctly Strong front-end experience is required.Prior hands-on experience with Claude CLI is required.Prior hands-on experience with MCP server integrations is required.Candidates should already be comfortable with vibe coding workflows.A strong QA mindset is essential for success in this role. The ideal candidate is someone who can look at a design, review the available backend and product documentation, identify what is missing, create the missing front-end documentation, and then help implement the feature properly inside a real software system. What This Role Involves This internship is centered around front-end product implementation. That includes work such as: • translating front-end screens into detailed implementation requirements • creating missing front-end documentation based on designs and backend docs • writing user stories for front-end behavior • defining front-end acceptance criteria before development starts • identifying edge cases, broken flows, and missing product logic • documenting empty states, loading states, error states, and validation behavior • identifying backend dependencies and data limitations that affect the front end • implementing front-end and supporting full-stack functionality in the codebase • reviewing whether a feature is actually complete, usable, and build-ready The goal is not to just make the UI look done.The goal is to make sure the screen translates into real functionality that works correctly. Development Workflow This role uses a terminal-based development workflow built around Claude CLI and MCP server integrations. The intern will be expected to already know how to: • use Claude CLI to work inside an existing repository • use MCP tools to retrieve codebase, architecture, design, and documentation context • analyze front-end requirements and identify missing implementation details • create missing front-end documentation based on designs and backend documentation • write or refine user stories, acceptance criteria, edge cases, data limitations, and error states • implement feature behavior across front-end and supporting backend logic • review code outputs critically instead of accepting them blindly • debug issues and validate that features work properly in real use cases • use Google Chrome Developer Tools within the MCP-supported workflow to inspect UI behavior, debug front-end issues, validate states, and verify that implemented functionality matches the intended screen behavior What You'll Work On Interns will primarily work from existing product screens, design files, backlog items, and backend documentation to help move features from UI concept to complete implementation. Work may include: • analyzing front-end screens and product flows • translating screens into implementation-ready front-end requirements • creating missing front-end documentation from designs and backend docs • writing front-end documentation for: • user stories • acceptance criteria • edge cases • empty states • loading states • error states • validation rules • data limitations • backend dependencies • identifying missing behavior or unclear requirements before development starts • building front-end components and feature flows • implementing supporting full-stack logic where needed • connecting the front end to APIs and backend services • debugging broken behavior and refining incomplete implementations • validating that features behave correctly across expected use cases Key Responsibilities • Work 100% inside a Claude CLI + MCP terminal-based workflow • translate front-end screens and product requirements into implementation-ready functionality • create any missing front-end documentation based on designs and backend documentation • write and refine user stories for front-end f