Backend Software Engineer - SDK
Digital Asset
About the role
Below is a tailored cover‑letter (and a few optional résumé bullet‑points) you can use when applying for the Software Engineer – SDK Team role at Digital Asset.
Feel free to edit the personal details, tweak the language to match your own voice, and add any additional projects or achievements that you think are relevant.
📄 Cover Letter – Software Engineer (Scala) – SDK Team
[Your Name]
[Your Address] • [City, Country] • [Phone] • [Email] • [LinkedIn] • [GitHub]
[Date]
Hiring Committee
Digital Asset
[Office Address – Budapest / Zurich]
Dear Hiring Committee,
I am excited to submit my application for the Software Engineer – SDK Team position at Digital Asset. With [X] years of professional experience building high‑performance, type‑safe Scala services, a deep expertise in reactive streams (Akka/Pekko), and a proven track record of designing secure, production‑grade APIs and SQL‑centric data layers, I am confident that I can help accelerate the Canton Network’s mission to bring the next trillion dollars of finance on‑chain.
Why I’m a strong fit
| Requirement | My Experience |
|---|---|
| Experienced Scala engineer (open‑source or commercial) | • Lead developer of [Project‑Name], an open‑source Scala library for [domain] (★ 4.8 on GitHub, 1 k+ weekly downloads). • Built and maintained a micro‑service ecosystem at [Current/Previous Company] using Scala 2.13/3, Cats‑Effect, and http4s. |
| Database development (PostgreSQL, Slick/Doobie) | • Designed a high‑throughput order‑book service backed by PostgreSQL, using Doobie for type‑safe queries and Flyway for migrations. • Optimized complex analytical queries (joins, window functions) that reduced latency from 120 ms to 35 ms, supporting >10 k TPS. |
| Secure API development (HTTP, gRPC, Tapir, TLS, JWT) | • Implemented a gRPC‑based settlement API with mutual TLS and JWT‑based auth, audited by an external security firm (no critical findings). • Built a Tapir + http4s HTTP gateway exposing idiomatic TypeScript SDKs, complete with OpenAPI docs and automated client generation. |
| Reactive streams (Akka/Pekko) | • Migrated a legacy Akka‑Streams pipeline to Pekko to achieve zero‑downtime scaling to 200 k msg/s. • Authored a custom back‑pressure strategy that prevented downstream overload during market‑data spikes. |
| Collaboration & documentation | • Regularly conduct code‑review sessions (30 + PRs/month) and mentor junior engineers. • Produced technical design docs, API reference guides, and tutorial notebooks that reduced onboarding time for external developers by 40 %. |
| Location | I am currently based in [Budapest/Zürich] and open to hybrid/remote work as required. |
What I can bring to the SDK team
- End‑to‑end ownership – From schema design in PostgreSQL to generating idiomatic TypeScript clients, I can deliver the full stack of SDK components while ensuring performance, scalability, and security meet production standards.
- Security‑first mindset – My experience with TLS, JWT, Auth0, and regular security‑audit cycles equips me to harden APIs against OWASP Top 10 threats and to guide the team through compliance reviews.
- Developer‑experience focus – By empathizing with API consumers, I have built SDKs that feel “native” in the target language (e.g., fluent TypeScript wrappers, Python async clients), which directly aligns with your goal of empowering third‑party developers.
- Thought leadership – I actively contribute to the Scala community (talks at Scala Days, blog series on functional relational mapping, and a Slick‑Doobie interoperability guide). I look forward to sharing that knowledge internally and externally to raise Digital Asset’s technical profile.
Closing
Digital Asset’s vision of a privacy‑enabled, interoperable financial infrastructure resonates deeply with my passion for trustworthy, high‑performance fintech. I would love the opportunity to discuss how my background aligns with the SDK team’s objectives and how I can help accelerate the adoption of the Canton Network.
Thank you for considering my application. I look forward to the possibility of contributing to Digital Asset’s groundbreaking work.
Sincerely,
[Your Name]
Optional résumé bullet‑points (for the “SDK – Scala Engineer” role)
Current / Most Recent Position – Senior Scala Engineer
Designed & delivered a high‑throughput settlement API (gRPC + HTTP/2) with mutual TLS & JWT auth, supporting 150 k TPS and passing a third‑party security audit.
Implemented a PostgreSQL data‑access layer using Doobie, introducing compile‑time query validation and reducing runtime SQL errors by 98 %.
Migrated legacy Akka‑Streams pipelines to Pekko, achieving a 3× increase in throughput and eliminating back‑pressure bottlenecks.
Authored comprehensive OpenAPI/Swagger specs and generated TypeScript & Python SDKs, cutting external developer onboarding time by 40 %.
Mentored a team of 5 engineers, instituted a code‑review culture, and introduced static analysis (Scalafix, WartRemover) to improve code quality.
Open‑Source Contributions
*Lead maintainer of [Project‑Name], a Scala library for [domain], with 1 k+ weekly downloads and active community contributions.*
Contributor to Akka/Pekko core, submitting patches that improve back‑pressure handling for high‑frequency data streams.
Feel free to copy‑paste, adjust the numbers, and insert your own project names or metrics. Good luck with your application – the SDK team would be lucky to have you!
Requirements
- Experienced Scala software engineer as demonstrated by either your open-source libraries or commercial experience.
- Specializing in either database development or writing secure APIs.
- Solid understanding of SQL and relational databases.
- Experience with Functional Relational Mappings in scala: slick, anorm, doobie or others.
- Solid understanding of network protocols and libraries: HTTP, gRPC, Netty, Tapir and others.
- Experience driven ability to empathize with API users allowing them to write efficient, robust and idiomatic client code in various front end languages such as TS and Python.
- Experienced with writing secure APIs.
- Familiarity with the technologies such as TLS, JWT, Auth0.
- Knowledge of frequent attack vectors and their mitigation.
- Experience with developing and deploying production systems.
Responsibilities
- Contributing to the SDK’s (mostly) Scala code base.
- Collaborate with other teams such as the Canton Ledger team on the integration of APIs in the Canton core or the product team on developer education.
- Hardening and testing the APIs to satisfy the production non-functional requirements in particular performance, scalability, and security.
- Assist other team members by providing code reviews, giving feedback and helping set direction.
- Following a collaborative approach that fosters, embraces, and insists upon diverse perspectives.
Benefits
Skills
Don't send a generic resume
Paste this job description into Mimi and get a resume tailored to exactly what the hiring team is looking for.
Get started free