- Business impact: always a business case to improve things with lower latency, higher availability, better scalability, lower operational costs. What some businesses really need is just a static webpage in Cloudfront: I want more.
- Corporate structure: a result-driven company that welcomes innovation. I'm happy with either large enterprises that move slowly or small nimble start-up, each has different strengths :-)
- Technical mindset: bottom-up tech design, right tool for the right job. Client-oriented design. Revenue-oriented & business-focused, it should matter from day 0. No abstraction is better than bad abstraction. Let free patterns emerge from organic growth.
- Technical landscape: data-intensive systems that can be relied upon, with strong business-relevant needs for performance, reliability, durability, and resilience.
- Team dynamics: engineers have and share areas of responsibility. No echo chamber or ivory-tower architect. All of us are collectively accountable for systems maintenance and architecture.
Remote: flexible, I'm very much office friendly but I like some remote blocks in summer and December
Willing to relocate: yes to Paris, France
Technologies: Python, Clojure, Java, AWS, Kafka, Terraform, Kubernetes, React, Avro, TypeScript
Résumé/CV: https://www.linkedin.com/in/piotr-yuxuan/
GitHub: https://github.com/piotr-yuxuan
Email: hn-hired@2bst.fr
My dream position:
- Business impact: always a business case to improve things with lower latency, higher availability, better scalability, lower operational costs. What some businesses really need is just a static webpage in Cloudfront: I want more.
- Corporate structure: a result-driven company that welcomes innovation. I'm happy with either large enterprises that move slowly or small nimble start-up, each has different strengths :-)
- Technical mindset: bottom-up tech design, right tool for the right job. Client-oriented design. Revenue-oriented & business-focused, it should matter from day 0. No abstraction is better than bad abstraction. Let free patterns emerge from organic growth.
- Technical landscape: data-intensive systems that can be relied upon, with strong business-relevant needs for performance, reliability, durability, and resilience.
- Team dynamics: engineers have and share areas of responsibility. No echo chamber or ivory-tower architect. All of us are collectively accountable for systems maintenance and architecture.