LogoLogo
  • 👋Cal.com Handbook
  • The Company
    • ❓What is Cal.com?
    • 📈Mission, Vision and Values
    • 🅰️Glossary
    • 📈Organization Chart
  • HR & Careers
    • 👷Contract-to-hire trials
    • 🛫Onboarding
    • 🏆IC Levels
      • ⛰️Engineering Levels
        • 🕵️IC1 Engineer (Code Cadet)
        • 👷‍♀️IC2 Engineer (Code Craftsperson)
        • 🧘‍♀️IC3 Engineer (Code Connoisseur)
        • 🧙‍♂️IC4 Engineer (Code Wizard)
    • 💡Sharing your views
    • 💸Bonus & Equity Structure
  • Policies
    • 🏖️Vacations
    • 💳Expenses
    • 🗣️Communications
  • Engineering
    • 🔔Managing Notifications
    • ⭐Valuable Bookmarks
    • 🐛How to report issues
    • 💻How we work on Tickets
    • 🔥What to do during Emergencies
    • ✅PR Reviews
    • ☑️Self-reviews
    • 📚Keeping Docs up-to-date
    • 🌐HTTPS & Subdomains
    • 🎯Best practices
      • Data fetching
      • Avoid Prop Drilling
      • Prefer defaultHandler for simple API handlers
      • Prefer inferred types over explicit ones
      • Prefer early returns
      • Avoid comparing multiple values with `includes`
      • Validate using zod instead of type casting
      • Prefer Composition over Prop Drilling
      • Prefer ternaries over Short Circuiting “&&” for React Components
      • Don't modularize prematurely
      • Only select data you need
      • Disallowing the use of unrestricted Metadata fields
      • E2E Tests Best Practices
    • 💻Codebase
      • 🔓Keeping the lock file in sync
      • 🚫Git Private Submodules
      • 🏎️Monorepo / Turborepo
      • 🌝Deploying to Production
      • ☁️Deployment
      • 💻Debug Desktop App
      • 🚩Enabling/Disabling Features
    • 🔺Resolving failed migration on Vercel Preview
    • 🔦Cal.com Status Page
  • Customer Success
    • 💟Tone
  • Marketing
    • 🎬Media
    • ☝️How to add a new Tip to Sidebar
  • 🤲Sales
    • Operations Stack
Powered by GitBook
On this page

Was this helpful?

  1. HR & Careers

Contract-to-hire trials

aka Lean Hire

PreviousOrganization ChartNextOnboarding

Last updated 1 year ago

Was this helpful?

At , we take a very different approach to hiring. Most of our full time employees will be preceded in a 30 day contract-to-hire trial period. A contract will be administered for a 30 day period with the company, and then at the end of the contract a final decision will be made on whether the person will be brought on full time.

A lot of people ask (for very good reason) what “success” looks like during the trial. The trial is less about “showing why you should join” and more like “finding reasons why you shouldn’t join”

If we extend an offer as a trial, we do it because we think you could be a great addition to the team. The trial is the last step to show both to you and the team if there are any red flags while working on the team.

Don’t feel like you need to be excellent only during the trial. See this as some sort of dating: be you, authentic, real.

The trial is more about you than us: it’s your chance to work without committing immediately. Your job is to figure out:

Do I like …

  • the mission?

  • the code base?

  • my team members?

  • working with the founders?

  • the market?

  • building in public?

  • working async?

  • threads and looms?

  • wearing pyjamas?

Lastly, for us it’s a chance to get to know you too, before extending a proper contract. Why? Because it is terrible for everyone, if we poach you from your existing employer, sign you into a yearly commitment, and then you (or us) figure out it’s not a good fit.

The bad outcome: you left your existing job and took a big risk without any upside.

We hate firing. Every company does. By discontinuing a LeanHire trial it feels a bit less shitty because you haven’t fully committed yet.

Like dating, it’s perfectly fine to part ways after the second week.

TLDR:

  • a lean hire has no “goal” in a sense of “success”

  • it is a tool for you to look behind the scenes faster

  • discontinuing should feel less bad as firing (still sucks, I know 😞)

Cal.com
👷
Page cover image