Full-stack engineer UI designer New Hampshire, fully remote

Yuval Levy

Software is a social craft.

I build tools for specific people with specific problems, and I’m not done until I bring smiles to their faces.

Say hello: yuval@yuvallevy.dev or see the contact section below.

Levy - say it like “levee”.
Yuval - say it like “you’ve all”. Yes: it's what yuval been waiting for. 🥁

01 How I think about software

Four things I keep believing.

Not a methodology, just the handful of convictions that drive every project.
02 Selected work

Tools I’ve loved making.

Side project · Since 2019

NPBloom

In regular use at the Linguistics Department, Tel Aviv University · try it ↗
Screenshot of NPBloom, a tool for drawing linguistic syntax trees

A tool for drawing linguistic syntax trees the way you’d draw them on paper. It spread almost entirely by word of mouth among professors, TAs, and students, and is now their go-to tool for this purpose.
Usability in tools for linguists often leaves a lot to be desired, and I wanted to raise the bar by building a tool that was a pleasure to use.

The highlight of my academic career was when a question on a final exam asked students to examine a tree drawn with NPBloom. I was one of the students taking that exam.

  • Kotlin/JS
  • TypeScript
  • React
  • SVG
Co-Founder / Software Engineer · 2020–2026

Mill Market

Forward Forestry – built from empty repo to acquisition

An online marketplace letting tree services sell their waste logs as material for wood products. I owned the UI and an SMS-based system for coordinating pickups: scheduling, rescheduling, delivery estimates, and more. SMS was where our non-technical users already lived, and getting them to download an app would have been a non-starter.

Forward Forestry was acquired by Cambium in 2024 and the whole team came along. I continued to work on the product and its integration into the Cambium ecosystem, this time implementing a design team’s vision instead of my own, down to the small details the lead designer was glad someone noticed.

The notification system had an especially interesting design and testing process. See more...

A notification system is a high-stakes component of any product, and it’s critical to get it right. Accordingly, it was the most heavily tested part of the codebase.
I wrote a little language where each case reads like a screenplay: a timed exchange of messages a non-coder can follow like a script for a movie scene, to pass to a product manager or designer and ask, “Does this look right?”
The very same screenplay would then compile down as valid test cases, since it was all valid code in the first place. This made it easy to get feedback from non-technical stakeholders and iterate quickly, without needing to translate back and forth between English and code.

The content of each test case looked like this – this is heavily extended Kotlin code which compiles as-is:

At time "2023-05-29T14:00:00" Send dispatcher "What is your ETA for tomorrow at 123 Main St, Anytown, US?" 2 minutes later Dispatcher replies "10 am" Send dispatcher "You have set a time of 10:00 for tomorrow. We're confirming this with the supplier..." Send supplier "Can you load tomorrow at 10:00 at 123 Main St, Anytown, US?" 5 minutes later Supplier replies "Yes" Send supplier "Thank you for confirming!" Send dispatcher "The supplier has confirmed a pickup time of 10:00 tomorrow. We'll text you tomorrow before the pickup in case there are any changes."

The tests would run against a simulated notification system with a fake clock. Each replies line would trigger a response from one of the fake users, the Send lines would check that the system reacted correctly at the right time, and the later and At time lines would advance the clock and trigger any time-based events that were supposed to happen in the meantime.
We had about 150 such test cases covering a wide variety of corner cases. We would run them before each deployment, and any deviation from the script would cause the test to immediately fail and abort the deployment.

Many bugs did not make it to production thanks to this system, including ones that would have been tricky to catch, annoying for the users, and highly impractical to reproduce manually.

  • Kotlin
  • TypeScript
  • React
  • MongoDB
Side project · 2026

Apartment complex navigator

3D wayfinding for one notoriously labyrinthine apartment complex

A 3D bird’s-eye map for an apartment complex so confusing even residents get lost in it. Includes labeled buildings, separate walking and driving routes between any two points, and the unofficial shortcuts the big mapping apps have never heard of (shh, don’t tell them).

Built with Three.js, a return to a tool I first used in high school to build a spatial geometry visualizer for a math teacher who needed one.

Released to residents in July 2026. A public demo with fictional data will be available in the future.

  • TypeScript
  • Three.js
  • WebGL
  • GIS-flavored

Smaller one-offs

03 An aside, with a slider

On rounded corners.

I find it extremely funny how quickly rounded corners go in and out of fashion.

Sometimes they stick around for years; other times they make a brief visit for a season and then disappear again, only to come back a few years later bigger and angrier than before.

So instead of me making a decision for this page, here you go: you drive. Drag the slider and watch the entire page change its mind about how round it wants to be.

a tag another tag the slider knob, too
5 px of opinion
Chef knife
Ice cream scoop

Scroll around the page to see how the corners change.

04 What’s next

Who I’m hoping to work with.

I’m looking for a remote early-IC seat at a small-to-mid, mission-driven team, where “designer” and “engineer” aren’t kept in separate departments, and where someone can tell you clearly why the work matters in a way that you’ll be able to explain to a five-year-old.

My favorite problems to solve are those in messy, complex domains that haven’t been fully digitized yet, and where people are skeptical about software in the first place.

I get on best with people for whom anything can become a toy – those who tinker, who play, who never quite believed work and play were opposites. If your instinct is that the two shouldn’t mix, we’ll both be happier knowing it now.

Finally, I’ll tell you what I really think, not “brutally” but plainly and kindly, and I’d love exactly the same in return.

Say hello

Let’s make something people love.