Thank you for your interest!
The best way to contact me about my resume is via LinkedIn. Email or voicemail is fine too, but both are more likely to get lost in the shuffle if I'm not able to reply immediately.

PDF for download/printing - note that these are not kept perfectly in sync.

Latest News

I've been at Atlassian for nearly 6 years and am really liking it here. I am not seeking or particularly interested in other opportunities, although I would not rule an interesting remote or local remote-friendly hybrid position out of hand.

I found during the pandemic that I strongly prefer remote-first work; I led a geographically distributed team, and am in-office for for one week each quarter for an on-site gathering and an odd day here and there, but do not regularly work on-site. I would not rule out a "few days each week" hybrid position, but it would not be my preference.

Please do not contact me about positions outside of the Bay Area unless they are 100% remote (with at most 2 weeks per quarter travel); I have family commitments that mean I cannot relocate now or in the forseeable future.

Lastly, please do not contact me about consulting or jobs related to my current or prior employers. I am not, and will never under any circumstances be, open to discussing any position relating directly to any of my employer's products or customers.

Highlights:

  • 25 years of Software Engineering, primarily Java enterprise and back-end cloud applications
  • 3.5+ years of engineering management experience, leading two internal-facing developer-productivity teams supporting around 500 engineers on Confluence Cloud.
  • 25+ years of Linux experience as user, developer, and administrator

    • WORK EXPERIENCE

    Atlassian
    Principal Software Engineer, Confluence Cloud Enterprise Compliance team
    Oct. 2023—
  • Technical lead/architect for Confluence's FedRAMP Moderate effort
    • Senior Engineering Manager, Confluence Cloud Developer Experience
    Jan 2020—Oct 2023
    The Developer Experience team was an internal facing team, responsible for all aspects of improving productivity and ensuring quality for around 500 developers working on the Confluence Cloud product.
  •   Grew team from two engineers to 17 engineers in two teams, one of them indirect.
  •   Coached and navigated the promotion cycle for multiple engineers, including senior to principal and senior to engineering manager.
  •   Drove projects to modernize the Confluence library/JVM usage, including retiring Jackson 1 and upgrading the JDK used first from 8 to 11, and then 11 to 17.
  •   Reduced local build-restart time times from 10 minutes to 4 minutes.
  •   Reduced CI build/test times from over 60 minutes to 20 minutes.
  •   Improved release frequency from 4 to 14 production releases per week.
  •   Improved BE release latency from 90 hours to under 24 hours.
  •   Promoted to Senior Engineering Manager in 2023.
    Principal Software Engineer, Confluence Cloud
    2018—2019
  •   Designed and led implementation of integration to the internal identity platform, our single highest volume platform integration to date; part of our GDPR compliance effort.
  •   Implemented tools to allow devs to debug the Confluence monolith locally with real staging traffic.
    • Technologies used: Java, PostgreSQL, REST, JSON, SQL, Docker, some AWS services, Maven, Gradle

    Zipcar
    Software Engineer
    2016—2018
  • Part of a small team building a new distributed system as the new core platform for Zipcar.
  • Back-end development of services in Java and Groovy, in particular extracting smaller services from a monolithic (Grails) fleet management application and writing new services to support broader Zipcar use cases.
  • Built a caching and search service used by the web UI and mobile apps.
    Technologies used: Java, Groovy, PostgreSQL, MongoDB, RabbitMQ, REST, SQL, Cassandra

    Facebook 
    Software Engineer (E5)
    Oct 2014 — Dec 2015   
  • Back-end development, primarily in Java.
  • Wrote code supporting internal applications moving from an old internal fork of an open-source infrastructure project to the mainline open-source version.
  • Contributed bug fixes and minor feature enhancements to the mainline open-source version of that project.
    I'm being intentionally vague about the specific project not because it's secret, but because I'm not an expert at it and don't want it to show up in keyword searches. Feel free to ask.
    Technologies used: Java, distributed databases, containers

    Guidewire Software 
    Senior Software Engineer
    2006 — 2014 
    Guidewire builds software for the global property/casualty insurance industry. Their core systems for claims, policy, and billing are deployed at 100+ companies, including some of the world's largest insurance carriers.
  • Implemented proximity-search and integration to outside geocoding services. Maintained the feature through 3 major release cycles. Improved performance by 10x across releases.
  • Built a "review" feature, which allowed users to author surveys, collect replies, and analyze the results. This project required a substantial integration between multiple existing products.
  • Worked with application developers on all three core products and platform team to find andfix performance and scalability issues.
  • Developer for internal "performance harness" application used for benchmark/scalability tests, cluster management, and performance-test analysis.
  • Implemented many new information and instrumentation pages to support internal benchmarking and to allow customer support to collect data for analysis from the field.
  • Responsible for a major expansion of shared storage for performance testing Guidewire'applications at large scale on Oracle RAC; wrote requirements and budget request, co-leadvendor evaluation and deployment.
  • Selected specifications and performed hardware/storage benchmarking for the application performance test practice.
  • Ordered, deployed and tuned Guidewire's first SSD-based database servers for performance testing. These systems accelerated two separate major proof-of-concept scalability tests, on two different products, each by more than a month.
    • Technologies used: Java, Linux, SOAP/REST, Tomcat, Servlets/JSP, Oracle, RAC, SQL, Perl, SSH, Virtualization, iSCSI, NFS, CIFS, Apache httpd, SSD, RAID

    See PDF for older experience

    EDUCATION

    University of California, Santa Cruz 
    M.S. in Computer Science 
  • Thesis: "MRAMFS: A Compressing File System for Byte-Addressable NVRAM" 
  • Advanced seminars included Operating Systems, Storage Systems and Archival Storage 
  • TA for CMPS115 Software Methodology, a senior level software engineering course 
     
    Dartmouth College, Hanover, NH 
  • B.A. in Anthropology. Computer Science Minor. 

    PUBLICATIONS 

    Nathan K. Edel, Deepa Tuteja, Ethan L. Miller, and Scott A. Brandt, " MRAMFS: A Compressing File System for Non-Volatile RAM," Proceedings of the 12th IEEE/ACM International Symposium on Modeling, Analysis, and Simulation of Computer and Telecommunication Systems (MASCOTS 2004), Volendam, Netherlands, Oct. 2004

    Nathan K. Edel, Ethan L. Miller, Karl S. Brandt, and Scott A. Brandt, "Measuring the Compressibility of Metadata and Small Files for Disk/NVRAM Hybrid Storage Systems," Proceedings of the 2004 International Symposium on Performance Evaluation of Computer and Telecommunication Systems (SPECTS'04), San Jose, CA, Jul. 2004

    RELEVANT SKILLS

    Languages:  (expert) Java (through JDK 21)
    (comfortable) Groovy, Kotlin, Perl, SQL
    (some familiarity) Python, C, C++, C#, PHP, Lua, x86 assembly
    Application/Web Server: Jetty, Tomcat, Apache httpd, php-fpm, nginx
    Technologies/APIs: Servlets/JSP/Jersey/Spring, JSON, Protobuf/GRPC, RabbitMQ/SQS/SNS, some familiarity with other J2EE technologies
    Development Tools: IntelliJ IDEA, gradle, maven, git/BitBucket/GitHub, Jira, gcc/gdb, Gentoo portage
    Operating Systems: Linux (from SLS & kernel 0.99), Windows
    Databases: developed applications on top of Oracle, mysql, PostgreSQL (including RDS & Aurora), MongoDB, Cassandra, HBase, and Redis, some familiarity with operational aspects of each
    Hardware: extensive familiarity with commodity servers and storage hardware; some exposure to datacenter networking; familiarity with deploying Amazon EC2

    ACTIVITIES & INTERESTS 

  •   Fiction writing 
  •   Photography 
  •   Travel and Frequent Flyer miles
    • Last updated 17 Feb 2024, Nathan Keir (Nate) Edel
    This site is in (badly) hand-coded HTML and CSS, let's party like it's 1996
    This website does not use cookies, has no interactive features, and does not collect personal data except indirectly via webserver access logs.