Rust/canister dev from YRAL looking for next ICP role

Developers Jobs
1

Hey everyone,

I’m Ravi — I’ve spent the last stretch building on the Internet Computer at YRAL working on Rust canisters and backend systems. I’m now looking for my next role in the ICP ecosystem and figured this is the right place to put up a hand.

What I bring

  • ~6 years as a software engineer, with deep focus on Rust systems programming

  • Hands-on production canister development at YRAL: state management, inter-canister calls, upgrade flows, stable memory, cycles accounting — the full surface area of running real workloads on the IC

  • Multi-subnet architecture experience — I gave a talk walking through how we approached it at YRAL: https://www.youtube.com/watch?v=yHcLixi6-fI

  • Strong Rust beyond canisters — built and shipped YRAL’s off chain services in Axum (Tokio, Tower, delegation identity flows, signature verification), plus the broader supporting stack: Cloudflare, CDN architecture in front of object storage, and GPU/ML infra integration

  • Deep SNS and governance experience — worked across the full SNS lifecycle (pre-decentralization sale, swap, post-launch governance), canister registration with SNS, programmatic interaction with governance canisters (proposals, voting, neuron management).

  • Contributions and code — most of my recent ICP work lives across these profiles: https://github.com/ravi-sawlani-yral (work) and https://github.com/gravityvi (personal)

  • Open source background — prior to ICP work, I was at BrowserStack contributing heavily to the Nightwatch.js end-to-end testing framework. Shipping in public, working with maintainers, and caring about API ergonomics is something I’ve actually done, not just a line on a resume

What I’m looking for

A Rust-heavy backend or canister engineering role on a team that’s serious about ICP. I’m open to:

  • Remote

  • Relocation for the right team

  • Contract or full-time

I care most about working on technically interesting problems with people who take the platform seriously.

Reach me

If your team is hiring or you know someone who is, I’d love to talk. Thanks for reading.

2

I can attest to Ravi’s skill working with Rust and large IC codebases

3

I hear the backend was so formidable that the front end was scared to even touch any of the endpoints.

4

Where will TOKO launch exactly ? You could use the inside info how not to get out of resources on one subnet. Now that the new app subnets only have 7 nodes one needs to be careful :wink:

5

I’d rather keep the discussion on-topic. The YRAL codebase is fully public, so if anyone wants to dig into specific code I’ve written and point out where I got things wrong, I’m genuinely up for that — worst case I learn something, which is the whole point. Happy to go deep on any specific snippet, design decision, or trade-off.