Software Engineer

You'd join a small engineering team and work across our client engagements. Our clients operate in complex, regulated domains where understanding the product matters more than writing the code. The codebases span legacy systems and modern stacks: PHP, React, Laravel, and Python across different projects. You don t need to know all of these coming in. You need to get comfortable in unfamiliar code fast. This is not a bench role. There s no extended training program where you watch and learn. You d be doing real work from your first week, with your output visible to the team and to leadership. That can be uncomfortable. It s also how you grow fastest. What We Care About You care about the problem, not just the ticket. The engineer who asks why does this feature existand what is the user actually trying to dois more valuable to us than the one who just ships what s in the spec. We want people who go deep into the domain, understand the business, and solve problems through technology, not just write code against requirements. You figure things out and leave a trail. Tickets won t always come fully specced. The codebase won t always make sense. you'll need to explore, ask questions, and sit with ambiguity. But when you figure something out, you document it, suggest a fix, or leave a note so the next person doesn t repeat the struggle. You communicate in writing, naturally. Slack is the primary channel with our US clients. They re responsive and they notice silence. If you can write a clear update, describe a problem without being asked, and keep people in the loop as habit rather than chore, you'll do well here. You ship steadily. Small, consistent progress beats big delayed deliverables. Our clients value responsiveness and visibility over perfection. AI is already part of how you work. We use Claude and other AI tools as a regular part of how we build, debug, and understand complex systems. During interviews, you'll have full freedom to use whatever tools you prefer. we're not testing if you can solve problems without help. we're testing if you can solve problems well, using everything available to you. What Would Set You Apart You tend to improve the process around you, not just follow it You follow up on your own work after deployment, not just move to the next ticket you're curious about how AI fits into a product, not just how it helps you code faster You take ownership of your credibility with the people you work with, whether that s a client, a teammate, or a reviewer This Role Is Not For You If You want a predictable 9-to-5 routine. Our client work sometimes requires flexibility with hours, including overlap with US time zones. You wait for instructions before acting. If a ticket is unclear, you're expected to explore, ask, and figure it out, not sit on it. You treat code as the finish line. We care just as much about what happens after deployment: bugs, user feedback, system behavior, follow-through. you're not comfortable with not knowing things. Our clients products are large, complex, and not always well-documented. you'll spend time in systems that nobody has explained to you. You see AI tools as shortcuts rather than thinking partners. Using AI to skip understanding is the opposite of what we value