Skip to content

Senior frontend contractorAvailable now

Senior frontend capacity without the three-month hire.

When your team is stretched and hiring is slow, I join as a senior contractor: read the codebase, pick up tickets in the first week, review code and ship features. No ramp-up theatre. I have done this inside a large accounting SaaS for six years and inside a pharma company for three.

Start here

To
hello@perhp.com
Subject
Project inquiry

Opens in your mail app

Is this a fit?

An honest fit check before we talk

I would rather tell you no on the first call than waste your budget. Here is what a good match looks like for this kind of work.

A good fit if

  • Your engineering team is stretched and you need a senior frontend developer who can start soon.
  • You want someone who ships and reviews code, not someone who needs to be managed.
  • You are a recruiter or agency placing a senior React, Next.js or Vue contractor with a verifiable profile.
  • You need a contractor who will still be here in a year, not just for a three-month gig.

Probably not a fit if

  • You need on-site presence most days. I work remotely from Denmark.
  • Your stack is Angular-only or something outside React and Vue. I have shipped Angular but it is not my main tool.
  • You need a team lead to manage other contractors rather than an individual contributor.

What I do

What the engagement typically covers

Feature delivery
Pick up tickets from your backlog, ship them in small reviewable pull requests, and keep the board moving from week one.
Code review and standards
Review the team's pull requests, document conventions and raise the bar on types, tests and accessibility without slowing anyone down.
Upgrades nobody has time for
Framework upgrades, dependency cleanup, build tooling and performance work that keeps getting pushed to next sprint.
Knowledge that stays
Written decisions and documentation so the team keeps the knowledge if I leave, which my track record suggests will not be soon.

Proof

Clients who kept me around

Embedded in existing teams, with how long each one kept me.

  1. Fintech · Accounting SaaS

    6 years

    Visma Dinero

    Frontend Developer · Full-time, then freelance

    Frontend development on Dinero, one of Denmark's most popular accounting platforms for entrepreneurs and small businesses. First as an employee for four years, then they brought me back as a freelancer for two more.

    Read the case study
  2. Biotech · Pharma

    3 years

    Y-mAbs Therapeutics

    Full-Stack Developer · Freelance

    Full-stack development of web solutions for a commercial-stage biopharmaceutical company, a regulated environment where reliability, correctness and clear documentation are not optional.

    Read the case study
  3. E-commerce · Fintech

    1 year

    Storebuddy

    Frontend Developer · Freelance

    Frontend for a platform that automates bookkeeping for webshop owners and flags imbalances on orders, turning messy e-commerce data into something an accountant can trust.

    Read the case study
  4. Climate tech · LCA

    2 years

    Målbar

    Full-Stack Developer · Freelance

    Ongoing development for a Danish life cycle assessment company. I have helped build their LCA screening tool, which lets companies estimate the climate footprint of their products, along with the internal tooling the team runs on every day.

    Read the case study

See all case studies and the full tenure ledger

Process

How we'll work together

The same four steps for a two-day fix and a two-year engagement.

  1. 01

    Intro call

    A free 30-minute call where you tell me about your project, goals and constraints. I ask a lot of questions and tell you honestly whether I'm the right fit.

  2. 02

    Proposal & estimate

    You get a short written proposal: scope, approach, timeline and price. Fixed price for well-defined projects, hourly or retainer for ongoing work.

  3. 03

    Build in the open

    Short iterations, working software early, and a weekly update you can actually read. You see progress and can change course before it gets expensive.

  4. 04

    Launch & support

    I handle deployment, hand over clean documentation, and stick around for support and further development if you want me to.

FAQ

Questions I get asked

How many hours a week are you available?
My preferred engagement is 20-40 hours a week for six months or more. Shorter or smaller engagements are possible when my calendar allows. Current availability is on the homepage.
Do you have a CV I can forward?
Yes, a printable CV is at perhp.com/cv. It covers the stack, every engagement with years, and contact details. Recruiters and agencies are welcome to forward it, and perhp.com/for-recruiters has everything needed to qualify me for a role on one page.
Which tools and workflows are you used to?
GitHub and GitLab, pull request reviews, CI/CD, Jira and Linear, Slack and Teams, async written updates. I adapt to your team's process rather than the other way around.
How do you invoice?
From my Danish company, Pekkel (CVR DK-37106666), in EUR, DKK or USD. Monthly for ongoing work, milestone-based for fixed-price projects.
Do you work with companies outside Denmark?
Yes. Most of my work is remote. I am in the Central European timezone, which gives full overlap with Europe and the UK and 3-6 hours of overlap with the US East and Central timezones. I work async-first with a written weekly update.
How quickly can you start?
I keep my availability status up to date on the homepage. If it says available, I can usually start within one to two weeks. The first step is a free 30-minute intro call.

Contact

Tell me what you are building

What it is, roughly when it needs to exist, and what a great result looks like. I usually reply within a day, and the first 30-minute call is free.

hello@perhp.com