Location: London or Paris (France)
Remote: flexible
Willing to relocate: if need be
Technologies: Python, Clojure, AWS, Kafka, Terraform, Kubernetes, React, Avro
Résumé/CV: https://www.linkedin.com/in/piotr-yuxuan/
GitHub: https://github.com/piotr-yuxuan
Email: [email protected]
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.
- Technical mindset: bottom-up tech design, right tool for the right job. Client-oriented design. Revenue-oriented, 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. We should all be collectively accountable for systems architecture.
Remote: flexible
Willing to relocate: if need be
Technologies: Python, Clojure, AWS, Kafka, Terraform, Kubernetes, React, Avro
Résumé/CV: https://www.linkedin.com/in/piotr-yuxuan/
GitHub: https://github.com/piotr-yuxuan
Email: [email protected]
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.
- Technical mindset: bottom-up tech design, right tool for the right job. Client-oriented design. Revenue-oriented, 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. We should all be collectively accountable for systems architecture.