An operations colleague was about to demo in front of 50 people and a feature broke. It was diagnosed, fixed and deployed in 15 minutes, before the demo started. We shall not focus on whose fault it was , but "what do we change so it can't recur." Solve the problem, not blame the people.
Every piece of work lives in Cadence, our own internal platform , built in-house, used daily. If something's broken, it becomes a ticket everyone can see, not a message that dies in someone's excel, whatsapp , notebook etc. No ticket means no work.
The best PR we merged recently wasn't the fastest one. It came with integration tests and a UX thought through so carefully that our operations team could teach it to a client without a manual. That's the bar: build for the person who receives your work, not the person who does it.
...
Experience: 4+ years in software development, with 2+ years of production Rust (or exceptional Rust proficiency with strong systems/backend background); enterprise or fintech/e-invoicing domain experience preferred.
Programming Skills: Proficient in Rust (async/await, traits, feature-gated compilation targets); working knowledge of SQL, HTML, CSS, TypeScript (for e2e tooling).
Full-Stack Rust: Hands-on experience with a Rust web framework (Leptos, Axum, Actix, Yew, or Dioxus) and WASM compilation; understanding of SSR + hydration trade-offs.
...
Assuming the role of a technical expert for solution design and development with the responsibilities below:
Partner with business stakeholders, product owners and project managers to understand business requirements and translate them into technical design.
...