{"id":3633389,"url":"https://alion.io/job/clientvalley-oue-senior-full-stack-engineer-remote-first-engineering-hire","title":"Senior Full-Stack Engineer (Remote): First Engineering Hire","company":{"id":4496138,"name":"Clientvalley OÜ","domain":null,"url":"https://alion.io/company/clientvalley-oue","size_band":null,"is_staffing_agency":false,"employer_type":"direct","is_intermediary":false,"listed_via":null,"ats_vendor":null,"truth_index":null},"role":"Backend","role_family":"Backend","seniority":"senior","employment_type":"full_time","work_mode":"remote","remote_scope":"stated_countries","remote_scope_basis":"board_field","remote_working_hours":null,"hiring_geo_confidence":"inferred","locations":["South Africa"],"countries":["ZA"],"hiring_countries":["ZA"],"hiring_countries_total":1,"salary":{"min":80000,"max":110000,"currency":"ZAR","period":"month","gross":true,"usd_annual":79620},"salary_estimate":null,"experience_years_min":null,"visa_sponsorship":false,"relocation_package":false,"has_equity":false,"technologies":[{"name":"Gmail","optional":false},{"name":"JavaScript","optional":false},{"name":"Next.js","optional":false},{"name":"Node JS","optional":false},{"name":"Outlook","optional":false},{"name":"PostgreSQL","optional":false},{"name":"React.js","optional":false},{"name":"Sentry","optional":false},{"name":"Slack","optional":false},{"name":"SQL","optional":false},{"name":"SQLite","optional":false},{"name":"Supabase","optional":false},{"name":"TypeScript","optional":false}],"status":"live","first_seen_at":"2026-11-02T13:27:09Z","employer_posted_date":null,"last_verified_at":"2026-11-02T13:27:09Z","board_verified":false,"closed_at":null,"days_open":1,"trust":{"level":"not_scored","repost_count":null,"flags":[],"days_open":1},"description":"Fully remote\n\nFull-time (40 hours/week) from day one · Long-term role · You report directly to the founder\n\nThe mission\n\nWe’re part of ScaleValley, a family of internet companies with two previous exits behind us. We’re building a new AI platform that helps professionals connect with podcast hosts, PR professionals, journalists, industry experts, and thought leaders. Our vision is to make discovery, research, personalized outreach and follow-ups fully autonomous. We’ve spent the past 3–4 months developing the initial version with a third-party development agency, and now we’re hiring our first in-house engineer to take full technical ownership and lead it toward launch. You’ll assess the existing code and integrations, decide what to keep or improve, and build a reliable product customers can use and trust.\n\nWe know what we’re building and why. You’ll get clear product direction and priorities directly from the founder, so you can focus on engineering. Within that direction, you’ll have the freedom to choose the technical approach, architecture and implementation details you believe are best. We welcome better ideas and keep meetings and process light so most of your time goes into building, testing and shipping.\n\nAbout us\n\nOur software helps professionals discover relevant people, understand why they’re a good fit, and build valuable connections across media, PR, and their industries.\n\nThe founder has spent years in this market. He built and sold a podcast production agency and a podcast host database, so he knows the customers and the data. You’ll be the first engineer on the team, with meaningful ownership of how the product is engineered and brought to market.\n\nWhat we sell\n\nA customer describes their background, expertise and goals. The platform researches relevant contacts and opportunities, recommends the strongest matches, and creates personalized outreach grounded in each person’s work. Over time, it will also automate sending, follow-ups and reply drafting.\n\nOur customers include founders, authors, executives and experts seeking meaningful media and industry connections, as well as PR agencies managing outreach for multiple clients. Podcast and media outreach are the starting points, with a broader vision for professional connections.\n\nWhat the full product does:\n\n Search in plain English. Typing “parenting podcasts with big audiences” or “reporters who cover fintech” returns a ranked list of active shows and writers, each with a verified email, audience size and fit score.\n\n Pitches written one person at a time, in the customer’s voice, mentioning the episode or article that person just published. Subject lines test themselves and the winners stay.\n\n Sending from the customer’s own inbox on a natural schedule, or from managed inboxes we warm up, with deliverability checks and dead contacts removed automatically.\n\n Follow-ups in the same thread until someone replies.\n\n One inbox for every reply, with a drafted answer waiting, plus open and reply alerts in the app and in Slack.\n\n Website visitor identification: a small pixel shows who is browsing the customer’s site, enriches them and queues outreach to the warm ones.\n\n Mention alerts on the customer’s name and keywords, a tracker for every booked interview and article, and an earned media value in dollars that agencies can export for their clients.\n\n Unlimited profiles for clients and executives, free team seats, an AI advisor that reviews campaigns and suggests the next move, and sequences across email, LinkedIn and text for outreach beyond press and podcasts.\n\nNot all of this exists yet. Researching the right people and creating useful, personalized outreach come first, because the broader automation only works when the matches are genuinely relevant. Sending, follow-ups, reply drafting, visitor identification and monitoring are planned for later stages.\n\nWhy this role exists\n\nWe’ve worked with a third-party development agency to build the initial version, including the core codebase, product designs and integrations. We’re now bringing development in-house and looking for an experienced engineer to take ownership of what’s been built, improve reliability and lead the product toward launch.\n\nThe hard parts sit where things connect: databases, external APIs, patchy data, background jobs, AI research steps and the interface on top. When one piece fails, everything after it fails too. There are two existing implementations to understand and reconcile, and the core workflows still need testing with real users and real data before they’re ready for production.\n\nYou’ll be inheriting code you didn’t write, chasing bugs across services and making decisions without all the facts. Keep what works. If something needs a bigger rewrite, make the case for it, with the cost and the migration plan.\n\nWhat you’ll do\n\n1. Own the path to launch\n\nUnderstand what runs today, what has been tested and which technical blockers stand between the current product and the agreed launch scope. Propose a practical engineering plan and timeline, then deliver it.\n\n Make the whole journey work start to finish: the customer enters and confirms their profile, the system researches them, recommends shows, saves the results, drafts pitches they can edit and finds contact details when asked.\n\n Fix the failures that matter most and check each fix in the running app against the live integrations.\n\n Handle everything technical the paid launch needs, including payments and account access.\n\n2. Make the matches and pitches good\n\nImprove how well the system understands each customer: who they are, what they want right now, where they’ve already appeared, which audiences fit them and which shows would realistically say yes.\n\n Judge recommendations against evidence, with a review process you can repeat. Keep facts, estimates and guesses clearly apart.\n\n Make matches and pitches more relevant, and track what each improvement does to speed and cost.\n\n Be honest when the data runs thin: people with little online footprint, people who share a name with someone else, stale records, or a niche with only a handful of good shows.\n\n3. Own the databases, APIs and background jobs\n\nYou own the data models, migrations, access controls, data quality, caching and how data moves between services.\n\n Handle timeouts, rate limits, malformed responses, retries, concurrency and jobs that die halfway through.\n\n Make sure nothing runs twice, no email goes out twice and no customer loses saved work.\n\n Track what each provider costs, enforce the spending limits we agree on, and make failed or half-finished work easy to see and recover.\n\n4. Own releases and production\n\nDeployments, monitoring, alerts that mean something, backups, restores, rollbacks and production fires are yours. So is keeping each customer’s data private and separate from everyone else’s.\n\nCheck changes before and after each release. When something breaks, find out why, explain it and stop it from coming back. Write enough documentation that another good engineer could pick up the system and run it.\n\n5. Keep improving the product\n\nShip across the frontend and backend. The founder sets product priorities based on customer needs; you recommend the best technical way to deliver them and explain trade-offs. Turn agreed work into reliable releases, flag risks early and demonstrate the results from a customer’s point of view.\n\nYour first 60 days\n\nYou’re accountable for delivery from the start. The milestones below assume a full-time commitment of 40 hours a week. In week one we agree the exact launch scope, the acceptance cases that must pass, and number targets for completion rate, recommendation quality, processing time and running cost. If something gets in the way, raise it early and bring a recommendation and a plan.\n\nFirst 7 days: take control and ship\n\n Get the existing apps running, walk through the core customer journey and recommend a single path to production.\n\n List the launch blockers that matter most, put them in order and commit to dates.\n\n Build a representative test set and measure where we start on completion, recommendation quality, processing time and provider cost.\n\n Find the cause of a real launch blocker, ship a fix and confirm it works in the live app with the real integrations.\n\nBy day 30: launch the core product for a paid pilot\n\n The agreed core journey is live in production: intake, research, recommendations worth acting on, saved results, editable pitches and contact research on request. You’ve tested it with real inputs and live providers, including the cases that used to fail.\n\n Payments and account access are ready for the paid pilot. Every agreed acceptance case passes, including data privacy between accounts and recovery from interrupted jobs.\n\n Monitoring tells you when something needs attention, provider costs are visible and there’s a recovery procedure. You’ve restored from a backup and rolled back a deploy at least once to prove both work.\n\n You ship tested improvements every week and fold pilot feedback into the next release, while handling releases and troubleshooting yourself.\n\nBy day 60: prove it’s reliable and getting better\n\n There’s one production version, and it’s maintained. Normal customer journeys finish without anyone stepping in by hand, and you handle support, releases and incidents.\n\n The agreed targets for completion, recommendation quality, speed and cost are met over the last two weeks. You show the evidence, the sample sizes and how far things moved from the starting baseline. Where live volume is low, you add repeatable test journeys and label them as tests.\n\n The worst recurring failures from the pilot are fixed, with checks that stop them coming back. Manual work in serving customers is gone wherever it can be.\n\n Every week has a useful product or reliability improvement to show for it, with evidence that it helped. Customer feedback turns into shipped changes, and you check how they land.\n\n You propose the technical execution plan for the next 30 days based on the founder’s product priorities, customer feedback and what you’ve learned from running the system, and you start delivering it.\n\nYour scorecard\n\nWe go through these five areas on the weekly call. Each metric has a defined denominator and data source, and missing results and failed attempts stay in the numbers.\n\n End-to-end completion: completed customer journeys divided by valid journeys started. Failures are reported with their reasons, and cases where there simply weren’t enough good shows are reported separately. Before launch, every agreed acceptance case has to pass.\n\n Recommendation quality: recommendations judged suitable divided by recommendations reviewed by someone independent, plus the share of profiles that get usable results at all. We score against a fixed test set, the source evidence and the fit rubric we agree on.\n\n Safe operation: before the paid pilot, the agreed account-access and permission checks pass, and you’ve shown one successful backup restore and one deploy rollback. When background work fails, it leaves a state someone can act on.\n\n Speed and economics: median and 95th-percentile time to usable results, completion and failure counts, and total provider cost per completed journey, failed attempts and retries included. We set the baseline and targets in week one, you report weekly, and by day 60 you’re within the targets and spending limits.\n\n Delivery and ownership: you own technical execution against clearly agreed product priorities. Break down the engineering work, ship tested improvements each week, and flag risks early with a recommended next step. Bring a short written update and the latest scorecard to each weekly call.\n\nWhat we’re looking for\n\n Around five or more years of professional full-stack work, with strong backend and database fundamentals.\n\n You’ve personally shipped and maintained a production web product, and you can tell us what you owned, what broke a...","description_format":"text","description_chars":16349,"description_truncated":true,"requirements":{"experience_years_min":null,"management_years_min":null,"team_size_min":null,"manages_managers":false,"education":null,"security_clearance":false,"languages":[]},"benefits":[],"hiring_locations":[{"name":"South Africa","iso":"ZA","kind":"country"}],"hiring_excludes":[],"relocation_offered":false,"industries":[],"lifecycle":[{"event":"open","at":"2026-11-02T20:26:03Z"}],"visa":[],"liveness":{"score":86,"band":"hot","label":"Hiring now","p_open":1,"p_active":0.86,"p_room":1,"age_days":0,"expected_fill_days":29,"reasons":["seen:0","win:early"],"computed_at":"2026-11-03T05:54:40Z"},"pay":{"stated_usd_annual":79620,"is_top_pay":false},"html_url":"https://alion.io/job/clientvalley-oue-senior-full-stack-engineer-remote-first-engineering-hire","json_url":"https://alion.io/job/clientvalley-oue-senior-full-stack-engineer-remote-first-engineering-hire.json","meta":{"generated_at":"2026-11-03T21:52:30Z","cache_seconds":300,"methodology":"https://alion.io/methodology","terms":"https://alion.io/terms","contact":"https://alion.io/contact","api":"https://alion.io/developers","about":"Alion is a live layer of people, companies and AI agents: who they are, whether they are real and active right now, what they do and how to work with them, readable by people and by agents and paid per call.","catalog":"https://alion.io/catalog.json","usage":{"tier":"assistant_verified","counted_by":"address","units_charged":1,"used_today":1600,"day_limit":null,"remaining_today":null,"minute_limit":300,"resets_at":"2026-11-04T00:00:00Z"}},"offers":[{"id":"company.slices","title":"One company in depth, by slice","status":"live","price":{"credits":0.02,"usd":0.002,"plus_per_slice":{"credits":0.05,"usd":0.005}},"unit":"per company, plus each slice with data","note":"the employer in depth","call":{"mcp_tool":"get_company","arguments":{"id":4496138},"rest":"https://alion.io/mcp/rest/get_company?id=4496138"},"human":"https://alion.io/catalog?offer=company.slices&for=job%2Fclientvalley-oue-senior-full-stack-engineer-remote-first-engineering-hire"},{"id":"market.stats","title":"A market slice: pay, demand and time to fill","status":"live","price":{"credits":1,"usd":0.1},"unit":"per slice","note":"pay, demand and time to fill for this role and place","call":{"mcp_tool":"market_stats"},"human":"https://alion.io/catalog?offer=market.stats&for=job%2Fclientvalley-oue-senior-full-stack-engineer-remote-first-engineering-hire"},{"id":"job.search","title":"Open jobs by role, technology, place, pay and visa","status":"live","price":{"credits":0.02,"usd":0.002},"unit":"per posting in a list","note":"similar open postings","call":{"mcp_tool":"search_jobs"},"human":"https://alion.io/catalog?offer=job.search&for=job%2Fclientvalley-oue-senior-full-stack-engineer-remote-first-engineering-hire"},{"id":"company.verify","title":"Is this company real and active right now","status":"pilot","price":null,"unit":"per company","request":{"url":"https://alion.io/catalog/request","method":"POST","body":"{\"offer\": \"company.verify\", \"for\": \"job/clientvalley-oue-senior-full-stack-engineer-remote-first-engineering-hire\", \"note\": \"what you need it for\"}"},"human":"https://alion.io/catalog?offer=company.verify&for=job%2Fclientvalley-oue-senior-full-stack-engineer-remote-first-engineering-hire"}],"agent":{"mcp":"https://alion.io/mcp/jobs","mcp_open":"https://alion.io/mcp/open","next":[{"tool":"get_job","arguments":{"id":3633389}},{"tool":"search_jobs","arguments":{"company":4496138,"detail":"compact"}},{"tool":"match_people","arguments":{"job_id":3633389},"note":"people open to offers who fit this vacancy"}],"note":"The same data through MCP tools: https://alion.io/mcp/open needs no sign-in (compact searches, postings, people); https://alion.io/mcp with an Alion account has everything. Docs: https://alion.io/developers"}}