Frontend Engineer

ppWe are looking for a builder‑designer hybrid who makes a developer‑facing product feel premium. You design it in Figma and ship it yourself in Hotwire. If you sweat the 200 ms of jank nobody else notices, and you have both the taste to design the thing and the skill to build it in production, this role is for you. /p h3About SearchApi /h3 pSearchApi is a real‑time SERP API delivering structured data from 100+ search engines and sources, including Google Search, Google Shopping, Google Jobs, Bing, Baidu, YouTube, Amazon, and many more. We power production workloads for Fortune 500 companies and fast‑moving startups who need reliable search data at scale. We're a lean, profitable, bootstrapped team. No VC pressure, no bloat. Just engineers shipping real products to real customers. /p h3Why Join Us /h3 ul liYou own what developers judge us by. The dashboard, the API playground, the docs, the marketing site. The first impression of our product is your work. /li liDesign and build, no handoff. You take a feature from a Figma mockup to a merged PR yourself. No designs thrown over a wall. /li liReal impact. A small team means your work shows up directly in signups, activation, and revenue. /li liThe best users to design for. You build developer tools for engineers, the most demanding and rewarding audience there is. /li liBootstrapped and Profitable. We answer to customers, not investors. /li /ul pWe'd rather hire one person with taste who can ship than a designer and a frontend developer who need a handoff between them. /p h3Tech Stack /h3 ul liRuby on Rails 8 with Hotwire (Turbo + Stimulus) /li liTailwind CSS and ViewComponent /li liesbuild for JavaScript /li liFigma for design /li liNative HTML first (, ) , Turbo Frames over single-page-app frameworks /li /ul pWe use Cursor, Claude, GitHub, and Slack daily. We ship multiple times a day with CI/CD. /p h3You Control AI, AI Doesn't Control You /h3 pWe ship faster because we use AI tools aggressively, Cursor and Claude. You scaffold components, generate layouts, and iterate on design variations with AI. But you own every pixel and every line that lands. You can tell when an AI-generated layout is generic slop and turn it into something with taste. If you can't, you're not ready for this role. /p h3What You'll Do /h3 ul liDesign and ship, not hand off. Take a feature from Figma to a merged PR: ViewComponents, Stimulus controllers, Tailwind, the whole thing. /li liOwn the dashboard. The logged‑in

experience:
usage analytics, request history, billing, API keys. Make a data-dense console feel calm instead of cluttered. /li liBuild interactive API playgrounds. Where a developer fires a real request and watches structured JSON come back live. Make it the thing people screenshot and share. /li liOwn the docs and marketing experience. Keep the component system coherent, fast, and beautiful as the product grows week over week. /li liBuild honest data viz. Turn raw metrics into charts a developer trusts at a glance, using a consistent, semantic color system. /li liHold the line on craft. Native HTML first, Turbo Frames over client-side state, Tailwind over inline styles. Push Hotwire to its limits before reaching for a dependency. /li liClean up as you go. Tame the JavaScript bundle, kill dead CSS and one-off controllers before they pile up. /li /ul bYou own the front end. /b pWe don't hand you pixel-perfect specs. You decide what deserves polish now and what ships good-enough, and you make the call. /p h3The Hard Parts /h3 ul liHotwire-first, on purpose. If your instinct for every interaction is to reach for React, you'll fight the stack instead of using it. The fun, hard part is getting SPA-grade polish out of Turbo, Stimulus, and native HTML. /li liYou design AND build. Plenty of people do one well. The bar here is taste plus the discipline to ship it in production code, with tests, that passes review. /li liDeveloper tools are unforgiving. Your users notice a 200 ms jank, a misaligned monospace column, or a chart that lies. There's nowhere to hide a sloppy detail. /li liWide surface, one owner. Dashboard, playground, docs, marketing. You constantly decide what to polish and what to leave, with no PM holding the list for you. /li liTaste is subjective. You'll defend a design decision in writing, ship it, watch real usage, and change your mind when the data disagrees with you. /li /ul pIf you want pixel-perfect specs handed to you and someone to manage you, this isn't for you. /p h3About You /h3 ul liYou design and build. You've shipped frontend you also designed, and it looked genuinely good. Not "good for an engineer." Good. /li liHotwire-native, or close. Fluent in a server-rendered, component-based stack (Rails + Hotwire ideal; Phoenix/LiveView, Django, or Laravel translate). You reach for native HTML before JavaScript. /li liTailwind cold. Real opinions about spacing, type scale, and color systems. /li liYou love developer tools. You have a favorite dashboard an