Ask HN: Who is hiring? (January 2018)

Join us in creating fintech solutions that amaze our customers.

We're using C# and .NET Core 2.0 on the backend and React, TypeScript and MobX on the frontend.

If you love programming and would like an entertaining job with smart and friendly colleagues, lots to learn and a wide variety of challenges, please get in touch. You can email me personally at jamie.mccrindle@investec.co.uk.

At Codurance we help development teams and business to continually improve their products and process. We value the principles of Software Craftsmanship and have a shared passion for continuous learning.

Our Software Craftspeople have a broad appreciation of technology and a depth of expertise in key areas. These will include expertise in the JVM, .Net or Node.js stacks, plus expertise in areas such as cloud technology, building a DevOps culture or perhaps Cyber Security. We believe however that technology can be taught. It’s more important that our Craftspeople, regardless of existing expertise and experience, share the same passion for continuous learning and clean code principles that we do.

Our Apprentices share our passion for creating well-crafted software but have not yet had the suitable learning opportunities to refine their craft. A typical Apprentice is already a productive developer in the language of their choice on the JVM, .NET, and/or Node JS platforms at the start of the programme. They will know of Agile processes and practices and can apply them and are looking to become an expert in reasoning about them. They will have basic knowledge of micro level and macro level design.

For more information, please visit https://codurance.com/careers/

We are looking for quick learners who enjoy working with modern software development tools in the financial and capital markets space.

Knowledge of specific frameworks or libraries is less important than a broad knowledge of software development practices, and an ability to learn.

At the NYSE, we are building customer-facing web applications with tons of referential data and many downstream systems.

Must haves:

1. Significant experience developing web applications and web sites.

2. Very good grasp of Python 3.5+ or TypeScript. Both are a plus.

3. Some knowledge of the other language listed above.

4. Willingness to work with both ecosystems.

5. Relational database experience, ideally PostgreSQL.

6. An understanding of automated testing and when it’s an asset and when it’s a liability.

7. Clear, concise coding skills. Your code is more often described as "clean and elegant" than "clever."

8. A healthy amount of patience for firewall/infrastructure navigation. We use modern stacks and have access to most tools, but still operate in a regulated environment.

Nice to haves:

1. Understanding of formal methods

2. Bash and vi fu.

3. Mypy and static typing experience in Python.

4. React experience.

5. Django experience.

6. Static typing experience in other languages: Java, C++

7. API design

8. Rust experience

Interested? Email me at silvio.gutierrez@nyse.com. Please put Hacker News in the subject line. Maybe even take a look at the shibboleths in the sub-comment below and try answering a few.

- You understand meta programming python. What the type() function really does, and how it can be used. And when it should not be used.

- You understand discriminated unions, and how to use the type system to enforce exhaustive checks and other useful patterns.

- You can describe good and bad use cases for single page applications.

- You can describe why nullable types and a type system that enforces it are advantageous over type systems like Java’s.

- You can and have extracted declarative implementations out of imperative code. You know when it’s worth it and when it’s not.

- You know what the right time is to add unit tests to your code.

- You can describe a list comprehension, and have strong opinions regarding when and when not to use them.

- You know the benefits of generators and the yield statement.

- John is in many bands. We want to keep track of them. And we also want to track when he joined them. You know exactly how to model this in a relational store.

- You understand higher order functions, and sometimes secretly wish Python had more of them.

- You can describe ways in which lambda in Python is limited. And the reasoning - however flawed or not - behind it.

- You know when to use composition over inheritance.

- You understand the article “What Color is Your Function?” and can discuss it with us.

- You think comments are a last resort for documenting an algorithm.

- You can describe a pure function. Bonus: you can explain referential transparency. Even I can’t.

- You hate repeating yourself. DRY not WET.

- You understand the illusion of complexity and why simplicity is always better.

- You know the different types of automated testing there are, and when to use each.

- You have strong opinions on handling nested resources in REST and can espouse all the benefits of your take.

- You have strong opinions on handling versioning in REST and can espouse all the benefits of your take.

- You know what a shibboleth is.

Open Collective allows communities (like Open Source projects, meetups, etc) to raise and spend money transparently. You can charge membership fees, get donations from individuals or companies and spend it by filing expenses. The entire financial ledger is publicly viewable to ensure transparency. Some examples: https://opencollective.com/webpack, https://opencollective.com/babel, and many more https://opencollective.com/opensource.

We are a founding team of 3 (two engineers) and are looking to hire our first full-time engineer (https://medium.com/open-collective/open-collective-is-hiring...).

Send me a note at aseem@opencollective.com with your GitHub, LinkedIn, resume, etc.