Technical Lead

About Wednesday
Wednesday builds software that moves a number the client's roadmap has been stuck on. Since 2020 we have shipped products for companies including PayU, Kotak Securities, PharmEasy, Rapido, and Kalshi. Our engineers work inside the client's production environment and their constraints, and they own the result.
How we work
We hire rarely and stay small on purpose, because every person changes what the team is. Everyone here is a forward deployed: a generalist with depth, who sits inside the client's business, finds the actual problem, and owns the number rather than the plan to reach it. We use AI to do most of the building, and we expect people to make those around them better.
Roles and responsibilities
You own an engagement and the pod delivering it.
Problem framing: Sit with the client's teams, see how the work really happens, and separate the pain that matters from the nice-to-haves.
Problem hunting: Find the problems the client has not named yet, and bring them back as things we can build.
Client relationship: Be the person the client calls first when something breaks or a new problem shows up.
ROI ownership: Set the target with the client and get the pod to hit it. Decide what we reuse, what we build, and what we drop.
Architecture and delivery: Design the system, direct the build, and get it running in the client's environment, in production, tied to the number they care about.
Running the pod: Mentor engineers on the problem and relationship work, not only on shipping.
Domain depth: Learn the client's products, their data, and the rules that constrain what we can build.
Requirements
Experience: 5 to 8 years building software, with at least one system you have architected and taken to production end to end.
Stack: Our current stack is JavaScript, Node on the backend, React on the web, React Native and Flutter on mobile, and AWS. We are not limited to it, and we do not expect you to be either. What matters is that you can design and build a system without the technology deciding for you.
AI fluency: You use models and agents to do most of your engineering work, you know where they fail, and you can design systems that put LLMs into production reliably.
Results in someone else's business: A metric you moved, a stakeholder you brought around, a legacy system you worked through.
People: You can run a small team and grow the people on it.
Communication: You can explain a technical decision to a head of operations and a compliance officer in the same meeting.
A note on the title: Internally this role is a Lead Forward Deployed Engineer. We post it as Technical Lead because that is what people search for. If you join, your title and level will be set against our engineering ladder based on where you actually fit, which may be above or below the advertised title. The ladder is public: playbook.wednesday.is/forward-deployment-handbook/engineering.

Work arrangement
No