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
  2. IC Levels
  3. Engineering Levels

IC4 Engineer (Code Wizard)

"I'm the wizard behind the code, conjuring up solutions to the most challenging problems and guiding our technical vision into the future."

  • Role: IC4s lead from the front, guiding the entire engineering team and working closely with collaborators from outside the company.

  • Responsibilities:

    • Mentor and guide team members across all IC levels.

    • Collaborate with external partners and lead integration projects with companies such as Prisma, BoxyHQ, and tRPC.

    • Work closely with Head of Engineering to drive technical roadmaps.

    • Respond to application alerts extremely quickly and ensure we are striving towards extremely high uptime.

  • Leadership:

    • IC4s are not just experts in their field but are also responsible for the growth and direction of the engineering team.

    • Be the rock the team needs when things are on fire. Your ability to demonstrate calmness and composure during difficult outages will go a long way in bringing the team together to quickly resolve the issue.

  • Expertise:

    • There's no problem they can't solve.

    • They know our tech like the back of their hand.

    • Their code is practically flawless.

      • They expertly design functions, classes and modules such that they are easily testable with unit and integration tests.

      • Other engineers easily understand their code and can extend it with little-to-no complications.

PreviousIC3 Engineer (Code Connoisseur)NextSharing your views

Last updated 1 year ago

Was this helpful?

🏆
⛰️
🧙‍♂️