🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Most companies divide product work among three people: A product manager decides what to build. A designer decides how it should work. An engineer builds it. We’re looking for someone who can move across all three. You’ll understand the problem, design a simple solution, and build it into the product. You’ll work closely with our team and users, but you won’t need someone to translate every idea into detailed requirements for you. About Tellos Tellos helps independent autism clinicians build and run their own practices. Our platform supports the work behind autism care—from bringing families into care and recruiting therapists to scheduling, documentation, billing, and practice management. The software you build will be used every day by families, clinicians, therapists, and our internal team. What You’ll Own Understand the problem: Talk with users, observe workflows, and separate the real problem from the requested solution. Decide what to build: Define the simplest useful solution and what can wait. Design the experience: Create clear, thoughtful interfaces and prototypes in Figma. Build it: Turn your designs into polished, production-ready React interfaces. Improve it: Watch how people use what you ship and iterate based on real behavior. Raise the bar: Improve existing workflows, components, interactions, and design consistency. What We’re Looking For Strong product judgment and comfort working through ambiguous problems. Excellent UX and visual design skills. Strong frontend engineering experience with React, TypeScript, and modern CSS. The ability to move naturally between Figma and production code. High standards for typography, spacing, responsiveness, states, and interaction details. Experience using AI tools to prototype and ship faster without sacrificing judgment. Clear communication and comfort collaborating with a remote U.S.-based team. A bias toward ownership, speed, and finishing what you start. You’ll be a strong fit if you think like a product manager, design like a product designer, and build like a frontend engineer. You ask “why?” before opening Figma or writing code, and you care more about solving the user’s problem than completing a ticket. Our Stack React, TypeScript, Material UI, Next.js, Node.js, PostgreSQL, and Figma. How To Apply Show us one product or feature you helped take from problem to production. Explain what you personally researched, decided, designed, and built. Please include: Your portfolio Examples of production interfaces you personally built A brief explanation of how you use AI in your work We care less about your title and more about whether you can understand a difficult problem, create a simple solution, and ship it. We believe in hiring people, not resumes. If you’re excited by Tellos’s mission but unsure if you meet every requirement, we still encourage you to apply, we’d love to learn what you’d bring to the team.
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.