Remote: Yes

Willing to relocate: No

Technologies: React Native, TypeScript, Python, Node.js, LangGraph, PostgreSQL, Supabase, AWS, Three.js, Expo, FastAPI, LLM integration

Résumé/CV: richard-simmons-portfolio.vercel.app

Email: fowl_137@hotmail.com

I build things that look like someone cared. Most engineers treat design as someone else's problem. I treat it as part of the job. Always have. My portfolio site is built in Three.js with custom Blender assets because I wanted to see if I could make a website feel like a place. Turns out you can.

That instinct runs through everything I build. Clean systems. Intentional interfaces. Products that don't just work but feel right. Dieter Rams called it "good design is as little design as possible." I think about that a lot when I'm writing a component or architecting a feature.

I've shipped mobile apps, AI pipelines, real-time streaming systems, and 3D web experiences. Enterprise scale at Toyota. Indie speed at my own studio. I've operated at both ends of that spectrum and I know what each one teaches you.

What I want next: a team that's building something new and wants an engineer who brings a point of view. Not just someone who closes tickets. Someone who asks why the ticket exists in the first place. If you care about craft as much as velocity, I want to hear from you.

You want to know what I think separates a good engineer from a great one? It ain't the stack. Everybody's got a stack. It's taste. Four years at Toyota. APIs handling a million requests a day. Ten enterprise apps across manufacturing and dealership platforms. I also led a UX audit that cut task completion time by 20% for 2,000+ users. Not because someone told me to. Because it was broken and I could see it. Then I went and built my own thing. Zoan Collective. Two production apps, FocusFi and Lucid, shipped to iOS and Google Play. Real users. Real payments. Real AI pipelines processing 1,000+ interactions a day. I cut infrastructure costs 80% by going serverless. I also cut audio generation time from 360 seconds to 120 seconds because waiting three minutes for music is not a product, it's a punishment. I care about software the way Dieter Rams cared about a transistor radio. Every button, every flow, every API response. If something feels clunky, I notice. And then I fix it. I'm not looking to be a cog. I want to own something. Ship it. Watch people use it. If you're building a product that actually matters, let's talk.

Remote: Yes

Willing to relocate: Yes

Technologies: TypeScript, React, Next.js, JavaScript, Node.js, Python, Flask, SQL, PostgreSQL, REST APIs, AWS, Docker

Résumé/CV: https://richard-simmons-portfolio.vercel.app

Email: fowl_137@hotmail.com

Full-stack engineer who will absolutely notice if your button padding is off by 4px. I build things that work and feel good to use, which sounds obvious until you've used enough enterprise software to know it very much isn't. I've shipped production apps at scale and internal tools that people actually open without sighing. The common thread: I can't stop caring about the details. My most personal project is Lucid, an AI music app I built solo from scratch. It's got Python/Flask on the backend, AI integrations that don't feel bolted on, and design decisions I stole from outside the software world entirely. I'm unreasonably proud of it. Building it scratched the itch I can never quite ignore, the one that says this should feel better than it does. Day-to-day I'm most at home in full-stack product roles: React + TypeScript on the front, APIs and SQL-heavy backends in the rear, cloud stuff in between. I'm the person who'll own a feature from the database schema to the hover state and care equally about both. Good fit if your team debates product decisions, ships things that make users feel something, and doesn't treat "good enough" as a finish line. Bad fit if your PRs are just vibes and your staging environment is production.