Skip to content

Freelance project · Websites

Coding Bootcamp Landing Page

A bootcamp page that answers the hard questions before anyone applies

A landing page for a coding bootcamp, written for career switchers and working learners deciding whether to commit. I structured the page around their doubts, designed the curriculum as a visual path and shaped the route to an application.

Role
Product design
Type
Freelance
Platforms
Web
Scope
Landing page, UI design

01The problem

What needed solving

Choosing a bootcamp is a big decision in time and money, and visitors arrive sceptical about outcomes and unsure they can keep up. Many tech course pages lead with buzzwords and logos, while the things people need to decide, such as syllabus, schedule and cost, sit deep in the page or behind a sales call.

Who it’s for

  • Career switchers

    Proof that a beginner can follow the course and finish with real work to show.

  • Working learners

    A schedule and weekly time commitment that fits around a job.

  • Recent graduates

    Practical skills and projects that go beyond their degree.

  • Admissions team

    Applicants who understand the format and what it asks of them.

02The main flow

From curious visitor to applicant

The moment in blue is the one the whole design is built around.
  1. 01

    Lands on the promise

  2. 02

    Follows the curriculum path

  3. 03

    Checks schedule and cost

  4. 04

    Takes the readiness check

  5. 05

    Applies for a cohort

03Structure

How Bootcamp landing page is organised

Everything has one home. Getting this right first keeps every screen simpler.

Hero

  • Outcome headline
  • Next cohort date
  • Apply action

Curriculum

  • Stage-by-stage path
  • Projects you build
  • Tools you learn

Format

  • Full-time and part-time options
  • Mentor support
  • Weekly time commitment

Cost

  • Pricing
  • Payment options
  • What’s included

Apply

  • Readiness check
  • Application form
  • Questions

04Key decisions

Choices that shaped it

What I considered, what I chose, and why.

Decision 01

Curriculum as a path of projects

A syllabus as a bullet list reads like jargon to a beginner and doesn’t show progress.

Considered

A tabbed list of modules and technologies.

Chosen

A path of stages, each showing the project a learner builds at that point and the skills it uses.

Why it works

Projects make the outcome tangible and show how someone gets from nothing to a portfolio. Technology detail moved into an expandable panel to make room.

Decision 02

A readiness check before the form

An application form is a big step for someone who isn’t sure they can code.

Considered

Send every visitor straight to a long application form.

Chosen

A short, low-stakes check on background, available time and goal that suggests a format and carries the answers into the application.

Why it works

It lowers the first step and gives admissions useful context. To stop it feeling like a test, it is brief and never scores anyone.

Decision 03

Cost shown, not behind a call

Hiding the price behind a sales call frustrates a sceptical audience and sends them elsewhere for answers.

Considered

Replace pricing with a Talk to us button.

Chosen

A clear pricing section with what’s included and payment options, placed next to the schedule.

Why it works

Being open about cost builds trust. The info call stays as a secondary action for people who still have questions.

05What’s inside

Key features

Project-led curriculum

Each stage of the course is shown through the project a learner ships.

Cohort dates

Upcoming start dates and formats sit side by side so visitors can plan.

Readiness check

A few quick questions that suggest a format and prefill the application.

Clear pricing

Cost, what’s included and payment options shown on the page.

Info call booking

A secondary route for visitors who want to talk before applying.

06Outcome

What was delivered

Delivered

  • Page structure and copy hierarchy
  • High-fidelity desktop and mobile designs
  • Curriculum path component with its states
  • Readiness check flow screens
  • Hand-off file with specs for development

What I learned

  1. 01

    A sceptical audience reads every section for what’s missing; leaving out the cost would have said more than any headline.

  2. 02

    Turning modules into projects made the page clearer for beginners, and for me.

Next step

Tell me what you're building.
I'll tell you how I'd ship it.

Pick a time that suits you. You'll leave the call with a clear next step, whether we work together or not.

Book a free call

Free · 30 minutes · No commitment

Prefer email? prashantkumarsingh.work@gmail.com